This PR (and corresponding ones on the other repos) refactors the G-TeCS packages to unify them into a single gtecs Python namespace package (https://github.com/GOTO-OBS/g-tecs/issues/434). This means the complete package code is split across 5 repos:
gtecs-common (NEW), a place to hold common functions like dealing with Slack messages
gtecs-control (previously just G-TeCS), which contains all the hardware control daemons
gtecs-obs (previously ObsDB), which contains the observation database (and will include the scheduler)
gtecs-alert (previously GOTO-alert), which contains the alert processing code (and will include the sentinel)
gtecs-simulations (NEW), which contains the simulation scripts
This does not, to be clear, implement "The Big Split" described in https://github.com/GOTO-OBS/g-tecs/issues/#496 (totally separating the scheduler from the control package), because it's not vital yet and anyway I ran out of time before the commissioning trip. But this PR does lay a lot of the foundations for that eventual split.
Note that GOTO-tile isn't included, I consider it an independent package and so unlike GOTO-alert it would be wrong to integrate it into the G-TeCS system.
This PR (and corresponding ones on the other repos) refactors the G-TeCS packages to unify them into a single
gtecsPython namespace package (https://github.com/GOTO-OBS/g-tecs/issues/434). This means the complete package code is split across 5 repos:gtecs-common(NEW), a place to hold common functions like dealing with Slack messagesgtecs-control(previously just G-TeCS), which contains all the hardware control daemonsgtecs-obs(previously ObsDB), which contains the observation database (and will include the scheduler)gtecs-alert(previously GOTO-alert), which contains the alert processing code (and will include the sentinel)gtecs-simulations(NEW), which contains the simulation scriptsThis does not, to be clear, implement "The Big Split" described in https://github.com/GOTO-OBS/g-tecs/issues/#496 (totally separating the scheduler from the control package), because it's not vital yet and anyway I ran out of time before the commissioning trip. But this PR does lay a lot of the foundations for that eventual split.
Note that GOTO-tile isn't included, I consider it an independent package and so unlike GOTO-alert it would be wrong to integrate it into the G-TeCS system.
Related PRs: