-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
AlCa DQM sequence for express stream #35850
Conversation
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35850/26223
|
A new Pull Request was created by @jfernan2 for master. It involves the following packages:
@perrotta, @qliphy, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-eea0af/19963/summary.html Comparison SummarySummary:
|
Thanks a lot @tvami I am using: CMSSW_12_1_X_2021-10-25-2300 |
the auto part of it. The is the literal version of what you need |
Hi @tvami If I try with --global-tag I get: I attach here what I do: Thanks |
Ahh I didn't know that, in that case please use |
Thanks @tvami ! python3 RunExpressProcessing.py --scenario cosmicsEra_Run2_2018 --global-tag 121X_upgrade2018cosmics_realistic_deco_v9 --lfn file:./eaceff12-9817-41eb-bc10-c133fbb62bf2.root --fevt --dqmio --alcareco SiStripCalCosmicsNano |
I don't know if we expect this to work. Running on data with an MC GT doesn't seem like something that we expect to work... I guess for a real validation one needs to create HI and Cosmics MCs. I dont think we are in a hurry anymore as the purpose of the original exercise is irrelevant now that we already have collisions (I mean that originally we wanted to study the rates, now one can just look at the relevant plot for data in today's datataking, right?) |
I agree. I did the exercise since you were asking for Cosmics and HI corner cases. |
hold |
Pull request has been put on hold by @mmusich |
the problem with:
is exactly the same thing that is described at #35586 (comment) |
Hi @jfernan2 I've created the new GTs
Please try with these, thanks! |
Thanks @tvami I confirm the first one of the two new GTs works well with the MinBias MC file, despite they are 12_1_X based and I run over 12_2_0_pre2. The command I did on top of this PR, for the records, was: python3 Configuration/DataProcessing/test/RunExpressProcessing.py --nThreads 8 --scenario ppEra_Run3 --global-tag 121X_mcRun3_2021_realistic_HI_forExpressRateStudies --lfn file:./12d0db89-7974-4418-bb7e-1e2fbb548d2e.root --fevt --dqmio --alcarecos SiStripPCLHistos+SiStripCalZeroBias+SiStripCalMinBias+SiStripCalMinBiasAAG+TkAlMinBias+LumiPixelsMinBias+SiPixelCalZeroBias+PromptCalibProd+PromptCalibProdSiStrip+PromptCalibProdSiPixelAli+PromptCalibProdSiStripGains+PromptCalibProdSiStripGainsAAG+PromptCalibProdSiPixel --dqmSeq=@express With the second (Cosmics) GT I get a crash, I guess that due to the fact that I do not have a MC Cosmic file: |
Yes, I think that's the issue indeed. |
one can generate it with one of the 7.xx wfs
|
Hi @jfernan2 I very quickly created the RAW file for you for wf 7.23 |
Thanks @mmusich @tvami python3 Configuration/DataProcessing/test/RunExpressProcessing.py --nThreads 8 --scenario cosmics --global-tag 121X_mcRun3_2021cosmics_realistic_deco_forExpressRateStudies --lfn file:./7.23_Cosmics_UP21+Cosmics_UP21+DIGICOS_UP21+RECOCOS_UP21+ALCACOS_UP21+HARVESTCOS_UP21/step2.root --fevt --dqmio --alcarecos=TkAlCosmics0T+SiStripCalZeroBias Please note that DQM sequence should be specified in case of MC Minbias/Data (@express) since none of the config files modified in this PR have a switch for mc case as cmsDriver.py does. In the case of Cosmics MC, since DQM does not distinguish between Real or Simulated Cosmics, the above statement does not apply. If not DQM sequence is specified, @standardDQM is used by default as explained in #35586 (comment) and comments onwards. |
unhold @tvami it would be perhaps convenient for future checks to include the |
Hi @mmusich hmm ok, I just thought all this was for a special case, and we dont really need to have it in autoCond for all RelVals/etc |
well, in that case you'll have to redo special GTs by hand in all future occurrences of such checks. Please state if you see any con in making this the default. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-eea0af/21432/summary.html Comparison SummarySummary:
|
Yes we did that, this is the PR #36326 |
"So, I guess I should close too the PR I made for fixing this issue which was put on hold: #35850", see Pending further clarifications, we'll keep this PR on hold |
hold |
Pull request has been put on hold by @perrotta |
@jfernan2 @tvami (periodic check): can this PR get closed, given #35586 (comment)? Or any other action is expected, also in the future? |
@perrotta I don't have objections as I have expressed before. Let me know if I should close it please. Thanks |
Thank you @jfernan2 |
PR description:
Added @express to Express pp AlCas and to UnitTest Configuration/DataProcessing/test/run_CfgTest.sh
Express AlCaRecos were taking as default DQM sequence @standardDQM which is not appropiated since not all products are available in reconstruction from AlCaReco stream. @express contains a subset of DQM sequences which fits better the AlCa streams
The corner cases for HeavyIons and Cosmics, in principle are running by default reduced sequences driven by HI and Cosmics scenarios, so the default DQM sequence seems to work and no dedicated @expressHI or @expressCosmics are needed (see below for Validation of this statement, up to GlobalTag settings). For a full validation I would need advice from @tvami about which GTs to use for Cosmics and HI
This PR solves issue #35586
Following changes suggested by @mmusich (thanks a lot!!) in:
#35586 (comment)
I understand this PR should go hand by hand with changes in Tier0 configuration for future processings setting @express there, in particular :
https://github.com/dmwm/T0/blob/master/etc/ProdOfflineConfiguration.py#L227 no DQM sequences mentioned explicitly
in https://github.com/dmwm/T0/blob/master/src/python/T0/RunConfig/Tier0Config.py#L890 initialized to an empty sequence
FYI: @mmusich @slava77 @tvami @jpata
PR validation:
python3 Configuration/DataProcessing/test/RunExpressProcessing.py --scenario HeavyIonsEra_Run2_2018 --global-tag 121X_mcRun3_2021_realistic_v11Based_forExpressRateStudies --lfn file:./F4CD260A-B956-084B-AFC3-EBFFB2A4E177.root --fevt --dqmio --alcareco TkAlMinBiasHI+SiStripCalMinBias
where input file came from: xrdcp root://cms-xrd-global.cern.ch//store/hidata/HIRun2018A/HIDoubleMuon/RAW/v1/000/327/554/00000/F4CD260A-B956-084B-AFC3-EBFFB2A4E177.root .
python3 Configuration/DataProcessing/test/RunExpressProcessing.py --scenario cosmicsEra_Run2_2018 --global-tag 121X_mcRun3_2021_realistic_v11Based_forExpressRateStudies --lfn file:./eaceff12-9817-41eb-bc10-c133fbb62bf2.root --fevt --dqmio --alcareco SiStripCalCosmicsNano
where input file came from: xrdcp root://cms-xrd-global.cern.ch//store/data/Commissioning2021/Cosmics/RAW/v1/000/345/823/00000/eaceff12-9817-41eb-bc10-c133fbb62bf2.root .