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

Civil Date
Ephemerides
2015-10-31SunsetSunriseMoon
Set12°18°18°12°RiseRiseSet
00:1201:0201:3011:4912:1713:0704:13-
Night Length10:19Sunset Temperature


On-Duty Personnel
Resident AstronomerTelescope OperatorOPS EngineerDay Ops
Matthew ShetroneJusten Pautzke--


Overlapsnone

Other Personnelnone

Guestsnone


Open/Close Log
Open timeOutdoor tempTruss tempClose timeReasonTime open
00:129.414.010:5510:43
Total Time Open10:43


      
ProgramNight PriorityEngineering
01:30Engineering (commission cwfs)
Stack Data
StartStopee50ee80Hefi FocusMars FocusOutside TempDome TempTruss TempWind DirectionWind SpeedStack Type
01:0801:550.510.78985-45908.99.09.53358First of Night
03:5704:248.68.78.831711Stack/Re-stack
08:1108:337.87.88.128920Stack/Re-stack


Problem Reports
PR NumberTimesTime LostDescriptionResponse
420700:47-00:5000:03Pas server went down while changing the exposure times on the PV Camera. Restarted all servers and the tcs_gui. The PV camera is also taking a really long time (~1 min on a 9 second exposure) to update frames. It is having this problem regardless of store image setting.
420808:07-08:1100:04While trying to stack scs gui shows moving for several minutes the only segment highlighted is 45. Would not complete so I tried to shutdown scs gui and sams server and restart them to see if it would fix it.
413503:07-03:3000:23HFC fault while slewing to GOES 14. Most likely a velocity error. Reset fault and attempted the trajectory again. This did not change slew and achieve the trajectory, when I hit the abort button I got another HFC fault. Killed all servers, shut down tcs gui started everything back up and moved the tracker to the right preset position. Then I resent the trajectory which worked.
420902:34-02:37, 03:48-03:48, 07:15-07:1500:03Clear fiducial and set fiducial not responding to commands. Had to shut down and restart tcs gui and servers.
413506:09-06:1500:06HFC fault while adjusting focus down by 0.4 mm (velocity error). Tried to reacquire but it did not go into track mode. No error reported. Abort, center tracker, and reacquired the trajectory.
421009:46-09:4600:00Started to get the dome move error every time I moved the dome (did not matter on how large the move). The dome still successfully reached the target position however, so this was more of a an annoyance. This error also happened again when trying to close the dome. See error below: { "__exception_type": 0, "__exception_string": "(dome) 'MOVETO 180.000000' failed", "__exception_file": "unknown", "__exception_line": 0, "__exception_func": "unknown", "__effective_id": 40, "__original_id": 8, "__origin": "tcsGuiLegacyAsyncCommandSender.jove.32341.017003459->tcp://192.168.66.31:30800", "__handler": "dome_MoveDomeTo", "__async": "true", "__done": "true", "__ack": "false", "__error": "true", "__data_time": "1446371171.713436474", "__wire_time": "1446371171.713438726", "__data": "false", "__pid": 18059 }


Ops Commentsnone


TO Commentsnone


RA CommentsTonight we took 3 sets of DWFS8 - CWFS data. We also took some data with the DWFS8 to show the theta-phi problem as a function of X tracker position. It really only shows up near the end of the trajectory at X > 1000, but it does seem to exist.


Observations
FileTarget/QIDExp StartExposureOverheadProgramInstrument ConfigurationData TypeIQDimmSkySBrtSkytransSNRCommentsCharge