Doublet tuning and new vertex algo #149
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… and filled the TTF4 trend plots with masking status from the current lumisection only.
fix fix
…t minbias/zero suppression discrepancies.
…g from miniAOD when possible except for making the nested bitmap)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains two independent components
(it reuses pieces of pixel cluster algo...)
the vertex algorithm will require tuning (to say the least) even to reach the performance of current DivisiveClustering algo used at HLT
MTV
http://innocent.home.cern.ch/innocent/RelVal/gpuverI2/
current DivisiveClustering algo in
https://innocent.web.cern.ch/innocent/RelVal/divverI/
(baseline is offline doublets and DA vertexing)