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
Phase2TrackerDigitizer: Activating Bias Rail Inefficiency #40069
Phase2TrackerDigitizer: Activating Bias Rail Inefficiency #40069
Conversation
… it is the intrinsic to the sensor itself. SimHits are discarded when the trajectory is entirely inside the bias rail region. At the moment we consider the SimHits for which the trajectory is partly outside the bias rail region
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40069/33053
|
A new Pull Request was created by @suchandradutta (Suchandra Dutta) for master. It involves the following packages:
@cmsbuild, @AdrianoDee, @srimanob, @civanch, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
-1 Failed Tests: RelVals-INPUT RelVals-INPUTThe relvals timed out after 4 hours. Comparison SummarySummary:
|
please test
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fc2b6b/29061/summary.html Comparison SummarySummary:
|
@suchandradutta , I agree with proposed implementation but am not sure if it is a correct approach to add any filter if the geometry the new tracker is not fully finalized. Usually such type of filter or mask are added to very final variant of simulation. |
Hi @civanch, as mentioned in the PR description, this inefficiency is kind of unavoidable. |
+1 |
+Upgrade Maybe Changes are seen in all Phase-2 workflows as expected since the PR effects only Phase-2. Note to @cms-sw/pdmv-l2 on the validation when the release with this PR comes out. |
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40069/33092
|
Pull request #40069 was updated. @AdrianoDee, @srimanob, @civanch, @mdhildreth can you please check and sign again. |
-1 Failed Tests: UnitTests Unit TestsI found errors in the following unit tests: ---> test test-das-selected-lumis had ERRORS Comparison SummarySummary:
|
please test
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fc2b6b/29130/summary.html
Comparison SummarySummary:
|
+1 |
+Upgrade Re-sign |
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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Activating the bias rails inefficiency for PS-p modules by default as it is the intrinsic to the sensor itself. SimHits are discarded (not considered for Digitization) when the trajectory is entirely inside the bias rail region. At the moment we consider also those SimHits for which the trajectory is partly outside (optimistic scenario with 'AND' condition for Entry/Exit points of SimHits) the bias rail region.
Note : the code was already integrated before we are now switching it on through a configuration parameter.
We expect to find less digis in PSP modules due to this inefficiency
At the moment we are estimating the effect of this inefficiency in L1 tracking and it is not fully optimized. We might move to a more pessimistic scenario when we shall not consider the SimHits where the the trajectory is event partly inside the bias rail region ( 'OR' condition for Entry/Exit points of SimHits)
PR validation and some performance updates
Bi-weekly modelling, simulation and performance Meeting 11/11/2022
Bi-weekly modelling, simulation and performance Meeting 11/11/2022
Bi-weekly modelling, simulation and performance Meeting 27/05/2022
Note : all the above validation plots are presented with the pessimistic 'OR' option
@emiglior