jaeger 1.3.2

🔧 Fixed

• Only retry FPS.update_firmware_version() if n_positioners is not None. Otherwise a time out is expected.

jaeger 1.3.1

jaeger 1.3.1

jaeger 1.3.0

✨ Improved

• Trajectories now save the snapshot asynchronously, which should save a few seconds at the end of each trajectory.
• Avoids saving trajectory dump file multiple times.
• FVC proc- image is saved asynchronously and the command doesn't wait for it to finish writing. The confSummaryF file is computed and saved asynchronously.
• plotFVCResults in coordio.transforms is monkeypatched to run as a task.

⚙️ Engineering

• Upgraded to Drift 1.0.0 which uses pymodbus 3.

jaeger 1.2.1

🔧 Fixed

• Require sdss-kaiju>=1.3.1 which solves a problem with a shapely dependency upgrade breaking some plotting.

jaeger 1.2.0

✨ Improved

• Output preloaded_is_cloned keyword indicating whether a preloaded design is cloned.
• Move the check for whether the FPS is moving before sending a new trajectory to Tracjectory.send() and after an FPS.update_status() has been issued, which may help with cases in which the FPS is stuck as moving because the status has not been updated.

🏷️ Changed

• Call cherno get-scale --max-age 3600.
• Changed max_cloned_time to 4500 and max_designs_epoch to 4 at both APO and LCO.
• Updated fudge factor at APO to 0.99988.
• Use zbplus2 as default for FVC centroiding at APO.

jaeger 1.2.0b1

🚀 New

• #193 Calculate delta_ra and delta_dec offsets using coordio's object_offset.

✨ Improved

• jaeger fvc snapshot now creates a snapshot based on the FVC-measured positions and alerts if a robots is more than 5 degrees off.

🔧 Fixed

• Keep disabled positioners after a power cycle.

🏷️ Changed

• Use MDP2 for LCO.

jaeger 1.1.1

🔧 Fixed

• Require kaiju>=1.3.0, which is needed for MDP2 path planning.

jaeger 1.1.0

This version has been yanked due to a missing dependency. All the changes are available in 1.1.1.

🚀 New

• #191 Support for MDP path generation mode. The default mode can be set in the configuration file under kaiju.default_path_generator and overridden in jaeger configuration load and jaeger configuration random with the --path-generation-mode flag.

✨ Improved

• Add FVCITER keyword to the FVC process image header with the number of the FVC iteration.

🏷️ Changed

• IEB never disables itself automatically. Now it will try five times to connect to the WAGO module and if that fails it will issue an error but not self disable itself.
• Use 5 degrees as start angle during homing.
• Update disabled/enabled positioners at APO and LCO.

🔧 Fixed

• #189 Prevent FPS initialisation from failing if a positioner is reporting a collided status.
• Fix SJD calculation for LCO.

jaeger 1.0.1

🔧 Fixed

• Bumped minimum version of sdssdb to 0.5.5 since jaeger requires the Design.field property.

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 set command now accepts auto, disable, or a value for either flow or temperature. The default values can be set in the configuration file under chiller.temperature (true for automatic mode, null to disable monitoring, or a fixed value) or chiller.flow (accepts null or a fixed value).
• Added --quiet flag to status that does not print the status of each robot.
• Added back jaeger configuration fake-field command.
• Fixed jaeger configuration slew command to work with lcotcc.
• Enabled additional alarms for LCO.

🏷️ Changed

• Reworked scale logic when loading a new design:
  • If a --scale flag 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=True and the scale_temperature_coeffs are 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=False and --scale is not passed, or otherwise the guider scale cannot be defined, the default_scale value is used.
• Use targetdb.design_to_field table.
• Use difference centroiding methods for APO and LCO.
• Change various configuration parameters for LCO.
• Renamed kludge_factor and --kludge-factor to fudge_factor and --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.