Skip to content

Initial/Demo Implementation of a Wait/Verify EHA for Flight Channels#1

Draft
swanchr wants to merge 11 commits intomainfrom
wait_verify
Draft

Initial/Demo Implementation of a Wait/Verify EHA for Flight Channels#1
swanchr wants to merge 11 commits intomainfrom
wait_verify

Conversation

@swanchr
Copy link
Copy Markdown
Contributor

@swanchr swanchr commented Aug 20, 2025

This is an initial implementation of a Wait/Verify EHA for Flight Channels using the step framework.

It also includes an initial implementation of an ampcs library (functions to query GLAD).

There are some known longer term issues including:

  • Local matplotlib graph and Ingenium series graph
  • Graphing always uses DN vs. actual value
  • Extensive testing (works, tested with Europa WSTS, but only spot checked)

Comment thread setup.py
Comment thread setup.py
Comment thread steps/wait_verify_eha_flight/custom_script.xml
<custom-scripts>
<!-- mission name is a string defined for each project -->
<header mission_name="UPDATE_ME"></header>
<custom_script script_name="wait-verify-eha-flight" script_path="wait_verify_eha_flight.py" description="Wait/Verify EHA measurements against predicts." hash="SHA256 Hash of your script - populated by create_catalog.py" script_id="unique id of your script - populated by create_catalog.py">
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step only handles FSW channels, which means you cannot check both FSW and SSE channels in the same step. this is quite limiting compared to the built in wait_eha step.

We will need to combine FLIGHT_TELEM and SIM_TELEM, so that an input control can handle either type.
Choice between FLIGHT vs. SIM would be done by the user through the UI.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We opted not to implement it this way because while AMPCS handles Flight/Sim telemetry together, other systems may not and forcing steps to support both Flight/Sim could cause additional burden.

I will also say that the actual use of mixed queries to both flight/sim is quite limited (~3% of Europa ALTO EHA steps) and the impact of using two steps with a common reference time is a low impact workaround.

@@ -0,0 +1,186 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--' If you are using an XML editor - like oXygen - update the next line to point to your local schema copy '-->
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You do not need to use quote in XML comment.

Comment thread steps/wait_verify_eha_flight/wait_verify_eha_flight.py
Comment thread steps/wait_verify_eha_flight/wait_verify_eha_flight.py
Comment thread steps/wait_verify_eha_flight/wait_verify_eha_flight.py
Comment thread steps/wait_verify_eha_flight/wait_verify_eha_flight.py

for point in raw_data:
if not isinstance(point, (list, tuple)) or len(point) != 2:
continue
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

log a warning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants