|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Stack Data | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Start | Stop | ee50 | ee80 | Hefi Focus | Mars Focus | Outside Temp | Dome Temp | Truss Temp | Wind Direction | Wind Speed | Stack Type | |
| 03:36 | 04:12 | 0.47 | 0.72 | 1005 | 661 | 23.5 | 23.5 | 23.3 | 151 | 8 | First of Night | |
| ↪ Comments | DMI 26.211904 | |||||||||||
| Problem Reports | ||||
|---|---|---|---|---|
| PR Number | Times | Time Lost | Description | Response |
| 4031 | 08:00-08:00 | 00:00 | When commanded from htcs the trajectory -c command does not run a trajectory. It only gives version information like so: version is 2.6.6 (r266:84292, Nov 21 2013, 10:50:32) [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] | |
| 4032 | 06:50-07:12 | 00:22 | Received several error messages stating, "Receiver for tcsGuiTcsAsyncCommandSender is likely offline." Restarted TCS twice and the problem went away, but after the third time the problem persisted. This occurred after initializing in ControlDesk and then running in TCS. | Shutting down everything including dSPACE and servo cabinets, bringing everything back up, and initializing in TCS seemed to prevent the problem during further testing. |
| Ops Comments | none |
|---|
| TO Comments | Mirror team: We did not see any donuts present on the array tonight. We closed to do tracking tests and before we remembered to do the donut-related piston tests the 0.3um dust shot up past 3000000. Successfully ran tracks in north, south, east, west via TCS gui. Vicki Riley for TO training. |
|---|
| RA Comments | wfu in progress |
|---|
| Observations | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| File | Target/QID | Exp Start | Exposure | Overhead | Program | Instrument Configuration | Data Type | IQ | Dimm | SkySBrt | Skytrans | SNR | Comments | Charge | |