Customization to run pp reco on XeXe events

[mandrenguyen]

For the XeXe data to be delivered on October 12th, Plan A is to run the pp reconstruction sequence.
The PR customizes the pp reco for that purpose.
It consists of the following:

1. Vertexing: Tight cuts to reduce the number of spurious PVs (PU will be very low). The inclusive vertex finder selections are also tightened to save time.
2. Iterative tracking: Raise pT min and region builder thresholds for some steps. Change region builder to be centered on early PV.
3. Cluster cuts: Tune max pixel and strip cluster selections, which make tracking bail on crazy events. These cuts were check on pileup events of two central (b=0) XeXe events in MC. An extra margin was left for data/MC differences.
4. Run island photon superclusters
5. Run HI-style photon isolation
6. Keep calotowers in AOD

With these inclusions, the pp reco runs in under 30 sec in our tests, compared to about 60 sec before this customization.
For reference, HI reco runs in about 10 sec.

To test on a b=0, i.e., a super-central event, run:
cmsDriver.py step3 --conditions auto:phase1_2017_realistic -n 10 --era Run2_2017 --eventcontent RECOSIM --runUnscheduled -s RAW2DIGI,L1Reco,RECO --datatier GEN-SIM-RECO --filein /store/user/mnguyen/hydjetDrum5_XeXe_b0_920/hydjetDrum5_XeXe_b0_920/crab_Hydjet_Quenched_XeXe_B0_5442GeV_HIDIGI_920/170928_065932/0000/step2_DIGI_L1_DIGI2RAW_HLT_PU_1.root --customise RecoHI/Configuration/customise_PPwithHI.customisePPwithHI

XeXe will only be in 92X, so I haven't made a PR into the master (but I could of course).

[cmsbuild]

A new Pull Request was created by @mandrenguyen (Matthew Nguyen) for CMSSW_9_2_X.

It involves the following packages:

RecoHI/Configuration

@perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks.
@MiheeJo, @jazzitup, @echapon, @yenjie, @kurtejung, @dgulhan, @yetkinyilmaz this is something you requested to watch as well.
@davidlange6, @slava77 you are the release manager for this.

cms-bot commands are listed here

[perrotta]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/23360/console Started: 2017/10/02 14:40

[slava77]

On 10/2/17 5:33 AM, Matthew Nguyen wrote: XeXe will only be in 92X, so I haven't made a PR into the master (but I could of course).

please make a PR for the master Thank you.

[cmsbuild]

+1
Tested at: fcbb8eb
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20714/23360/summary.html

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
0393326
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20714/23360/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20714/23360/git-merge-result

[cmsbuild]

Comparison job queued.

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20714/23360/summary.html

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 23
• DQMHistoTests: Total histograms compared: 1959431
• DQMHistoTests: Total failures: 14970
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 1944289
• DQMHistoTests: Total skipped: 172
• DQMHistoTests: Total Missing objects: 0
• Checked 94 log files, 9 edm output root files, 23 DQM output files

[davidlange6]

hi @slava77 @mandrenguyen - how do you plan to propagate this to config/dataprocessing? A new scenario definition? (likely the cleanest mechanism)

[mandrenguyen]

@davidlange6 I let Slava respond to your question. As just agreed upon, I want to add relval workflow. Should I just update this PR, since it will need the customization?

[mandrenguyen]

Superseded by #20760