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
[12_4_X] PPS reco patch for bad pot #38581
Conversation
A new Pull Request was created by @fabferro (Fabrizio Ferro) for CMSSW_12_4_X. It involves the following packages:
@jpata, @cmsbuild, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f1f495/25942/summary.html Comparison SummarySummary:
|
@fabferro there are no reco changes detected by the bot (CTPPS stuff maybe not tracked?), but does this change Run3 MC in any way? Does it need to be protected with a modifier? |
Run3 MC are effected in the sense that if the Simulation simulates PPS with all working planes, then unneeded 2-hit tracks will be added in the track collection. They can be easily identified and taken care of at analysis level. |
backport of #38553 |
It doesn't seem like this is supported. Perhaps it would be better to create a new era that is only enabled when data is processed? Note that this has to be done in both the master version and this backport. |
If it's not supported, I'd say that PPS simulation can live with this patch unitl the detectors are repaired and the patch definitely disabled. The 2-hit tracks that are created reconstructing simulated data can be easily recognized and dealt with at analysis level. |
@fabferro I think that the actual (time dependent) detector configuration should be available in the DB, and the reconstruction should act according to that configuration, irrespectfully of being real data or MC. Hybrid cases as "I have a description in the DB, but I let my reconstruction operate as if it was different" are only expected to lead to confusion and possible mistakes. |
cmsDriver can do |
@perrotta @tvami @jpata Another way not to disrupt the recostruction of simulated data would be put if(run==1) isBadPot = false; somewhere. A bit rough but probably effective. It would disappear once that the patch is not needed anymore. |
On Jul 6, 2022, at 12:35 PM, Fabrizio Ferro ***@***.***> wrote:
Another way not to disrupt the recostruction of simulated data would be put if(run==1) isBadPot = false; somewhere. A bit rough but probably effective. It would disappear once that the patch is not needed anymore.
Eg, you will instead have if (run>x and run<y)?
… —
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
@davidlange6 you mean something like if(run>first.run3.run && run<99999999) isBadPot=true; ? |
Why dont we just do the tag update? In that way we are independent of the release schedule. For example I understand that 12_4_X is to be cut today, and this PR will not be in it... (given that it's master is not merged yet) |
Pull request #38581 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @clacaputo, @jpata, @pmandrik, @micsucmed, @rvenditti can you please check and sign again. |
type bugfix,ctpps |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f1f495/26200/summary.html Comparison SummarySummary:
|
+reconstruction
|
@perrotta is this being merged? |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_4_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_5_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR provides a patch to be able to produce tracks inside PPS roman pot 45-220-fr that has only 2 planes working out of 6 (as to the current date). The code creates tracks using two hits (one per plane) drawing a straight line between them. The track is required to be isolated and horizontal. The goal is to recover at least some proton tracks for alignment/debugging purposes.
The patch is enabled by means of a runtime flag. Run2 processes are protected via Era mechanism.
PR validation:
Run2 data show no difference. Preliminary run3 data show recovered tracks as expected.
This PR is a backport of PR#38553.
@jpata @grzanka @AndreaBellora