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

Civil Date
Ephemerides
2015-11-01SunsetSunriseMoon
Set12°18°18°12°RiseRiseSet
00:1201:0201:3011:5012:1813:0805:09-
Night Length11:20Sunset Temperature


On-Duty Personnel
Resident AstronomerTelescope OperatorOPS EngineerDay Ops
-Justen Pautzke--


Overlaps
TO OverlapRA Overlap
Amy Westfall-

Other Personnelnone

Guestsnone


Open/Close Log
Open timeOutdoor tempTruss tempClose timeReasonTime open
00:1212.817.108:5308:41
Total Time Open8:41


      
ProgramNight Priority
Stack Data
StartStopee50ee80Hefi FocusMars FocusOutside TempDome TempTruss TempWind DirectionWind SpeedStack Type
01:1502:150.510.76975-549911.912.012.528518First of Night
↪ CommentsSWAG set to high had to wait for the truss to cool at beginning of the night.
03:4804:4412.111.912.228722First of Night
↪ Commentsone bad iteration messed up the stack and had to go back to the last reference. Turned fixedap on.


Problem Reports
PR NumberTimesTime LostDescriptionResponse
421106:09-06:1500:06Tip tilt not able to keep up with slew to target. Got the birdies again. Shut down tcs gui and servers and restarted. Perhaps this is due to the large offsets we made in phi during our last test. These were never reset.
421207:40-07:4000:00We were doing a combination pointing and drift test leaving the telescope azimuth the same. We sent the telescope to a target at Ra:0.8246944 Dec:35.9154694 staying at the azimuth we were currently at (293.7347). The telescope said that it was on trajectory but did not seem to be settling into a certain ra and dec. This meaning that while watching the telescope on trajectory the Ra was changing by about -0.00010 hours every few seconds. The Dec was changing by about +.0180 degrees every few seconds. These changes were occurring in declination and right ascension at the same time as if the tracker was doing some sort of correction. The structure azimuth also seemed to change even though the structure never picked up. It went from 293.7374 to 290.13 which was the optimal azimuth for the target. Tried a similar test later on in the night and could not reproduce this problem.


Ops Commentsnone


TO CommentsSWAG set at 16C, the temperature outside at 6pm local time was 12.6C. Flushed the dome for awhile to even out temps. Moved the tracker to ITF X=0 Y=0 Z=0 rho=0 theta=0 and phi=0 (current values were reading X=-0.388, Y=0.091, Z= 0.00, rho=-0.01, theta=0.00, phi=0.00). The corresponding RTF values are: X=-10.798, Y=22.949, Z=2.101, rho=-0.01, theta=-0.19, and phi=0.01.


RA Commentsnone


Observations
FileTarget/QIDExp StartExposureOverheadProgramInstrument ConfigurationData TypeIQDimmSkySBrtSkytransSNRCommentsCharge