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

[uss_qualifier] Optimize RID tests #261

Merged
merged 5 commits into from
Oct 18, 2023

Conversation

BenjaminPelletier
Copy link
Member

Currently, RID tests take a long time and we perform two of them in series (F3411-22a + U-space Remote Identification). This PR makes an effort to reduce the time these tests take by shortening the simulated flights and bringing in the lead time between injection and monitoring. It also removes the separate F3411-19 CI job in favor of resolving the TODO to add the netrid_v19 test to the standard set of tests.

In the process of making these changes, a number of issues were resolved or improved:

  • In the sequence view artifact, unattributed (no associated participant IDs) events are now handled more clearly
  • The time each scenario took is included on the sequence view artifact overview page
  • The duration of the injected NetRID flights is noted in the report upon injection
  • A bug in display_data_evaluator is fixed
  • Additional information is printed when a duplicate telemetry error is encountered in display_data_evaluator
  • The scenario query log message now includes the time the query took (to potentially visually identify long queries)

@BenjaminPelletier BenjaminPelletier marked this pull request as ready for review October 17, 2023 21:15
Copy link
Contributor

@mickmis mickmis left a comment

Choose a reason for hiding this comment

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

LGTM - nice improvements

@@ -156,8 +156,15 @@ <h2>Scenarios executed</h2>
{% endif %}
<th>Scenario</th>
{% for participant_id in all_participants %}
<th>{{ participant_id }}</th>
<th>
{% if participant_id != "unattributed" %}
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not familiar with this templating, but is it possible to refer to the variable from here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes; the variable has to be passed into the templating engine specifically, but that's probably still a good idea. Will do.

@BenjaminPelletier BenjaminPelletier merged commit ba6597c into interuss:main Oct 18, 2023
10 checks passed
@BenjaminPelletier BenjaminPelletier deleted the optimize-rid-tests branch October 18, 2023 17:25
github-actions bot added a commit that referenced this pull request Oct 18, 2023
* Add scenario durations to sequence view artifact

* Optimize RID tests

* Use unattributed participant constant in templates

* Fix merge issue, improve error message ba6597c
github-actions bot added a commit to punamverma/monitoring that referenced this pull request Oct 18, 2023
* Add scenario durations to sequence view artifact

* Optimize RID tests

* Use unattributed participant constant in templates

* Fix merge issue, improve error message ba6597c
github-actions bot added a commit to openskies-sh/monitoring that referenced this pull request Oct 20, 2023
* Add scenario durations to sequence view artifact

* Optimize RID tests

* Use unattributed participant constant in templates

* Fix merge issue, improve error message ba6597c
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.

2 participants