APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Monday August 22, 2005 (MJD 53605) ---=== OBSERVING TEAM ===--- night: John Barentine Dan Long swing: Steph Snedden Jurek Krzesinski Kaike Pan Eric Neilsen, Kurt Biery by phone. ---=== OBSERVING PLAN ===--- New DA Shakedown ---=== OBSERVING SUMMARY ===--- Continued testing of the new DA in concert with the fermiFolk. We shook out several items as weather and telescope condition permitted. ---=== OBSERVING LOG ===--- Afternoon checking: ------------------- Spectrographs: We've got partial readouts on sp1 and sp2 (it still looks like lots of wrong number of pixels). File sizes were ok, but for a single exposure the file name numbers were like this: 16:13 devel1.apo.nmsu.edu % cd /data/spectro/53605 16:48 devel1.apo.nmsu.edu % ls -l total 34516 -rw-rw-r-- 1 observer dss 366 Aug 22 16:46 frames.list -rwxrwxr-x 1 observer dss 8815680 Aug 22 16:45 sdR-b1-00033427.fit* -rwxrwxr-x 1 observer dss 8815680 Aug 22 16:46 sdR-b2-00033428.fit* -rwxrwxr-x 1 observer dss 8815680 Aug 22 16:46 sdR-r1-00033427.fit* -rwxrwxr-x 1 observer dss 8815680 Aug 22 16:46 sdR-r2-00033428.fit* While we run logTool, we saw the errors: im> logTool 2005-08-22 23:36:58Z: Failed to execute command on observer@sos.apo.nmsu.edu; ssh error was Son-of-Spectro cron IS running for USER=observer MACHINE=sos.apo.nmsu.edu. Loaded version=v4_10_7. No aporsync jobs are currently running. No startapo jobs are currently running. No lock files exist. Warning: Permanently added the RSA1 host key for IP address '192.41.211.136' to the list of known hosts. 2005-08-22 23:36:59Z: Failed to execute command on observer@hoggpt.apo.nmsu.edu; ssh error was HoggPT IS running for USER=observer MACHINE=hoggpt.apo.nmsu.edu. Loaded version=v1_6_9. No hoggrsync jobs are currently running. No lock files exist. Warning: Permanently added the RSA1 host key for IP address '192.41.211.154' to the list of known hosts. 2005-08-22 23:36:59Z: Failed to execute command on observer@plate-mapper.apo.nmsu.edu; ssh error was WARNING: RSA1 key found for host plate-mapper.apo.nmsu.edu in /home/observer/.ssh/known_hosts:36 RSA1 key fingerprint 50:79:a0:1e:a2:71:9e:63:a8:30:c6:d3:79:97:99:46. Host key verification failed. .logtool.logviewer2 ------------------------------------------------------------ Night ----- Kurt worked on the spectrograph readout situation. Eric advised different tests we carried out. The telescope had not been officially released to the observers so we did not attempt to open the 2.5m. We did some PT troubleshooting involving starting the MOP GUI. The GUI was very slow in starting up, trying to generate param files. There was an apparent problem with the SSH forwarding to the new setup on devel1, so we ran ssh agent to get the forwarding correct. Once that was accomplished and we had the GUI up and running, we checked readout times for Eric. Readouts had recently been running ~20 s longer than expected, and Kurt had applied a fix. It now appeared that the underestimation of readout times was more on the order of about 5 seconds, an acceptable amount of time. We got a doghouse bias run to have some data for endNight to detect and archive later on in the night, then ran biasCheck from devel1. It was run on frame 30 of run 5495, which appeared to be an otherwise "good" bias. I got the following result: im> checkBias 5495 30 . {26 WARN: } {26 FAIL: rightRNComp } {35 WARN: } {35 FAIL: rightRNComp } {61 WARN: } {61 FAIL: leftRNComp } error making html display of bias vectors: could not make director /skycat/imager/53605: mkdir: cannot create directory `/skycat/imager/53605': No such file or directory {photo h1} {astro h2} We had a similar result from trying to run biasGen: Directory /data/photo/53605/5495, Field 31 Writing files to directory /skycat/bias/53605 Error: /bin/mkdir: cannot create directory `/skycat/bias/53605': No such file or directory This apparently results from the inability of checkBias to create a subdirectory off /skycat/imager, but the imager subdirectory did not exist, nor can the observers make directories off /skycat. None of us the root password for devel1 -- an apprently closely-guarded secret -- so we left this for Fritz' intervention. As a hack, Eric edited his procedure to bypass creation of the skycat directory so at least we could test whether checkBias would execute at all. We ran the hacked version, which completed successfully. Meanwhile, the bias run 5495 had produced a failure to archive frame 20 on chip r2; the file existed in the pool but was not actually archived (i.e., did not appear on disk). Watcher threw two errors for id2: dsc W archNoFtp Could not make FTP connection (dsc_W_archNoFtp Could not make FTP connection : 2005-08-23 04:04:27Z) and TEXTONLY *** FATAL *** dscArch: While writing frames - 1 (TEXTONLY *** FATAL *** dscArch: While writing frames - 1 : 2005-08-23 04:04:27Z ) This problem recurred three times: twice on the first attempt at a bias run and once on the second attempt. Eric suggested that while we could retrieve the missing frames with poolCopy, his new endNight should catch the unarchived frames and complain about them. In the interest of catching (and fixing) the error, he asked that we leave the frames in the pool for the time being. With Eric still on the phone, we tested endNight with the predictable result that it identified the unarchived frames. We did find something interesting about the new DA which caused a conflict in endNight: imager files are identified according to field number versus frame number. endNight expects frame numbers and complained when it did not receive them. Recent discussions regarding how the DA handles imager files resulted, we believe, in a consensus to stick with the earlier convention using frame numbers, but it appears that the changes have only been made on the UNIX side (idGang files begin with 8, referring back to field numbers). However, that means that the numbering scheme does not agree between files in the pool and files on disk, resulting in the endNight conflict when there are unarchived frames still in the pool. Further, on doing a poolDir, it seems that the archival state of the gangs is correct but not the frames (only the gangs are shown as archived while frames are not). At least we think so... assuming the -a flag is "archived" and -c is "complete". In hopes of collimating the PT tonight, we started cooling the telescope around 06:00Z. At 06:25Z we started ventilating the 2.5m so that fiducial table information could be gathered in the morning. The humidity was rising after about 07:00Z and we watched it carefully, making sure the rain sensor was enabled. Clouds thickened and the humidity climbed over the next couple of hours; by 09:30Z it was sprinkling lightly. We shut down ventilation of the 2.5m and put the PT away at this time. Decided to call it a night at 09:45Z with little chance of opening before twilight. ---=== IMAGING RUN SUMMARY ===--- Run Time Stripe Lambda Last Flavor Comments Start End Begin End Frame ------------------------------------------------------------------------- 5494 03:43Z 03:45Z 100 O 96.53 97.07 10 ignore 5495 03:51Z 04:07Z 100 O 98.55 102.46 40 ignore 5496 05:10Z 05:25Z 100 O 118.43 122.15 39 ignore ---=== IMAGING RUN DETAILS ===--- ---=== SKIPPY RESULTS ===--- Run Frame nFrames stars muErr muRms nuErr nuRms rot az el --------------------------------------------------------------------------- ---=== LTMATCH RESULTS ===--- Run Field nFields alt az nGood rowMean rowSig colMean colSig rot ------------------------------------------------------------------------ ---=== SPECTROSCOPY DATA SUMMARY ===--- Summary Checked (y/n): QA Procedures Done (y/n): UT Exp Time flavor comment (S/N)^2 totals ========================================== b1 r1 b2 r2 ----- sequence 33422, plate -9999 ------- 20:23 33422 0.0 bias 20:23 33424 0.0 bias 20:23 33425 0.0 bias 20:23 33426 0.0 bias ----- sequence 33427, plate -9999 ------- 22:34 33427 0.0 bias 22:34 33429 0.0 bias ----- sequence 33430, plate 0 ------- 22:34 33430 0.0 bias 01:42 33432 0.0 bias 03:14 33433 0.0 bias ---=== TELESCOPE OFFSETS AND SCALE I ===--- Time Instrument Az Alt Rot Scale pos offset pos offset pos offset ------------------------------------------------------------------------------ ---=== TELESCOPE OFFSETS AND SCALE II ===--- ---=== DATA TAPE SUMMARY ===--- Goes: JL Stays: JL ---=== FOCUS LOG ===--- setmir piston Temp Wind Time Inst scale M1 M2 Foc Az Alt (C) MPH Dir filt fwhm ------------------------------------------------------------------------------ 23:58Z 9 0 1.00000 0 1259 0 121 30.4 15.7 8 107 ---=== WEATHER LOG ===--- Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky 23:58Z 60 51 8 106 (ESE) 611 - PtlyCldy 02:14Z 58 45 11 166 (SSE) 506 - PtlyCldy 02:48Z 57 44 10 171 (S) 578 - PtlyCldy 03:19Z 55 45 7 190 (S) 869 - PtlyCldy 03:52Z 55 46 12 178 (S) 770 - PtlyCldy 04:24Z 55 46 12 180 (S) 737 - PtlyCldy 04:56Z 56 45 16 177 (S) 795 - PtlyCldy 05:37Z 57 46 9 183 (S) 809 - PtlyCldy 06:09Z 56 46 13 185 (S) 825 - PtlyCldy 06:41Z 55 47 11 203 (SSW) 828 - MstlyCldy 07:13Z 55 49 11 199 (SSW) 1003 - MstlyCldy 07:45Z 55 49 8 189 (S) 1028 - MstlyCldy 08:18Z 54 50 10 217 (SW) 1040 - MstlyCldy 08:50Z 55 50 7 208 (SSW) 1109 - MstlyCldy 09:22Z 54 51 4 252 (WSW) 1107 - MstlyCldy 09:54Z 53 51 4 200 (SSW) 1149 - MstlyCldy ---=== TELESCOPE STATUS ===--- Telescope is stowed at 121,90 No interlocks bypassed Spectrographs are warm ---=== SOFTWARE USED ===--- IOP/SOP: iop Watcher: watcher MCP: v5_26_0 TPM: tpm_v3_0_0 AstroDa: biery TCC: TCC 2.7.2.1 August 6 2004 sdssProcedures: v2_03 SoS: v4_10_7 hoggPT: v1_6_9 plate-mapper: v4_3_1 ---=== MIRROR NUMBERS ===--- ---=== PROBLEMS IN DETAIL ===---