make hcal digitization changes the default

[davidlange6]

time slew parameters and hf1 sampling factors now the default - consistent with GT in 76x already

[cmsbuild]

A new Pull Request was created by @davidlange6 (David Lange) for CMSSW_7_6_X.

make hcal digitization changes the default

It involves the following packages:

RecoLocalCalo/HcalRecProducers
SLHCUpgradeSimulations/Configuration
SimCalorimetry/HcalSimProducers

@cmsbuild, @cvuosalo, @civanch, @mdhildreth, @slava77 can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[davidlange6]

@cmsbuild, please test

[cmsbuild]

The tests are being triggered in jenkins.

[cmsbuild]

-1

Tested at: e7b3117
I found errors in the following addon tests:

cmsDriver.py RelVal -s HLT:50nsGRun,RAW2DIGI,L1Reco,RECO --data --scenario=pp -n 10 --conditions auto:run2_data_50nsGRun --relval 9000,50 --datatier "RAW-HLT-RECO" --eventcontent FEVTDEBUGHLT --customise=HLTrigger/Configuration/CustomConfigs.L1THLT --customise=SLHCUpgradeSimulations/Configuration/postLS1Customs.customisePostLS1_50ns --magField 38T_PostLS1 --processName=HLTRECO --filein file:RelVal_Raw_50nsGRun_DATA.root --fileout file:RelVal_Raw_50nsGRun_DATA_HLT_RECO.root : FAILED - time: date Wed Oct 7 22:23:15 2015-date Wed Oct 7 22:18:53 2015 s - exit: 16640
cmsDriver.py RelVal -s HLT:PIon,RAW2DIGI,L1Reco,RECO --data --scenario=pp -n 10 --conditions auto:run2_data_PIon --relval 9000,50 --datatier "RAW-HLT-RECO" --eventcontent FEVTDEBUGHLT --customise=HLTrigger/Configuration/CustomConfigs.L1THLT --customise=SLHCUpgradeSimulations/Configuration/postLS1Customs.customisePostLS1 --magField 38T_PostLS1 --processName=HLTRECO --filein file:RelVal_Raw_PIon_DATA.root --fileout file:RelVal_Raw_PIon_DATA_HLT_RECO.root : FAILED - time: date Wed Oct 7 22:31:51 2015-date Wed Oct 7 22:28:54 2015 s - exit: 16640
cmsDriver.py RelVal -s HLT:GRun,RAW2DIGI,L1Reco,RECO --data --scenario=pp -n 10 --conditions auto:run2_data_GRun --relval 9000,50 --datatier "RAW-HLT-RECO" --eventcontent FEVTDEBUGHLT --customise=HLTrigger/Configuration/CustomConfigs.L1THLT --customise=SLHCUpgradeSimulations/Configuration/postLS1Customs.customisePostLS1 --magField 38T_PostLS1 --processName=HLTRECO --filein file:RelVal_Raw_GRun_DATA.root --fileout file:RelVal_Raw_GRun_DATA_HLT_RECO.root : FAILED - time: date Wed Oct 7 22:39:05 2015-date Wed Oct 7 22:34:10 2015 s - exit: 16640

you can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-11675/8676/summary.html

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-11675/8676/summary.html

[davidlange6]

@slava77 - the customizeHLTforMC function is not touched in this PR - I think it can be removed though.

[slava77]

On 10/8/15 1:00 AM, David Lange wrote:

@slava77 https://github.com/slava77 - the customizeHLTforMC function
is not touched in this PR - I think it can be removed though.

OK.
But this also means that this PR modifies only DIGI step in a noticeable
way.

—
Reply to this email directly or view it on GitHub
#11675 (comment).

[davidlange6]

On Oct 8, 2015, at 8:09 AM, Slava Krutelyov [email protected] wrote:

On 10/8/15 1:00 AM, David Lange wrote:

@slava77 https://github.com/slava77 - the customizeHLTforMC function
is not touched in this PR - I think it can be removed though.

OK.
But this also means that this PR modifies only DIGI step in a noticeable
way.

ah - sorry - indeed, I need to update that. Thanks!

—
Reply to this email directly or view it on GitHub
#11675 (comment).

—
Reply to this email directly or view it on GitHub.