From: Craig Loomis Date: Thu, 26 Jan 2012 13:54:58 -0500 Subject: Re: [sdss3-25mlog 483] Re: 2.5m obslog 20120125 (MJD 55952) --f46d0447f0eadfb57c04b772eb43 Content-Type: text/plain; charset=UTF-8 Since you need a new arc+flat pair after moving the collimator, there is no meaningful shortcut within gotoField. The slew won't take any time and the guider flat is taken during the required spectro flat. The HgCd lamp warmup will stand out because there is no concurrent slew, but I don't think there is anything to do about that. - craig On Thu, Jan 26, 2012 at 10:30, Kaike Pan wrote: > David, > > Thanks. Okay we will take one more exposure on this plate tonight. > > "gotoField" will take another guider flat, but it will not cost us time > because > it is taken when calibration flat is taking. Yes, we can manually do the > hartmann, > adjust collimators, take another set of calibration (flat and arc should > be take > after the collimator adjustments?). I feel that manually doing these > three steps > will take more time than another "gotoField". "gotoField" does slew the > telescope, > take guider flat. But in this case, it will not cost us time. > > -kaike > > > On Jan 26, 2012, at 8:08 AM, David Schlegel wrote: > > > Kaike, > > > > I'd rather not include that first exposure on plate 5411. The PSFs will > be different > > even if the CCD locations are the same. Unfortunately, we've decided to > not deal > > with data like that in the past (OK, you can blame me for that!). > > > > The procedure change for getting into focus sounds like a good idea. > Does one > > need to issue another "gotoField", or can one just do the Hartmanns? We > shouldn't > > need to get another guider flat or any of the other business associated > with a gotoField. > > > > Thanks, > > David > > > > > > On Jan 26, 2012, at 6:38 AM, Kaike Pan wrote: > > > >> Hi Kyle and David, > >> A question on plate 5411, cart 16: > >> > >> Looks like that the only difference among the first exposure and the > last three is slightly different > >> SP2 focus (collimators on SP2 was adjusted by -2300 steps), XMIDs and > WAVEMIDs are the same. > >> Should we declare the first exposure back to excellent so that we can > declare the plate > >> done, and request it to be replaced with a new plate. This will save us > 30 min on sky time. > >> Please let me know asap so that I can choose a plate for the cartridge. > Thanks, > >> > >> A related question: Looks to me that if an adjustment needed is huge > (more 10,000 steps), > >> quick hartmann usually can not get spectrograph into its optimal focus > position. From operation > >> point of view, should we use second "gotoField" (like Dan and Audrey > did last night) to ensure > >> the best focus. The extra "goto Field" takes ~ 5 more minutes. If no > objection, I will modify our > >> SDSS procedure to implement the change. > >> > >> -kaike > >> > >> > >> > >>> > >>> Cart. 16, 5411 > >>> > >>> > >>> > >>> We had to take a second set of Hartmanns on Cart. 16 because of a red > b2 xsigma > >>> value in the flat. After the second set, all SoS values were in spec. > >>> > >>> We had about a half dozen internet interruptions throughout the night. > Note that > >>> while they did not cause any problems with observing, we did lose > weather > >>> information, etc., from time to time. > >>> > >>> > >>> > >>> Cart. 16, 5411 > >>> ************** > >>> 11:25Z - Hartmanns. > >>> > >>> 11:25:07 hartSp2: r=-1043, b=-3.6, txt=OK, sp2Temp = 3.3 ; > >>> 11:25:07 sos.sp2AverageMove = -11345 > >>> 11:25:35 motorPos.sp2.move: -11345, -11346, -11345; > >>> 11:25:35 hartSp1: r=584, b=2.0, txt=OK, sp1Temp = 3.8 ; > >>> 11:25:35 sos.sp1AverageMove = 561 > >>> 11:25:39 motorPos.sp1.move: 561, 561, 560; > >>> > >>> 11:26Z - Cals. > >>> 11:29Z - GSOGTF. > >>> > >>> 11:31:19 boss exposure 900.0, file=139094 (Declared bad because SoS > showed out > >>> of spec in b2 xsigma.) > >>> > >>> 11:47:42 boss exposure 900.0, file=139095 (Aborted because we > noticed a red > >>> b2 xsigma value). > >>> > >>> We tried another set of Hartmanns after seeing the red b2 xsigma value > in the flat. > >>> > >>> 11:58Z - Hartmanns. > >>> > >>> 1:58:13 hartSp2: r=-465, b=-1.6, txt=OK, sp2Temp = 3.4 ; > >>> 11:58:13 sos.sp2AverageMove = -2315 > >>> 11:58:21 motorPos.sp2.move: -2315, -2314, -2315; > >>> 11:58:21 hartSp1: r=570, b=2.0, txt=OK, sp1Temp = 4.0 ; > >>> 11:58:21 sos.sp1AverageMove = 255 > >>> 11:58:24 motorPos.sp1.move: 255, 255, 254; > >>> > >>> 12:03:34 boss exposure 900.0, file=139100 > >>> 12:19:57 boss exposure 900.0, file=139101 > >>> 12:36:20 boss exposure 900.0, file=139102 > >>> > >>> 12:56Z - Closed. Note that APOGEE cals were taken at 02:17Z. > >>> > >> > > > > _______________________________________________ > Message 483 of sdss3-25mlog - Logs of nightly APO activities. > sdss3-25mlog@sdss3.org > https://sdss3.org/mailman/listinfo/sdss3-25mlog > --f46d0447f0eadfb57c04b772eb43 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =C2=A0Since you need a new arc+flat pair after moving the co= llimator, there is no meaningful shortcut within gotoField. The slew won= 9;t take any time and the guider flat is taken during the required spectro = flat. The HgCd lamp warmup will stand out because there is no concurrent sl= ew, but I don't think there is anything to do about that. =C2=A0- craigOn Thu, Jan = 26, 2012 at 10:30, Kaike Pan wrote: David, =C2=A0Thanks. Okay we will take one more exposure on this plate tonight. =C2=A0"gotoField" will take another guider flat, but it will not= cost us time because it is taken when calibration flat is taking. Yes, we can manually do the ha= rtmann, adjust collimators, take another set of calibration (flat and arc should be= take after the collimator adjustments?). =C2=A0I feel that manually doing these = three steps will take more =C2=A0time than another "gotoField". "gotoFie= ld" does slew the telescope, take guider flat. =C2=A0But in this case, it will not cost us time. -kaike On Jan 26, 2012, at 8:08 AM, David Schlegel wrote: > Kaike, > > I'd rather not include that first exposure on plate 5411. =C2=A0Th= e PSFs will be different > even if the CCD locations are the same. =C2=A0Unfortunately, we've= decided to not deal > with data like that in the past (OK, you can blame me for that!). > > The procedure change for getting into focus sounds like a good idea. = =C2=A0Does one > need to issue another "gotoField", or can one just do the Ha= rtmanns? =C2=A0We shouldn't > need to get another guider flat or any of the other business associate= d with a gotoField. > > Thanks, > David > > > On Jan 26, 2012, at 6:38 AM, Kaike Pan wrote: > >> Hi Kyle and David, >> =C2=A0A question on plate 5411, cart 16: >> >> Looks like that the only difference among the first exposure and t= he last three =C2=A0is slightly different >> SP2 focus (collimators on SP2 was adjusted by -2300 steps), XMIDs = and WAVEMIDs are the same. >> Should we declare the first exposure back to excellent so that we = can declare the plate >> done, and request it to be replaced with a new plate. This will sa= ve us 30 min on sky time. >> Please let me know asap so that I can choose a plate for the cartr= idge. Thanks, >> >> A related question: Looks to me that if an adjustment needed is hu= ge (more 10,000 steps), >> quick hartmann usually can not get spectrograph into its optimal f= ocus position. From operation >> point of view, should we use second "gotoField" (like Da= n and Audrey did last night) to ensure >> the best focus. The extra "goto Field" takes ~ 5 more mi= nutes. If no objection, I will modify our >> SDSS procedure to implement the change. >> >> -kaike >> >> >> >>> >>> Cart. 16, 5411 >>> >>> >>> >>> We had to take a second set of Hartmanns on Cart. 16 because o= f a red b2 xsigma >>> value in the flat. After the second set, all SoS values were i= n spec. >>> >>> We had about a half dozen internet interruptions throughout th= e night. Note that >>> while they did not cause any problems with observing, we did l= ose weather >>> information, etc., from time to time. >>> >>> >>> >>> Cart. 16, 5411 >>> ************** >>> 11:25Z - Hartmanns. >>> >>> 11:25:07 =C2=A0hartSp2: r=3D-1043, b=3D-3.6, txt=3DOK, sp2Temp= =3D 3.3 ; >>> 11:25:07 =C2=A0sos.sp2AverageMove =3D -11345 >>> 11:25:35 motorPos.sp2.move: -11345, =C2=A0-11346, =C2=A0-11345= ; >>> 11:25:35 =C2=A0hartSp1: r=3D584, b=3D2.0, txt=3DOK, sp1Temp = =3D 3.8 ; >>> 11:25:35 =C2=A0sos.sp1AverageMove =3D 561 >>> 11:25:39 motorPos.sp1.move: =C2=A0 =C2=A0561, =C2=A0 =C2=A0 56= 1, =C2=A0 =C2=A0 560; >>> >>> 11:26Z - Cals. >>> 11:29Z - GSOGTF. >>> >>> 11:31:19 =C2=A0boss exposure =C2=A0900.0, file=3D139094 (Decla= red bad because SoS showed out >>> of spec in b2 xsigma.) >>> >>> 11:47:42 =C2=A0boss exposure =C2=A0900.0, file=3D139095 =C2=A0= (Aborted because we noticed a red >>> b2 xsigma value). >>> >>> We tried another set of Hartmanns after seeing the red b2 xsig= ma value in the flat. >>> >>> 11:58Z - Hartmanns. >>> >>> 1:58:13 =C2=A0hartSp2: r=3D-465, b=3D-1.6, txt=3DOK, sp2Temp = =3D 3.4 ; >>> 11:58:13 =C2=A0sos.sp2AverageMove =3D -2315 >>> 11:58:21 motorPos.sp2.move: =C2=A0-2315, =C2=A0 -2314, =C2=A0 = -2315; >>> 11:58:21 =C2=A0hartSp1: r=3D570, b=3D2.0, txt=3DOK, sp1Temp = =3D 4.0 ; >>> 11:58:21 =C2=A0sos.sp1AverageMove =3D 255 >>> 11:58:24 motorPos.sp1.move: =C2=A0 =C2=A0255, =C2=A0 =C2=A0 25= 5, =C2=A0 =C2=A0 254; >>> >>> 12:03:34 =C2=A0boss exposure =C2=A0900.0, file=3D139100 >>> 12:19:57 =C2=A0boss exposure =C2=A0900.0, file=3D139101 >>> 12:36:20 =C2=A0boss exposure =C2=A0900.0, file=3D139102 >>> >>> 12:56Z - Closed. Note that APOGEE cals were taken at 02:17Z. >>> >> > _______________________________________________ Message 483 of sdss3-25mlog - Logs of nightly APO activities. sdss3-25mlog@sdss3.org https://sdss3.org/mailman/listinfo/sdss3-25mlog --f46d0447f0eadfb57c04b772eb43--