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
Add pixel-only seed extension #14356
Conversation
A new Pull Request was created by @makortel (Matti Kortelainen) for CMSSW_8_1_X. It involves the following packages: DQM/TrackingMonitor @perrotta, @cmsbuild, @cvuosalo, @fwyzard, @dmitrijus, @Martin-Grunewald, @deguio, @slava77, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
7405b49
to
584b548
Compare
@cmsbuild , please test |
The tests are being triggered in jenkins. |
There was an issue with git-cms-merge-topic you can see the log here: |
Looks like a transient issue, maybe try again? |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 |
+1
|
+1 |
@dmitrijus Merging of this PR is now blocking further developments |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
+1 |
This PR adds a "pixel-only" flavour of the SeedExtensionTrajectoryFilter (one of the explored pixel-quadruplet approaches for phase1). As a prerequisite, Trajectory and TempTrajectory are extended to count also found pixel hits (which may have other uses too).
The SeedExtensionTrajectoryFilter is also extended to act as "qualityFilter()" in addition to "toBeContinued()". The point is that if seed extension decides that a propagation of a trajectory should be stopped, the trajectory should also be discarded (in my opinion). This way the assumption is enforced without relying on the value of
minimumNumberOfHits
(alternatively we would needminimumNumberOfPixelHits
). The easiest way to communicate the "trajectory was stopped because of seed extension" fromtoBeContinued()
toqualityFilter()
was to use the existingStoppingReason
enum, so I added aSEED_EXTENSION
enumerator there.I updated the tracking DQM for the new
StoppingReason
(*), also adding a run-time check in case new StoppingReasons are added. (Maybe we should eventually abstract the string representation of StoppingReasons similarly to TrackBase::TrackAlgorithm?)(*) After the "qualityFilter()" change we expect to see zero tracks with
SEED_EXTENSION
stopping reason, so the DQM change serves mainly as a sanity check (seeing something there indicates a bug).Tested in CMSSW_8_1_X_2016-05-01-2300 (rebased on top of
CMSSW_8_1_X_2016-05-09-2300CMSSW_8_1_X_2016-05-16-2300), no changes expected in standard workflows (new functionality is added but not enabled; StopReason DQM plots show changes because of added bin).@rovere @VinInn @mtosi