Subject: 2.5m obs log 20 May 2000 (mjd 51685) Date: Sun, 21 May 2000 05:01:23 -0600 (MDT) From: hayes@apo.nmsu.edu (Jeffrey Hayes) [mail to: obs-report-25m@apo.nmsu.edu include MJD in subject] Saturday May 20 2000 Apache Point Observatory SDSS 2.5m Observing Log (MJD 51685) OBSERVING TEAM: =============== Atsuko Nitta Kleinman (APO) - shift 1 Scot Kleinman (APO) - shift 1 Jeffrey Hayes (APO) - shift 2 Ellyne Kinney (APO) - shift 2 VISITORS: ========= Jim Annis (FNAL) - phone THE PLAN: ========= Engineering tests. SYNOPSIS FOR NIGHT: =================== Initially cloudy for the night, with hinted precip at Holloman AFB via NextRad. Clouds dogged us for most of the night until 18deg twilight. TELESCOPE STATUS: ================= At stow, 30deg ALT, with engineering camera on. DIMM: ----- INTERLOCKS: =========== None bypassed. SOFTWARE USED: ============== IOP/SOP: v3_15_2 Watcher: v2_8_2 MCP: v4_2_4 TPM: v1_0_8 AstroDa: 14_28 TCC: 2.2.9 WEATHER SYNOPSIS (see below for hourly data): ============================================= Overcast with dark and pendulous clouds. Started to clear out by twilight. GENERAL COMMENTS (see Problems below for details): ================================================== The day shift cut IOP v3_15_2 and did an afternoon bias and endNight. During the bias, ID4-1 shut down. Using the WWW trouble shooting, we re-enabled it simply by remounting the current tape. In the past, we put in a new tape to get things to work- it's interesting that the same tape worked. Basically, all we did was an archPause, archUseDrv, and an archResume. IOP v3_15_2 does indeed ask the question about wanting to ship tapes first, but it doesn't ask the question about the tapes surviving nor the question about the log tapes being ready nor the one about which runs to archive until later. One down -three to go. This might not normally be a problem since these questions might get asked before too much processing time - this afternoon, it took hours to get to the last question because it had to skip past roughly a zillion and two filemarks before it could start thinking about what to do with the logs. Other than this, the daytime endNight ran fine. While cleaning up the murmur, one of the processes it told me to kill ended up killing my IOP session. Details in Problems below. We cleaned all the tape drives before the night crew came in. endDrift of our second bias run resulted in errors (I'm not sure why the first one didn't - maybe it did and we didn't notice?). See Problems. Jim made some corrections which we tested by sourcing. We set about testing the PRs 1052, 1012, 988, 987, 892, and 881. See the comments in the Problems section below. We put the engineering camera camera on at 01:20, but by the time we were finished, the clouds came back over us. It was our intention to do a short (40 pt) pointing model. We had a bit of trouble with getting the engineering camera to respond (our friend error code 116 again), but a power cycle of the camera and a reboot of the guider Mac cured the problem. While waiting for the weather, we decided to home and relax the primary. Following the instructions on the Web page, we homed the primary, and then relaxed it. However, when we tried to put the primary back to the default locations listed below, we found the following values from the TPM: Axial A= 1.9455 Axial B= 0.5510 Axial C= 0.5565 Transverse D= 0.3835 Lateral E= 1.8985 Lateral F= 0.3980 Through the TCC we also did a "mirror stat prim" and obtained: 0 1 I PrimCmdMount=0., 0., 0., 0., 0., 0. 0 1 I PrimActMount=0., 0., 0., 0., 0., 0. 0 0 F Modu="mir_OneMount2Orient"; Text="Fit error too large for Prim" 0 1 W Text="Failed to compute PrimOrient" 0 1 I PrimStatus=65537, 65537, 65537, 65537, 65537, 65537 0 1 I Received=" 1 lateral links (0 disengaged, 1 engaged)" Collimation was turned off and the procedure was thrice repeated so as to minimize uer error. At this point, the documentation tails off, and so we are puzzled by the primary not going back to where we expected it to. "endNight $mjd" was run, to make sure that the time tracking log files are being copied correctly. This now appears to be the case, and "endNight" finished up without problems. NB: NO TAPES ARE TO BE SHIPPED. DATA ACQUISITION (see IOP/SOP output below): =========================================== IMAGING: -------- Run Type --- ---- 1490 bias 1491 bias 1492 bias 1493 bias SPECTROSCOPY: ------------- Exposure Type -------- ---- 3752 bias init MIRRORS: ======== PRIMARY: -------- MIGS SHOULD BE Axial A= 1.9284 Axial B= 0.5594 Axial C= 0.5579 Transverse D= 0.3744 Lateral E= 1.9065 Lateral F= 0.4074 GALILS Commanded: Actual: SETMIR VALUES primDesOrient: primOrient: SECONDARY: ---------- Focus: Temp: Altitude: MIGS Axial A= Axial B= Axial C= Transverse D= GALILS Commanded: Actual: SETMIR VALUES secDesOrient: secOrient: FOCUS LOG: ========== M1 Piston M2 Piston Temp Wind Time Inst setmir TCC setmir Az Alt C Dir MPH filt FWHM " LN2 SCHEDULE: ============= Spectros filled at 01:20. PROBLEMS: ========= Murmur killing: --------------- This is what my IOP session looked like before I ran the kill task and after: ---------------- ... You probably have to be su for the kill commands. dscRun stop_mursrvr kill 82730 kill 187685 kill 167567 kill 334075 kill 88226 kill 87402 kill 336647 kill 317749 kill 82476 kill 331691 rm /astrolog/astroda.v14_28.log dscRun start_mursrvr im> dscRun stop_mursrvr dscRun using system v14_28 im> /p/astroda/v14_28/bin/dscRun[422]: 317749 Terminated ~ Host> ---------------- This is what I killed: # kill 187685 82730 167567 334075 88226 87402 336647 317749 82476 331691 endDrift -------- filling out runlog //astrolog/51685/runlog-1490.txt for this run I cannot find all your requested files ... searching makeRunLog has failed: no files matched glob pattern "/51685/1490/idGang-001490-c1-[0-9][0-9][0-9][0-9].fit" finishing endDrift (forgot to do a tb - sorry, but this should be easy to find...) Later, it failed with a different message: leap seconds = 32 filling out runlog //astrolog/51685/runlog-1491.txt for this run makeRunLog has failed: Failed to read desired columns from /astrolog/51685/idAstroline-r6-001491.par: No lines read finishing endDrift im> tb Failed to read desired columns from /astrolog/51685/idAstroline-r6-001491.par: No lines read while executing "error "Failed to read desired columns from $paramFile: $msg"" invoked from within "if [catch { seek $fd $linestart vectorsReadFromFile $fd $veclist -type $k } msg] { cmdtrace $savecmdtrace close $fd foreach el $veclist { vec ..." (procedure "param2Vectors" line 254) invoked from within "param2Vectors $file $paramList dummy" invoked from within "set list [param2Vectors $file $paramList dummy]..." invoked from within "if {$goodStats} { set paramList "" foreach ccd $ccdList($node) { append paramList "rMinor$ccd rMajor$ccd skyL$ccd skyR$ccd biasL$ccd biasR ..." ("foreach" body line 19) invoked from within "foreach node "ad1 ad2 id1 id2 id3 id4 id5 id6 ad3 ad4" { if {![regexp {^([ai])d([1-6])$} $node foo type n] || ($type == "a" && $n > 4)} { ..." (procedure "makeRunLog" line 125) invoked from within "makeRunLog $mjd $run" Jim was on the phone and looked into all this. ------------------------------------------------------------- TCC PR 1052 Logged into TCC25M and started a telrun session. As the version still is 2.2.9, the error about the a command line of 256 or more characters is still occuring. The traceback from the TCC is included for completeness: $ telrun 0 1 I YourUserNum=1 0 1 : UserNum=1; UserAdded track 11111111111111111111111111111111111111111111111111111111111111111111111111 11111111111111111111111111111111111111111111111111111111111111111111111111111111 11111111111111111111111111111111111111111111111111111111111111111111111111111111 1111111111111111 0 0 ! Facil="FOR"; VMSMsg="ERRDURREA"; EText="error during read unit 5 file SYS$COMMAND:.; user PC 00000000" 0 0 W Facil="RMS"; VMSMsg="TNS"; EText="terminator not seen" %FOR-F-ERRDURREA, error during read unit 5 file SYS$COMMAND:.; user PC 00000000 -RMS-W-TNS, terminator not seen %TRACE-F-TRACEBACK, symbolic stack dump follows Image Name Module Name Routine Name Line Number rel PC abs PC 0 80295034 80295034 DEC$FORRTL 0 000424D8 003004D8 DEC$FORRTL 0 0005AE04 00318E04 TCCINTERP IO_GETRECORD IO_GETRECORD 52 00000098 0006C288 TCCINTERP IO_GETCMD IO_GETCMD 56 00000098 000509D8 TCCINTERP EXE_TCCINTERP EXE_TCCINTERP 164 000000FC 000500FC 0 81DFE8F0 81DFE8F0 show version 0 1 I Text="TCC 2.2.9, May 18, 2000" --------------------------------------------------------- sop PR 1012 We tested the pauseGuider -all command, and found that a "startGuider " worked okay (i.e. it started again), but we did not receive the expected stats from the guide fibres. We do note that guider images continue to be taken even after the "pauseGuider -all" command. "stopGuider" works fine. Inasmuch as we do not have to reinitialize the guiderInfo array, we can declare this one tested. Output below: sp1> startGuider 1 Using 1 second gcam exposures sp1> /data/spectro/guider/gimg0026.fits /data/spectro/guider/gimg0027.fits /data/spectro/guider/gimg0028.fits sp1> pauseGuider -all 1 sp1> /data/spectro/guider/gimg0029.fits /data/spectro/guider/gimg0030.fits /data/spectro/guider/gimg0031.fits /data/spectro/guider/gimg0032.fits /data/spectro/guider/gimg0033.fits /data/spectro/guider/gimg0034.fits /data/spectro/guider/gimg0035.fits /data/spectro/guider/gimg0036.fits /data/spectro/guider/gimg0037.fits /data/spectro/guider/gimg0038.fits /data/spectro/guider/gimg0039.fits sp1> startGuider 1 /data/spectro/guider/gimg0040.fits Using 1 second gcam exposures sp1> /data/spectro/guider/gimg0041.fits /data/spectro/guider/gimg0042.fits sp1> stopGuider ------------------------------------------------ sop PR 988 We tried the "reloadcart" command, and while it seemed to work okay, we had an interesting message back from sop: sp1> reloadCart 5 312 /p/iop/v3_15_2/params/cartridgeInfo.par Please choose one of the plugmap files below (-1 to escape) Choice Filename 0 /data/spectro/plugMapM/plPlugMapM-0312-51666-01.par 1 /data/spectro/plugMapM/plPlugMapM-0312-51673-01.par 2 /data/spectro/plugMapM/plPlugMapM-0312-51684-01.par 2 Reading /data/spectro/plugMapM/plPlugMapM-0312-51684-01.par Taking absolute values of GUIDE fiberId Taking absolute values of ALIGNMENT fiberId Coordinates are 229.076622 0.024522 Starting weather Handler reload file does not exist: /astrolog/51685/cartridgeReload-51685-0312.par Coordinates are 229.076622 0.024522 It appears that its looking for /astrolog/51685/cartridgeReload-51685-0312.par.Shouldn't the script create it if it does not exist already? -------------------------------------------------------- sop PR 881 Asking for plate ID. We did a "goStare 0 -init -bias" and did not get asked for a plate ID. This seems okay, as we had already done a "loadCart". -------------------------------------------------------- sop PR 892 Double beep for end of exposures. We did another "goStare 0 -bias" and only heard a single beep. Perhaps a 1 second pause between beeps? -------------------------------------------------------- WEATHER DATA: ============= Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky Precip. [pmt]cl = partly, mostly, totally cloudy DATA LOGS FROM IOP/SOP: =======================