Skip to content
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

Printoutpolice #10676

Merged
merged 3 commits into from Aug 11, 2015
Merged

Printoutpolice #10676

merged 3 commits into from Aug 11, 2015

Conversation

davidlange6
Copy link
Contributor

avoid filling log files while fixing bugs in L1 prescale information

vasile-ghete and others added 3 commits July 20, 2015 17:09
L1GlobalTriggerReadoutRecord product when the input tag is retrieved
from provenance and more products of this type exist, with different
input tags. 

If a single input tag is found from provenance, one keeps this input
tag.

If more  products with different input tags exist, choose the input tag
from a vector of preferred input tags (hardwired now to "gtDigis" and
"hltGtDigis"). 
The first input tag from the vector of preferred input tags, with the 
same label as the input tag found from provenance, is kept as input tag. 
No comparison is done for instance or process.

If no input tag matches the label of a preferred tag, an empty input tag
is returned: L1GtUtils will return an error code in this case.
@cmsbuild
Copy link
Contributor

A new Pull Request was created by @davidlange6 (David Lange) for CMSSW_7_4_X.

Printoutpolice

It involves the following packages:

L1Trigger/GlobalTriggerAnalyzer

@cmsbuild, @mulhearn can you please review it and eventually sign? Thanks.
@Martin-Grunewald this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@davidlange6
Copy link
Contributor Author

@cmsbuild, please test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants