Releases: sot/kadi
Releases · sot/kadi
Version 0.10
This version adds the ability to select events based on overlaps with other events. For instance:
- Select maneuver events either inside or outside the radiation zone.
- Select SIM moves that occur during a maneuver.
- Select maneuvers that have a SIM or Grating move.
This is possible using the select_overlapping() method of a QuerySet object. For documentation details see the Selecting overlapping events section.
Version 0.9
New features:
- Add LTT bad times events corresponding to the list of GRETA LTT bad times maintained by the FOT. See the LTT bad times section. [Pull Request #45]
- Add ability to define event intervals based on a filtered subset of the event type. Previously the fetch
remove_intervals
andselect_intervals
methods always used all the events, but now it has the flexibility to use a subset of the events. See the Filtering interval events section. [Pull Request #46] - Made
EventQuery
objects provide a more useful and human-readable representation when printed. This works even for complex compositeEventQuery
objects, e.g.
>>> good_times
(<EventQuery: Dwell pad=-100.0> AND NOT ((<EventQuery: GratingMove pad=(100.0, 300.0)>
OR <EventQuery: Dump pad=(100.0, 300.0)>) OR <EventQuery: TscMove pad=(100.0, 300.0)>))
Version 0.8
The safe sun interval now covers what is normally considered the "safe mode" interval, starting from safe mode entry and finishing when the OBC is full back in control near the end of the recovery process.
As a somewhat unrelated change, the default event plotting was improved. This was needed to validate the new event times vs. telemetry.
Version 0.7
Features:
- Add Load Segment events
- Add Grating Move events
- Add Dark Cal events
- Add Pass Plan events (from iFOT).
- Add OC, CC and GOT to DSN comm events when available.
- Make relevant event types include events into the future as available.
- Improve interval pad interface
- Add web interface (only available on local development server)
- Initial release that is formally part of the Ska runtime environment. Deployment of new versions will now be controlled through skare.