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

bsunanda:Run2-alca52 Add AlCaReo stream for muon events #15266

Merged
merged 6 commits into from Aug 26, 2016

Conversation

bsunanda
Copy link
Contributor

@bsunanda bsunanda commented Jul 22, 2016

This is in view of disappearance of RECO data. Need AlCaRecoSelector for calibrating HB/HE with muons. This is in preparation for calibration of 2017 data. Data volume required is ~1.6 TB per 1 /fb integrated luminosity with the latest correction

@bsunanda
Copy link
Contributor Author

@cmsbuild Please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 22, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/14214/console

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @bsunanda for CMSSW_8_1_X.

It involves the following packages:

Calibration/HcalAlCaRecoProducers

@ghellwig, @cerminar, @cmsbuild, @franzoni, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @tocheng this is something you requested to watch as well.
@slava77, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@bsunanda bsunanda changed the title Add AlCaReo stream for muon events bsunanda:Run2-alca52 Add AlCaReo stream for muon events Jul 24, 2016
@bsunanda
Copy link
Contributor Author

@cmsbuild Please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 24, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/14216/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@mmusich
Copy link
Contributor

mmusich commented Jul 25, 2016

@bsunanda few comments questions.
If this has to be run at Tier-0 you will need to update also:

Configuration/StandardSequences/python/AlCaRecoStreams_cff.py
Configuration/EventContent/python/AlCaRecoOutput_cff.py
Configuration/AlCa/python/autoAlCa.py

just as you did for HcalCalIsoTrkFilter in #13251.

Also, what is the expected data volume generated by this AlCaReco?

@@ -5,5 +5,5 @@
TriggerResultLabel= cms.InputTag("TriggerResults","","HLT"),
MuonLabel = cms.InputTag("muons"),
MinimumMuonP = cms.double(10.0),
Triggers = cms.vstring("HLT_IsoMu17","HLT_IsoMu20","HLT_IsoMu24","HLT_IsoMu27","HLT_Mu45","HLT_Mu50"),
Triggers = cms.vstring("HLT_IsoMu","HLT_Mu"),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bsunanda shouldn't this contain a wildcard like HLT_IsoMu* ?

@mmusich
Copy link
Contributor

mmusich commented Jul 25, 2016

For the record, an answer to my previous question was given during the AlCa/DB meeting Jul 25th.

  • Propagation of the AlCa producer to the Configuration package on hold, since the the producer is being finalized for 2017 production.
  • The expected data volume is 10TB/fb (which is too high to sustain). Hcal experts to reduce the rate by imposing a pT cut (currently under study) to reduce throughput by a factor 5-10.

@bsunanda
Copy link
Contributor Author

@mmusich It is like a wild card - within the code it looks for "HLT_IsoMu" in the trigger path. We shall update the momentum cut and trigger names to make the disk requirement to something affordable. At that time we introduce changes in the 3 cff files.

@mmusich
Copy link
Contributor

mmusich commented Jul 25, 2016

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 23, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/14653/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@bsunanda
Copy link
Contributor Author

@mmusich @ggovi Could you please approve this PR now?

@franzoni
Copy link

@bsunanda

from the discussion at yesterday's ALCa/DB meeting https://indico.cern.ch/event/560332/contributions/2280818/attachments/1325371/1989361/Phase1-Talk06.pdf
it remains clear that 1.6/1.9 TB/fb do not fit the budget for ALCARECO currently available to the overall AlCa/Db phedex group.

We asked what is the dependence of the performance of this calibration as a function of statistics, the answer to which question remains to be quantified.

We agreed on moving this PR forward to expand the studies and either reduce the rate or build a solid physics case for the resources you ask.

@franzoni
Copy link

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar

@bsunanda
Copy link
Contributor Author

@davidlange6 Please merge this PR

@davidlange6
Copy link
Contributor

not that my comment was really addressed - but I tried adding this to a workflow as it is not normally tested in the short matrix. I don't see big issues, however do we really need the dozens of value maps from muons?

@mmusich
Copy link
Contributor

mmusich commented Aug 25, 2016

@davidlange6

as it is not normally tested in the short matrix.

it actually is, via wf. 1000.0, or that's not what you are referring to?
see: HcalCalHBHEMuonFilter.root

@bsunanda
Copy link
Contributor Author

@davidlange6 We find that dropping some of the value maps we cannot proceed with the next step of final calibration. We tested that by dropping one at a time

@davidlange6
Copy link
Contributor

+1

@bsunanda - bizarre to have developed such a calibration. but ok

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

5 participants