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

bsunanda:Run2-hcx67 Default 2017 scenario which has 2017 pixel but 2016 HCAL #13307

Merged
merged 2 commits into from Feb 19, 2016

Conversation

bsunanda
Copy link
Contributor

The 2017dev version has 2017 pixel and 2017 HCAL

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @bsunanda for CMSSW_8_0_X.

It involves the following packages:

Configuration/Geometry
Geometry/CMSCommonData

@civanch, @Dr15Jones, @ianna, @mdhildreth, @cmsbuild, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@bsunanda
Copy link
Contributor Author

@cmsbuild Please test

@cmsbuild
Copy link
Contributor

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

@cmsbuild
Copy link
Contributor

@davidlange6
Copy link
Contributor

@bsunanda - We need the reverse of this - we need the 2017 geometry to be working (as it has been), so 2017dev should be the 2017 hcal (not working yet) until its working.

@bsunanda
Copy link
Contributor Author

@davidlange6 That is precisely what it is. 2017 is the one with 2016 HCAL and 2017 pixel and it is supposed to be working while 2017dev is the one with 2017 HCAL and Pixel where we have to put more work to make it working

@davidlange6
Copy link
Contributor

ok, I misread - testing now.. Thanks

On Feb 16, 2016, at 8:08 PM, bsunanda notifications@github.com wrote:

@davidlange6 That is precisely what it is. 2017 is the one with 2016 HCAL and 2017 pixel and it is supposed to be working while 2017dev is the one with 2017 HCAL and Pixel where we have to put more work to make it working


Reply to this email directly or view it on GitHub.

@davidlange6
Copy link
Contributor

workflow 10039 still has a problem

----- Begin Fatal Exception 16-Feb-2016 20:19:10 CET-----------------------
An exception of category 'Filling of conditions failed' occurred while
[0] Processing run: 1 lumi: 1 event: 1
[1] Running path 'digitisation_step'
[2] Calling event method for module MixingModule/'mix'
[3] Using EventSetup component HcalDbProducer/'hcal_db_producer' to make data HcalDbService/'' in record HcalDbRecord
[4] Using EventSetup component HcalHardcodeCalibrations/'es_hardcode' to make data HcalGainWidths/'' in record HcalGainWidthsRcd
Exception Message:
no valid filling possible for Conditions of type HcalGainWidths for DetId (0x43300448) (HB -1,72,3)
----- End Fatal Exception -------------------------------------------------
Another exception was caught while trying to clean up files after the primary fatal exception.
16-Feb-2016 20:19:10 CET Closed file file:step1.root

@bsunanda
Copy link
Contributor Author

@davidlange6 This will be cured after merging of bsunanda:Run2-hcx66

@davidlange6
Copy link
Contributor

ok, checking that (since its merged since a few hours its not in my test)

@cmsbuild
Copy link
Contributor

@davidlange6
Copy link
Contributor

can be good if you take over the testing... not so simple [its progress though]

%MSG-e HCAL: MixingModule:mix 16-Feb-2016 21:11:42 CET Run: 1 Event: 1
Inconsistent dense packing between current topology (10) and calibration object (0)
%MSG
----- Begin Fatal Exception 16-Feb-2016 21:11:51 CET-----------------------
An exception of category 'Conditions mismatch' occurred while
[0] Processing run: 1 lumi: 1 event: 1
[1] Running path 'digitisation_step'
[2] Calling event method for module MixingModule/'mix'
Exception Message:
Requested conditions of type HcalGains for cell (0x43182c42) (HB 11,66,1) got conditions for cell (0x42004290) (HB -5,16,1)
----- End Fatal Exception -------------------------------------------------
Another exception was caught while trying to clean up files after the primary fatal exception.
16-Feb-2016 21:11:51 CET Closed file file:step1.root

@cmsbuild
Copy link
Contributor

Pull request #13307 was updated. @civanch, @Dr15Jones, @ianna, @mdhildreth, @cmsbuild, @davidlange6 can you please check and sign again.

@bsunanda
Copy link
Contributor Author

@cmsbuild Please test

@cmsbuild
Copy link
Contributor

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

@bsunanda
Copy link
Contributor Author

@davidlange6 Now the workflow 10039 runs without crashes. I do not know why but had to check out L1Trigger/L1TGlobal and compile before the who;e thing works

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@bsunanda
Copy link
Contributor Author

@ianna Could you please review and sign this. It is needed to make the 2017 workflow operational

@ianna
Copy link
Contributor

ianna commented Feb 19, 2016

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar

davidlange6 added a commit that referenced this pull request Feb 19, 2016
bsunanda:Run2-hcx67 Default 2017 scenario which has 2017 pixel but 2016 HCAL
@davidlange6 davidlange6 merged commit 14b7cb5 into cms-sw:CMSSW_8_0_X Feb 19, 2016
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.

None yet

4 participants