-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
CTPPS: bug fix #2 in run ranges for FEDs channels mapping #18732
Merged
davidlange6
merged 5 commits into
cms-sw:CMSSW_8_0_X
from
forthommel:ctpps-runranges_patch2-8_0_X
May 19, 2017
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
483c886
Replacing the homebrewed validity ranges check by a edm::contains
forthommel 8d46580
Replacing the boost shared pointers by the STL ones
forthommel 0e9a341
Treating the event id 1:min as a special case
forthommel 897ebd3
Using the amended validity range instead of the one stored in the con…
forthommel 57dbdeb
Save twice an allocation of shared pointers using the make_shared sta…
forthommel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
just for me to understand: using event number '0' has what exact special meaning?
or phrased differently, what kind of magic happens in
EventRange
andEventID
that prevents the kind of failure mentioned by @franzoni from happening again?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.
Hi @ghellwig,
It appears that the nomenclature
<run_number>:min
used for the run ranges in the python configuration refers to the event<run_number>:0:1
instead of<run_number>:0:0
(first event effectively observed in the stream), thus preventing any channels mapping to be associated for this first, boundary, event.Again, this is a temporary workaround while a frontier conditions-based mapping is being developed!
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.
thanks for the explanation