From: Kaike Pan Subject: Re: [sloan-25mlog 5392] 2.5m obslog 20210215 (SJD 59261) Date: Tue, 16 Feb 2021 08:26:36 -0700 --Apple-Mail=_7CBFD997-0A51-4783-8A1B-F712E9974D03 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Thanks Dan and Christian, This is very informative and helpful. I am adding Jeff into the = conversation for his inputs (Thanks Jeff). To summarize the test:=20 1. If the telescope is in the halt status (tcc does not owns the = semaphore) and MCP takes semaphore normally, the fellowing MCP/TPM GUI = slew or goto5 script slew, which is a MCP slew, could result in an = overshoot, but at a very rare rate. This is what we observed in the = past. 2. If MCP steals semaphore while the telescope is in the tracking = status, a fellowing MCP slew will consistently overshoot or undershoot. = The overshoot or undershoot amount is the difference between the = starting and ending positions. Specifically, MCP will slew the distance = between the starting position of the previous slew and the end position = of the current slew, while it should move the distance between the = ending position of the previous and the ending position of the current = slew.=20 Thanks a lot, -Kaike > On Feb 16, 2021, at 5:06 AM, Christian Carter = wrote: >=20 > Hi everyone, >=20 > As Dan has described in the log, we made progress tonight in = reproducing the slew overshoots when going to 5 degrees. We worked all = night to compartmentalize and characterize the issue and are learning a = lot but still have tests we plan to run tomorrow night (assuming we'll = be weathered out again). >=20 > Here are some visuals that can hopefully help explain the behavior we = are seeing. This behavior is very consistent and repeatable. We plan to = investigate this more as we have time and hopefully can send more = comprehensive/cohesive explanations of what we're seeing after a bit = more troubleshooting. >=20 > Christian >=20 >=20 >=20 > On 2/16/2021 5:03 AM, doravetz@apo.nmsu.edu = wrote: >> APACHE POINT OBSERVATORY SDSS 2.5M >>=20 >> OBSERVING LOG >> Monday February 15, 2021 >>=20 >> (SJD 59261) >>=20 >> ---- Observing Team ---- >>=20 >> Christian Carter >> Dan Oravetz >>=20 >> ---- Observing Plan ---- >>=20 >> Mon 15 FEB 2021 59261.0 BHM (10.6 h) >>=20 >> ---- Observing Summary ---- >>=20 >> We didn't open due to weather. BHM lost 10.6 hr to weather. >>=20 >> Notes >> =3D=3D=3D=3D=3D >> (1) /data disk space is 94% full >>=20 >> (2) We performed more test slews attempting to reproduce the = overshoot >> misbehavior. We discovered that we could reproduce overshoots and = undershoots >> consistently, and by a predictable amount, when we commanded the = telescope to >> move via MCP when the axes were still tracking. It's not necessarily = news that >> the leftover frames during tracking causes overshoots, but it's new = info that we >> could figure out by how much an overshoot (or undershoot) would occur = based on >> the preceding slew destination. Additional notes in log. >>=20 >> ---- Observing Log ---- >>=20 >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D >> AFTERNOON CHECKOUT >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D >>=20 >> No problems to report during afternoon checkout. Ventilation and = opening delayed >> due to bad weather. >>=20 >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D >> NIGHT >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D >>=20 >> We performed more slews trying to reproduce the overshoot problems. >>=20 >> The first test slew ended in an overshoot. Telescope was at = 121,30,00. The >> semaphore was still owned by the MCP when we got to the telescope = laptop after >> following the afternoon moves by the day crew. >>=20 >> 02:44Z - Grabbed the semaphore with TCC. Slewed to instChange first. = E-stop and >> pin were cycled just like during an instrument change. Then slewed to = 121,30,00 >> using the 'stow' button. Issued a 'SEM TAKE' and then clicked 'Move' = to 5 and >> the telescope failed to decelerate near 5 and was going to overshoot, = so we >> stopped it. End time for this was about 02:47Z. We were unable to = reproduce an >> overshoot using this sequence. >>=20 >> We tried experimenting with the use of the E-stop, the cycling of the = pin, the >> order in which the E-stop and pin were moved, etc., trying to = systematically >> rule things out one layer at a time. After many attempts, we could = not tickle an >> overshoot problem again, though. >>=20 >> We tried to be more "rough" with reproducing an overshoot by issuing = the MCP >> move command when the telescope axes were tracking. We determined = that it didn't >> matter whether a move was issued from the Goto5 script or from the = MCP GUI via >> the 'Move' button, overshoots could be triggered both ways. >>=20 >> The recipe to produce an overshoot was to command a slew with a 'tcc = track' to >> ALT=3Dposition_1 and when that slew completes, then 'axis stop'. Then = issue 'axis >> init'. Slew to some *other position* for ALT=3Dposition_2 and leave = axes >> "Tracking". Issue a 'SEM STEAL' and then move ALT=3Dposition_3 using = the 'Move' >> button in GUI. >>=20 >> What seems to happen is that the MCP calculates the relative move = from >> position_1 *INSTEAD OF* position_2 and overshoots/undershoots the = destination >> position_3 by the difference between position_1 - position_2. An = example helps a >> lot: >>=20 >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,31 mount /rota=3D0 /rotty=3Dmount #position_1 >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount #position_2 >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 5 #position_3 >> Slew ends at ALT=3D4 >>=20 >> We verified that there's nothing special about 5 degrees being = overshot. We were >> able to overshoot and undershoot several different destination = altitudes. Also, >> there's nothing special about starting from 121,30,00. We produced = overshoots of >> 5 degrees at ALT=3D45, for instance. >>=20 >> We still need to understand how to tickle the bug when the axes are = not in a >> Tracking state, but these tests do help us to understand the = overshoots a little >> bit more predictably. >>=20 >> Here are some additional specific notes from some of our tests: >>=20 >> (1) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,31 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> E-stop in >> E-stop out >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> Goto5 Script >> Slew ends at ALT=3D4 >>=20 >> (2) >> at 121,30,00 to begin with >> tcc track 121,31 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> Goto5 Script >> Slew ends with ALT=3D4 >>=20 >> (3) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,31 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> E-stop in >> E-stop out >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 5 >> Slew ends at ALT=3D4 >>=20 >> (4) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,31 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 5 >> Slew ends at ALT=3D4 >>=20 >> At this point we've determined that the behavior in all four tests = above is >> identical - ALT ended at 4 degrees even though commanded to 5 via = Goto5 script >> and the MCP GUI. >>=20 >> (5) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,29 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 5 >> Slew ends at ALT=3D5 >>=20 >> (6) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,31 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 5 >> Slew ends at ALT=3D4 >>=20 >> (7) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,29 mount /rota=3D0 /rotty=3Dmount >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 55 >> Slew ends at ALT=3D55 >>=20 >> We think we didn't issue a 'stop' OR 'init' and that's why the slew = got to 55. >>=20 >> (8) >> at 121,55,00 to begin with >> tcc axis init >> tcc track 121,56 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,55 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 5 >> Slew ends at ALT=3D4 >>=20 >> (9) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,30.5 mount /rota=3D0 /rotty=3Dmount >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 5 >> Slew ends at ALT=3D5 >>=20 >> (10) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,30.5 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 5 >> Slew ends at ALT=3D4.5 >>=20 >> In (10) compared to (9), the only difference was using the 'stop' and = 'init' in >> between the 'track' commands. >>=20 >> (11) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,31 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 10 >> Slew ends at ALT=3D9 >>=20 >> So, 5 degrees isn't a special destination; we overshot 10 by 1 = degree. >>=20 >> (12) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,31 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 20 >> Slew ends at ALT=3D19 >>=20 >> (13) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,31 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 55 >> Slew ends at ALT=3D54 >>=20 >> This was an UNDERSHOOT. >>=20 >> (14) >> at 121,30,00 to begin with >> tcc axis init >> tcc track 121,29 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,30 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 55 >> Slew ends at ALT=3D56 >>=20 >> A slew completes, then 'axis stop'. 'Axis init'. Slew to some other = position, >> leave axes "Tracking". Issue a 'SEM STEAL' and then 'Move' button in = GUI. >>=20 >> (15) >> at 121,56,00 to begin with >> tcc axis init >> tcc track 121,50 mount /rota=3D0 /rotty=3Dmount >> tcc axis stop >> tcc axis init >> tcc track 121,55 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 40 >> Slew ends at ALT=3D45, a 5-deg UNDERSHOOT. >>=20 >> (16) >> at 121,45,00 to begin with >> tcc axis init >> tcc track 121,50 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> tcc track 121,55 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 40 >> Slew ends at ALT=3D50, a 10-deg UNDERSHOOT. It remembered the 45-deg = position and >> only thought it had to move -5 deg to get to 45. >>=20 >> (17) >> at 121,50,00 to begin with >> tcc axis init >> tcc track 121,44 mount /rota=3D0 /rotty=3Dmount >> 'tcc axis stop' >> tcc axis init' >> tcc track 121,46 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> tcc track 121,41 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> tcc track 121,49 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 70 >> Slew ends at ALT=3D70 >>=20 >> (18) >> at 121,70,00 to begin with >> tcc axis init >> tcc track 121,51 mount /rota=3D0 /rotty=3Dmount >> 'tcc axis stop' >> tcc axis init' >> tcc track 121,52 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> tcc track 121,53 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> tcc track 121,54 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 60 >> Slew ends at ALT=3D63 >>=20 >> (19) >> at 121,63,00 to begin with >> tcc axis init >> tcc track 121,51 mount /rota=3D0 /rotty=3Dmount >> 'tcc axis stop' >> tcc axis init' >> tcc track 121,52 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> tcc track 121,54 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> tcc track 121,53 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 60 >> Slew ends at ALT=3D62 >>=20 >> (20) >> at 121,62,00 to begin with >> tcc axis init >> tcc track 121,51 mount /rota=3D0 /rotty=3Dmount >> 'tcc axis stop' >> tcc axis init' >> tcc track 121,52 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> tcc track 121,54 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> tcc track 121,53 mount /rota=3D0 /rotty=3Dmount >> "Tracking" >> SEM STEAL >> GUI =3D=3D> 'Move' button to 40 >> Slew ends at ALT=3D42 >>=20 >> (21) >> at 121,42,00 to begin with >> tcc axis init >> tcc track 121,40 mount /rota=3D0 /rotty=3Dmount >> 'tcc axis stop' >> tcc axis init' >> tcc track 121,39 mount /rota=3D0 /rotty=3Dmount >> 'tcc axis stop' >> SEM TAKE >> GUI =3D=3D> 'Move' button to 30 >> Slew ends at ALT=3D30 >>=20 >> 11:44Z - Called it a night. Started morning cals. >>=20 >> ---- BOSS Spectrograph Collimation Summary ---- >>=20 >> Afternoon focus check: >>=20 >> Time Cart TSP1 R1 B1 Move1 B1Resid >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >> 23:28 2-15002A 2.0 -2308 2.8 -1603 -2.2 >> 23:32 2-15002A 2.0 -659 -3.2 184 -2.6 >>=20 >> 23:29:01 boss exposure 4.0, file=3D325416 >> 23:30:13 boss exposure 4.0, file=3D325417 >> 23:31:32 sp1.motor.move=3D 184, 183, 184 >> 23:31:32 Hartmann collimate output on cart #2 >> sp1: offset: r=3D -659 (In Focus); b=3D -3.2 (In Focus) >> sp1: pred. move: spAverageMove=3D 184 >> sp1: pred. resid: r=3D -843, b=3D -2.6, txt=3D OK, spTemp =3D 2.0 >>=20 >> 23:31:29 OBSERVER.doravetz.sop 225 hartmann i r1MeanOffset=3D-0.10,"In = Focus" >> 23:31:29 OBSERVER.doravetz.sop 225 hartmann i b1MeanOffset=3D0.16,"In = Focus" >>=20 >> ---- Mirror Numbers ---- >>=20 >> PRIMARY: >> -------- >> Scale: 1.000000 >>=20 >> MIGS TONIGHT NOMINAL >> Axial A: -4.9250 -4.9280 >> Axial B: -4.6680 -4.6660 >> Axial C: -5.7720 -5.7770 >> Trans D: -4.3720 -4.3890 >> Lateral E: 0.3750 0.3750 >> Lateral F: 0.5720 0.5675 >>=20 >> GALILS >> Commanded: 5850 -4500 14850 28200 25200 24900 >> Actual: 5850 -4500 14850 28200 25200 24900 >>=20 >> SETMIR VALUES >> PrimDesOrient: 0.0 69.89 100.0 375.3 622.11 >> PrimOrient: 0.04 69.89 100.0 375.3 622.11 >>=20 >> SECONDARY: >> ---------- >> Focus: 0.0000 >> Air temp: 1.00 >> Altitude: 30.000015622922977 >>=20 >> MIGS TONIGHT NOMINAL >> Axial A: -9.4430 -9.4420 >> Axial B: -9.4090 -9.4070 >> Axial C: -9.4980 -9.4960 >> Trans D: 0.0430 0.0420 >>=20 >> GALILS >> Commanded: 4620350 4603650 4674250 -2000 -6600 >> Actual: 4605360 4587193 4633713 -2000 -6600 >>=20 >> SETMIR VALUES >> SecDesOrient: 3657.0 -14.01 -2.9 12.5 114.22 >> SecOrient: 3658.15 -14.02 -2.88 12.71 114.22 >>=20 >> ---- Telescope Status ---- >>=20 >> Status at 11:11Z: >>=20 >> Telescope stowed at: 121.0, 30.0, 0.0 mount >> Instrument mounted: cartridge =3D 2 >> Counterweights at: 447 >> LN2 autofill systems: Connected and turned on >> 180L LN2 dewar scales: SP1 196 lbs, 21.2 psi >>=20 >> Recirculation fan is OFF because it's windy and more snow is forecast = today. >>=20 >> ---- Software Used ---- >>=20 >> --- Afternoon disk space --- >> /dev/vdd 688G 611G 77G 89% /home >> /dev/vdc1 11T 11T 700G 94% /data >>=20 >> Get Versions, 02/15/21, 23:25:56 >> --- STUI software --- >> STUI : 1.7.12 >> alerts : 2.0.1 >> apo : v1_11 >> boss : 5.0.1 >> -boss.specMec : 3.0.4 >> gcamera : v2_2 >> guider : 3.9.4 >> hartmann : 1.8.0 >> hub : v4.2.4 >> mcp : 1.12-12-g222b >> -mcp.plc : 34 >> -mcp.azFiduci : v1_144 >> -mcp.altFiduc : v1_144 >> -mcp.rotFiduc : v1_144 >> platedb : 2.8.0 >> sop : 4.0.8 >> tcc : 1.4.0 >> apogee : not availble >> apogeecal : not availble >> apogeeql : v1_7_0dev >> STUIAdditions : 3.1.4 >>=20 >> --- Other versions --- >> idlspec2d : v5_7_12 >> plate-mapper3 : NOCVS:v7_0_9 >> petunia : 2.2.2 >> autoscheduler : 1.5.4 >> sdss_python_module: trunk >> mangadrp : trunk exported >>=20 >> ---- APOGEE Data Summary ---- >>=20 >> [observer@sdss4-hub ~]$ list_ap -m 59260 -morning >> APOGEE data list, mjd=3D59260, morning >> raw_data: /data/apogee/utr_cdr/59260/apRaw-*.fits >> archive: /data/apogee/archive/59260/apR-[a,b,c]-*.apz >> quickred: /data/apogee/quickred/59260/ap2D-a-*.fits.fz >> = --------------------------------------------------------------------------= ------ >> mjd i UT File/Exp Imtype Nread A/B Dth Ct-Plate Arch Offset = %Flux Comm >> = --------------------------------------------------------------------------= ------ >> 59260 1 08:18 36980009 Dark 60 A 13.0 2-15002 a-b-c - = - >> 59260 2 08:28 36980010 Dark 60 A 13.0 2-15002 a-b-c - = - >> 59260 3 08:39 36980011 Dark 60 A 13.0 2-15002 a-b-c - = - >> 59260 4 08:50 36980012 QuarFlat 10 A 13.0 2-15002 a-b-c - = 46 >> 59260 5 08:52 36980013 QuarFlat 10 A 13.0 2-15002 a-b-c - = 46 >> 59260 6 08:53 36980014 QuarFlat 10 A 13.0 2-15002 a-b-c - = 46 >> 59260 7 08:55 36980015 Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.50 - >> 59260 8 08:57 36980016 Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.50 - >> 59260 9 09:00 36980017 Arc-Une 40 A 13.0 2-15002 a-b-c - = - >> 59260 10 09:07 36980018 Arc-Une 40 A 13.0 2-15002 a-b-c - = - >> 59260 11 09:14 36980019 Dark 30 A 13.0 2-15002 a-b-c - = - >> 59260 12 09:19 36980020 InteFlat 30 A 13.0 2-15002 a-b-c - = 0 >> 59260 13 09:25 36980021 InteFlat 30 A 13.0 2-15002 a-b-c - = 0 >> 59260 14 09:30 36980022 InteFlat 30 A 13.0 2-15002 a-b-c - = 0 >> 59260 15 09:35 36980023 Dark 30 A 13.0 2-15002 a-b-c - = - >> = --------------------------------------------------------------------------= ------ >> APOGEE data list, mjd=3D59261, all >> raw_data: /data/apogee/utr_cdr/59261/apRaw-*.fits >> archive: /data/apogee/archive/59261/apR-[a,b,c]-*.apz >> quickred: /data/apogee/quickred/59261/ap2D-a-*.fits.fz >> = --------------------------------------------------------------------------= ------ >> mjd i UT File/Exp Imtype Nread A/B Dth Ct-Plate Arch Offset = %Flux Comm >> = --------------------------------------------------------------------------= ------ >> 59261 1 21:58 36990001 Dark 3 A 13.0 2-15002 a-b-c - = - >> 59261 2 22:31 36990002 Dark 60 A 13.0 2-15002 a-b-c - = - >> 59261 3 22:42 36990003 QuarFlat 10 A 13.0 2-15002 a-b-c - = 47 >> 59261 4 22:44 36990004 Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.51 - >> 59261 5 22:46 36990005 Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.51 - >> 59261 6 22:48 36990006 Arc-Une 40 A 13.0 2-15002 a-b-c - = - >> 59261 7 22:55 36990007 Arc-Une 40 A 13.0 2-15002 a-b-c - = - >> 59261 8 23:03 36990008 Dark 60 A 13.0 2-15002 a-b-c - = - >> 59261 9 23:21 36990009 Dark 60 A 13.0 2-15002 a-b-c - = - >> 59261 10 23:32 36990010 QuarFlat 10 A 13.0 2-15002 a-b-c - = 47 >> 59261 11 23:34 36990011 Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.51 - >> 59261 12 23:36 36990012 Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.51 - >> 59261 13 23:38 36990013 Arc-Une 40 A 13.0 2-15002 a-b-c - = - >> 59261 14 23:45 36990014 Arc-Une 40 A 13.0 2-15002 a-b-c - = - >> 59261 15 23:52 36990015 Dark 60 A 13.0 2-15002 a-b-c - = - >> cannot read file : /data/apogee/utr_cdr/59261/apRaw-36990016.fits >> = --------------------------------------------------------------------------= ------ >>=20 > ___________________________________________________________= _ > Logs of Nightly APO Activities > > = https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html = --Apple-Mail=_7CBFD997-0A51-4783-8A1B-F712E9974D03 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Thanks Dan and Christian,This is very informative and helpful. = I am adding Jeff into the conversation for his inputs (Thanks = Jeff).To = summarize the test: 1. If the telescope is in the halt status (tcc does not owns = the semaphore) and MCP takes semaphore normally, the fellowing MCP/TPM = GUI slew or goto5 script slew, which is a MCP slew, could result in an = overshoot, but at a very rare rate. This is what we observed in the = past.2. If = MCP steals semaphore while the telescope is in the tracking status, a = fellowing MCP slew will consistently overshoot or undershoot. The = overshoot or undershoot amount is the difference between the starting = and ending positions. Specifically, MCP will slew the distance between = the starting position of the previous slew and the end position of the = current slew, while it should move the distance between the ending = position of the previous and the ending position of the current = slew. Thanks a lot,-KaikeOn Feb = 16, 2021, at 5:06 AM, Christian Carter wrote:Hi everyone,As Dan has described in the log, we made progress tonight in = reproducing the slew overshoots when going to 5 degrees. We worked all = night to compartmentalize and characterize the issue and are learning a = lot but still have tests we plan to run tomorrow night (assuming we'll = be weathered out again).Here are some visuals that can hopefully help explain the = behavior we are seeing. This behavior is very consistent and repeatable. = We plan to investigate this more as we have time and hopefully can send = more comprehensive/cohesive explanations of what we're seeing after a = bit more troubleshooting.ChristianOn 2/16/2021 5:03 AM, doravetz@apo.nmsu.edu wrote: &nb= sp;  = ;APACHE POINT OBSERVATORY SDSS 2.5M &nb= sp;  = ; OBSERVING = LOG &nb= sp;  = ; Monday February 15, 2021 &nb= sp;  = ; (SJD = 59261)---- Observing Team ----Christian CarterDan Oravetz---- Observing Plan ----Mon 15 FEB 2021 59261.0 BHM (10.6 = h)---- Observing Summary ----We didn't open due to weather. BHM lost 10.6 = hr to weather.Notes=3D=3D=3D=3D= =3D(1) /data disk space is 94% full(2) We performed more test slews attempting to reproduce the = overshootmisbehavior. We discovered that we could = reproduce overshoots and undershootsconsistently, and by = a predictable amount, when we commanded the telescope tomove via MCP when the axes were still tracking. It's not = necessarily news thatthe leftover frames during tracking = causes overshoots, but it's new info that wecould figure = out by how much an overshoot (or undershoot) would occur based onthe preceding slew destination. Additional notes in log.---- Observing Log ----=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D &nb= sp;  = ; AFTERNOON CHECKOUT=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3DNo problems to report = during afternoon checkout. Ventilation and opening delayeddue to bad weather.=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D &nb= sp;  = ; &= nbsp;NIGHT=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3DWe performed more slews = trying to reproduce the overshoot problems.The first test slew ended in an overshoot. Telescope was at = 121,30,00. Thesemaphore was still owned by the MCP when = we got to the telescope laptop afterfollowing the = afternoon moves by the day crew.02:44Z - = Grabbed the semaphore with TCC. Slewed to instChange first. E-stop = andpin were cycled just like during an instrument change. = Then slewed to 121,30,00using the 'stow' button. Issued a = 'SEM TAKE' and then clicked 'Move' to 5 andthe telescope = failed to decelerate near 5 and was going to overshoot, so westopped it. End time for this was about 02:47Z. We were = unable to reproduce anovershoot using this sequence.We tried experimenting with the use of the = E-stop, the cycling of the pin, theorder in which the = E-stop and pin were moved, etc., trying to systematicallyrule things out one layer at a time. After many attempts, we = could not tickle anovershoot problem again, though.We tried to be more "rough" with reproducing = an overshoot by issuing the MCPmove command when the = telescope axes were tracking. We determined that it didn'tmatter whether a move was issued from the Goto5 script or = from the MCP GUI viathe 'Move' button, overshoots could = be triggered both ways.The recipe to = produce an overshoot was to command a slew with a 'tcc track' toALT=3Dposition_1 and when that slew completes, then 'axis = stop'. Then issue 'axisinit'. Slew to some *other = position* for ALT=3Dposition_2 and leave axes"Tracking". = Issue a 'SEM STEAL' and then move ALT=3Dposition_3 using the 'Move'button in GUI.What seems to = happen is that the MCP calculates the relative move fromposition_1 *INSTEAD OF* position_2 and overshoots/undershoots = the destinationposition_3 by the difference between = position_1 - position_2. An example helps alot:at 121,30,00 to begin withtcc = axis inittcc track 121,31 mount /rota=3D0 /rotty=3Dmount = #position_1tcc axis stoptcc axis = inittcc track 121,30 mount /rota=3D0 /rotty=3Dmount = #position_2"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 5 #position_3Slew ends at ALT=3D4We verified = that there's nothing special about 5 degrees being overshot. We wereable to overshoot and undershoot several different = destination altitudes. Also,there's nothing special about = starting from 121,30,00. We produced overshoots of5 = degrees at ALT=3D45, for instance.We still = need to understand how to tickle the bug when the axes are not in aTracking state, but these tests do help us to understand the = overshoots a littlebit more predictably.Here are some additional specific notes from some of our = tests:(1)at 121,30,00 to = begin withtcc axis inittcc track 121,31 = mount /rota=3D0 /rotty=3Dmounttcc axis stopE-stop inE-stop outtcc axis = inittcc track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"Goto5 ScriptSlew ends = at ALT=3D4(2)at 121,30,00 = to begin withtcc track 121,31 mount /rota=3D0 = /rotty=3Dmounttcc axis stoptcc axis = inittcc track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"Goto5 ScriptSlew ends = with ALT=3D4(3)at 121,30,00 = to begin withtcc axis inittcc track 121,31 = mount /rota=3D0 /rotty=3Dmounttcc axis stopE-stop inE-stop outtcc axis = inittcc track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D>= 'Move' button to 5Slew ends at ALT=3D4(4)at 121,30,00 to begin withtcc = axis inittcc track 121,31 mount /rota=3D0 /rotty=3Dmounttcc axis stoptcc axis inittcc = track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 5Slew ends at ALT=3D4At this = point we've determined that the behavior in all four tests above isidentical - ALT ended at 4 degrees even though commanded to 5 = via Goto5 scriptand the MCP GUI.(5)at 121,30,00 to begin withtcc = axis inittcc track 121,29 mount /rota=3D0 /rotty=3Dmounttcc axis stoptcc axis inittcc = track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 5Slew ends at ALT=3D5(6)at 121,30,00 to begin withtcc axis inittcc track 121,31 mount /rota=3D0 /rotty=3Dmounttcc axis stoptcc axis inittcc = track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 5Slew ends at ALT=3D4(7)at 121,30,00 to begin withtcc axis inittcc track 121,29 mount /rota=3D0 /rotty=3Dmounttcc track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D>= 'Move' button to 55Slew ends at ALT=3D55We think we didn't issue a 'stop' OR 'init' and that's why = the slew got to 55.(8)at = 121,55,00 to begin withtcc axis inittcc = track 121,56 mount /rota=3D0 /rotty=3Dmounttcc axis = stoptcc axis inittcc track 121,55 mount = /rota=3D0 /rotty=3Dmount"Tracking"SEM = STEALGUI =3D=3D> 'Move' button to 5Slew = ends at ALT=3D4(9)at = 121,30,00 to begin withtcc axis inittcc = track 121,30.5 mount /rota=3D0 /rotty=3Dmounttcc track = 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 5Slew ends at ALT=3D5(10)at 121,30,00 to begin withtcc axis inittcc track 121,30.5 mount /rota=3D0 /rotty=3Dmounttcc axis stoptcc axis inittcc = track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 5Slew ends at ALT=3D4.5In (10) = compared to (9), the only difference was using the 'stop' and 'init' = inbetween the 'track' commands.(11)at 121,30,00 to begin withtcc= axis inittcc track 121,31 mount /rota=3D0 = /rotty=3Dmounttcc axis stoptcc axis = inittcc track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D>= 'Move' button to 10Slew ends at ALT=3D9So, 5 degrees isn't a special destination; we overshot 10 by = 1 degree.(12)at 121,30,00 = to begin withtcc axis inittcc track 121,31 = mount /rota=3D0 /rotty=3Dmounttcc axis stoptcc axis inittcc track 121,30 mount /rota=3D0 = /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 20Slew ends at = ALT=3D19(13)at 121,30,00 to = begin withtcc axis inittcc track 121,31 = mount /rota=3D0 /rotty=3Dmounttcc axis stoptcc axis inittcc track 121,30 mount /rota=3D0 = /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 55Slew ends at = ALT=3D54This was an UNDERSHOOT.(14)at 121,30,00 to begin = withtcc axis inittcc track 121,29 mount = /rota=3D0 /rotty=3Dmounttcc axis stoptcc = axis inittcc track 121,30 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D>= ; 'Move' button to 55Slew ends at ALT=3D56A slew completes, then 'axis stop'. 'Axis = init'. Slew to some other position,leave axes "Tracking". = Issue a 'SEM STEAL' and then 'Move' button in GUI.(15)at 121,56,00 to begin withtcc= axis inittcc track 121,50 mount /rota=3D0 = /rotty=3Dmounttcc axis stoptcc axis = inittcc track 121,55 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D>= 'Move' button to 40Slew ends at ALT=3D45, a 5-deg = UNDERSHOOT.(16)at 121,45,00 = to begin withtcc axis inittcc track 121,50 = mount /rota=3D0 /rotty=3Dmount"Tracking"tcc = track 121,55 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 40Slew ends at ALT=3D50, a 10-deg UNDERSHOOT. It remembered the = 45-deg position andonly thought it had to move -5 deg to = get to 45.(17)at 121,50,00 = to begin withtcc axis inittcc track 121,44 = mount /rota=3D0 /rotty=3Dmount'tcc axis stop'tcc axis init'tcc track 121,46 mount /rota=3D0 = /rotty=3Dmount"Tracking"tcc track 121,41 = mount /rota=3D0 /rotty=3Dmount"Tracking"tcc = track 121,49 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 70Slew ends at ALT=3D70(18)at 121,70,00 to begin withtcc axis inittcc track 121,51 mount /rota=3D0 /rotty=3Dmount'tcc axis stop'tcc axis init'tcc = track 121,52 mount /rota=3D0 /rotty=3Dmount"Tracking"tcc track 121,53 mount /rota=3D0 /rotty=3Dmount"Tracking"tcc track 121,54 mount /rota=3D0 = /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 60Slew ends at = ALT=3D63(19)at 121,63,00 to = begin withtcc axis inittcc track 121,51 = mount /rota=3D0 /rotty=3Dmount'tcc axis stop'tcc axis init'tcc track 121,52 mount /rota=3D0 = /rotty=3Dmount"Tracking"tcc track 121,54 = mount /rota=3D0 /rotty=3Dmount"Tracking"tcc = track 121,53 mount /rota=3D0 /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 60Slew ends at ALT=3D62(20)at 121,62,00 to begin withtcc axis inittcc track 121,51 mount /rota=3D0 /rotty=3Dmount'tcc axis stop'tcc axis init'tcc = track 121,52 mount /rota=3D0 /rotty=3Dmount"Tracking"tcc track 121,54 mount /rota=3D0 /rotty=3Dmount"Tracking"tcc track 121,53 mount /rota=3D0 = /rotty=3Dmount"Tracking"SEM STEALGUI =3D=3D> 'Move' button to 40Slew ends at = ALT=3D42(21)at 121,42,00 to = begin withtcc axis inittcc track 121,40 = mount /rota=3D0 /rotty=3Dmount'tcc axis stop'tcc axis init'tcc track 121,39 mount /rota=3D0 = /rotty=3Dmount'tcc axis stop'SEM TAKEGUI =3D=3D> 'Move' button to 30Slew ends at = ALT=3D3011:44Z - Called it a night. = Started morning cals.---- BOSS = Spectrograph Collimation Summary ----Afternoon focus check:Time = Cart TSP1 R1 = B1 Move1 B1Resid=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D23:28 2-15002A 2.0 -2308 = 2.8 -1603 -2.223:32 = 2-15002A 2.0 -659 -3.2 184 = -2.623:29:01 boss = exposure 4.0, file=3D32541623:30:13 = boss exposure 4.0, file=3D32541723:31:32 sp1.motor.move=3D 184, 183, 18423:31:32 Hartmann collimate output on cart #2 sp1: offset: r=3D -659 (In Focus); b=3D= -3.2 (In Focus) sp1: pred. move: = spAverageMove=3D 184 sp1: pred. resid: = r=3D -843, b=3D -2.6, txt=3D OK, spTemp =3D 2.023:31:29 OBSERVER.doravetz.sop 225 hartmann i = r1MeanOffset=3D-0.10,"In Focus"23:31:29 = OBSERVER.doravetz.sop 225 hartmann i b1MeanOffset=3D0.16,"In Focus"---- Mirror Numbers ----PRIMARY:--------Scale: = 1.000000MIGS TONIGHT = NOMINALAxial A: -4.9250 = -4.9280Axial B: -4.6680 = -4.6660Axial C: -5.7720 = -5.7770Trans D: -4.3720 = -4.3890Lateral E: 0.3750 0.3750Lateral = F: = 0.5720 0.5675GALILSCommanded: 5850 -4500 14850 28200 = 25200 24900Actual: 5850 -4500 = 14850 28200 25200 24900SETMIR VALUESPrimDesOrient: 0.0 69.89 100.0 375.3 622.11PrimOrient: 0.04 69.89 100.0 375.3 = 622.11SECONDARY:----------Focus: 0.0000Air = temp: 1.00Altitude: = 30.000015622922977MIGS = TONIGHT NOMINALAxial A: = -9.4430 -9.4420Axial B: = -9.4090 -9.4070Axial C: = -9.4980 -9.4960Trans D: 0.0430 0.0420GALILSCommanded: 4620350 4603650 4674250 -2000 = -6600Actual: 4605360 4587193 4633713 = -2000 -6600SETMIR VALUESSecDesOrient: 3657.0 -14.01 -2.9 12.5 114.22SecOrient: 3658.15 -14.02 -2.88 12.71 = 114.22---- Telescope Status ----Status at 11:11Z:Telescope stowed at: 121.0, 30.0, 0.0 = mountInstrument mounted: = cartridge =3D 2Counterweights at: = 447LN2 autofill systems: = Connected and turned on180L LN2 dewar scales: = SP1 196 lbs, 21.2 psiRecirculation = fan is OFF because it's windy and more snow is forecast today.---- Software Used ---- --- Afternoon disk space ---/dev/vdd= 688G 611G = 77G 89% /home/dev/vdc1 = 11T 11T 700G = 94% /dataGet Versions, 02/15/21, = 23:25:56 --- STUI software ---STUI : = 1.7.12alerts : = 2.0.1apo = : v1_11boss : = 5.0.1-boss.specMec : 3.0.4gcamera = : v2_2guider = : 3.9.4hartmann = : 1.8.0hub = : v4.2.4mcp = : = 1.12-12-g222b-mcp.plc : = 34-mcp.azFiduci : v1_144-mcp.altFiduc : = v1_144-mcp.rotFiduc : v1_144platedb = : 2.8.0sop = : 4.0.8tcc = : 1.4.0apogee : not = availbleapogeecal : not = availbleapogeeql : = v1_7_0devSTUIAdditions : 3.1.4 --- Other versions ---idlspec2d = : v5_7_12plate-mapper3 : NOCVS:v7_0_9petunia = : 2.2.2autoscheduler : 1.5.4sdss_python_module: trunkmangadrp = : trunk = exported---- APOGEE Data Summary ----[observer@sdss4-hub ~]$ list_ap -m 59260 = -morningAPOGEE data list, mjd=3D59260, = morningraw_data: = /data/apogee/utr_cdr/59260/apRaw-*.fitsarchive: = /data/apogee/archive/59260/apR-[a,b,c]-*.apzquickred:= /data/apogee/quickred/59260/ap2D-a-*.fits.fz---------------------------------------------------------------= -----------------mjd i = UT File/Exp Imtype Nread A/B Dth = Ct-Plate Arch Offset %Flux Comm---------------------------------------------------------------= -----------------59260 1 08:18 36980009 = Dark 60 A 13.0 = 2-15002 a-b-c - -59260 2 08:28 36980010 = Dark 60 A 13.0 = 2-15002 a-b-c - -59260 3 08:39 36980011 = Dark 60 A 13.0 = 2-15002 a-b-c - -59260 4 08:50 36980012 QuarFlat 10 = A 13.0 2-15002 a-b-c - = 4659260 5 08:52 36980013 = QuarFlat 10 A 13.0 2-15002 a-b-c = - 4659260 6 = 08:53 36980014 QuarFlat 10 A 13.0 = 2-15002 a-b-c - 4659260 7 08:55 36980015 Arc-Thar 12 = A 13.0 2-15002 a-b-c -1.50 -59260 8 08:57 36980016 Arc-Thar 12 = A 13.0 2-15002 a-b-c -1.50 -59260 9 09:00 36980017 Arc-Une = 40 A 13.0 2-15002 a-b-c = - -59260 10 09:07 = 36980018 Arc-Une 40 A 13.0 = 2-15002 a-b-c - -59260 11 09:14 36980019 Dark = 30 A 13.0 2-15002 a-b-c = - -59260 12 09:19 = 36980020 InteFlat 30 A 13.0 2-15002 = a-b-c - 059260 = 13 09:25 36980021 InteFlat 30 A 13.0 = 2-15002 a-b-c - = 059260 14 09:30 36980022 = InteFlat 30 A 13.0 2-15002 a-b-c = - 059260 15 = 09:35 36980023 Dark 30 A = 13.0 2-15002 a-b-c - = ----------------------------------------------------------------= -----------------APOGEE data list, mjd=3D59261,= allraw_data: = /data/apogee/utr_cdr/59261/apRaw-*.fitsarchive: = /data/apogee/archive/59261/apR-[a,b,c]-*.apzquickred:= /data/apogee/quickred/59261/ap2D-a-*.fits.fz---------------------------------------------------------------= -----------------mjd i = UT File/Exp Imtype Nread A/B Dth = Ct-Plate Arch Offset %Flux Comm---------------------------------------------------------------= -----------------59261 1 21:58 36990001 = Dark 3 A 13.0 = 2-15002 a-b-c - -59261 2 22:31 36990002 = Dark 60 A 13.0 = 2-15002 a-b-c - -59261 3 22:42 36990003 QuarFlat 10 = A 13.0 2-15002 a-b-c - = 4759261 4 22:44 36990004 = Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.51 -59261 5 22:46 36990005 = Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.51 -59261 6 22:48 36990006 = Arc-Une 40 A 13.0 2-15002 = a-b-c - -59261 = 7 22:55 36990007 Arc-Une 40 A = 13.0 2-15002 a-b-c - = -59261 8 23:03 36990008 = Dark 60 A 13.0 = 2-15002 a-b-c - -59261 9 23:21 36990009 = Dark 60 A 13.0 = 2-15002 a-b-c - -59261 10 23:32 36990010 QuarFlat 10 A = 13.0 2-15002 a-b-c - = 4759261 11 23:34 36990011 = Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.51 -59261 12 23:36 36990012 = Arc-Thar 12 A 13.0 2-15002 a-b-c = -1.51 -59261 13 23:38 36990013 = Arc-Une 40 A 13.0 2-15002 = a-b-c - -59261 = 14 23:45 36990014 Arc-Une 40 A 13.0 = 2-15002 a-b-c - -59261 15 23:52 36990015 Dark = 60 A 13.0 2-15002 a-b-c = - - cannot read file : = /data/apogee/utr_cdr/59261/apRaw-36990016.fits---------------------------------------------------------------= -----------------____________________________________________________________Logs of = Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/= index.html= --Apple-Mail=_7CBFD997-0A51-4783-8A1B-F712E9974D03--