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

Civil Date
Ephemerides
2015-12-29SunsetSunriseMoon
Set12°18°18°12°RiseRiseSet
00:0701:0001:3012:2712:5613:4904:25-
Night Length10:57Sunset Temperature


On-Duty Personnel
Resident AstronomerTelescope OperatorOPS EngineerDay Ops
-Amy Westfall--


Overlaps
TO OverlapRA Overlap
Justen Pautzke-

Other Personnelnone

GuestsSeveral tour groups


Open/Close Log
Open timeOutdoor tempTruss tempClose timeReasonTime open
23:453.16.408:55PR09:10
Total Time Open9:10


      
ProgramNight Priority
Stack Data
StartStopee50ee80Hefi FocusMars FocusOutside TempDome TempTruss TempWind DirectionWind SpeedStack Type
00:1003:270.470.7811413800.0-0.10.429216First of Night


Problem Reports
PR NumberTimesTime LostDescriptionResponse
431404:41-04:55, 05:17 - 05:25, 07:39 - 07:5200:35First HFC faults occurred repeatedly when beginning to slew to targets, then repeated HFC faults occurred when there was absolutely no activity and TCS was merely running. In the latter case, after shutting down all systems, clearing the HFC fault, the HFC fault reappeared when TCS was restarted. In both the former and the latter cases restarting dSpace seems to eliminate this problem for over an hour, but it kept returning to the point where longer tests could not be finished. I made two brief recordings in ControlDesk, one called coldweather.idf (since I originally thought this was a cold weather problem) in which the HFC fault occurred when slewing to a target began, and one called tcsstartuphfc.idf, in which the HFC fault occurred after issuing startsys command at index time 49825.
431102:00-02:0000:00Segment 85 could not be stacked because it hit an actuator limit
431207:12-07:1500:03While on trajectory we had an unceremonious abort with no error lights or error reports. TCS seemed to be behaving strangely, so I killed system processes in htcs terminal with ctrl-c. This left behind one TCS server and did not indicate that it was defunct. If I had checked the top processes I'm guessing that it would have been hung up, using 100%+ CPU.
431308:45-08:5500:10While on trajectory we got a very large Y following error that made no sense. The commanded value seemed to jump so far away from the Y position. At the same time the H2 Prof light turned orange. I did not move the tracker afterward.


Ops Commentsnone


TO CommentsWe were able to get on sky, and it was clear and fairly calm, but due to problems we were not able to complete any tests apart from post-stacking test on GOES 14.


RA Commentsnone


Observations
FileTarget/QIDExp StartExposureOverheadProgramInstrument ConfigurationData TypeIQDimmSkySBrtSkytransSNRCommentsCharge