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 1.5.3 #790

Closed
javierggt opened this issue Feb 24, 2022 · 0 comments · Fixed by #812
Closed

Update acisops/backstop_history to 1.5.3 #790

javierggt opened this issue Feb 24, 2022 · 0 comments · Fixed by #812
Milestone

Comments

@javierggt
Copy link
Contributor

Release Notes for Version 3.0.1 of Backstop History

Change Description

tbegin is used by backstop_history to know how far back in time to backchain loads.
tbegin is supplied by the user of backstop_history. The Assemble_History method
generated both a DOY and Chandra Seconds version of that time, and rounded the
time off. Rounding is unnecessary and was incorrectly applied in one instance.
The incorrect application did not affect the operation of the program as it was
done only for logger purposes.

Also the initial logger comment under "debug" was modified.

Comments were added or modified for clarification.

Files Changed:

acisops/backstop_history#23

Testing:

Unit and functional testing completed to assure that the
assembled histories were unchanged from previous runs.

Interface impacts

None.

Review

Objectives and Results by ACIS Ops

Deployment Plan

Installation of Backstop History will occur once approved by FSDS.

Includes the following merges:

  • PR #23: Remove unnecessary and incorrectly applied round off
  • PR #22: Now processes a full continuity (science + vehicle commands) load as …
@javierggt javierggt added this to the 2022.3 milestone Mar 25, 2022
@javierggt javierggt mentioned this issue Mar 25, 2022
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