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

Civil Date
Ephemerides
2016-03-02SunsetSunriseMoon
Set12°18°18°12°RiseRiseSet
00:5901:4802:1612:0012:2813:1608:49-
Night Length9:44Sunset Temperature


On-Duty Personnel
Resident AstronomerTelescope OperatorOPS EngineerDay Ops
Matthew ShetroneEusebio Terrazas--


Overlapsnone

Other Personnelnone

Guestsnone


Open/Close Log
Open timeOutdoor tempTruss tempClose timeReasonTime open
00:5719.018.708:15PR07:18
Total Time Open7:18


      
ProgramNight PriorityEngineering
02:16Engineering (probe positioning)
Stack Data
StartStopee50ee80Hefi FocusMars FocusOutside TempDome TempTruss TempWind DirectionWind SpeedStack Type
01:0001:430.430.641090965718.118.618.824217First of Night
↪ Commentsmoved a few mirrors in manually; some dome seeing


Problem Reports
PR NumberTimesTime LostDescriptionResponse
428800:04-00:0800:04Trajectory failed; 1 hour in the future error for start of trajectory after we pass 00 UT. Even though this trajectory still has more than 30 mins of time left on track.
169600:10-00:1000:00removed LTSE sensors from SAMS
420003:09-03:11, 05:23-05:24, 05:04-05:06, 05:11-05:12, 05:30-05:31, 05:42-05:43, 05:43-05:58, 06:42-06:43, 06:53-06:55, 08:12-08:1300:27HFC fault on tracker; no error just the trajectory stopping; cleared fault on panel and dspace;
440203:27-03:29, 05:07-05:08, 05:14-05:16, 05:25-05:26, 06:00-06:01, 06:48-06:49, 06:55-06:56, -00:09TMCS failed to acquire trajectory; this occured each time after an hfc fault had been cleared.cleared error box and resent same target
441907:15-07:2500:10When testing marker offsets on acqcam found that the X and Y axis need to be reversed. offsets being made in opposite direction of desired motion.
442000:20-00:2000:00Ice machine in Fridge not working; Checked water flow and that seemed fine; could be frozen nozzle or ???


Ops Commentsnone


TO CommentsTonight's problems seemed to be in a sequence. We would be guiding and testing probe positions when we would get an HFC fault. Once the fault was cleared then the trajectory was reloaded we would get a Trajectory failure error. Once that error was cleared we would be able to track but then we would receive another HFC fault and so on... very repetitive. At times we tried shutting down and restarting all servers and tcs but no difference noted. Also tried shutting down and restarting DSpace software .. no difference noted as well.


RA CommentsHigh thin clouds, modest wind and increasing dust values Tested probe/trajectory offsetting and found a sign error for both X,Y and RA,DEC. In addition the RA offset seems to have a scale problem. Perhaps cos(DEC) Found some probably wind induced jumping of just GC1. Many Many faults probably related to timing issues.


Observations
FileTarget/QIDExp StartExposureOverheadProgramInstrument ConfigurationData TypeIQDimmSkySBrtSkytransSNRCommentsCharge