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
Beamspot nominal collision2015: set new default #5464
Beamspot nominal collision2015: set new default #5464
Conversation
franzoni
commented
Sep 22, 2014
- introduce beamspot parameters as agreed during PPD General discussion https://indico.cern.ch/event/341218/ , NominalCollision2015
- the defaualt beamspot (used by ConfigBuilder if no option is specified) is updated to be NominalCollision2015
- use the NominalCollision2015 for postLs1 relvals, keep Realistic8TeVCollision in runI relvals
… left as they were, making it explicit Realistic8TeVCollision (note: Realistic8TeVCollision is still the cmsDriver default)
A new Pull Request was created by @franzoni (Giovanni Franzoni) for CMSSW_7_3_X. Beamspot nominal collision2015: set new default It involves the following packages: Configuration/PyReleaseValidation @civanch, @nclopezo, @vlimant, @mdhildreth, @cmsbuild, @franzoni, @davidlange6 can you please review it and eventually sign? Thanks. |
+1 |
+1 |
normally this change will not give good results until the reco BS is updated. Is there some reason to expect things won't be broken this time around? |
…CMSSW_7_3_X_2014-09-22-0200 Beamspot nominal collision2015: set new default
we aren't ready for this, afaik. Backing out |