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

Civil Date
Ephemerides
2016-01-03SunsetSunriseMoon
Set12°18°18°12°RiseRiseSet
00:1101:0401:3312:2812:5713:5008:46-
Night Length10:55Sunset Temperature


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


Overlapsnone

Other Personnelnone

Guestsnone


Open/Close Log
Open timeOutdoor tempTruss tempClose timeReasonTime open
23:382.08.309:40PR10:02
Total Time Open10:02


      
ProgramNight Priority
Stack Data
StartStopee50ee80Hefi FocusMars FocusOutside TempDome TempTruss TempWind DirectionWind SpeedStack Type
01:2102:350.550.801030+9741.31.72.11063First of Night
04:5706:150.480.781070+1816-1.3-1.3-1.07613First of Night


Problem Reports
PR NumberTimesTime LostDescriptionResponse
432000:00-01:2001:20At ops time dome air temperature was 8 degrees and chiller was running and set to 3 degrees. Because sunset temp was actually around 0 was not able to run AOA routine for a long time due to very bad dome seeing.
431903:22-04:57, 06:56 - 06:57, 08:39 - 08:40, 09:03 - 09:3002:04When tracking or slewing at subzero temperatures, tracker motion will often cease due to Sensor error. Error is only visible when Fault Processing is set to Eng.Mode. In TCS mode it will look like HFC triggered for no reason. (It is very likely the sensor error. This is not connected with skews since many times it triggered when skew value was less than 5mm.) This seemed to happen particularly often between X positions of positive 800mm and 900mm.
429805:00-05:0000:00Tonight got several torque limiter-related skews-- could tell because of clicking noise before skew. Usually occurred moving in positive X, and in positive X range. These occurred around a temperature of -1.
431805:00-05:0000:00focusCurve fails on GSS target (More details from RA)


Ops Commentsnone


TO CommentsClear all night, but low temperature-related issues interfered greatly with tests. Discovered that when structure is already at target azimuth using HTOP loaded data with Go Next command takes MUCH LONGER than manually loading target and hitting Go Next.


RA Commentsnone


Observations
FileTarget/QIDExp StartExposureOverheadProgramInstrument ConfigurationData TypeIQDimmSkySBrtSkytransSNRCommentsCharge