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 Phase I #2265

Merged
merged 25 commits into from
Feb 4, 2014
Merged

Hcal Phase I #2265

merged 25 commits into from
Feb 4, 2014

Conversation

ianna
Copy link
Contributor

@ianna ianna commented Feb 2, 2014

  • Merging all branches
  • Fix from Sunanda for Phase I

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 2, 2014

A new Pull Request was created by @ianna for CMSSW_6_2_X_SLHC.

Hcal Phase I

It involves the following packages:

CalibCalorimetry/CaloMiscalibTools
CalibCalorimetry/HcalAlgos
CalibCalorimetry/HcalPlugins
CalibCalorimetry/HcalStandardModules
CalibCalorimetry/HcalTPGEventSetup
CalibFormats/HcalObjects
Calibration/HcalCalibAlgos
Calibration/IsolatedParticles
CaloOnlineTools/HcalOnlineDb
CondFormats/DataRecord
CondTools/Geometry
CondTools/Hcal
Configuration/Geometry
DQM/HcalMonitorClient
DQM/HcalMonitorTasks
FastSimulation/CaloRecHitsProducer
FastSimulation/L1CaloTriggerProducer
Geometry/CMSCommonData
Geometry/CaloEventSetup
Geometry/CaloTopology
Geometry/HcalCommonData
Geometry/HcalEventSetup
Geometry/HcalTowerAlgo
Geometry/Records
L1TriggerConfig/L1ScalesProducers
RecoEgamma/EgammaIsolationAlgos
RecoJets/JetProducers
RecoLocalCalo/CaloRecCandCreator
RecoLocalCalo/CaloTowersCreator
RecoLocalCalo/HcalRecProducers
RecoParticleFlow/PFClusterProducer
SimCalorimetry/HcalSimAlgos
SimCalorimetry/HcalSimProducers
SimCalorimetry/HcalTrigPrimProducers

@diguida, @deguio, @lveldere, @ianna, @anton-a, @thspeer, @rcastello, @civanch, @ojeda, @cmsbuild, @ktf, @Dr15Jones, @mdhildreth, @rovere, @giamman, @slava77, @ggovi, @Degano, @mulhearn, @apfeiffer1, @nclopezo, @danduggan can you please review it and eventually sign? Thanks.
@ghellwig, @yslai, @TaiSakuma 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.
@andersonjacob, @mark-grimes you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@ianna
Copy link
Contributor Author

ianna commented Feb 2, 2014

+1

tested with

runTheMatrix.py --what upgrade -l 3300 

all steps pass.

@mark-grimes
Copy link

Full test suite still running, but testing the GEMs with

runTheMatrix.py -w upgrade -l 3400 --command "--customise SLHCUpgradeSimulations/Configuration/combinedCustoms.cust_2019WithGem”

fails when customising:

customising the process with cust_2019WithGem from SLHCUpgradeSimulations/Configuration/combinedCustoms
Traceback (most recent call last):
  File "/afs/cern.ch/cms/sw/ReleaseCandidates/vol0/slc5_amd64_gcc472/cms/cmssw/CMSSW_6_2_X_SLHC_2014-02-02-1400/bin/slc5_amd64_gcc472/cmsDriver.py", line 43, in <module>
    run()
  File "/afs/cern.ch/cms/sw/ReleaseCandidates/vol0/slc5_amd64_gcc472/cms/cmssw/CMSSW_6_2_X_SLHC_2014-02-02-1400/bin/slc5_amd64_gcc472/cmsDriver.py", line 15, in run
    configBuilder.prepare()
  File "/afs/cern.ch/cms/sw/ReleaseCandidates/vol0/slc5_amd64_gcc472/cms/cmssw/CMSSW_6_2_X_SLHC_2014-02-02-1400/python/Configuration/Applications/ConfigBuilder.py", line 2082, in prepare
    self.pythonCfgCode += self.addCustomise()
  File "/afs/cern.ch/cms/sw/ReleaseCandidates/vol0/slc5_amd64_gcc472/cms/cmssw/CMSSW_6_2_X_SLHC_2014-02-02-1400/python/Configuration/Applications/ConfigBuilder.py", line 795, in addCustomise
    self.process=getattr(package,fcn)(self.process)
  File "/afs/cern.ch/cms/sw/ReleaseCandidates/vol0/slc5_amd64_gcc472/cms/cmssw/CMSSW_6_2_X_SLHC_2014-02-02-1400/python/SLHCUpgradeSimulations/Configuration/combinedCustoms.py", line 62, in cust_2019WithGem
    process=cust_2019(process)
  File "/afs/cern.ch/cms/sw/ReleaseCandidates/vol0/slc5_amd64_gcc472/cms/cmssw/CMSSW_6_2_X_SLHC_2014-02-02-1400/python/SLHCUpgradeSimulations/Configuration/combinedCustoms.py", line 57, in cust_2019
    process=customise_HcalPhase1(process)
  File "/afs/cern.ch/cms/sw/ReleaseCandidates/vol0/slc5_amd64_gcc472/cms/cmssw/CMSSW_6_2_X_SLHC_2014-02-02-1400/python/SLHCUpgradeSimulations/Configuration/HCalCustoms.py", line 61, in customise_HcalPhase1
    process.es_hardcode.hcalTopologyConstants.mode=cms.string('HcalTopologyMode::SLHC')
AttributeError: 'ESSource' object has no attribute 'hcalTopologyConstants'

I'll report on the other tests when they're finished.

@ianna
Copy link
Contributor Author

ianna commented Feb 2, 2014

@mark-grimes - customisations are not needed for Hcal.

process.es_hardcode.hcalTopologyConstants

should be removed from where it is defned.

@ianna
Copy link
Contributor Author

ianna commented Feb 3, 2014

@mark-grimes - this should fix the 3400 workflow.

@salavat - could you, please, check customisations for Hcal? I think, I've removed everything unneeded.

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 3, 2014

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 3, 2014

@ianna
Copy link
Contributor Author

ianna commented Feb 3, 2014

+1

1 similar comment
@lveldere
Copy link
Contributor

lveldere commented Feb 3, 2014

+1

@mark-grimes
Copy link

This fixes the configuration problem (3400, 4400, 4500, 4502 and 15001 also failed before this fix). Now 3400 and 15001 fail in harvesting with:

----- Begin Fatal Exception 03-Feb-2014 11:02:47 CET-----------------------
An exception of category 'Conditions mismatch' occurred while
   [0] Processing run: 1
   [1] Running path 'dqmHarvesting'
   [2] Calling beginRun for module HcalMonitorClient/'hcalClient'
Exception Message:
Requested conditions of type HcalPedestals for cell (0x42006101) (HB 2,1,1) got conditions for cell (0x4200608d) (HB 1,13,1)
----- End Fatal Exception -------------------------------------------------

Note that there are several of these messages in the log:

%MSG-e HCAL:  HcalMonitorClient:hcalClient@beginRun 03-Feb-2014 11:06:07 CET  Run: 1
Inconsistent dense packing between current topology (10) and calibration object (0)

3400 when running with combinedCustoms.cust_2019WithGem crashes in harvesting with the following stack trace:

%MSG-e FatalSystemSignal:  HcalDigisClient:hcaldigisClient@endRun  03-Feb-2014 11:03:34 CET End Run: 1
A fatal system signal has occurred: segmentation violation

<trimmed>

#5  0x00002b8b696e3a74 in MonitorElement::Fill(double, double) () from /afs/cern.ch/cms/sw/ReleaseCandidates/vol0/slc5_amd64_gcc472/cms/cmssw/CMSSW_6_2_X_SLHC_2014-02-02-1400/lib/slc5_amd64_gcc472/libDQMServicesCore.so
#6  0x00002b8b79128cdc in HcalDigisClient::HcalDigisEndjob(std::vector<MonitorElement*, std::allocator<MonitorElement*> > const&, std::string) () from /tmp/grimes/CMSSW_6_2_X_SLHC_2014-02-02-1400/lib/slc5_amd64_gcc472/pluginValidationHcalDigis.so
#7  0x00002b8b79129878 in HcalDigisClient::runClient() () from /tmp/grimes/CMSSW_6_2_X_SLHC_2014-02-02-1400/lib/slc5_amd64_gcc472/pluginValidationHcalDigis.so
#8  0x00002b8b5a8e9330 in edm::EDAnalyzer::doEndRun(edm::RunPrincipal const&, edm::EventSetup const&, edm::CurrentProcessingContext const*) () from /afs/cern.ch/cms/sw/ReleaseCandidates/vol0/slc5_amd64_gcc472/cms/cmssw/CMSSW_6_2_X_SLHC_2014-02-02-1400/lib/slc5_amd64_gcc472/libFWCoreFramework.so   

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 3, 2014

@ianna
Copy link
Contributor Author

ianna commented Feb 3, 2014

@mark-grimes - strange, the following command runs fine for me:

runTheMatrix.py --what upgrade -l 3400 --command "--customise SLHCUpgradeSimulations/Configuration/combinedCustoms.cust_2019WithGem"

@ianna
Copy link
Contributor Author

ianna commented Feb 3, 2014

+1

@mark-grimes
Copy link

Tried again with the updated pull request. The GEM test (as in @ianna's comment above) now runs fine but still get the same errors in harvesting for tests 3400 and 15001.

@ianna
Copy link
Contributor Author

ianna commented Feb 3, 2014

@mark-grimes - is it step4 your talking about?

@mark-grimes
Copy link

@ianna Yes, step 4 for both 3400 and 15001.

Tests 3300, 4100, 4400, 40001, 50002, 60002, 60001, 4502, 4500, 5001, and 50001 run fine all the way through.

@ianna
Copy link
Contributor Author

ianna commented Feb 3, 2014

@mark-grimes - I guess, the errors come when you do not have additional (correct?) customize option. Harvesting fails due to collection name mismatch which is defined in customization fragments for all other steps. Customization of step4 does not include "--customise SLHCUpgradeSimulations/Configuration/combinedCustoms.cust_2019" as the other steps do, there is only tracker customization.

diff 3400_FourMuPt1_200+FourMuPt1_200_UPG2019+DIGIUP19+RECOUP19+HARVESTUP19/step4_HARVESTING.py ../relval/3400_FourMuPt1_200+FourMuPt1_200_UPG2019+DIGIUP19+RECOUP19+HARVESTUP19/.
5c5
< # with command line options: step4 --conditions auto:upgrade2019 -s HARVESTING:validationHarvesting+dqmHarvesting --customise SLHCUpgradeSimulations/Configuration/phase1TkCustoms.customise --geometry Extended2019 --mc --magField 38T_PostLS1 -n 100 --filein file:step3_inDQM.root --fileout file:step4.root
---
> # with command line options: step4 --conditions auto:upgrade2019 -s HARVESTING:validationHarvesting+dqmHarvesting --customise SLHCUpgradeSimulations/Configuration/phase1TkCustoms.customise --geometry Extended2019 --mc --magField 38T_PostLS1 --customise SLHCUpgradeSimulations/Configuration/combinedCustoms.cust_2019WithGem -n 100 --filein file:step3_inDQM.root --fileout file:step4.root
70,71c70,71
< # Automatic addition of the customisation function from SLHCUpgradeSimulations.Configuration.phase1TkCustoms
< from SLHCUpgradeSimulations.Configuration.phase1TkCustoms import customise 
---
> # Automatic addition of the customisation function from SLHCUpgradeSimulations.Configuration.combinedCustoms
> from SLHCUpgradeSimulations.Configuration.combinedCustoms import cust_2019WithGem 
73,74c73,74
< #call to customisation function customise imported from SLHCUpgradeSimulations.Configuration.phase1TkCustoms
< process = customise(process)
---
> #call to customisation function cust_2019WithGem imported from SLHCUpgradeSimulations.Configuration.combinedCustoms
> process = cust_2019WithGem(process)

@ianna
Copy link
Contributor Author

ianna commented Feb 3, 2014

@mark-grimes - correction - hcal conditions mismatch

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 3, 2014

-1
I ran the usual tests and I found errors in the following unit tests:

---> test runtestPhysicsToolsPatAlgos had ERRORS

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

@ianna
Copy link
Contributor Author

ianna commented Feb 4, 2014

@cmsbuild - the test which fails is not applicable to SLHC. It test LHC startup scenario:
https://github.com/cms-sw/cmssw/blob/CMSSW_6_2_X_SLHC/PhysicsTools/PatAlgos/python/patTemplate_cfg.py

@mark-grimes
Copy link

merge

@ianna yes, harvesting only has the tracking customisations. Tried step4 of 3400 with the full customisation and it ran through.

cmsbuild added a commit that referenced this pull request Feb 4, 2014
@cmsbuild cmsbuild merged commit bd7c0ca into cms-sw:CMSSW_6_2_X_SLHC Feb 4, 2014
@davidlange6
Copy link
Contributor

did we then update 3400 to have the full customization in step4? (this can be generally fixed I guess - indeed was a problem before)

On Feb 4, 2014, at 11:36 AM, Mark Grimes notifications@github.com
wrote:

merge

@ianna yes, harvesting only has the tracking customisations. Tried step4 of 3400 with the full customisation and it ran through.


Reply to this email directly or view it on GitHub.

@ianna
Copy link
Contributor Author

ianna commented Feb 4, 2014

@davidlange6 - or we see if Hcal relabeling settings can be moved out. I'll check it when the new IB is ready.

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.

5 participants