-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Support for Phase-2 mkFit initialStep track building #44708
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44708/39914
|
A new Pull Request was created by @mmasciov for master. It involves the following packages:
@srimanob, @miquork, @AdrianoDee, @subirsarkar, @cmsbuild, @sunilUIET, @jfernan2, @mandrenguyen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
test parameters:
|
please test |
-1 Failed Tests: ClangBuild Clang BuildI found compilation warning while trying to compile with clang. Command used:
See details on the summary page. |
@osschar this is probably for you |
uhm, or does this message just mean we need also if everything is default, is there even a point to list anything? |
Correct. Or remove the definition copy assignment operator.
Generally speaking no, there is no point in default-defining member functions where it is clear the compiler generates the expected definitions implicitly (i.e. the "rule of 5" still holds). Elsewhere we have generally preferred to remove the default-defined copy constructor or assignment operator when only one of those was defined. |
@cms-sw/pdmv-l2 @cms-sw/upgrade-l2 your signature is needed for this PR. |
@@ -437,6 +437,28 @@ def condition_(self, fragment, stepList, key, hasHarvest): | |||
'--procModifiers': 'trackingMkFitDevel' | |||
} | |||
|
|||
# mkFit for phase-2 initialStep tracking | |||
class UpgradeWorkflow_trackingMkFitPhase2(UpgradeWorkflowTracking): |
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.
Why a different class (and then a different offset)? I don't see anything that could not have been done with UpgradeWorkflow_trackingMkFit
as is using the same *.7
offset. Or am I missing something?
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.
(Ok, not with the same suffix but within the same class yes)
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.
Phase-2 would need a different process modifier, and should not modify step2 on the other hand.
That's why we went with a different class, because it was the simplest solution. We may review this (and remove the class) when we'l have more than one iteration working in phase-2, so that we can reduce otherwise-needed modifications to the mkFit procModifiers?
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.
Yea, this was clear. And yes, most probably it's easier to have this rather than "disabling" the other iterations with something like ~phase2_tracker
. Maybe I would have inverted the logic here (so a UpgradeWorkflow_trackingMkFitInitialStep
) just to have it clear what's happening in the wf from the name. Anyway as you say, this will need to be reviewed anyway later.
+pdmv |
@cms-sw/upgrade-l2 your signature is needed for this PR. I'm not sure @AdrianoDee still has the upgrade signature rights ;) |
@cms-sw/orp-l2 @rappoccio |
Hi @mmasciov @slava77 @mmusich |
+Upgrade This PR adds new Phase-2 mkfit workflow, and it will run in the long matrix (IB). The new workflow runs fine in the PR test. |
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. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
only your "ORP" signature is missing |
+1 |
Add description of .702 workflow offset, introduced in PR #44708
PR description:
This PR adds the ability to run mkFit on Phase-2 data / geometry. Only initialStep iteration is supported so far, with a dedicated workflow (
24834.702
).Add CMSSW Phase-2 hit and seed converters.
Properly support binary readout for Phase-2 strips where cluster-charge cut can
not be applied.
Improve standalone performance monitoring & debugging tools.
It requires also a new JSON file in cmssw/data repository:
cms-data/RecoTracker-MkFit#14
PR validation:
In TTbar events, with PU:
FYI: @osschar, @slava77, @kskovpen