Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update acisops/backstop_history to v3.2.1 #1111

Closed
javierggt opened this issue Jun 6, 2023 · 0 comments · Fixed by #1088
Closed

Update acisops/backstop_history to v3.2.1 #1111

javierggt opened this issue Jun 6, 2023 · 0 comments · Fixed by #1088
Milestone

Comments

@javierggt
Copy link
Contributor

New variations of SI modes, and their associated RTS files, for Long Term ECS
measurements were created to provide a more flexible chip selection.
Backstop History was updated to incorporate these new RTS files in future
history assemblies.

Includes the following merges:

  • PR #25: Incorporation of new RTS files for new Long Term ECS SI modes
  • PR #24: New ECS RTS file, New method added, SCS-107 bug fixed
  • PR #23: Remove unnecessary and incorrectly applied round off
  • PR #22: Now processes a full continuity (science + vehicle commands) load as …
  • PR #21: Update to the PR 20 prior to installation
  • PR #20: Update for SCS-106 change and new power commands
  • PR #19: Run on filesystems which are not case-sensitive
  • PR #18: Replace Chandra.Time with cxotime
  • PR #17: Modifications to Baskstop History to accommodate data structure change…
  • PR #13: Changes to accomodate NLET events in normal, too and maneuver only loads
  • PR #9: SHINY: migrate from Chandra.cmd_states / Ska.ParseCM to kadi
  • PR #11: Shiny workflow update
  • PR #10: Shiny workflow update
  • PR #8: Setting up automated builds
  • PR #7: Remove version from setup.py
  • PR #6: Code changes needed for SCM versioning
@javierggt javierggt added this to the 2023.3 milestone Jul 11, 2023
@javierggt javierggt mentioned this issue Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant