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

Add a test of the change-rate command to RandomTriggerCandidateMaker #358

Merged
merged 3 commits into from
Nov 7, 2024

Conversation

eflumerf
Copy link
Member

@eflumerf eflumerf commented Nov 5, 2024

No description provided.

@eflumerf eflumerf added the enhancement New feature or request label Nov 5, 2024
@eflumerf eflumerf self-assigned this Nov 5, 2024
Copy link
Contributor

@ArturSztuc ArturSztuc left a comment

Choose a reason for hiding this comment

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

Overall looks good to me, although the unit test doesn't pass for me.
I either keep getting:

🚨 Event count 4 is outside the tolerance of 1 from an expected value of 2 🚨
or

>       assert len(run_nanorc.data_files) == expected_number_of_data_files
E       AssertionError: assert 3 == 4

Which probably means more checks with RTCM are needed to confirm it definitely works... I don't understand how we get 4 events (maybe there's another bug hiding in RTCM somewhere?) or 3 data files where there's clearly 4 tests.

Copy link
Contributor

@bieryAtFnal bieryAtFnal left a comment

Choose a reason for hiding this comment

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

LGTM

@ArturSztuc ArturSztuc merged commit 3092618 into prep-release/fddaq-v5.2.0 Nov 7, 2024
@ArturSztuc ArturSztuc deleted the eflumerf/ChangeRateTest branch November 7, 2024 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants