-
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
New Scenarios for SD: HGCAL ee18 without Tracker Extension #10156
Conversation
A new Pull Request was created by @boudoul (boudoul) for CMSSW_6_2_X_SLHC. New Scenarios for SD: HGCAL ee18 without Tracker Extension It involves the following packages: Configuration/PyReleaseValidation The following packages do not have a category, yet: RecoParticleFlow/PandoraTranslator @cmsbuild, @srimanob, @boudoul, @franzoni can you please review it and eventually sign? Thanks. |
For 17800 (Extended2023HGCalNoExtPix_ee18 with pileup) I get a segfault in digitisation:
17662 (same but without pileup, different physics process but I don't think that's the problem) runs fine though. I guess the minimum bias file in |
thanks Mark, yes please ignore the PU (i mentionned this is the description of the PR) the minbias will be generated with a first set of relvals - Since it's a different geometry we need to produce first a consistent minbias before the PU scenario can work |
Oops, so you did. I really should pay more attention, sorry. I'll give the automatic tests on #10152 another half hour or so to complete, if they're not done by then I'll merge and ask for a release. My private tests of both PRs together should be enough, but since the tests are running might as well wait for the results. |
perfect, thanks a lot Mark ! |
merge Tested privately with #10152, details of the testing are on there. |
New Scenarios for SD: HGCAL ee18 without Tracker Extension
As requested for the Scope Document, I created a new scenario which corresponds to
the scope scenario HGCAL version ee18 but where the tracker is not extended at high eta .
This PR can only work with #10152
the New scenario are
No PU --> -l 176XX
PU --> -l 178XX
(the latter cannot work yet, we need MinBias which this new geometry which will be generated with the next set of relvals )
NB at the same time , I reduced the length of the name for the already existing hgcal descope scenario, the string length was preventing the workflows to be injected in relvals production..