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
Run2-TB61 Modify the cfg's for testbeam simulation of the combined calorimeter ECAL+HCAL #34162
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34162/23368
|
A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master. It involves the following packages: Geometry/HcalTestBeamData @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild Please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-84f53e/16062/summary.html Comparison SummarySummary:
|
@@ -109,6 +109,8 @@ | |||
MaxTrackTime = cms.double(1000.0), | |||
MaxTimeNames = cms.vstring(), | |||
MaxTrackTimes = cms.vdouble(), | |||
MaxTrackTimeForward = cms.double(2000.0), # ns |
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.
@bsunanda , as far as I remember the max time in TB 2006 was 1000 ns, also why you need to change MaxZCentralCMS?
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.
The common_maximum_timex is used in the local definition of PS SteepingAction and CaloSD. Running the code complained about missing parameter MaxTrackTimeForward and MaxZCentralCMS - so I copied the ones from default g4SimHits there
@@ -173,6 +181,7 @@ | |||
|
|||
process.g4SimHits.SteppingAction = cms.PSet( | |||
process.common_maximum_timex, | |||
MaxNumberOfSteps = cms.int32(50000), |
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.
There is not need to reduce the default value.
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.
This is the default value but since SteppingAction is redefined here, I have to add this
@bsunanda , I would keep g4SimHits parameters unchanged if they are not modified. Only beam properties and time cut are different in TB and in the data, also you add recently the list of SDs. I would not redefine MaxNumberOfSteps and similar parameters - they are included for a particular use case and may disappear in future. |
@civanch I wanted to have the cfg's functional. Ince I added list of SD's, running the cfg's complained about missing parameters. So I copied the ones from g4SimHits in appropriate places. Most likely we need to revise all these cfg's later on and seeing the changed parameters from defaults and changing these. |
+1 I agree, that this is a working solution but likely in future scripts will require modifications. |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Modify the cfg's for testbeam simulation of the combined calorimeter ECAL+HCAL
PR validation:
Test by running all the cfg's in SimG4CMS/HcalTestBeam/test/python and Geometry/HcalTestBeamData/test/python
if this PR is a backport please specify the original PR and why you need to backport that PR:
Nothing special