-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Configure DtCalib AlCaReco for heavy Ion 2018 #25004
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25004/6982 |
A new Pull Request was created by @tocheng (Tongguang) for master. It involves the following packages: CalibMuon/DTCalibration @cmsbuild, @franzoni, @pohsun, @tocheng, @lpernie can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
The tests are being triggered in jenkins. |
|
||
OutALCARECODtCalibHI = copy.deepcopy(OutALCARECODtCalib_noDrop) | ||
OutALCARECODtCalibHI.outputCommands.insert(0, "drop *") | ||
OutALCARECODtCalibHI.outputCommands.append("keep *_hiSelectedVertex_*_*") |
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.
Hi @tocheng I am wondering is this event product available with thepp_on_AA_2018
era customisations?
@mandrenguyen
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.
@mmusich Thanks for pointing it out. I checked the configuration generated using DP config with pp_on_AA scenario, the hiSelectedVertex is not in the sequence. It should be the module in heavyIon typed reconstruction. I can remove it after the test is done.
Hello @fabiocos, @slava77, python $CMSSW_BASE/src/Configuration/DataProcessing/test/RunExpressProcessing.py --scenario ppEra_Run2_2018_pp_on_AA --global-tag 103X_dataRun2_Express_v1 --lfn /store/t0streamer/Data/HIExpress/000/325/112/run325112_ls0013_streamHIExpress_StorageManager.dat --fevt --dqmio --alcareco DtCalib and then changing the event source with:
while doing the same in 10.4.X I notice I incur in this error:
the same error is also obtained in a vanilla |
No, hiSelectedVertex is not available.
It’s from the old HeavyIons scenario.
With the pp_on_AA era, we use offlinePrimaryVertices
… On Oct 25, 2018, at 23:04, Marco Musich ***@***.***> wrote:
Hello @fabiocos, @slava77,
while this PR runs fine in the last IB of 10.3.X using:
python $CMSSW_BASE/src/Configuration/DataProcessing/test/RunExpressProcessing.py --scenario ppEra_Run2_2018_pp_on_AA --global-tag 103X_dataRun2_Express_v1 --lfn /store/t0streamer/Data/HIExpress/000/325/112/run325112_ls0013_streamHIExpress_StorageManager.dat --fevt --dqmio --alcareco DtCalib
and then changing the the event source with:
process.source = cms.Source("NewEventStreamFileReader"
while doing the same in 10.4.X I notice I incur in this error:
----- Begin Fatal Exception 25-Oct-2018 22:56:57 CEST-----------------------
An exception of category 'ScheduleExecutionFailure' occurred while
[0] Calling beginJob
Exception Message:
Unrunnable schedule
Module run order problem found:
hiConformalPixelTracks after hiConformalPixelTracksPhase1Filter [path reconstruction_step], hiConformalPixelTracksPhase1Filter after pixelFitterByConformalMappingAndLine [path reconstruction_step], pixelFitterByConformalMappingAndLine after hiConformalPixelTracksPhase1HitQuadrupletsCA [path reconstruction_step], hiConformalPixelTracksPhase1HitQuadrupletsCA after hiConformalPixelTracksPhase1HitDoubletsCA [path reconstruction_step], hiConformalPixelTracksPhase1HitDoubletsCA after hiConformalPixelTracksPhase1SeedLayers [path reconstruction_step], hiConformalPixelTracksPhase1SeedLayers after hiConformalPixelTracksPhase1TrackingRegions [path reconstruction_step], hiConformalPixelTracksPhase1TrackingRegions after hiClusterCompatibility [path reconstruction_step], hiClusterCompatibility after hiCentrality [path reconstruction_step], hiCentrality consumes hiConformalPixelTracks
Running in the threaded framework would lead to indeterminate results.
Please change order of modules in mentioned Path(s) to avoid inconsistent module ordering.
----- End Fatal Exception -------------------------------------------------
the same error is also obtained in a vanilla CMSSW_10_4_X_2018-10-25-1100.
Is there any substantial difference between the tip of 10.3.X and the tip of 10.4.X that can cause this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Comparison job queued. |
The code-checks are being triggered in jenkins. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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 now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
@tocheng did you verify it works? If I use your recipe python $CMSSW_BASE/src/Configuration/DataProcessing/test/RunExpressProcessing.py --scenario ppEra_Run2_2018_pp_on_AA --global-tag 103X_dataRun2_Express_v1 --lfn /store/whatever --fevt --dqmio --alcareco DtCalib and replace the input with process.source = cms.Source("NewEventStreamFileReader", I get the following problem: ----- Begin Fatal Exception 26-Oct-2018 06:44:50 CEST----------------------- |
@fabiocos
|
+1 |
Greetings,
The PR is to add DtCalibHI into the AlCaReco stream.
The DtCalib in the AlCaReco stream is replaced by sequence in DtCalibHI using the pp_on_AA_2018 era.
Also the DtCalibOutput is replaced by the DtCalibHIOut using the pp_on_AA_2018 era.
The configuration is checked using
python $CMSSW_BASE/src/Configuration/DataProcessing/test/RunExpressProcessing.py --scenario ppEra_Run2_2018_pp_on_AA --global-tag 103X_dataRun2_Express_v1 --lfn /store/whatever --fevt --dqmio --alcareco DtCalib
After changing pickle to python config,
one can see that the DtCalib path and output is replaced by the path and output in DtCalibHI