Skip to content
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

HCAL 2017 Phase1 Workflows #15889

Merged
merged 18 commits into from
Sep 23, 2016
Merged

HCAL 2017 Phase1 Workflows #15889

merged 18 commits into from
Sep 23, 2016

Conversation

kpedro88
Copy link
Contributor

@kpedro88 kpedro88 commented Sep 17, 2016

Long-anticipated... thanks to @mmusich for the autocond in #15884.

This PR adds two new workflows: 2017HCALdev ("old" pixel with new HCAL geometry/conditions/customizations for 2017) and 2017AllNew ("new" pixel with new HCAL).

Tested using workflows 10624.0, 10824.0 (ttbar, HCALdev and AllNew respectively).

@igv4321, @mariadalfonso, let me know if I missed any reco settings you want to have turned on by default.

attn: @abdoulline, @lihux25, @hatakeyamak, @pdudero

@kpedro88
Copy link
Contributor Author

@cmsbuild please test

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @kpedro88 (Kevin Pedro) for CMSSW_8_1_X.

It involves the following packages:

Configuration/Eras
Configuration/PyReleaseValidation
Configuration/StandardSequences
DQM/HcalTasks
EventFilter/HcalRawToDigi
EventFilter/RawDataCollector
RecoLocalCalo/Configuration
RecoLocalCalo/HcalRecProducers

@dmitrijus, @cvuosalo, @emeschi, @franzoni, @fabozzi, @cmsbuild, @srimanob, @slava77, @mommsen, @vanbesien, @hengne, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @makortel, @GiacomoSguazzoni, @rovere, @VinInn, @Martin-Grunewald, @deguio, @mariadalfonso, @dgulhan this is something you requested to watch as well.
@slava77, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 17, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/15233/console

@cmsbuild
Copy link
Contributor

-1

Tested at: a19eefb

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
813e5ad
51dd54a
12077f8
851461b
5cb0fc2
43dfd1b
032ad55
3cfd184
4c378a3
f569019
941fa6e
a53847c
a03ca88
bc0c679
af763d9
ec5ff3c
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-15889/15233/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-15889/15233/git-merge-result

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

I found follow errors while testing this PR

Failed tests: RelVals

  • RelVals:

When I ran the RelVals I found an error in the following worklfows:
20824.0 step3

runTheMatrix-results/20824.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2023D3_GenSimFull+DigiFull_2023D3+RecoFullGlobal_2023D3+HARVESTFullGlobal_2023D3/step3_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2023D3_GenSimFull+DigiFull_2023D3+RecoFullGlobal_2023D3+HARVESTFullGlobal_2023D3.log

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
813e5ad
51dd54a
12077f8
851461b
5cb0fc2
43dfd1b
032ad55
3cfd184
4c378a3
f569019
941fa6e
a53847c
a03ca88
bc0c679
af763d9
ec5ff3c
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-15889/15233/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-15889/15233/git-merge-result

@kpedro88
Copy link
Contributor Author

Looks like an IB issue, let's try again with the new one

@kpedro88
Copy link
Contributor Author

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 17, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/15241/console

@cmsbuild
Copy link
Contributor

-1

Tested at: a19eefb

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

I found follow errors while testing this PR

Failed tests: RelVals

  • RelVals:

When I ran the RelVals I found an error in the following worklfows:
20824.0 step3

runTheMatrix-results/20824.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2023D3_GenSimFull+DigiFull_2023D3+RecoFullGlobal_2023D3+HARVESTFullGlobal_2023D3/step3_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2023D3_GenSimFull+DigiFull_2023D3+RecoFullGlobal_2023D3+HARVESTFullGlobal_2023D3.log

@kpedro88
Copy link
Contributor Author

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 18, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/15246/console

@slava77
Copy link
Contributor

slava77 commented Sep 22, 2016

On 9/22/16 11:07 AM, Kevin Pedro wrote:

@slava77 https://github.com/slava77 this is the best way to remove
|HBHEChannelInfo| from the event products, according to @igv4321
https://github.com/igv4321

OK, if you do not need them produced, it is even better.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#15889 (comment), or
mute the thread
https://github.com/notifications/unsubscribe-auth/AEdcbjb3pOFPmw6CivyclgMSWg2mxhdzks5qssPogaJpZM4J_ha_.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

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

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • 10424.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2017NewFPix_GenSimFull+DigiFull_2017NewFPix+RecoFull_2017NewFPix+HARVESTFull_2017NewFPix

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

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

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • 10424.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2017NewFPix_GenSimFull+DigiFull_2017NewFPix+RecoFull_2017NewFPix+HARVESTFull_2017NewFPix

@slava77
Copy link
Contributor

slava77 commented Sep 23, 2016

Looking at jenkins output (done with CMSSW_8_1_X_2016-09-22-0900)

  • 10024 has all hbhe flags disappear

all_oldvsnew_ttbar13tev2017wf10024p0c_hbherechitssorted_hbhereco__reco_obj_obj_flags
otherwise, downstream reco objects appear to be unchanged. This is probably not so good for the flags, but it is good enough for the purpose of keeping the default old 2017 hcal setup unchanged.

@slava77
Copy link
Contributor

slava77 commented Sep 23, 2016

+1

for #15889 21e6fec

  • new workflows, including full HCAL 2017 setup (still XML, but apparently OK for now). The PR description and title has to be updated to describe what was added. The current default 2017 as in pre11 is essentially preserved (modulo the flag settings).
  • jenkins tests pass and comparisons with baseline show changes only in 2017 workflows in hcal flags (there is no cross-comparison between scenarios, which would have shown some more noticeable changes)
  • signoff for reco relies mostly on results of comparisons as of Monday (commit range in the latest version of this PR is 86cd2d7...909daed) which included what now would be a cross-workflow comparison of "2017" and "2017HCALdev" workflows (see HCAL 2017 Phase1 Workflows #15889 (comment))
    • hbhe channel infos are now not saved, which should reduce the increase in RECO on disk by ~2/3.

@slava77
Copy link
Contributor

slava77 commented Sep 23, 2016

given a possibility to compare the 4 types of 2017 workflows even with the short matrix,
it may be more productive to merge this and then aim to fix up the DB geometry and related GT updates separately rather than converge on a more perfect setup.

@kpedro88 kpedro88 changed the title HCAL 2017 Phase1 Workflow HCAL 2017 Phase1 Workflows Sep 23, 2016
@kpedro88
Copy link
Contributor Author

@slava77 updated the title and description

@ianna
Copy link
Contributor

ianna commented Sep 23, 2016

+1

@davidlange6 davidlange6 merged commit 831786b into cms-sw:CMSSW_8_1_X Sep 23, 2016
@ianna
Copy link
Contributor

ianna commented Sep 23, 2016

@mmusich - just for the record: HCal 2017dev simulation geometry as in XMLFILE_Geometry_81YV8_Extended2017dev_mc is fine. Here is one built from XML vs DB one - they are identical:
screenshot 2016-09-23 12 42 39
screenshot 2016-09-23 12 46 50

@mmusich
Copy link
Contributor

mmusich commented Sep 23, 2016

@ianna, thanks does this mean that #15889 (comment) had a bug in it?

@bsunanda
Copy link
Contributor

@ianna I find strange results from the geometry in data base. I am using the xml geometry using the lines:
process.load('Geometry.CMSCommonData.cmsExtendedGeometry2017devXML_cfi')
process.load('Geometry.HcalCommonData.hcalDDConstants_cff')
process.load("Geometry.HcalEventSetup.hcalTopologyIdeal_cfi")
and compare with results from DB using the prescription from you
process.load("Configuration.StandardSequences.FrontierConditions_GlobalTag_cff")
from Configuration.AlCa.autoCond import autoCond
process.GlobalTag.globaltag = autoCond['phase1_2017_hcaldev']
process.load('Configuration.StandardSequences.GeometryDB_cff')

I do not see any difference in the HcalParameters as used in the test for HcalParameters, HcalSimNumberingConstants or HcalRecNumberingConstants. But there are large differences in the geometry values. The number of ValidId's are the same but the centers and the corners are widely different which cannot be due to rounding. I wonder what could have caused this,

@ianna
Copy link
Contributor

ianna commented Sep 26, 2016

@bsunanda - I've opened a separate issue #15985

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants