fix: silenece misleading warnings #64
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
Member
c-dilks
commented
Jan 7, 2025
•
c-dilks
commented
- pass 1 charge, since we have FC charge per DST file fails to account for charge between last and first scaler readouts #48 and refer users to check such pinned issues in the documentation
- this warning was printed regardless of whether the dataset has the issue (QA per DST file) or not (QA per time bin)
- sometimes the first or last time bin has zero events, and therefore the min and max event numbers are equal
- pass 1 charge, since we have #48 and refer users to check such pinned issues in the documentation - sometimes the first or last time bin has zero events, and therefore the min and max event numbers are equal
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.