-
Notifications
You must be signed in to change notification settings - Fork 4
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
Use chandra limits #71
Conversation
… information in the hot ACIS table anymore
…L file. Also print the limit that is violated in the table
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just want to confirm the intentionality of having syntax of odb.caution for the limits for the official models vs the safety.caution for the "informal" models.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not so much "official" vs "informal" as what limits are stored in the ODB (related to engineering telemetry) vs the ones related to DEA HKP telemetry
# For the ACIS FP limit we write out an obsid table | ||
context["acis_obs"] = self.acis_and_ecs_obs | ||
template_path = ( | ||
TASK_DATA / "acis_thermal_check/templates/obsid_template.rst" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see where TASK_DATA is defined.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In passing - I think it is imported from utils here
TASK_DATA, |
Thanks
…On Thu, Mar 28, 2024 at 8:47 AM Jean Connelly ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In acis_thermal_check/main.py
<#71 (comment)>
:
> @@ -1393,6 +1286,23 @@ def write_index_rst(self, outdir, context):
# Render the template and write it to a file
with open(outfile, "w") as fout:
fout.write(template.render(**context))
+ if self.msid == "fptemp":
+ # For the ACIS FP limit we write out an obsid table
+ context["acis_obs"] = self.acis_and_ecs_obs
+ template_path = (
+ TASK_DATA / "acis_thermal_check/templates/obsid_template.rst"
In passing - I think it is imported from utils here
https://github.com/acisops/acis_thermal_check/blob/4f7c496bb51f327b16a75066896d5c5e5dfbe55d/acis_thermal_check/main.py#L25
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACN5TGO43PQIXA35QFQCBG3Y2QGMDAVCNFSM6AAAAABEQX7YRSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSNRWGEYDMMBTGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Good, so long as the syntax was as intended
…On Thu, Mar 28, 2024 at 9:08 AM John ZuHone ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
On acis_thermal_check/tests/bep_pcb/answers/JUL2919A_viol.json
<#71 (comment)>
:
It's not so much "official" vs "informal" as what limits are stored in the
ODB (related to engineering telemetry) vs the ones related to DEA HKP
telemetry
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACN5TGNJQS6CFRF5TDSDKLDY2QI5NAVCNFSM6AAAAABEQX7YRSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSNRWGE3TCNZTGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All my comments were addressed. Looks good!
Looks good to me. |
Description
This version of
acis_thermal_check
hands violations checking and plotting of limits over completely to thechandra_limits
package. A review of the most important changes is as follows:chandra_limits
is largely copied and refactored over from the code originally inacis_thermal_check
.Practical effects of these changes:
Interface impacts
The table reporting violations on the webpages has changed slightly, but is human-read. Plots show limit lines as a function of time instead of every limit line across the whole plot; also human-read.
Testing
Unit tests
All tests which do not depend on violations checking pass without any answer updates as expected. Some answer changes are necessary for the FP and a couple of other models. All of these answer changes were hand-checked and they were found to be correct based on the code changes.
Independent check of unit tests by [REVIEWER NAME]
Functional tests
Ran the code in this PR at weekly load reviews for several weeks and results were checked for consistency with flight code; any differences are explained by changes to the violations checking changes.