[10.2.X] Introduce a special AlCaReco for Strip Small Bias Scans

[mmusich]

backport of #24383

---

Greetings,
in the Tracker DPG we are trying to find a systematic solution to the chronic lack of RECO data-tier to analyze the output of SiStrip (small) Bias scans.
These scans are not affecting physics (so they are standard production runs) and therefore normally only standard AOD output is available for the high rate (ie. non commissioning) datasets, which is not enough for the sensor aging monitoring purposes.
A viable solution would be to run one of our ALCARECO producers saving tracks and Strip clusters , but this solution might be in general disfavored due to concerns about output dataset size.
Since we are scanning only few (fixed) power groups in a small bias scan and we are interested only in the clusters of tracks that have at least one hit on one of the modules being scanned, and we could select the output tracks to drastically reduce the data throughput.
This is what has been implemented in the PR.
A new track selector CalibrationTrackSelectorFromDetIdList, allowing to save a collection of track candidates leaving hits through a certain list of Tracker modules is employed in the novel SiStripCalSmallBiasScan ALCARECO producer.
The new ALCARECO producer has been added to several 2018 matrix workflows, including wf 136.85 which is in the short list used in PR tests.
To allow the ALCARECO producer to run I have changed the AlCaRecoTriggerBits in the run2_data_relval and run2_data_promptlike autoCond keys with temporary candidate GTs.
@lpernie @tocheng you might want to change them into full-fledged Global Tags.
I report here for completeness the average compressed size in bytes/event of the branches of the new ALCARECO compared with SiStripCalMinBias.

Branch name	SiStripCalMinBias	SiStripCalSmallBiasScan
recoTrackExtras	39791	1982.09
TrackingRecHitsOwned	27896.9	1505.75
recoTracks	24399.7	1160.07
SiStripClusteredmNewDetSetVector	22430.6	1043.46
SiPixelClusteredmNewDetSetVector	13553.5	1001.83
LumiScalerss_scalersRawToDigi	1179.33	951.02
EventProductProvenance	1004.8	786.41
DcsStatuss	349.09	310.52
L1AcceptBunchCrossings	217.85	196.37
edmTriggerResults	192.13	181.04
DetIdedmEDCollection	158.74	144.52
edmTriggerResults	127.18	118.99
edmTriggerResults	71.18	63.34
L1GlobalTriggerReadoutRecord	63.36	56.98
EventAuxiliary	56.24	52.17
EventSelections	28.55	24.4
BranchListIndexes	17.88	15.5

[cmsbuild]

A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_10_2_X.

It involves the following packages:

Calibration/TkAlCaRecoProducers
Configuration/AlCa
Configuration/EventContent
Configuration/PyReleaseValidation
Configuration/StandardSequences

@cmsbuild, @prebello, @zhenhu, @arunhep, @tocheng, @fabozzi, @pgunnell, @franzoni, @kpedro88, @GurpreetSinghChahal, @pohsun, @davidlange6, @fabiocos, @lpernie can you please review it and eventually sign? Thanks.
@makortel, @felicepantaleo, @GiacomoSguazzoni, @rovere, @VinInn, @Martin-Grunewald, @tocheng, @mmusich, @threus, @dgulhan this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

• Backported from [10.3.X] Introduce a special AlCaReco for Strip Small Bias Scans  #24383

[tocheng]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/30208/console Started: 2018/09/02 19:57

[cmsbuild]

+1
Tested at: 4b08e87
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-24437/30208/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 31
• DQMHistoTests: Total histograms compared: 2985378
• DQMHistoTests: Total failures: 2
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2985186
• DQMHistoTests: Total skipped: 190
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.023 KiB( 30 files compared)
• DQMHistoSizes: changed ( 136.85 ): 0.012 KiB MessageLogger/Errors
• DQMHistoSizes: changed ( 136.85 ): 0.012 KiB MessageLogger/Warnings
• Checked 129 log files, 14 edm output root files, 31 DQM output files

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 31
• DQMHistoTests: Total histograms compared: 2985378
• DQMHistoTests: Total failures: 2
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2985186
• DQMHistoTests: Total skipped: 190
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.023 KiB( 30 files compared)
• DQMHistoSizes: changed ( 136.85 ): 0.012 KiB MessageLogger/Errors
• DQMHistoSizes: changed ( 136.85 ): 0.012 KiB MessageLogger/Warnings
• Checked 129 log files, 14 edm output root files, 31 DQM output files

[lpernie]

+1

[kpedro88]

+upgrade

[mmusich]

@prebello, @zhenhu, @pgunnell,
any objection in signing this PR as its 10.3.X counterpart is now already in CMSSW_10_3_0_pre3 (and CMSSW_10_3_0_pre4)?
Thanks

[prebello]

+1

@mmusich absolutely as tests were approved after new GTs

[fabiocos]

+operations

the backport is consistent with the master version

[fabiocos]

+1

validated by M. Musich on old data, not active by default at Tier0

[mmusich]

I also checked that this works on recent data taking advantage of ConfigDP tools:

cmsrel CMSSW_10_2_4_patch1
cd CMSSW_10_2_4_patch1/src/
cmsenv
git cms-addpkg Configuration/DataProcessing
git cms-merge-topic 24437
scramv1 b -j 8
cmsenv
cd Configuration/DataProcessing/test/
python RunPromptReco.py --scenario=ppEra_Run2_2018 --reco --global-tag 102X_dataRun2_Prompt_v5 --lfn=/store/data/Run2018D/EGamma/RAW/v1/000/322/625/00000/F683DC0C-ADB4-E811-84A1-FA163E448F1D.root --alcarecos=SiStripCalSmallBiasScan

unpickle the config via [0]:

change the trigger bit selection in GT:
by adding the lines:

process.GlobalTag.toGet = cms.VPSet(
cms.PSet(record = cms.string("AlCaRecoTriggerBitsRcd"),
         tag = cms.string("test"),
         connect = cms.string('sqlite_file:/afs/cern.ch/user/m/musich/public/forStripDBcontacts/test.db')
         )
)

in the configuration file and then run with:

cmsRun myPset.py

I run over 100 events with no problem.

[0]

import pickle
pickleHandle = open('RunPromptRecoCfg.pkl','rb')
process = pickle.load(pickleHandle)
f = open('myPSet.py', 'w')
f.write(process.dumpPython())
f.close()

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_10_2_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_10_3_X is complete. This pull request will be automatically merged.