Date: Sun, 21 Apr 2002 10:19:22 GMT From: jurek@apo.nmsu.edu (Jurek Krzesinski) Subject: 2.5m obslog 20020420 (MJD 52385) APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Saturday April 20, 2002 (MJD 52385) ---=== OBSERVING TEAM ===--- Scot Kleinman Eric Neilsen & Jurek Krzesinski ---=== OBSERVING PLAN ===--- Schakeup. ---=== OBSERVING SUMMARY ===--- Tested all the stuff but PLC changes 2 and up. Most ofsoftware problems Eric fixed on on the spot. DA failed during Apache Wheel test but we recovered. cart 9 plt 903 - additional exposure done, but got only 12.6 S/N and we need additional exposure for it (smear was done on clear sky). ---=== OBSERVING LOG ===--- Afternoon checkout ok. Scot installed new versions of software (see software section) and declared them current. MCP was rebooted, telescope fiducialized. OBSERVATIONS ------------- 05:28Z We try to finish yesterday's plate 903 working with new software - stars on slew. Well - we are missing 0.4 in S/N, smear done on clear sky. 06:19Z switching to imgager 07:15Z testing PR 3208 on stripe 34 S. (focus formula -20*T gaved focus -70 but we knew that it should be about three time more and were right, so finaly focus loop set the focus to -250). skippy: logTool/skippy now shows: Run Frame nFrames stars muErr muRms nuErr nuRms rot az el ------------------------------------------------------------------------- 3138 11 4 31 9.400 0.163 -7.500 0.275 -0.00195 324 49 3138 18 1 17 10.400 0.261 -7.200 0.094 -0.00263 324 50 So the new feature is muRms (mu error) and nuRms (nu error) and for Ltmach: Run Field nFields nGood rowMean rowSig colMean colSig rot --------------------------------------------------------------- 3138 21 1 6 -0.824 0.105 1.015 0.211 -0.00341 3138 21 1 11 -0.566 0.221 1.068 0.198 -0.00359 there are rowSig and colSig collumns witch are errors of rowMean and colMean accordingly. sdssProcedures - checked - the changes are there and work. ------------------------------------------ IOP ________________ PR 3502 calcStripeParams help string shows now UT time: "Times are assumed to be in the time system defined by TZ, hopefully UT". TZ is an enviromental variable set to UT while iop is run. So, if you'll change TZ after iop, then it will be using that setting as a time specification for calcStripeParams. PR 2718 logExtract command works and you can get information from murmur, TCC, MCP etc (see help logExtract) between specified times with it. For example if you need something from murmur on 2002 Apr 20, between 1:30 and 1:35 Z time, just type: im> logExtract "2002-04-20 01:30:00Z" "2002-04-20 01:35:00Z" -murmur it's very slow when you ask it to get something from TCC or MCP... (but you have to setup your ssh properly to "pod" machine - try to log as arc: >ssh arc@pod - can you log in - if yes, then you can get TCC information). Well - still needs some feedback from users and work around it). Eric says that Criag needs to setup our ssh properly for that. PR not closed since more work might be done on it. PR 3420 ltMatch and skippy now complain if they are run on frames, which gangs are not yet transfered. PR Closed. Apache Wheel: ______________ Preparing linestart (scan rate): im> set cameraSet(linestart_period) 16050 im> iccExec [vmeList] statusSet aldoAnalysis 0 im> cc 100 vs- settolerance im> cc 25 vs+ settolerance Switching to 4x4 binned mode: im> init4Bin 4 4 Checking the switch by taking bias in that mode: im> goDrift -bias im> endDrift Works. Now in TCC: 1. Very short rim scan: LST is almost 15 h, and it will be 225 deg, so the tcc command: TRACK (LST-15 deg) 0.0 FK5 /SCANVELOCITY=(0.0275,0) Wait!!! here HAVE TO Be a coma between LST-15deg nad 0.0 !!!! - anyway the proper command is: tcc: TRACK 210, 0.0 FK5 /SCANVELOCITY=(0.0275,0) and that worked we so satrs on long frames! So we endDrift that and go for next prart. 2. Modified northward spoke: The spoke that most recently transited should be observed, where the spokes are every hour in RA. Now LST is 15h (well aproximately) so RA is 225 deg. We ussued then: tcc: TRACK 225, -10.0 FK5 /SCANVELOCITY=(0,0.0275) and Da failed right at the beginning (blue screens) :( We killed teamster: im> kill_teamster waited a few minutes, then restarted the servers. im> start_servers -K from the session on MONX3 which was running the servers. foloowing Dan's DA recovery instruction we checked: iop> iccExec ad4 iciShow inprog, should be (according to instruction): .inprog: 0x00000001 queued: 0x00000000 -if there is en error but we've got: .inprog: 0x00000000 queued: 0x00000000 -which means it's ok. therefore we omited: im> iccExec ad4 iciSetInprog 1 off since .inprog was already 0x00000000 and issued: im> iccExec [vmeList] statusGet daqBusy (are crates busy?) most of them were busy {id1 1}, ...{id3 1}, but id4 {id4 0}, so to stop those bussy ids we asked to abort all of them: im> iccExec [vmeList] readoutAbort Because we started a new IOP, we set the linestart and binned mode again: im> set cameraSet(linestart_period) 16050 im> init4Bin 4 4 then im> goDrift stars were there, so we: im> endDrift and tried tried to scan again on: 3. Modified southward spoke: LST is 225 deg, so it will be 225-10 deg in the track command: tcc: TRACK 125, 70.0 FK5 /SCANVELOCITY=(0,-0.0275) im> goDrift stars were there and we im> endDrift Now we tried the last one: 4. Modified hub scan: LST is 225 now, so it will be 225-55 TCC> TRACK 170,43.969234 FK5 /SCANVELOCITY=(0.01614811,0.02225957) im> goDrift stars are scrolling up im> endDrift NOTE: it takes a long time to start doDrift. Also when you endDrift, you'll see blue stripes scrolling up, wich is a result of closing shutters. Now go back to normal mode: im> init4Bin 1 1 im> set cameraSet(linestart_period) 26322 im> cc startscan im> cc deftolerance im> cc setvdefault im> iack im> setImagerAmpsOn Turned astroline back on in the DA im> iccExec [vmeList] statusSet aldoAnalysis 1 Tested that all is OK when you're back to normal binning im> goDrift -bias answered yes to: [...] Is this ok? [no/yes]: yes and it was working. im> endDrift However we've got a problem with endDrift, after answering "bad" to the quality flag, it failed saying: "Failed to read desired columns from /astrolog/52385/idAstroline-r6-003145.par: No lines read im>" We tried again goDrift and endDrift to see what is the problem... but this time it worked fine. ---------------------------- end of Apache Wheel test ------------------------ SOP __________________ PR 3174 goStare frame numbe out of synch... spectro DA rebooted - sop sesion lost with a message: sp1> Access to shared data area at 0x18000000 lost (errno=0x5 I/O error) Read failed from PT icc40 CSB=0x80430010 rmt=0x18000000 cnt=0x0009ABE8 ******************************************************************************** * * * Backplane communications between the ICC/OAC are no longer possible. * * * * Perform the following steps until operations are possible. * * * * 1. Check connections between the machines. * * 2. Reboot (reset) the ICC. * * 3. Restart this (OAC) program. * * 4. Reset the local PT-VME940 (ptvmeMode -R). * * 5. Power-cycle the VMEbus crates. * * 6. Reboot the local machine (host). * * * ******************************************************************************** So, sop was restarted: sdsshost> sop then initNight and goStare issued: sp1> initNight 2002-04-21 02:40:23Z: SOP Ready for flight rpc.pcnfsd appears to be running - good. nfsd appears to be registered - good. sp1> goStare 0 -init -bias DA rebooted... attempting to fix exposure number. I will, however, fail, so you will need to take another bias and request that it correct the exposure numbers when prompted. Error: Invalid state for this command Status entry is read-only sp1> As advised another goStare was issued (we forget to grab instruments, but the bias was taken anyway): sp1> goStare 0 -init -bias PlateId [-9999]: Flushing charge for 15 sec appending BEGIN appending END EXPOSURE TIME is: 0 1019357272 1019357273 There already is a teamster, PID 526456, owned by neilsen Seq 14708 Exp 14708 Frame 14709 Do not schedule startFlushCharge sp1 200 Do not schedule startFlushCharge sp2 200 sp1> No complains about the wrong exposure number.... Eric made a fix to the Error: Invalid state for this command sp1> tb Invalid state for this command Status entry is read-only while executing "statusSet asmPrvSeqNum [expr $localExposureFrameStamp - 1]" invoked from within "if {[getFrameNumber] 0} { error "The DA has been rebooted; you need to take two bias frames to get the exposure numbe ..." (procedure "goStare" line 19) invoked from within "goStare 0 -init -bias" Then we tried again reboot, and this time (we did not loose SOP session): After rebooting spectro DA, goStare was issued: sp1> goStare 0 -init -bias DA rebooted... attempting to fix exposure number. I will, however, fail, so you will need to take another bias and request that it correct the exposure numbers when prompted. PlateId [-9999]: Flushing charge for 15 sec appending BEGIN appending END EXPOSURE TIME is: 0 1019358638 1019358638 Seq 14709 Exp 14709 Frame 14710 Do not schedule startFlushCharge sp1 200 Do not schedule startFlushCharge sp2 200 sp1> Then as asked, we issued another goStare: sp1> goStare 0 -init -bias PlateId [-9999]: ***************************************** WARNING: SOP and the DA have conflicting records of the current frame number. SOP's value: 14709 DA's value: 14710 You can: 1. Type "1" to have goStare set both to 14710 and continue 2. Type "2" to abort goStare and fix it yourself goStare> 1 After the answer: 1. Flushing charge for 15 sec appending BEGIN appending END EXPOSURE TIME is: 0 1019358918 1019358918 Seq 14711 Exp 14711 Frame 14711 Do not schedule startFlushCharge sp1 200 Do not schedule startFlushCharge sp2 200 sp1> exposure and frame number were the same. The error message has been improved, but since there is no real fix to the problem, we didn't close the PR but changed sbumiter-id to notapproved. PR 3052 NAME keword in spectro headers incorrect for special plates. We found the plug map files in /spectro/plugMapM on host, and chose one whose file name indicated that it was a special plate. 10 sec exposure was taken and when we saw the information: Seq 14712 Exp 14712 Frame 14712 We checked fits header NAME keyword for frame: /data/spectro/52385/sdR-b1-00014712.fit and it was correct: NAME = '0799-52292-01F' / Name of target; PlateId-MJD-Mapper Re Then we took an exposure with a "normal" plate and the NAME was set properly in the fits file header for that exposure. PR Closed ---------------- We didn't see the weather information scrollling up the OP windows tonight. ---------------- PLC ________________ PR 3115 closed: Rotator stops when the dog house is opened. endNight worked fine and PR 3233 archive duplicate copies ... closed. PR 3221 remove oldMurmur.tar ... works. Pr closed. The IOP with the code that passed shakes is in v3_77_0, now declared test. ---=== IMAGING RUN SUMMARY ===--- Run Time Stripe Lambda Last Flavor Comments Start End Begin End Frame ------------------------------------------------------------------------- 3136 23:17Z 02:24Z 100 O -92.73 -45.73 38 bias 3137 04:45Z 05:00Z 100 O -10.49 -6.68 37 bias 3138 07:17Z 07:42Z 34 S -10.34 -4.05 55 engineering 3139 07:59Z 08:03Z 100 O 38.15 39.38 18 engineering 3140 08:07Z 08:13Z 100 O 40.14 41.79 19 engineering 3142 08:29Z 08:36Z 100 O 45.79 47.43 19 engineering 3143 08:41Z 08:45Z 100 O 48.89 49.72 17 engineering 3144 08:48Z 08:51Z 100 O 50.46 51.32 17 engineering 3145 08:55Z 08:57Z 100 O 52.34 52.77 17 bias 3146 09:01Z 09:08Z 100 O 53.74 55.62 27 bias ---=== IMAGING RUN DETAILS ===--- ---=== SKIPPY RESULTS ===--- Run Frame nFrames stars muErr muRms nuErr nuRms rot az el --------------------------------------------------------------- 3138 11 4 31 9.400 0.163 -7.500 0.275 -0.00195 324 49 3138 18 1 17 10.400 0.261 -7.200 0.094 -0.00263 324 50 3138 43 4 43 11.400 0.189 -7.400 0.153 -0.00304 327 51 ---=== LTMATCH RESULTS ===--- Run Field nFields nGood rowMean rowSig colMean colSig rot --------------------------------------------------------------- 3138 21 1 6 -0.824 0.105 1.015 0.211 -0.00341 3138 21 1 11 -0.566 0.221 1.068 0.198 -0.00359 3138 21 1 5 0.276 0.233 1.026 0.253 -0.00345 3138 21 1 9 0.929 0.176 1.292 0.215 -0.00434 3138 21 1 15 1.538 0.245 1.356 0.250 -0.00456 3138 23 1 12 -1.379 0.268 1.616 0.258 -0.00543 3138 23 1 13 -1.066 0.222 1.783 0.169 -0.00599 3138 23 1 11 -0.449 0.201 1.834 0.243 -0.00617 3138 23 1 10 0.265 0.236 1.580 0.239 -0.00531 3138 23 1 11 0.997 0.419 1.631 0.189 -0.00548 3138 36 1 11 -1.263 0.206 1.989 0.333 -0.00669 3138 36 1 7 -0.409 0.217 2.025 0.299 -0.00681 3138 36 1 14 0.296 0.190 1.819 0.142 -0.00612 3138 36 1 9 0.815 0.408 1.677 0.232 -0.00564 3138 36 1 12 1.204 0.308 1.809 0.244 -0.00608 ---=== SPECTROSCOPY DATA SUMMARY ===--- UT Exp Time flavor comment (S/N)^2 totals ========================================== b1 r1 b2 r2 02:26 14707 0.0 bias 02:48 14708 0.0 bias ----- sequence 14709, plate -9999 ------- 03:11 14709 0.0 bias 03:16 14711 0.0 bias ----- sequence 14712, plate 799 ------- 03:37 14712 11.0 target ----- sequence 14713, plate 903 ------- 03:53 14713 11.0 target ----- sequence 14714, plate -9999 ------- 05:16 14714 0.0 bias 05:20 14715 0.0 bias ----- sequence 14716, plate 903 ------- 05:37 14716 10.0 flat 05:39 14717 2.0 arc 06:09 14718 1600.0 target 06:15 14719 240.0 smear ---=== TELESCOPE OFFSETS AND SCALE I ===--- Time Instrument Az Alt Rot Scale pos offset pos offset pos offset ------------------------------------------------------------------------------ 05:34Z 9 903 221.64 0.0005 57.54 0.0029 66.77 -0.0114 1.000360 ---=== TELESCOPE OFFSETS AND SCALE II ===--- ---=== DATA TAPE SUMMARY ===--- Goes: JL 5274 Stays: JL 5275 ---=== FOCUS LOG ===--- setmir piston Temp Wind Time Inst scale M1 M2 Foc Az Alt (C) MPH Dir filt fwhm ------------------------------------------------------------------------------ 05:47Z 9 903 1.00036 -3554 -1509 270 223 55.7 5.1 23 285 gdr 1.8 ---=== WEATHER LOG ===--- Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky 01:02Z 49 6 17 271 (W) 3282 - 01:34Z 46 3 20 284 (WNW) 2641 - 02:07Z 44 2 17 265 (W) 9733 - 02:39Z 43 1 23 279 (W) 7705 - 03:11Z 42 0 18 268 (W) 3746 - 03:43Z 41 -1 13 264 (W) 2328 - 04:13Z 42 -1 20 280 (W) 1755 - 04:44Z 41 -2 23 291 (WNW) 1373 - 05:16Z 41 -1 12 311 (NW) 1097 - 05:47Z 41 -2 23 284 (WNW) 1349 - 06:18Z 40 -3 21 278 (W) 1253 - 06:48Z 40 -3 18 299 (WNW) 1512 - 07:18Z 38 -5 15 299 (WNW) 1684 - 07:48Z 38 -4 7 330 (NNW) 1339 - 08:19Z 38 -4 14 315 (NW) 937 - 08:49Z 39 -5 17 293 (WNW) 908 - 09:22Z 39 -5 16 297 (WNW) 849 - 09:55Z 40 -7 19 306 (NW) 729 - ---=== TELESCOPE STATUS ===--- 05:15Z Telescope opened. 09:35Z Telescope closed. ---=== SOFTWARE USED ===--- IOP/SOP: v3_76_0 Watcher: v2_17_0 MCP: v5_11_3 TPM: v2_5_3 AstroDa: v14_47 TCC: 2.6.2 sdssProcedures: v1_43 ---=== MIRROR NUMBERS ===--- PRIMARY: -------- Scale: 1.000000 MIGS TONIGHT NOMINAL Axial A 0.0870 0.0880 Axial B 0.7970 0.7980 Axial C 0.0700 0.0700 Trans D -1.5220 -1.5230 Lateral E 1.8360 1.8320 Lateral F 1.4030 1.4000 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.: 6.6 Alt.: 30.000051 MIGS TONIGHT NOMINAL Axial A 1.5590 1.5580 Axial B 1.2350 1.2350 Axial C 1.2660 1.2650 Trans D -0.5860 -0.5860 GALILS Commanded: 1599599. 1565236. 1586351. -10400. -9750. Actual: 1599600. 1565250. 1586350. -10400. -9750. SETMIR VALUES SecDesOrient: 1257.00 -3.40 -10.00 0.00 133.82 SecOrient: 1256.99 -3.41 -10.00 -0.24 133.70 ---=== PROBLEMS IN DETAIL ===---