Failed to connect to MySQL: Access denied for user ''@'localhost' (using password: NO)

Civil Date
Ephemerides
2016-04-19SunsetSunriseMoon
Set12°18°18°12°RiseRiseSet
01:3002:2202:5210:5711:2812:1923:2611:43
Night Length8:05Sunset Temperature


On-Duty Personnel
Resident AstronomerTelescope OperatorOPS EngineerDay Ops
Sergey RostopchinJusten Pautzke--


Overlapsnone

Other Personnelnone

Guestsnone


Open/Close Log
Open timeOutdoor tempTruss tempClose timeReasonTime open
01:1519.216.211:11engineering09:56
Total Time Open9:56


      
ProgramNight PriorityEngineering
02:52Engineering (lrs2/virus commisioning)
Stack Data
StartStopee50ee80Hefi FocusMars FocusOutside TempDome TempTruss TempWind DirectionWind SpeedStack Type
02:1103:120.410.631088+1143016.817.417.726712First of Night
04:0904:370.430.641078+1201413.514.114.732510Stack/Re-stack


Problem Reports
PR NumberTimesTime LostDescriptionResponse
449300:30-00:3000:00At the beginning of large offset_trajectory moves hex velocity faults sometimes occur. Even when the same large offset is made from the same starting position on the same track, sometimes it succeeds and sometimes it fails. (AW)
447102:02-02:0300:01Getting ready to stack I sent the tracker to the lower right preset. Almost immediately I got a H6 Velocity Fault.Reset the Fault hit abort tracker a couple times and resent the lower right preset. Worked without fault the second time.
449402:10-02:1400:04lrs2 cal script died because lrs2 server crushed
169602:44-02:44, 03:31-03:3100:00Took out 42-2 for LTRSE. 03:31 UT Took out 55-3 for LTRSE.
449504:17-04:1800:01While re-stacking it was noticed that mirror 89 is taking many iterations to move to correct place. Only moves a small amount each move (much smaller than the required move as shown by the vector in SAMS). It did eventually reach the correct position after many moves.
446106:52-06:52, 06:57-06:5700:00uptime:46333 uptime:46666 Oscillations were seen in the x direction again tonight at the above uptimes. The second occurance was after a 11570" offset.
449609:02-09:1400:1220 mins into a trajectory all of a sudden the brakes engaged and both the tracker and TCS indicator lights went off. chksys revealed that both servers were defunct. More details in PR.kill -6 the defunct servers and restarted them. Restarted all other servers as well as the tcs gui. After servers and tcs gui were restarted we successfully sent another trajectory.


Ops Commentsnone


TO CommentsClear and calm all evening. At the end of the night I turned on AHUs but left the chiller off as instructed by Herman.


RA Commentsnone


Observations
FileTarget/QIDExp StartExposureOverheadProgramInstrument ConfigurationData TypeIQDimmSkySBrtSkytransSNRCommentsCharge
lrs20000001_01duskflat01:3215 lrs2calS  Yes
lrs20000001_02duskflat01:3915 lrs2calS  Yes
lrs20000001_03duskflat01:4025 lrs2calS  Yes
lrs20000001_04duskflat01:4240 lrs2calS  Yes
lrs20000002-04lrs cal01:420 lrs2calS ldas server crush. PR 4494No
virus0000001_01duskflat01:4660 viruscalS overexpYes
virus0000001_02duskflat01:4930 viruscalS  Yes
virus0000001_03duskflat01:4960 viruscalS  Yes
virus0000001_04duskflat01:5360 viruscalS  Yes
virus0000001_05duskflat01:5690 viruscalS  Yes
virus0000002-09duskflat01:560 viruscalS vdas server crushNo
lrs20000005-10lrs cal04:330 lrs2calS  Yes
nonefcs13_J16041+510805:47080.0lrs2eng trajectory offset testYes
nonefcs13_J12390+505707:30085.0lrs2eng trajectory offset testYes
nonefcs14_J19092+504808:52045.0lrs2eng tcs crushed. trajectory offset testNo
nonefcs14_J19465+504109:26077.0lrs2eng trajectory offset testYes
lrs20000011_01fcs15_J16461+633310:45120019.0lrs2beng no acam imageYes
lrs20000012-17lrs cal11:170 lrs2calS  Yes