jaeger 1.0.0
π Version 1.0.0
jaeger is now working reliably at APO and LCO. This is a good time to tag the first production version.
β¨ Improved
- #188 Chiller temperature and flow can now be set to a fixed value which is monitored and reset if necessary. Temperature can still be set to an "auto" mode that will maintain the set point slightly below the ambient temperature. The
chiller setcommand now acceptsauto,disable, or a value for eitherflowortemperature. The default values can be set in the configuration file underchiller.temperature(truefor automatic mode,nullto disable monitoring, or a fixed value) orchiller.flow(acceptsnullor a fixed value). - Added
--quietflag tostatusthat does not print the status of each robot. - Added back
jaeger configuration fake-fieldcommand. - Fixed
jaeger configuration slewcommand to work withlcotcc. - Enabled additional alarms for LCO.
π·οΈ Changed
- Reworked scale logic when loading a new design:
- If a
--scaleflag is passed, that scale is passed directly to coordio without any additional fudge factor. - If the guider scale is available and
use_guider_scale=True, the guider scale multiplied by the fudge factor is passed. - If
use_guider_scale=Trueand thescale_temperature_coeffsare defined, and the guider scale is not available, the guider scale is defined by the scale-temperature correlation and the fudge factor is applied. - If
use_guider_scale=Falseand--scaleis not passed, or otherwise the guider scale cannot be defined, thedefault_scalevalue is used.
- If a
- Use
targetdb.design_to_fieldtable. - Use difference centroiding methods for APO and LCO.
- Change various configuration parameters for LCO.
- Renamed
kludge_factorand--kludge-factortofudge_factorand--fudge-factor.
π§ Fixed
- Alerts and chiller bots were not being started on init.
- Solve a case in which a manually disabled positioner could not be re-enabled after the FPS had been power cycled or reinitialised.