New PrintDQ tool for DataQuality monitoring of processed beam runs #312
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
New PrintDQ tool to be used for a quick snapshot of beam run quality.
|
This tool uses the BRF waveform fit passed along to the Store by the new |
adjust verbose from v_error to v_debug if it can't find objects in the Stores. It's a printing tool so not accessing those Stores will just lead the counts to be 0 for that particular event.
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.
Tool that can be ran over Processed beam run data to provide a snapshot summary of various event/cluster/track rates. I have tried to include many parameters that are good indications of a high quality beam run.
PrintDQcan be used by the Data Quality group to get a quick statistical look on individual beam runs as they are event built. It's meant to bridge the gap between instance shift plots (RawData) and the long-term analysis. See the README for more details.