| Problem Reports |
|---|
| PR Number | Times | Time Lost | Description | Response |
|---|
| 4230 | 04:07-04:08 | 00:01 | Right before Index Time 36500 tracker seemingly stopped or offset and then moved back to the correct position.
Subsequent Index Times: 53815, 65555
During the last incident watched the Tracker Monitoring tab and noticed that nothing was moving-- everything was perfectly still. When it reacquired the object everything seemed to move like normal again. | |
| 4232 | 01:45-02:55 | 01:10 | Misplaced variable in TCS code caused phi to consistently drift a great deal in the positive direction, and badminton birdies to reliably form on ACQ cam. | |
| 4233 | 06:34-06:36 | 00:02 | Never-before-seen error message: Trajectory already active when trying to go to next target. Previous track had been aborted. Index Time: 45200 | Restarted TCS. |
| 4234 | 07:38-07:39 | 00:01 | After moving to a trajectory, On Trajectory light turned green but streaks kept running across guider. Turned out to be a bad azimuth request, but no error was given to that effect. (Optimal azimuth for the track was around 60 and current azimuth was around 280. This may have been the software thinking that we were very early before the track even started, come to think of it.) | |
| 4235 | 05:00-05:00 | 00:00 | We could not get guide probe to move past a certain position, and gave up on testing it. More info in PR. | |
| 4132 | 07:42-07:44, 08:50 - 08:52 | 00:04 | tcs_server hung and used 100% of CPU. Could not load trajectories. | Restarted TCS both times. |