Make ATDome configurable in the standard fashion:
Please provide an event in ATDome that tells us where the dome is headed
Add support for configurable CSCs
I also made some improvements to ts_salobj, to make this work easier:
ts_salobj pull request: https://github.com/lsst-ts/ts_salobj/pull/41
ts_ATDome pull request: https://github.com/lsst-ts/ts_ATDome/pull/6
ts_config_attcs pull request: https://github.com/lsst-ts/ts_config_attcs/pull/2
Trivial changes that I think the package authors should merge when they are ready to update to ts_salobj v12:
ts_ATDomeTrajectory pull request: https://github.com/lsst-ts/ts_ATDomeTrajectory/pull/7 (I will merge this one)
ts_scheduler pull request: https://github.com/lsst-ts/ts_scheduler/pull/21
ts_ATWhiteLightSource pull request: https://github.com/lsst-ts/ts_ATWhiteLightSource/pull/2
ts_salobjATHexapod pull request: https://github.com/lsst-ts/ts_salobjATHexapod/pull/1
Please look at the changes to at_salobj, ts_ATDome and ts_config_attcs. The changes to the other packages are trivial, but I would like your opinion on how to proceed with them. I'm thinking I should notify the package owners and have them merge the changes when they are ready to update to ts_salobj 12 (which will have this ticket's changes).
I think the package owners must have received a notification of the PR. But, we may want to make sure everyone is informed about the change in the ts_salobj.
I reviewed the PRs on GitHub. Most of them where trivial. We'll need to coordinate the update with all the other CSC once they upgrade to the next release of salobj. Will probably require some announcements during standup.
Merged ts_salobj to develop and master and tagged v3.12.0
Merged ts_ATDome to develop and master and tagged v0.5.0
Merged ts_config_attcs to develop
Merged ts_ATDomeTrajectory to develop and master and tagged v0.7.0
Updated served docs for ts_salobj, ts_ATDome and ts_ATDomeTrajectory at http://staff.washington.edu/rowen/
That leaves 3 packages with trivial changes to be merged.