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

Complete low pT electron chain #25696

Closed
wants to merge 34 commits into from

Conversation

bainbrid
Copy link
Contributor

@bainbrid bainbrid commented Jan 17, 2019

This PR builds on top of the #25455 PR, entitled "Low pT electrons (up to GsfTracks)".

The diff with respect to #25455 is here.

In summary, the PR:

  • completes the low pT electron chain by adding new modules and extending in a minor way the functionality of the existing Seeding module;
  • does not introduce any new DataFormat and simply reuses existing ones;
  • adds new collections to the Event;
  • does not alter any of the default EGamma code and workflows,
  • integrates within the miniAOD workflows,
  • relies on a new BDT model for ID purposes, found in this PR.

The modified existing modules are:

  • LowPtGsfElectronSeedProducer: this producer is minimally extended to produce a ValueMap indexed by an ElectronSeedRef. The PreIds hold the discriminator outputs of the BDT models used by this producer but the PreIds cannot be accessed directly from the GsfElectrons and related interfaces, while the ElectronSeeds are accessible. Hence this ValueMap allows the LowPtGsfElectronSeedValueMaps module to link the BDT output from the Seeding module to electrons, details below.

The new modules are:

  • LowPtGsfElectronSCProducer: A new "tracker-driven" SuperCluster producer, seeded by extrapolating the low pT GsfTracks and brem trajectories to the ECAL.
  • LowPtGsfElectronCoreProducer: this straightforward module produces GsfElectronCore objects and borrows heavily from the standard EGamma code.
  • LowPtGsfElectronProducer: this straightforward module produces GsfElectron objects and borrows heavily from the standard EGamma code.
  • lowPtGsfElectronSeedValueMapsProducer: This module consumes GsfElectrons and the ValueMap from the LowPtGsfElectronSeedProducer module. It produces two ValueMap indexed by a GsfElectronRef that contain the BDT discriminator values.
  • LowPtGsfElectronIDProducer: this module consumes GsfElectrons and makes use of a BDT model to ID the electrons, i.e. discriminate genuine electrons from fakes. The XML description of the model can be found in this PR to the cms-data repository.
  • miniAOD integration: modifications to the PhysicsTools/PatAlgos package allow to produced a slimmed low pT electron collection.

Here is the new sequence.

Here are the output collections stored for the RECO and AOD data tiers.

Here and here are the collections stored in the miniAOD data tier.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25696/8151

  • This PR adds an extra 124KB to repository

  • Found files with invalid states:

    • Configuration/Eras/python/Modifier_BParking_cff.py:
    • Configuration/Eras/python/Modifier_bParkingOpen_cff.py:

@cmsbuild
Copy link
Contributor

Pull request #25696 was updated. @perrotta, @ssekmen, @lveldere, @civanch, @mdhildreth, @cmsbuild, @franzoni, @slava77, @santocch, @fabiocos, @davidlange6 can you please check and sign again.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@bainbrid
Copy link
Contributor Author

We have pushed a fix for errors observed with mAOD when running over data.
Please can you runTheMatrix again?

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25696/8152

  • This PR adds an extra 140KB to repository

  • Found files with invalid states:

    • Configuration/Eras/python/Modifier_BParking_cff.py:
    • Configuration/Eras/python/Modifier_bParkingOpen_cff.py:

@bainbrid
Copy link
Contributor Author

bainbrid commented Jan 23, 2019

The numbers below show the additional footprint (Bytes) to RECO and AOD from the new low pT electron collections, as determined with 25202 TTBar (PU=50). The "standard" RECO workflows use the Tight working point and pT > 1 GeV threshold. The "bParking" era uses the Loose working point and pT > 0.5 GeV threshold. It's worth noting that the "bParking" numbers are likely to be substantially smaller for data, because of a mean pileup of ~20.

Collection                                                  Standard  bParking
recoGsfTracks_lowPtGsfEleGsfTracks__RECO		      1403.0    6043.2     
recoSuperClusters_lowPtGsfElectronSuperClusters__RECO	       465.8    1655.0     
recoCaloClusters_lowPtGsfElectronSuperClusters__RECO	      2977.6    6171.7     
recoGsfElectronCores_lowPtGsfElectronCores__RECO	       124.5     276.6     
recoGsfElectrons_lowPtGsfElectrons__RECO		      3301.6   13067.0     
floatedmValueMap_lowPtGsfElectronSeedValueMaps_ptbiased_RECO   112.4     227.7     
floatedmValueMap_lowPtGsfElectronSeedValueMaps_unbiased_RECO   112.4     227.2     
floatedmValueMap_lowPtGsfElectronID__RECO                      105.0     214.7     
TOTALS                                                        8808     27880

@cmsbuild
Copy link
Contributor

Pull request #25696 was updated. @perrotta, @ssekmen, @lveldere, @civanch, @mdhildreth, @cmsbuild, @franzoni, @slava77, @santocch, @fabiocos, @davidlange6 can you please check and sign again.

@perrotta
Copy link
Contributor

@bainbrid could you please rebase on top of a recent 10_5_X IB, so that this PR will contain only the additions on top of #25679?
If you also squash all commits then you can get rid of the files with invalid state mentioned in #25696 (comment)

@bainbrid
Copy link
Contributor Author

@perrotta how does this look? Do I force push to this branch? Or create a new PR?

@perrotta
Copy link
Contributor

@bainbrid : hard to tell at the first glance. The reduction in the number of lines is rather similar to the number of lines in #25679, and this looks healty, indeed.
I would open a new PR with your latest commit, and close this one once we are sure that the operation ended up as expected.

@bainbrid
Copy link
Contributor Author

@perrotta We may have one or two final commits to make, pending some final checks. Should I still go ahead?

@perrotta
Copy link
Contributor

perrotta commented Jan 23, 2019 via email

@bainbrid
Copy link
Contributor Author

ok, I did it. #25753

@perrotta
Copy link
Contributor

-1
(the review will continue in #25753)

@bainbrid bainbrid closed this Jan 30, 2019
@bainbrid bainbrid deleted the LowPtElectronsFull_105X branch August 6, 2019 12:00
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

8 participants