-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Use modifier phase2_etlv4 for any scenario using MTD I12 or I13 #33130
Comments
A new Issue was created by @fabiocos Fabio Cossutti. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign upgrade (not sure who else) |
Thanks for the report @fabiocos @gsorrentino18 |
Issue solved by #33139 |
The validation of scenario D76 by @gsorrentino18 shows a dramatic drop in efficiency of ETL, incompatible with the previous validation of D73. I independently noticed that only a very small number of tracks has ETL hits associated in D76.
One possible source of the problem is the lack of https://github.com/cms-sw/cmssw/blob/master/Configuration/Eras/python/Modifier_phase2_etlV4_cff.py in the definition of the Eras used for newest scenarios, based on MTD I13, as it was done in https://github.com/cms-sw/cmssw/blob/master/Configuration/Eras/python/Era_Phase2C11_etlV4_cff.py . This should be fixed asap, @gsorrentino18 is verifying whether such a fix is enough to recover the previously observed situation.
Ideally it would be simpler to embed this in the Phase2C11 era, but this is still used also for some scenarios using MTD I11 (D64 till D71). These scenarios should not be taken seriously as far as ETL is concerned, but still if they are required to be functional an "_etlv4" version of the Eras should be provided and used.
@parbol FYI
The text was updated successfully, but these errors were encountered: