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
Update Standard Sequences for L1T in 2016 #13271
Conversation
please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @mulhearn for CMSSW_8_0_X. It involves the following packages: Configuration/StandardSequences @cmsbuild, @franzoni, @mulhearn, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
-1 runTheMatrix-results/1306.0_SingleMuPt1_UP15+SingleMuPt1_UP15+DIGIUP15+RECOUP15+HARVESTUP15/step3_SingleMuPt1_UP15+SingleMuPt1_UP15+DIGIUP15+RECOUP15+HARVESTUP15.log 1330.0 step3 runTheMatrix-results/1330.0_ZMM_13+ZMM_13+DIGIUP15+RECOUP15+HARVESTUP15/step3_ZMM_13+ZMM_13+DIGIUP15+RECOUP15+HARVESTUP15.log 50202.0 step3 runTheMatrix-results/50202.0_TTbar_13+TTbar_13+DIGIUP15_PU50+RECOUP15_PU50+HARVESTUP15_PU50/step3_TTbar_13+TTbar_13+DIGIUP15_PU50+RECOUP15_PU50+HARVESTUP15_PU50.log 25202.0 step3 runTheMatrix-results/25202.0_TTbar_13+TTbar_13+DIGIUP15_PU25+RECOUP15_PU25+HARVESTUP15_PU25/step3_TTbar_13+TTbar_13+DIGIUP15_PU25+RECOUP15_PU25+HARVESTUP15_PU25.log you can see the results of the tests here: The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
please test |
@Martin-Grunewald this version satisfies the requirement that every parameter has a default value. Parameters in HLT/L1T interface are still singled out (in comments). |
@mulhearn |
Update Standard Sequences for L1T in 2016
@davidlange6 , could this Pr be the cause of few of RelVals failures in 80X IB
|
Yes, it is.. @mulhearn is fixing |
Hi In todays IB CMSSW_8_0_X_2016-02-15-2300 I find the following
I suspect it to be related to this PR. |
import L1Trigger.RPCTechnicalTrigger.rpcTechnicalTrigger_cfi | ||
simRpcTechTrigDigis = L1Trigger.RPCTechnicalTrigger.rpcTechnicalTrigger_cfi.rpcTechnicalTrigger.clone() | ||
#import L1Trigger.RPCTechnicalTrigger.rpcTechnicalTrigger_cfi | ||
#simRpcTechTrigDigis = L1Trigger.RPCTechnicalTrigger.rpcTechnicalTrigger_cfi.rpcTechnicalTrigger.clone() |
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.
This broke a number of IB RelVal workflows. E.g. see
Hmm, in my error case, my tests also works fine in CMSSW_8_0_X_2016-02-15-1100 which |
#13206 didn't get into the IB until CMSSW_8_0_X_2016-02-15-2300 but the failures started in the IB before that (CMSSW_8_0_X_2016-02-15-1300) which is where this pull request came in. @Martin-Grunewald notice that there was an additional IB run (1300 after 1100) after your test. |
@Dr15Jones |
@Martin-Grunewald can you tell me what work flow failed in IB so that I can investigate? |
All the tests that returned 256 failed because of the python configuration problem https://cms-sw.github.io/relvalLogDetail.html#slc6_amd64_gcc493;CMSSW_8_0_X_2016-02-15-1300 |
@mulhearn - it is one in our TSG tests (have not checked relval IB tests), look at the RelVal_RECO_GRun_DATA.log file: |
BTW, "my" problem is not fixed by #13298 ... and has exit status 65, not 256... |
@mulhearn
the above script generates several cfg files and then runs some of them leading to the observed error. |
I can reproduce it. It is a problem with "DQMOffline.Configuration.DQMOffline_cff"... |
Fine... OK... I'll just unpack everything always... |
OK, fix is here: #13310 |
Updates the standard sequences for RawToDigi, DigiToRaw, and SimL1Emulation using Eras to correctly configure these sequences based on the Legacy, Stage-1 (2015), or Stage-2 (2016+) L1 trigger.
It adds a new version of L1REPACK (Full) which re-Emulates the entire L1T including HF Trigger Primitives. This is currently only supported for the Stage-2 Era.
The intention is that the new features (supporting Stage-2 configuration via Eras) will not disrupt the legacy and 2015 RelVals, and recent successful tests indicate this is indeed working.
Since it is not yet included in any rel vals, a simple test of the new L1REPACK feature is to run:
cmsDriver.py RepackTest -s L1REPACK:Full,RAW2DIGI --era=Run2_2016 --conditions=auto:run2_data -n 10 --data --filein=/store/data/Run2015D/ZeroBias/RAW/v1/000/260/627/00000/00A76FFA-0C82-E511-B441-02163E01450F.root --no_output --customise=L1Trigger/Configuration/customiseUtils.L1TStage2DigisSummary
which L1REPACK's followed by vanilla RAW2DIGI and a screen dump of the Stage-2 output.