Jaeger

Latest version: v1.7.5

Safety actively analyzes 638819 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 7

1.0.0

✨ Improved

* [188](https://github.com/sdss/jaeger/issues/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.

0.16.1

🚀 New

* [183](https://github.com/sdss/jaeger/issues/183) The `FVC.write_summaryF()` method now also produces some histograms and quiver plots that show the FVC convergence in wok and ra/dec coordinates.
* [184](https://github.com/sdss/jaeger/issues/184) Added a `jaeger.fvc.reprocess_configuration()` coroutine that allows to reprocess the final FVC image for a configuration with a different centroid method.
* [185](https://github.com/sdss/jaeger/issues/185) Support for LCO and additional improvements:
* General support for running jaeger at APO and LCO.
* The `jaeger` and `ieb` configuration files have been split into `_APO` and `_LCO`.
* Makes `fvc loop` more reliable. The `proc-` image is now saved in most conditions.
* Use `FVCTransformAPO` or `FVCTransformLCO` depending on the observatory.
* Fix `fvc loop` with `--fbi-level 0`.
* Chiller and alerts bots are now run as part of the actor instead of in the `FPS` object. Alerts are now observatory-specific.
* Do not calculate paths when using `jaeger configuration load --from-positions`.
* Fix for 182: GFA alerts are disabled if the camera is powered off.
* New `home` command to send `GO_TO_DATUMS` to multiple or all positioners at once.
* [186](https://github.com/sdss/jaeger/issues/186) New command `fvc snapshot` that creates a temporary configuration from the current positions and takes an FVC measurement.
* Add `jaeger configuration reload` command. It's equivalent to using `jaeger configuration load --no-clone DESIGNID` where `DESIGNID` is the currently loaded design.
* If called without arguments, `disable` now outputs the list of currently disabled robots.

✨ Improved

* The list of manually disabled positioners is kept during reinitialisation.

🏷️ Changed

* Default FVC centroid algorithm is now `zbplus`.

🔧 Fixed

* [182](https://github.com/sdss/jaeger/issues/182) GFA alert for a camera is disabled if the camera is off.
* Bump sdssdb to ^0.5.2 to ensure that `assignment_hash` is available

0.16.0

* Yanked due to error releasing.

0.15.1

🔧 Fixed

* Pin `pydl` 1.0.0rc1 since rc2 has been yanked.

0.15.0

🔥 Breaking changes

* Minimum Python version is now 3.8. Astropy 5 required.

🚀 New

* [180](https://github.com/sdss/jaeger/issues/180) A design can now be preloaded using `jaeger configuration preload [DESIGNID]`. If a design ID is not provied, the first element from the queue will be used. Preloading calculates the trajectories for the new configuration but does not write to the database, generate the configuration summary file, or output keywords. To make the preloaded design active, use `jaeger configuration load --from-preloaded`.
* [181](https://github.com/sdss/jaeger/issues/181) Automatically determine the epoch delay for a new configuration created from a design in the queue. If there are multiple consecutive designs in the queue with the same hash (i.e., that will be cloned), determines the epoch delay so that the array is reconfigured for the middle epoch of the observations.
* Added `fvc_percent_reached` and `perc_95` keywords to the FVC loop to show the percentage of robots that have reached their positions (within the FVC tolerance) and the 95% percentile respectively.
* `delta_ra` and `delta_dec` from the database are now applied.
* Require coordio 1.3.0.

✨ Improved

* If a new configuration is loaded while the array is unfolded and `jaeger configuration reverse` is called, the reverse trajectory from the previous configuration will be used.
* Update coordinates using `delta_ra` and `delta_dec` from `targetdb.carton_to_target`.
* Introduced an empirical kludge factor for the guider scale that can be adjusted in the configuration file as `configuration.scale_kludge_factor`.
* Use reverse trajectory from previous configurations if the current one has not been executed.
* `jaeger configuration reverse` now accepts an `--explode` flag.
* FVC loops succeeds if `fvc_perc_90 < 30`.
* Add `fvc_image_path` to confSummaryF.
* Allow to home alpha and beta independently.

🔧 Fixed

* Fixed an issue in which the epoch RA/Dec in a configuration had the correctly propagated proper motions but those were not used for observed, field, etc. coordinates. Those coordinated derived in practice from the catalogue coordinates at the catalogue epoch.

0.14.0

🚀 New

* [177](https://github.com/sdss/jaeger/issues/177) When `jaeger configuration load` is called with a design that has the same targets as the currently loaded (as it happens for multi-exposure fields), the existing configuration and metadata are copied but decollision is not run and new paths are not generated.
* [175](https://github.com/sdss/jaeger/issues/175) Added alert system.
* [176](https://github.com/sdss/jaeger/issues/176) Refine configuration focal plane scale using the guider measured scale.
* Addded a scale factor when loading a configuration.
* Allow to load a design from the queue.

✨ Improved

* [178](https://github.com/sdss/jaeger/issues/178) Major refactor of the chiller code.
* [179](https://github.com/sdss/jaeger/issues/179) Refactored FVC code to use coordIO's `FVCTransformAPO`.
* Add jaeger, kaiju, and coordio versions to confSummary.
* Allow to disable chiller watcher.
* Store positioners in trajectory data file. Dump trajectory data even if trajectory fails.

🔧 Fixed

* `jaeger status` now won't output additional information if the status of a single positioner is requested.

Page 5 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.