Date: Fri, 22 Feb 2002 05:56:41 -0700 (MST) From: ank@apo.nmsu.edu (Atsuko Kleinman) Subject: 2.5m obslog 20020221 (MJD 52327) APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Thursday February 21, 2002 (MJD 52327) ---=== OBSERVING TEAM ===--- Jurek Krzesinski Eric Neilsen Atsuko Nitta Scot Kleinman ---=== OBSERVING PLAN ===--- Shake the telescope, the software and your mind, body and soul. ---=== OBSERVING SUMMARY ===--- Jurek shook more than his share tonight. He did not run away at the end of the twilight but stayed and helped us shake many item. The most exciting result of the shake: o We now have a nice window where all the guider info is sent to. o Eric fixed the battle over UDP port between fsaoImage, PGPLOT and granInst is solved! We finished off plate 2 cart 784. We declared iop/sop v3_69_2 current. We saw the following message tonight. What does it mean? We checked the umbilica and found nothing wrong with it. umbilical position: failed to get semSLC: S objLib OBJ TIMEO (umbilical_position: failed to get semSLC: S_objLib_OBJ_TIMEO (Feb 22 02:02:19): Feb 22 02:02:32 MST ) ---=== OBSERVING LOG ===--- Software install ------------------ Jurek installed astrotools v5_6 dervish v8_7 sdssmath v5_4 sdsstools v4_14 Scot installed sdssProcedures v1_40 Eric built and installed iop/sop v3_67_0 bsed on the software installed by Jurek. Spectrographs ------------- The first bias in the afternoon showed up in pink on the monitor in the control room. SoS complained also. Has any work done to the spectrographs today? The second bias still had r1 showing in red number on sos www page, but the third exposure showed them to be all in spec. Telescope/Enclosure --------------------- There was some trouble with the nitrogen gas bottle in the afternoon and Norm asked us to motnitor it during the night. At the end of the night, the pressures has dropped to 500psi. (It had 1500 psi at the beginning of the night.) Cone fan did not come on. We asked Robert R. who was working inside PT enclosure tonight to see if he has touched the electronic box that is common to both PT and 2.5m and he said he has not done anything. We understand that there was work done inside the cone. Perhaps it was unplugged during the work and not reconnected later? Who knows. We tried to connect Jon B. but we could not reach him. We left a message on his phone. There seems to be a flaky contact inside the switch box of the enclosure that moves it to the east. When you try to open the enclosure, it seems to move for a while and then slow down and halt and the beeping sound comes on. We were able to open by turning the keys back and forth. The switch box on the west does not seem to have this problem. Atsuko dropped the east switch box to the floor before opeing and might have caused the contact to be flaky. The exhaust fan alarm was on at the beginning of the night, but off at the end of the night. sdssProcedures v1_40 ---------------------- Jurek carefully went through all that has changed. Jurek did not know what was updated on idlspec2d_install.html. While checking the sdssProcedure www page's links, he found that he could not find the following page. Mainly because there were no such documents. We should either get rid of the links, find the documents or write the documents if we need them. SOP FocalPlane Mapping SOP Commands IOP/MOP Interface Interlock Bypass Policy Chiller Guide The "test" docs for the following are not there because there are no documents to be tested. Perhaps instead of getting "FileNotFound", we should have "No new Doc to test" message? PTVME sdsstools watcher dervish We did use the new "2.5m Preflight Check" list. The list is now broken down in caegories under location (i.e. Control Room, Ouside, Telescope Upstairs, Telescope Downstairs, PT). The only comment was to have the Downstairs list to be before pPstairs list. IOP/SOP ------------ PR 2230: please provide a way to input exposure quality. --> postponed to shakedown because this needs to be tested at the beginning of the night. PR 2810: Yes, it reformats a paragraph. PR 2924: Then tcc now gets command indexes from IOP processes. PR 2217: Battle of udp port --- Closed!!!!!! Yipppppeeeeee!!!! PR 3097: Make errors from SOP commands executed by the GUI less easy to miss "guiderDataWindow" is a new command that will pop up a window with guide stars info. The warning such as goStare failure will go to the sop window which is no longer a crowded scrolling window to make it easy to read without hurting your eyes. PR 3125: Cannot Exit IOP when started from non-X terminal In the process of testing this, I started iop from sdsshost session connected from LANDRU via "ssh -x sdsshost". It took many minutes to start IOP. Exiting was very easy and painless. The PR is closed. PR 3173: Changes teamster transferring spectro files to say so spectro TMS says "transferring frames" imager TMS says "transferring gangs" So we won't confuse the TMS messages. PR closed. PR 3098: SOP reports bad interlock status for goStare -bias Closed. We did not see the bad interlock status messages any more. PR 2811: cancel button for switching activities Closed. There is a cancel button and it works. PR 2951: fk5InFiber -test is now fk5InFiber This works. Closed. While testing this, we encountered a peculiar probelm. After running this command serveral times, we saw a message: sp1> fk5InFiber 200 10 -fiber 5 Slewing to an fk5 at 200.024236 10.000049 (J2000) Tracking to 201.1822241272, 9.6518191759 Old starInFiber errors: RA 2.34'' DEC 7.95'' Warning! I can't talk to the TCC, or the telescope brakes are on. We could not do any command to move the telescope from this TCC session, but we could send command such as gcam, show inst without any problem. We started a new sop session and try the fk5InFiber and it worked fine. Finally, Eric suggested that we set the TCCCommandSerialNumber=1 in the sop session that is having problem sending track commands to TCC. This solved the problem. We were able to continue with the fk5InFiber command test in the original sop session. After two hours of trying many things, Eric discovered that the source of the problem was the way IOP read back info from TCC. IOP expects to read info 6th column onward in TCC. When the command sequence number exceeds 10, then the column which says what TCC is doing is shifted to 7th column. Eric fixed this in v3_69_2. PR 3011: Request to have SOP send guider probe geomertry to the TCC 06:20:19Z We tried the new command: sp1> informTCCOfGProbes Rot_Inst_ang is -89.97..., cosine is 0.00052359877097206972 sine is -0.99999986292215415 sp1> This prompted a lot of messages in TCC. Eric will contact Russell for more info. 0 00 0 I TrackAdvTime=3.52 0 0 I TCCStatus="TTT","NNN"; TCCPos=121.00,90.00,0.00; AxePos=121.00,90.00,0.00 0 0 I AxisErrCode="OK","OK","OK" 0 0 I TrackAdvTime=3.56 0 0 I TrackAdvTime=3.52 0 0 I TCCStatus="TTT","NNN"; TCCPos=121.00,90.00,0.00; AxePos=121.00,90.00,0.00 0 0 I AxisErrCode="OK","OK","OK" 0 0 I TrackAdvTime=3.56 0 0 I TrackAdvTime=3.52 0 0 I TCCStatus="TTT","NNN"; TCCPos=121.00,90.00,0.00; AxePos=121.00,90.00,0.00 0 0 I AxisErrCode="OK","OK","OK" 0 0 F Modu="blk_LoadInst"; Text="unknown keyword :5" 0 0 I Modu="blk_LoadInst"; Text="file:" 0 0 I Modu="blk_LoadInst"; Text="record: 5 GProbe 1 T" 4 8 F Failed; cmdStr='SET BLOCK INST' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" " 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 6 8 F Failed; cmdStr='440.5100' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" M" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 7 8 F Failed; cmdStr='115.1800 408.6600' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" €" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 8 8 F Failed; cmdStr='178.8800 472.3600' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 9 8 F Failed; cmdStr='0.2907 0.8974' 10 8 : cmdStr='-278.1745' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" GPROBE" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 11 8 F Failed; cmdStr='GProbe 2 T' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" Î" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 12 8 F Failed; cmdStr='296.8000' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" O" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 13 8 F Failed; cmdStr='117.0800 264.9500' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" €" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 14 8 F Failed; cmdStr='180.7800 328.6500' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" I TrackAdvTime=3.52 0 0 I TCCStatus="TTT","NNN"; TCCPos=121.00,90.00,0.00; AxePos=121.00,90.00,0.00 0 0 I AxisErrCode="OK","OK","OK" 0 0 I TrackAdvTime=3.56 0 0 I TrackAdvTime=3.52 0 0 I TCCStatus="TTT","NNN"; TCCPos=121.00,90.00,0.00; AxePos=121.00,90.00,0.00 0 0 I AxisErrCode="OK","OK","OK" 0 0 I TrackAdvTime=3.56 0 0 I TrackAdvTime=3.52 0 0 I TCCStatus="TTT","NNN"; TCCPos=121.00,90.00,0.00; AxePos=121.00,90.00,0.00 0 0 I AxisErrCode="OK","OK","OK" 0 0 F Modu="blk_LoadInst"; Text="unknown keyword :5" 0 0 I Modu="blk_LoadInst"; Text="file:" 0 0 I Modu="blk_LoadInst"; Text="record: 5 GProbe 1 T" 4 8 F Failed; cmdStr='SET BLOCK INST' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" " 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 6 8 F Failed; cmdStr='440.5100' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" M" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 7 8 F Failed; cmdStr='115.1800 408.6600' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" €" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 8 8 F Failed; cmdStr='178.8800 472.3600' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 9 8 F Failed; cmdStr='0.2907 0.8974' 10 8 : cmdStr='-278.1745' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" GPROBE" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 11 8 F Failed; cmdStr='GProbe 2 T' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" Î" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 12 8 F Failed; cmdStr='296.8000' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" O" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 13 8 F Failed; cmdStr='117.0800 264.9500' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" €" 0 0 W Facil="FORT"; VMSMsg="NOMSG"; EText="Message number 006A6010" 14 8 F Failed; cmdStr='180.7800 328.6500' 0 0 W Facil="CLI"; VMSMsg="IVVERB"; EText="unrecognized command verb - check validity and spelling" 0 0 W Facil="CLI"; VMSMsg="CMDSEG2"; EText=" SoS ------ PR 3185: (S/N)^2 What shall we do? Edit headers by hand and try to have SoS reduce it? PR 2231: we'd like to be able to see the SoS -extracted spectra --> We were able to see some spectra using apoplot, 784, 180, mjd=52327 command. Without specifying mjd we could not get the spectra (which is first example in the doc). We would like to have all examples in doc work. MCP ---- PR 3005: Reassigned to Robert since we saw "too large to correct" messages this dark run, there cause of it is still not complately eliminted. PR 2848: "Add code to detect inconsistencies between encoders" We did not test this since we did not know how to. We have been using "-scale" when we build the fiducials. What else do you want us to do in what condition? I could not understand from the PR's "Fix_change_To" section what I was to do and look for to test and what I need to verify to know that this PR can be closed. Feedback info on "an error question in SOP not allowing a response because the command was issued from SOPGUI instead of the command line." This indeed happened to night when we did a goStare and the DA and sop did not agree on the exposure number. goStare now asks you what you want to do and the questions were sent to the sop window scrolling over and over, but we could not answer it. We had to control-C out of it in sop window to stop the scrolling questions and issue the command on comand line in sop window. Cartridge 2 Plate 784 -------------------------------- We used this plate to do fk5InFiber tests. We took the one last exposure necessary to finish off this plate. We noticed a streak of something on fiber 10 when we took flats. Please check this fiber. endNight rejoiced. ---=== IMAGING RUN SUMMARY ===--- Run Time Stripe Lambda Last Flavor Comments Start End Begin End Frame ------------------------------------------------------------------------- 3000 0039Z 0133Z 100 O -129.32 -115.73 43 ignore 3001 0233Z 0412Z 100 O -100.73 -75.88 180 ignore ---=== IMAGING RUN DETAILS ===--- ---=== SKIPPY RESULTS ===--- Run Frame nFrames stars muErr muRms nuErr nuRms rot --------------------------------------------------------------- ---=== LTMATCH RESULTS ===--- Run Field nFields nGood rowMean rowSig colMean colSig rot --------------------------------------------------------------- ---=== SPECTROSCOPY DATA SUMMARY ===--- UT Exp Time flavor comment (S/N)^2 totals ========================================== b1 r1 b2 r2 01:51 13441 0.0 bias ----- sequence 13442, plate 810 ------- 04:08 13442 10.0 flat 04:10 13443 2.0 arc 04:51 13444 0.0 bias ----- sequence 13445, plate -9999 ------- 04:59 13445 0.0 bias 05:08 13447 0.0 bias ----- sequence 13448, plate 810 ------- 05:13 13448 10.0 flat 05:15 13449 2.0 arc ----- sequence 13450, plate -9999 ------- 05:51 13450 0.0 bias 05:58 13451 0.0 bias 06:07 13452 0.0 bias ----- sequence 13453, plate 810 ------- 06:15 13454 10.0 flat 06:17 13455 2.0 arc ----- sequence 13456, plate -9999 ------- 06:32 13456 0.0 bias 06:41 13457 0.0 bias ----- sequence 13459, plate 810 ------- 06:50 13459 0.0 bias 06:56 13460 0.0 bias 07:02 13461 0.0 bias ----- sequence 13470, plate -9999 ------- 08:06 13470 0.0 bias ----- sequence 13472, plate -9999 ------- 08:20 13472 0.0 bias 08:26 13474 0.0 bias ----- sequence 13475, plate -9999 ------- 08:34 13475 0.0 bias 08:38 13477 0.0 bias ----- sequence 13480, plate -9999 ------- 09:18 13480 0.0 bias 09:25 13481 0.0 bias 10:12 13482 0.0 bias 10:15 13483 0.0 bias 10:18 13485 0.0 bias ----- sequence 13486, plate -9999 ------- 10:59 13486 0.0 bias ----- sequence 13487, plate 784 ------- 11:17 13487 10.0 flat 11:19 13488 2.0 arc 11:37 13489 901.0 target 11:44 13490 240.0 smear ---=== TELESCOPE OFFSETS AND SCALE I ===--- Time Instrument Az Alt Rot Scale pos offset pos offset pos offset ------------------------------------------------------------------------------ 1108Z 2 0 192.65 -0.0044 59.61 0.0006 23.07 0.0000 1.000000 ---=== TELESCOPE OFFSETS AND SCALE II ===--- ---=== DATA TAPE SUMMARY ===--- Goes: JL5064 Stays: JL5065 ---=== FOCUS LOG ===--- setmir piston Temp Wind Time Inst scale M1 M2 Foc Az Alt (C) MPH Dir filt fwhm ------------------------------------------------------------------------------ 19:25 1 810 1.00000 0 1188 0 -46 47.5 -4.2 15 46 19:49 1 810 1.00000 0 1702 500 -52 43.7 -3.3 19 19 20:16 1 810 1.00000 0 1720 500 -59 39.0 -2.7 13 4 00:19 2 784 1.00000 0 1614 500 121 90.0 -3.1 11 14 01:08 2 784 1.00000 0 1169 0 151 54.1 -3.1 15 4 03:30 2 0 1.00000 0 1150 0 184 60.8 -3.8 21 22 03:36 2 0 1.00000 0 1149 0 184 61.2 -3.6 12 14 04:02 2 784 1.00000 0 1151 0 191 60.4 -3.9 10 346 ---=== WEATHER LOG ===--- Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky 18:29 23 11 15 68 (ENE) 112 - 19:01 23 10 16 55 (NE) 88 - 19:33 24 4 11 18 (NNE) 122 - 20:05 26 7 14 358 (NNW) 153 - 20:36 27 7 12 0 (N) 256 - 21:07 26 7 19 14 (NNE) 271 - 21:39 27 6 17 23 (NNE) 237 - 23:54 26 6 11 34 (NE) 395 - 00:58 26 5 12 4 (N) 211 - 02:02 24 9 8 7 (N) 172 - 05:42 27 3 18 18 (NNE) 166 - ---=== TELESCOPE STATUS ===--- ---=== SOFTWARE USED ===--- IOP/SOP: v3_67_0 to v3_69_2. v3_69_2 declared current. Watcher: v2_15_0 MCP: v5_9_6 TPM: v2_4_7 AstroDa: v14_36 TCC: 2.6 sdssProcedures: 1_40 ---=== MIRROR NUMBERS ===--- PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A 0.0730 0.0750 Axial B 0.8050 0.8020 Axial C 0.0780 0.0710 Trans D -1.5280 -1.4860 Lateral E 1.8640 1.8540 Lateral F 1.4310 1.4240 GALILS Commanded: 5400. -3700. 900. -200. 31550. 30650. Actual: 5400. -3700. 900. -200. 31550. 30650. SETMIR VALUES PriDesOrient: 0.00 -11.80 23.00 1256.90 642.10 PriOrient: 0.00 -12.16 22.81 1257.41 642.19 SECONDARY: ---------- Focus: 0.00 Air Temp.: -4.7 Alt.: 29.997539 MIGS TONIGHT NOMINAL Axial A 1.5500 1.5500 Axial B 1.2390 1.2260 Axial C 1.2490 1.2480 Trans D 0.2200 0.2320 GALILS Commanded: 1599479. 1565255. 1586332. -10400. -9750. Actual: 1599600. 1565250. 1586350. -10400. -9750. SETMIR VALUES SecDesOrient: 1257.00 -3.40 -10.00 0.00 133.82 SecOrient: 1256.96 -3.41 -9.95 -0.21 133.70 ---=== PROBLEMS IN DETAIL ===--- Too large to correction: We had problem gettint go the instChange position because the telescope will halt, and at the same time, we got the "too large to correct" messages and the windscreen message Here are the too large to correct messages. Feb 21 20:49:04 sdssmcp tLatch dsc_I_trcInfo Applying correction 17091 to azimuth Feb 21 20:49:04 sdssmcp tLatch dsc_E_trcErr correction for azimuth 17091 is too large Feb 21 20:49:08 sdssmcp tLatch dsc_I_trcInfo Applying correction 17091 to azimuth Feb 21 20:49:08 sdssmcp tLatch dsc_E_trcErr correction for azimuth 17091 is too large Feb 21 20:49:54 sdssmcp tLatch dsc_I_trcInfo Applying correction 17091 to azimuth Feb 21 20:49:54 sdssmcp tLatch dsc_E_trcErr correction for azimuth 17091 is too large Another message when we slew to field: azimuth (correction for azimuth 33883 is too large (Feb 22 00:20:30): Feb 22 00:22:03 MST ) azimuth (correction for azimuth 33883 is too large (Feb 22 00:25:05): Feb 22 00:25:21 MST ) Umbilical error from watcher: umbilical position: failed to get semSLC: S objLib OBJ TIMEO (umbilical_position: failed to get semSLC: S_objLib_OBJ_TIMEO (Feb 22 02:02:19): Feb 22 02:02:32 MST )