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
Forward port CMSSW_7_0_X into CMSSW_7_1_X (Fixed Conflicts) #4207
Conversation
…ng wherever needec by premix workflows; TEMPORARY
…sequent releases)
…e with premixed events
…sure RECO of prod premix workflows use consistent GT
…en prescale column
…up_70x hltGetConfiguration cleanup for 7.0.x
…-23-0200-premixPROD2 premix relvals: adapt to fixes of premixing
…ix_from-CMSSW_7_0_X_2014-05-23-1400 Fix for jet flavour clustering: Backport from 7_1_X to 7_0_X
Conflicts: Configuration/PyReleaseValidation/python/relval_steps.py
A new Pull Request was created by @nclopezo (David Mendez) for CMSSW_7_1_X. Forward port CMSSW_7_0_X into CMSSW_7_1_X (Fixed Conflicts) It involves the following packages: Configuration/PyReleaseValidation @nclopezo, @vlimant, @cmsbuild, @franzoni, @Degano, @davidlange6 can you please review it and eventually sign? Thanks. |
steps['DIGIPRMXUP15_PROD_PU25']=merge([premixProd,digiPremixUp2015Defaults25ns]) | ||
steps['DIGIPRMXUP15_PROD_PU50']=merge([premixProd,digiPremixUp2015Defaults50ns]) | ||
|
||
|
||
dataReco={'--conditions':'auto:run1_data', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left this as it is in CMSSW_7_1_X
Forward port CMSSW_7_0_X into CMSSW_7_1_X (Fixed Conflicts)
I continued with the forward port done here #4190
I fixed the conflicts that were in the file:
Configuration/PyReleaseValidation/python/relval_steps.py
I left what currently is in 7_1_X, I would like to know if this is correct.