Releases: sdss/jaeger
Releases · sdss/jaeger
jaeger 1.2.1
🔧 Fixed
- Require
sdss-kaiju>=1.3.1
which solves a problem with ashapely
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 anFPS.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 andmax_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
anddelta_dec
offsets usingcoordio
'sobject_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 injaeger configuration load
andjaeger 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 theDesign.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 acceptsauto
,disable
, or a value for eitherflow
ortemperature
. The default values can be set in the configuration file underchiller.temperature
(true
for automatic mode,null
to disable monitoring, or a fixed value) orchiller.flow
(acceptsnull
or a fixed value). - Added
--quiet
flag tostatus
that does not print the status of each robot. - Added back
jaeger configuration fake-field
command. - Fixed
jaeger configuration slew
command to work withlcotcc
. - 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 thescale_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, thedefault_scale
value is used.
- If a
- 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
tofudge_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.
jaeger 0.16.1
🚀 New
- #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 Added a
jaeger.fvc.reprocess_configuration()
coroutine that allows to reprocess the final FVC image for a configuration with a different centroid method. - #185 Support for LCO and additional improvements:
- General support for running jaeger at APO and LCO.
- The
jaeger
andieb
configuration files have been split into_APO
and_LCO
. - Makes
fvc loop
more reliable. Theproc-
image is now saved in most conditions. - Use
FVCTransformAPO
orFVCTransformLCO
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 sendGO_TO_DATUMS
to multiple or all positioners at once.
- #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 usingjaeger configuration load --no-clone DESIGNID
whereDESIGNID
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 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
jaeger 0.15.1
🔧 Fixed
- Pin
pydl
1.0.0rc1 since rc2 has been yanked.
jaeger 0.15.0
🔥 Breaking changes
- Minimum Python version is now 3.8. Astropy 5 required.
🚀 New
- #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, usejaeger configuration load --from-preloaded
. - #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
andperc_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
anddelta_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
anddelta_dec
fromtargetdb.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.