Subject: Re: [sdss3-25mlog 67] 2.5m obslog 20110331 (MJD 55652) From: Kaike Pan Date: Fri, 1 Apr 2011 09:08:22 -0600 On Apr 1, 2011, at 6:07 AM, asimmons@apo.nmsu.edu wrote: >=20 > APACHE POINT OBSERVATORY SDSS 2.5M >=20 > OBSERVING LOG > Thursday March 31, 2011 >=20 > (MJD 55652) >=20 > ---- Observing Team ---- >=20 > Daniel Oravetz > Audrey Simmons >=20 > ---- Observing Summary ---- >=20 >=20 > We lost some science time due to hartmanns failing on numerous = occasions. >=20 > We adjusted b1 by +11 degrees at the beginning of the night (it was = much warmer=20 > tonight) and at the end of the night we needed to adjust it back by = -11 degrees,=20 > when the temperature only changed by a few degrees. The camera was = basically in=20 > focus all observations in between. Yes, there is some inconsistence at beginnings of nights = (spectrographs are not in equilibrium?). But overall, the relationship is okay. In last night case, when = collimations is checked, temperature was at ~14C, it asked for +11 degrees. Temperature dropped to 10~ C at = the time of gotoField for the first cartridge of the night. At that time, b1 ring asked for -1 = degree adjustment. We had problem on gotoField of cartridge 14, at that time temperature was + 7C. The = temperature change was only about 3C during the night, but it was 7C from the time when collimation = was checked to the morning. Dan and Audrey did fellowed the current procedure last night. I think = we should consider to add one=20 more step in the procedure. During the twilight, we check collimation = again, make sure that required=20 b1 adjustment is 3 to 6 degree.=20 >=20 > Another problem: We filed a ticket #1266 relating to inconsistencies = with failed=20 > hartmanns. >=20 > Another problem: Once we came across a hartmann sequence that failed = and gave no=20 > reason for it. A timeout issue? See problem section. >=20 I think that we may still have timeout issue. Thanks to Elena who = write the logFun script. Please run the script during observations, monitor BOSS status window, make = sure two things: collimator motors get to their destinations, and all calibrations was taken, decide = what the nest step should be. I found in most cases, we have anything (failed for no reason), we just = need to start guider. Hope it can fixed. Currently, we just need to carefully monitor logFun window = and BOSS status during=20 gotoField. =20=