Upgarde Tracker pahse1&2 Development configuration #5720
Conversation
|
A new Pull Request was created by @boudoul (boudoul) for CMSSW_6_2_X_SLHC. Upgarde Tracker pahse1&2 Development configuration It involves the following packages: Configuration/Geometry @civanch, @Dr15Jones, @vlimant, @ianna, @mdhildreth, @cmsbuild, @franzoni, @nclopezo, @ktf, @davidlange6 can you please review it and eventually sign? Thanks. |
|
I took the liberty to update this PR with the new digitizer (in the dev customisations, so no worry for the official WF) |
|
Pull request #5720 was updated. @civanch, @Dr15Jones, @vlimant, @ianna, @mdhildreth, @cmsbuild, @franzoni, @nclopezo, @ktf, @davidlange6 can you please check and sign again. |
| from SLHCUpgradeSimulations.Configuration.phase1TkCustomsPixel10D import customise as customisePhase1TkPixel10D | ||
| from SLHCUpgradeSimulations.Configuration.combinedCustoms_TTI import customise as customiseTTI | ||
| from SLHCUpgradeSimulations.Configuration.combinedCustoms_TTI import l1EventContent_TTI as customise_ev_l1tracker | ||
| from SLHCUpgradeSimulations.Configuration.combinedCustoms_TTI import l1EventContent_TTI_forHLT | ||
|
|
||
| from SLHCUpgradeSimulations.Configuration.customise_mixing import customise_NoCrossing | ||
| from SLHCUpgradeSimulations.Configuration.phase1TkCustoms import customise as customisePhase1Tk | ||
| from SLHCUpgradeSimulations.Configuration.phase1TkCustomsdev import customise as customisePhase1Tkdev |
There was a problem hiding this comment.
@boudoul
This line should be in addition instead of replacing, otherwise the non-dev cust_2017 and cust_2019 don't work. I have it fixed in a branch which I'm currently testing and will merge soon - no need for you to do anything. Sorry for the delay.
|
Superseded by #5810. This should close automatically when that is merged. |
|
Thanks @mark-grimes ! Sorry I didn't check my git folder for a few days and I read with a bit of delay your comments/ work - Perfect- Thanks for having noticed the pb with 2017 and 2019! |
Configuring dev scenarios for tracker phase1 and phase2 :
xmls/ config are for the moment clone in dev folders and dev extensions to allow further developments without disturbing anybody (in particular TP MC production) - To test these 2 new scenarios I used runTheMatrix.py --what upgrade -l 10600,10800 (or in general 106xx for phase1 and 108xxx for phase2 - those are replacing the old Be5Dfast and 2017fast never used)
None of the usual numbering in runthematrix is touched (which means that this should be transparent for any shashlik , hgcal etc .. scenarios ) - I took also this opportunity to remove LongBarrel old config files (deprecated for 1.5 years)