-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Add new reco::Muon 'displacedMuons' collection to AOD #36926
Add new reco::Muon 'displacedMuons' collection to AOD #36926
Conversation
…splacedStandAloneMuons to create a recoMuon collection with MuonReducedTrackExtras
…CO now but not in AOD, remove unecessary producers.
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36926/28246
|
A new Pull Request was created by @CeliaFernandez (Celia Fernández Madrazo) for master. It involves the following packages:
@jpata, @cmsbuild, @clacaputo, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
-1 Failed Tests: RelVals AddOn RelVals
Expand to see more relval errors ...AddOn Tests
|
…onstruction is not available there
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36926/28271
|
Pull request #36926 was updated. @jpata, @cmsbuild, @clacaputo, @slava77 can you please check and sign again. |
@@ -0,0 +1,103 @@ | |||
# This file name is temporary and ment for development only. |
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.
Maybe these two lines are outdated. If so, could you remove them?
@@ -36,6 +36,15 @@ | |||
#'drop *_muons_muons1stStep2muonsMap_*', | |||
#'drop recoIsoDepositedmValueMap_muons_*_*', #not really used | |||
#'drop doubleedmValueMap_muons_muPFIso*_*', #already inside the muon | |||
# displacedMuons collection | |||
'keep recoMuons_displacedMuons_*_*', |
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.
Do you know what is the contribution to the total size increase given by each of these new collections?
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.
We have computed it in a ttbar sample (runTheMatrix.py workflow 11634.0). The table with the size increase is in slide 28 of this presentation: https://cernbox.cern.ch/index.php/s/FfAZonfSest7kqQ
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-e70a53/22411/summary.html Comparison SummarySummary:
|
|
test parameters:
|
after discussing with David and Danilo:
|
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-e70a53/22551/summary.html Comparison SummarySummary:
|
Just for reference:
|
I checked with very reduced statistics, 2000-2500 events. |
Hi @CeliaFernandez , could you please check the size increase on wf |
Hi @clacaputo , I'm working on checking the size increase with the mentioned workflow. However, I have seen that when I run it I get several warning/error messages which I'm not pretty sure if they come from the implementation, the workflow itself or some bad configuration that I'm setting... For example, for step 3 (the one mentioned above):
I got this for most of the events... Is this normal? |
this is a known issue #35798 and should not affect your studies |
I compute the sizes again with the 11834.21 workflow. I did it with 1k events, which is the number used to compute the numbers above (I revisited the computation and I found that only 1k events were used), and also with a total of 16k which is the number of events we produced to obtain the validation plots. For the 1k sample I obtain a +1% relative increase, and with the 16k sample, a +0.97% relative increase. These numbers doesn't match with yours... Maybe we are missing something and we are underestimating the increase in size? We are computing these numbers with the methods provided in printSizes.C macro, that you can find here: https://root.cern/doc/v610/printSizes_8C_source.html I also attach 2 txt files with the space taken by each branch in case you want to check: |
Hi @CeliaFernandez , thanks for having performed the measurement using So, considering that the size increase is
Did @cms-sw/muon-pog-l2 have the chance to start a discussion with EXO ? |
Not yet, we will start the discussion soon. In this moment we are developing a filter that will reduce the increase by removing overlapping muons with standard 'muons' collection. If the filter is efficient, we will also estimate the increase in MiniAOD to see if it is doable to extend the implementation there. In case you want to do a quick estimate, one file is available here: |
type muon |
since you opened #37805, can you close this one here? |
PR description:
This PR adds a new reco::Muon collection, called 'displacedMuons', that includes the dedicated displaced muon reconstructions: 'displacedTracks', 'displacedGlobalMuons' and 'displacedStandAloneMuons' (all of them saved in AOD as reco::Track collections).
In this PR we add the necessary modifications to:
The sequences are implemented to run independently to the default reco::Muon 'muons' collection and avoid interferences. Muons of the 'muons' collection should remain untouchable. They also emulate the existing implementation and make use of the existing tools and sequences so the new information is computed with the default parameters configuration.
The following packages are modified:
The increase in size was measured by using a ttbar benchmark model (runTheMatrix.py workflow 11634.0), where we obtained a relative increase of the 1.23%
Backup documentation, detailed information about the modifications and validation can be found here: https://cernbox.cern.ch/index.php/s/FfAZonfSest7kqQ
The implementation was built on top of CMSSW_12_3_0_pre2
@gkaratha @sscruz @trocino
PR validation:
We have checked out all dependencies and have a clean build.
The actions defined in the new sequences were validated and these results are presented in the backup documentation:
https://cernbox.cern.ch/index.php/s/FfAZonfSest7kqQ