-
Notifications
You must be signed in to change notification settings - Fork 13
Adding offbeam gate counting in the CAFs #67
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
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -11,7 +11,9 @@ | |||||||||||
| <version ClassVersion="11" checksum="4062206176"/> | ||||||||||||
| <version ClassVersion="10" checksum="3057205612"/> | ||||||||||||
| </class> | ||||||||||||
| <class name="sbn::EXTCountInfo" ClassVersion="11"> | ||||||||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think @wesketchum complains when people manually change these, but I am not sure why, I defer to him
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @wesketchum is there a procedure for this? I start at 10 and increment from there as I have seen in other examples
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My main issue is to avoid proliferation of the version numbers during development. If data hasn't been written in 'older' versions that needs to be re-read, then we can remove those versions. So, in this case: if no one has ever made data with 'version 10' that we need to read back, then I'd advocate that we make version 11 --> 10, and 'start' from there. If that's not the case, what you've done is exactly right.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (or, to this point, if version 12 needs to be kept or not ... if not, can replace 12 with 13, and drop line 16). |
||||||||||||
| <class name="sbn::EXTCountInfo" ClassVersion="13"> | ||||||||||||
| <version ClassVersion="13" checksum="90106564"/> | ||||||||||||
| <version ClassVersion="12" checksum="3544499454"/> | ||||||||||||
|
Comment on lines
+14
to
+16
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That would be:
Suggested change
Rule of thumb is that a pull request should add at most one version per class. |
||||||||||||
| <version ClassVersion="11" checksum="2738807909"/> | ||||||||||||
| <version ClassVersion="10" checksum="1347272"/> | ||||||||||||
| </class> | ||||||||||||
|
|
||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Majority" and "MinBias" are a bit ICARUS jargon-y, could you add a comment after each explaining what they are and/or adopting a more detector agnostic naming nomenclature?