| Problem Reports |
|---|
| PR Number | Times | Time Lost | Description | Response |
|---|
| 4132 | 02:13-02:18 | 00:05 | Targets would not load if sent from either RA side or if loaded manually on TO side. TCS server using 275% of CPU when top command issued, but it died shortly thereafter; did not have to be killed.
Update: Justen informed me that next time this happens I should try the cancel_trajectory command in an htcs terminal. | |
| 4178 | 02:24-02:30 | 00:06 | Unceremonious abort after tracker finally started to move on target after waiting 4 minutes for track to start. Received an error message about dome timing out before unceremonious abort, which caused go_next command to turn red in Command Status window. Unsure if that is related.
Immediately after another remote exception -- dome never moved, timeout error -- preceded another unceremonious abort.
From the PR:
Early on in a couple of tracks, which were moved to with the Move Dome checkbox checked, recieved a timeout notification stating that the dome never moved, or the dome did not make it. This happened once the tracks had started, well after the dome successfully made the move. These errors seemed to have a hand in causing the tracks to abort because both times an error message was received the current track aborted.
Ran without the Move Dome checkbox checked, moved the dome manually, and everything was okay. | |
| 4179 | 03:57-04:00, 06:13 - 06:16 | 00:06 | Saw two instances of badminton birdie images on guider tonight. One only looked like a badminton birdie after the correct_for_structure() function was applied-- I watched it happen. Both times restarting TCS fixed behavior. | |
| 4135 | 04:39-04:43, 07:54 - 07:57 | 00:07 | While slewing to next target HFC fault triggered. No error codes.
Later HFC fault triggered during track. No error codes. | |