Workflow tricks

A typical workflow for the relval for the 2017 workflow (using the phase1 pixel , also true for 2018, 2019 when the only relevant change is for hcal ) , can be found like this , let's say as example for SingleMuPt10 : 
runTheMatrix.py -n | grep 2017 | grep SingleMuPt10 
--> if you type yourself this command, you will see that the Workflow number is 10007 

Therefore you if you finally type 
runTheMatrix.py -l 10007 -ne 
--> it gives you the cmsdriver commands for this particular workflow, that are actually used in Pull request test and in relvals. 
--> you can notice typing the command above that the era actually used is --era Run2_2017 

Inserting the name of this era in the github search leads you to see the config listing the various detector eras to build a 2017 CMS era : 
please look here : 
https://github.com/cms-sw/cmssw/blob/master/Configuration/Eras/python/Era_Run2_2017_cff.py 
where you can see that for the pixel it is phase1Pixel 

So looks like what you did was good (I mean by adding the modifier) . 

For the workflow you were testing 11624 (2019 configuration) , you can try to same and find out that the era is --era Run3 , therefore you could look at : 
https://github.com/cms-sw/cmssw/blob/master/Configuration/Eras/python/Era_Run3_cff.py 
which is loading 
from Configuration.Eras.Era_Run2_2018_cff import Run2_2018 
which loading the 2017 one , so we are in the same config for the pixel as before. 


Something to think about on the pixel team side is whether we would not need to deploy eras according to the year (as hcal is doing) , so far the 2017 pixel is only different that the <2016 pixel (for obvious reasons :) ) but the same as in 2018 , 2019 - Perhaps one should think to have different reconstruction (or simulation) configurations/parameters depending on the years even for the same pixels. Maybe this is irrelevant , but in case the era mechanism will be easily to implement.