Skip to content
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

"Showstoppers" for CMSSW_9_4_0_pre3 (and thus CMSSW_9_4_0) closing #20867

Closed
davidlange6 opened this issue Oct 9, 2017 · 15 comments
Closed

"Showstoppers" for CMSSW_9_4_0_pre3 (and thus CMSSW_9_4_0) closing #20867

davidlange6 opened this issue Oct 9, 2017 · 15 comments

Comments

@davidlange6
Copy link
Contributor

davidlange6 commented Oct 9, 2017

Please add your comments below.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 9, 2017

A new Issue was created by @davidlange6 David Lange.

@davidlange6, @Dr15Jones, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

@Martin-Grunewald
Copy link
Contributor

We (TSG) would like L1T v4 and HLT v4 to be used for the v2 MC production. The v4 menus require a set of new GTs (as the L1T menu is part of the GT) and a HLT PR with the HLT v4 menu dump.

@Martin-Grunewald
Copy link
Contributor

assign hlt

@cmsbuild
Copy link
Contributor

New categories assigned: hlt

@Martin-Grunewald,@silviodonato,@fwyzard you have been requested to review this Pull request/Issue and eventually sign? Thanks

@Martin-Grunewald
Copy link
Contributor

Martin-Grunewald commented Oct 10, 2017

To use V4 (L1T/HLT):
The HLT V4.0 PRs are available as #20872 (94X) and #20873 (92X).
They are mergable on their own as they do not yet switch relvals to HLT v4.

Still to do (needs to be done together in a PR):

  • update the L1T menu to V4 in 94X and 92X GTs (request sent to AlCa)
  • switch relvals to use V4 L1T + V4 HLT ( one-line change in Configuration/HLT/python/autoHLT.py)

@Martin-Grunewald
Copy link
Contributor

A problem has been found online with the L1T menu v4, both in its
original incarnation and in its slimmed version (the latter asked
for inclusion into the GTs) - it leads to crashes of the HLT.

Given that the problem is not understood and it is unclear whether
it is the firmware or also affecting the xml file (the latter is
used for the GTs), TSG coordination decided to stay with the current
V3 setup for the big MC production, rather than moving to V4.

Hence the deployment of the GTs with L1T v4 should be delayed until
the problem is understood, at which time we either use those updated
GTs or need to request new ones due to a fix in the xml file.
This affects both 92X and 94X.

I am sorry that this issue requires a change of the originally
envisioned plan.

(We still ask for integration of the HLT PRs ADDING the HLT v4,
it is just a delay into the switchover of GTs and @relval2017).

@slava77
Copy link
Contributor

slava77 commented Oct 12, 2017

From reco:

More critical (affects products in RECO)

Possibly critical (affects products in RECO)

Less critical (affects only miniAOD or can be redone from AOD)

@crovelli
Copy link
Contributor

Dear all, in ECAL we are checking the value of one parameter entering the sim to digi step,
https://github.com/cms-sw/cmssw/blob/master/SimCalorimetry/EcalSimProducers/python/ecalNotContainmentSim_cff.py
It may have slightly changed due to the recent changes in the simulated geometry.
Things should converge by Friday, but this is to alert you. Thanks and sorry for the very short notice - ECAL DPG

@Martin-Grunewald
Copy link
Contributor

TSG request for pre3: #20872 (94X).

@davidlange6
Copy link
Contributor Author

davidlange6 commented Oct 13, 2017

#20872 is not a showstopper as it won't be used for MC prod. (but of course if it gets integrated that will be great)

@arunhep
Copy link
Contributor

arunhep commented Oct 16, 2017

Two PRs from AlCa/DB side needed for pre3 :

  1. GT Updates with Pixel Local Reco conditions for V2 MC #20922 : Important for V2 MC production. This contains Pixel local reco conditions for V2 MC. Tracker alignment group will use pre3 relvals to produce misalignment scenario.

  2. add LumiCorrections records and definitions; adding LumiInfo.h members/methods #20651
    in pre-release so that further developments can be done as this will eventually become a PCL workflow.

  3. [94X] more Strip conditions supported by Payload Inspector #20643
    this is for Payload inspector. Further developments are waiting for this to be merged.

@lpernie @ggovi

@arunhep
Copy link
Contributor

arunhep commented Oct 16, 2017

assign alca

@cmsbuild
Copy link
Contributor

New categories assigned: alca

@cerminar,@arunhep,@franzoni,@lpernie,@ghellwig you have been requested to review this Pull request/Issue and eventually sign? Thanks

@slava77
Copy link
Contributor

slava77 commented Oct 17, 2017

New "showstopper" for reco category:

  • Introducing "Inactive" inner/outer hits... (Introducing "Inactive" inner/outer hits... #20938)
    • Due to the "unexpected" increase in inactive ROCs we need a clear estimate of REAL tracking efficiency to answer questions such as "how many tracks do not have a BPIX1 hit?" w/o this PR such a question will be much harder to answer.

@arunhep
Copy link
Contributor

arunhep commented Oct 19, 2017

+1

for 940_pre3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants