Renaming some of the CTB TC types #36
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wesketchum
approved these changes
Jul 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed some of the Cherenkov trigger TC types for CTB after request form the CTB group. Renamed them to
CustomX, so they can still be reused later.This PR goes together with DUNE-DAQ/trigger#321
Tests done:
3ru_3df_multirun_test.pyintegration test passes, but I doubt it would fail if there was some strange mistake in CTB TC types...hdf5libs, ran the daq offline with custom trigger candidate maker with the changed trigger types, and looked at the generated raw file withHDF5LIBS_TestDumpRecord. Looks as expected given the changes.