Creation of provisional Run3 (postLS2) scenario

[kpedro88]

Currently, we have some pieces of Run3 scattered here and there in CMSSW (notably run3_HB and run3_GEM Eras, used only for Phase2 at the moment).

@slava77 suggested a little while ago that it could be useful to create a full (provisional) Run3 scenario that incorporates all the postLS2 changes. I think this would be useful (and it would be nice to exercise a little foresight here, given the rush for 2017).

I propose that we start from the 2017 scenario and make all necessary changes: geometry, Eras, workflows, etc.

Geometry:

1. Either @bsunanda or I can make the HCAL topology changes for HB segmentation.
2. @calabria, can you specify which GEM components will be installed during LS2?
3. @ianna, any other geometry changes expected?
4. I propose calling the geometry 2021, based on the expected start of running after LS2 (LHC calendar). We currently have a 2019 geometry leftover from the SLHC era; this can probably be deleted unless anyone is still using it.

Eras:
We already have a Run3 Era which is Run2_2017 + run3_GEM; run3_HB can be added (I missed it previously).

Workflows:
I propose to add a set of workflows to the upgrade matrix starting with number 30000, as was foreseen a while ago.

GT:
I am not sure if @mmusich wants to start a new queue for Run3 at the moment. Personally, I think we should conserve focus for 2017 until things settle down. We can use the 2017 tag as a base. For HCAL, we can use the hardcode conditions, as we currently do for Phase2 (this also reduces the load on @abdoulline et al.). @calabria, are there any GT conditions needed for GEM?

Of course, when we put all this together, we'll have to see if it actually runs...

[cmsbuild]

A new Issue was created by @kpedro88 Kevin Pedro.

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

cms-bot commands are listed here

[kpedro88]

assign upgrade

[cmsbuild]

New categories assigned: upgrade

@kpedro88 you have been requested to review this Pull request/Issue and eventually sign? Thanks

[kpedro88]

addressed by #19889, w/ followup #20104 and related changes in #19883, #19480

[kpedro88]

+1

[cmsbuild]

This issue is fully signed and ready to be closed.