Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:0
-
Epic Link:
-
Sprint:TSSW Sprint - Jan 18 - Feb 1
-
Team:Telescope and Site
-
Urgent?:No
Description
During the last run (see entry in log at 05:51am CLT) the ATDometrajectory CSC started sending negative positions to the ATDome CSC which only accepts a range of 0-360. Obviously the dome was in the wrong position but also no errors were thrown from either CSC which were apparent to the operator.
https://confluence.lsstcorp.org/display/LSSTCOM/2021-01-21+Night+Log
The issue was resolved by cycling both the Dome and ATDomeTrajectory CSCs. I can't remember off hand if we tried cycling just the ATDomeTrajectory or not...
I proppose to fix this by allowing ATDome to accept azimuth outside the range 0-360 (and wrapping it to >= 0, < 360 for the low-level dome controller). It may be worth updating ATDomeTrajectory as well, but I consider that optional.