From: =?UTF-8?B?Sm9zw6kgU8OhbmNoZXotR2FsbGVnbw==?= Date: Sun, 11 Jun 2017 15:00:14 -0400 Subject: Re: [sloan-25mlog 3554] Re: 2.5m obslog 20170610 (SJD 57915) --001a1144c0a20b2d980551b3d0a5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Elena, There have been some changes to the hartmann in gotoField, but only to the argument with which hartmannActor is called. In particular, we are now always calling hartmann collimate ignoreResiduals. If your log function is looking for something else you may need to modify it. Brian has pushed a few changes to STUI that are ready to be built. Maybe you=E2=80=99ll want to make sure your log function is working correctly bef= ore doing so. I=E2=80=99m not sure about the problem with the Timer function. Brian has b= een working on something similar so he may know more. Apart from that, I think we are ready to tag the several actors we have been testing the last few days. I=E2=80=99ll do so unless somebody disagree= s. Cheers, Jos=C3=A9 -- Jos=C3=A9 S=C3=A1nchez-Gallego Research Associate Astronomy Department University of Washington On June 11, 2017 at 08:22:50, Elena Malanushenko (elenam@apo.nmsu.edu) wrote: Dmitry, I think, new changes of sop actor affects these scripts. My function listens tron and there is call back on =E2=80=9Chartman=E2=80= =9D command. During gotoField, I do not see this command anymore, so this function do not get such callback. I will contact Jose to find out the changes and try to fix it or to find another solution how to get this information for observers. Regards, Elena > On 06 /11/ 17, at 05:43, dmbiz@apo.nmsu.edu wrote: > > > APACHE POINT OBSERVATORY SDSS 2.5M > > OBSERVING LOG > Saturday June 10, 2017 > > (SJD 57915) > > ---- Observing Team ---- > > > Katie Grabowski > Dmitry Bizyaev > > ---- Observing Plan ---- > > Sat 10 JUN 2017 57915.0 0.99 02:52 11:15 13:08 21:31 Night > APOGEE-2 ( 8.4 h) > Eng test if weather permits: two-three starInFiber exposures with a > MaNGA-plugged plate > > > ---- Observing Summary ---- > > It was a mostly clear night, with rare waves of very thin clouds. Good seeing, a > lot of Moon. > =3D=3D APOGEE lead exposures =3D=3D > 6 9683 060+75 A: 2xAB, M: 2xC 2 missing 5 faint COMPLETED > 9 9859 030+30 A: 6xAB, M: -- 3 missing 2 faint not done > 1 9974 033+00 A: 6xAB, M: 6xC 1 missing 3 faint COMPLETED > 3 9976 034-06 A: 3xAB, M: 3xC 1 missing 3 faint not done > 5 9115 025+06 A: 4xAB, M: 4xC 2 missing 3 faint no done > 2 9307 064+06 A: 2xAB, M: 2xC 5 missing 1 faint not done > =3D=3D We've got MaNGA starInFiber exposures: > Feige 67: a WD spectrophotometric standard with cart 6 > on the clear sky, site seeing ~ 1,2". See log for detail > (2 exposures: 00245828 - 120 sec, 00245829 - 300 sec) > and BD+28 4211 a WD spectrophotometric standard with cart 5 > clear sky, seeing ~ 1.3" > (2 exposures: 00245857 - 120 sec, 00245858 - 300 sec > > =3D=3D Notes: > - about 5 minutes lost t recovery of the Netrurner failure, see below. > - 8 more minutes lost to APOGEE failure (dither and coll), see log. > > - Elenas's script "Log Function" does not report the piston > shift and the blue ring spread anymore (after software works). > - Elena's script "Timer" (for APOGEE-only exposures) doesn't count > time anymore, and displays error "Unsupported operand type(s) for": 'None' > - Elena's script "Log Support" does not update the BOSS spectrograph > collimation information automatically, but is "Start" is clicke, > manually, it shows correct line. > - Nathan, we have a disk alert: > Apogeediskwarn apogeeql.icsDiskAlarm ('Warning', 694) > - ALT axis stopped once, at 10:31, with a python error. See log. No time lost. > - foam wrapping on B2 dewar is snapped from the bottom part and hangs loose. > Please take a look how it might happen. > ____________________________________________________________ Logs of Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html --001a1144c0a20b2d980551b3d0a5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable body{font-family:Helvetica,Arial;font-size:13px}= Hi Elena,There have been some changes to the hartmann in gotoField, b= ut only to the argument with which hartmannActor is called. In particular, = we are now always calling hartmann collimate ignoreResiduals. If your log f= unction is looking for something else you may need to modify it.Brian has pushed a few changes = to STUI that are ready to be built. Maybe you=E2=80=99ll want to make sure = your log function is working correctly before doing so.I=E2=80=99m not sure about the problem w= ith the Timer function. Brian has been working on something similar so he m= ay know more.Apart f= rom that, I think we are ready to tag the several actors we have been testi= ng the last few days. I=E2=80=99ll do so unless somebody disagrees.Cheers,Jos=C3=A9 --Jos=C3=A9 S=C3=A1n= chez-GallegoResearch AssociateAstronomy DepartmentUniversity of Washington On= June 11, 2017 at 08:22:50, Elena Malanushenko (elenam@apo.nmsu.edu) wrote: Dmitry, I think, new c= hanges of sop actor affects these scripts. My function listens tron and= there is call back on =E2=80=9Chartman=E2=80=9D command. During gotoFi= eld, I do not see this command anymore, so this function do not get suc= h callback. I will contact Jose to find out the changesand try to f= ix it or to find another solution how to get this information for obser= vers.Regards, Elena> On 06 /11/ 17, at 05:43, dmbiz@apo.nmsu.edu wrote:> > > APACHE POINT OBSERVATORY SDSS 2.5M> > OBSERVING LOG> = Saturday June 10, 2017> > = (SJD 57915)> > ---- Observing Team ----> > > Katie Grabowski> Dmitry Bizyaev> = > ---- Observing Plan ----> > Sat 10 JUN 2017 57915.0 = 0.99 02:52 11:15 13:08 21:31 Night > APOGEE-2 ( 8.4 h)= > Eng test if weather permits: two-three starInFiber exposures wit= h a> MaNGA-plugged plate> > > ---- Observing Su= mmary ----> > It was a mostly clear night, with rare waves of= very thin clouds. Good seeing, a> lot of Moon. > =3D=3D APOG= EE lead exposures =3D=3D> 6 9683 060+75 A: 2xAB, M: 2xC 2 missing 5 = faint COMPLETED > 9 9859 030+30 A: 6xAB, M: -- 3 missing 2 faint = not done > 1 9974 033+00 A: 6xAB, M: 6xC 1 missing 3 faint COMPLETE= D> 3 9976 034-06 A: 3xAB, M: 3xC 1 missing 3 faint not done>= 5 9115 025+06 A: 4xAB, M: 4xC 2 missing 3 faint no done> 2 9307 06= 4+06 A: 2xAB, M: 2xC 5 missing 1 faint not done> =3D=3D We've g= ot MaNGA starInFiber exposures:> Feige 67: a WD spectrophotometric s= tandard with cart 6 > on the clear sky, site seeing ~ 1,2". See= log for detail> (2 exposures: 00245828 - 120 sec, 00245829 - 300 se= c)> and BD+28 4211 a WD spectrophotometric standard with cart 5&= gt; clear sky, seeing ~ 1.3"> (2 exposures: 00245857 - 120 sec,= 00245858 - 300 sec> > =3D=3D Notes:> - about 5 minute= s lost t recovery of the Netrurner failure, see below.> - 8 more min= utes lost to APOGEE failure (dither and coll), see log.> > - = Elenas's script "Log Function" does not report the piston > shift and the blue ring spread anymore (after software works).&g= t; - Elena's script "Timer" (for APOGEE-only exposures) doesn= 't count> time anymore, and displays error "Unsupported op= erand type(s) for": 'None' > - Elena's script "= ;Log Support" does not update the BOSS spectrograph> collimati= on information automatically, but is "Start" is clicke, > = manually, it shows correct line. > - Nathan, we have a disk alert:= > Apogeediskwarn apogeeql.icsDiskAlarm ('Warning', 694)> - ALT axis stopped once, at 10:31, with a python error. See log. No t= ime lost.> - foam wrapping on B2 dewar is snapped from the bottom pa= rt and hangs loose. > Please take a look how it might happen. &= gt; ____________________________________________________________Logs of Nightly APO Activities https://trac.sdss.org/tracmai= lman/browser/private/sloan-25mlog/index.html --001a1144c0a20b2d980551b3d0a5--