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
Added extra parameters for Geant4 tracking in field #31665
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31665/18780
|
A new Pull Request was created by @civanch (Vladimir Ivantchenko) for master. It involves the following packages: SimG4Core/Application @cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
The code-checks are being triggered in jenkins. |
@bendavid , here a simple variant to suppress bias within tracker is introduced. Optimal values of new parameters should be defined, first of all, energy limit. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31665/18804
|
Pull request #31665 was updated. @cmsbuild, @civanch, @mdhildreth can you please check and sign again. |
please test |
The tests are being triggered in jenkins.
|
Thanks, (For 10_6_X in any case I think we prefer to do this without code changes/new release just changing the parameters.) |
The results of some tests I've done changing the parameters globally. CPU Timing: Nominal: Test1:
16.9 s/event Test2
16.5 s/event Test3:
18.6 s/event Test4:
19.5 s/event So it seems Minimum/MaximumEpsilonStep have some impact on CPU performance, but the others not really. If I tried setting ONLY
This error did NOT occur in the "Test4" configuration with other parameters tightened, so maybe it was due to the mismatch, or just "luck". In terms of physics performance, in a "deterministic" closure test with all random processes for muons turned off, I saw ONLY DeltaIntersection making a difference, between 5.5 GeV and 150GeV in pt within the tracker volume at eta of around 2.3-2.4 Plots of the bias vs q/pT on the last TEC layer, and vs z for muons with pT=150GeV: |
I should also add that "Test2", "Test3", and "Test4" configurations here have been tested with several million Z->mu mu events each without provoking any of the EstimateIntersectionPoint errors. |
Pull request #31665 was updated. @cmsbuild, @civanch, @mdhildreth can you please check and sign again. |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 history change in previous version of this PR is understood. |
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:
To address problem discussed in https://indico.cern.ch/event/958339/contributions/4032381/attachments/2110000/3549315/muoncal-Sept25-2020.pdf extra parameters for Geant4 tracking in field are added. This will allow simulation of high energy tracks without reported bias in trajectories. Optimal values of new parameters require evaluation, because of that in this PR new set of parameters are not yet enabled.
Also printouts are improved.
PR validation:
private
if this PR is a backport please specify the original PR and why you need to backport that PR:
to be discussed if it should be backported to legacy for Run-2 or not.