-
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
AlCa Run3 Heavy Ion scenarios #39387
Conversation
assign alca |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39387/32087
|
New categories assigned: alca @yuanchao,@francescobrivio,@malbouis,@saumyaphor4252,@tvami,@ChrisMisan you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A new Pull Request was created by @malbouis for master. It involves the following packages:
@perrotta, @malbouis, @rappoccio, @yuanchao, @ChrisMisan, @emanueleusai, @ahmad3213, @tvami, @cmsbuild, @jfernan2, @pmandrik, @syuvivida, @saumyaphor4252, @rvenditti, @micsucmed, @fabiocos, @francescobrivio, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
@malbouis can you please add it to the unit test in the same folder? |
assign reconstruction |
New categories assigned: reconstruction @mandrenguyen,@clacaputo you have been requested to review this Pull request/Issue and eventually sign? Thanks |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39387/32088
|
Pull request #39387 was updated. @perrotta, @malbouis, @rappoccio, @yuanchao, @pmandrik, @mandrenguyen, @emanueleusai, @ahmad3213, @tvami, @cmsbuild, @ChrisMisan, @jfernan2, @clacaputo, @syuvivida, @saumyaphor4252, @rvenditti, @micsucmed, @fabiocos, @francescobrivio, @davidlange6 can you please check and sign again. |
DQM/TrackingMonitorSource/python/PPonPbPbTrackingOnly_custom.py
Outdated
Show resolved
Hide resolved
Pull request #39387 was updated. @perrotta, @malbouis, @rappoccio, @yuanchao, @pmandrik, @mandrenguyen, @emanueleusai, @ahmad3213, @tvami, @cmsbuild, @ChrisMisan, @jfernan2, @clacaputo, @syuvivida, @saumyaphor4252, @rvenditti, @micsucmed, @fabiocos, @francescobrivio, @davidlange6 can you please check and sign again. |
@cmsbuild , please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-667b52/27581/summary.html Comparison SummarySummary:
|
tests have passed. If there are no objections I will turn this into a full PR. |
+alca
|
+1 |
urgent
|
+1 |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will be automatically merged. |
PR description:
This is a tentative to integrate the AlCa related Run3 scenarios for the HI Run.
We have adapted three scenarios existing for Run2 2018 HI Run to create the corresponding Run3 ones, namely:
trackingOnlyEra_Run3_pp_on_PbPb
(adapted from trackingOnlyEra_Run2_2018_pp_on_AA.py ),ppEra_Run3_pp_on_PbPb
( from ppEra_Run2_2018_pp_on_AA.py )hcalnzsEra_Run3_pp_on_PbPb
(from hcalnzsEra_Run2_2018_pp_on_AA.py ).Once these scenarios are integrated, the plan is to test them with a Tier0 replay on HI 2018 data.
In order to be able to run the Express processing without crashes, we had to introduce a new customization for the offline Tracking DQM,
PPonPbPbTrackingOnly_custom.py
. @mandrenguyen, please advise and feel free to include any interested parties. We would be specially interested in knowing how will the tracking be handled for the HI and if/how we should adapt the AlCa scenarios introduced here to take it into account.PR validation:
We have used the tests below for validating each of the workflows. They all run without any crashes.
+=+=+=
trackingOnlyEra_Run3_pp_on_PbPb scenario:
+=+=+=
python3 Configuration/DataProcessing/test/RunRepack.py --lfn file:/eos/cms/store/t0streamer/Data/HIExpressAlignment/000/327/527/run327527_ls0051_streamHIExpressAlignment_StorageManager.dat
python3 Configuration/DataProcessing/test/RunExpressProcessing.py --scenario trackingOnlyEra_Run3_pp_on_PbPb --global-tag 124X_dataRun3_Express_TIER0_REPLAY_Run2_v2 --lfn file:write_PrimDS1_RAW.root --alcarecos=TkAlMinBias+PromptCalibProdBeamSpotHP
python3 Configuration/DataProcessing/test/RunAlcaSkimming.py --scenario trackingOnlyEra_Run3_pp_on_PbPb --lfn file:output.root --global-tag 124X_dataRun3_Express_TIER0_REPLAY_Run2_v2 --skims TkAlMinBias,PromptCalibProdBeamSpotHP
python3 Configuration/DataProcessing/test//RunAlcaHarvesting.py --scenario trackingOnlyEra_Run3_pp_on_PbPb --lfn file:TkAlMinBias.root --dataset /A/B/C --global-tag 124X_dataRun3_Express_TIER0_REPLAY_Run2_v2 --alcapromptdataset=PromptCalibProdBeamSpotHP
+=+=+=
ppEra_Run3_pp_on_PbPb scenario:
+=+=+=
python3 Configuration/DataProcessing/test/RunRepack.py --lfn file:/eos/cms/store/t0streamer/Data/HIExpressAlignment/000/327/527/run327527_ls0051_streamHIExpressAlignment_StorageManager.dat
python3 Configuration/DataProcessing/test/RunPromptReco.py --scenario ppEra_Run3_pp_on_PbPb --reco --aod --dqmio --global-tag 124X_dataRun3_Prompt_TIER0_REPLAY_Run2_v2 --lfn file:write_PrimDS1_RAW.root --alcareco TkAlMinBias+SiStripCalMinBias
+=+=+=
hcalnzsEra_Run3_pp_on_PbPb scenario:
+=+=+=
python3 Configuration/DataProcessing/test/RunRepack.py --lfn file:/eos/cms/store/t0streamer/Data/HIExpressAlignment/000/327/527/run327527_ls0051_streamHIExpressAlignment_StorageManager.dat
python3 Configuration/DataProcessing/test/RunPromptReco.py --scenario hcalnzsEra_Run3_pp_on_PbPb --reco --aod --dqmio --global-tag 124X_dataRun3_Prompt_TIER0_REPLAY_Run2_v2 --lfn file:write_PrimDS1_RAW.root --alcareco HcalCalMinBias
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
If/when it decided to move forward with this, it should be backported to the HI data-taking release, 125X.