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
External conditions (technical) triggers for L1 Stage2. #13905
External conditions (technical) triggers for L1 Stage2. #13905
Conversation
…mulation sequence.
A new Pull Request was created by @rekovic for CMSSW_8_1_X. It involves the following packages: L1Trigger/Configuration @cmsbuild, @rekovic, @mulhearn, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
+1 |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
@rekovic |
@Martin-Grunewald There is no packer or unpacker for this external In HLT, the GT emulator uses the external conditions as part of the unpacked GT information process.hltGtStage2ObjectMap = cms.EDProducer("L1TGlobalProducer", MuonInputTag = cms.InputTag("hltGmtStage2Digis","Muon"), ExtInputTag = cms.InputTag("hltGtStage2Digis"), # (external conditions are not emulated, use unpacked) Now, in simulation, we run the The GT emulator is configured to use it Now, if we want to re-emulate on Legacy 2015 data, the above producer in the simulation We can add this configuration specialisation. It is good to run on MC as is. |
@rekovic |
@Martin-Grunewald Yes, exactly. |
const TechnicalTriggerWord& gtTTWord = gtReadoutRecord->technicalTriggerWord(useBx); | ||
int tbitNumber = 0; | ||
TechnicalTriggerWord::const_iterator GTtbitItr; | ||
bool pass_BptxAND = false; |
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.
I would suggest putting these 4 bools into an array - then all the if statements below do not need the if elses
Pull request #13905 was updated. @cmsbuild, @rekovic, @mulhearn, @davidlange6 can you please check and sign again. |
@Martin-Grunewald Additions with customisation for cmsDriver will come in separately. |
+1 please test |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
bool pass_BptxMinus = false; | ||
bool pass_BptxOR = false; | ||
|
||
std::vector<bool> pass_externs(4, false); //BptxAND, BptxPlus, BptxMinus, BptxOR |
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.
even better if std::array - maybe next time?
+1 |
New producer for external conditions triggers for Stage2.
Included now in the L1T simulation sequence for Stage2.