Closed slava77 closed 2 years ago
Can you please rather figure out where the difference comes from? We will need this for seed region rebuilding and will need to figure it out anyway.
Can you please rather figure out where the difference comes from? We will need this for seed region rebuilding and will need to figure it out anyway.
OK, I'll give it a try (not before Monday), although I'd guess that you may be more familiar with this part of the code.
if me or someone gets to this before Friday, this PR can wait; otherwise for the next CMSSW update, I'd like to fall back to this revert PR.
OK, I'll give it a try (not before Monday), although I'd guess that you may be more familiar with this part of the code.
it's likely later than Monday. My next item is the pixel bad modules.
OK, then it's on me, I can start looking into this Monday morning. I agree we fall back to this if we can't figure it out in time :)
superseded by #351
345 was not in an obvious way supposed to modify the iterations without the backward search. This PR recovers that behavior.
plots are available for
mkfit=all
option compiled withAVX2:=1 USE_INTRINSICS:=-DMPT_SIZE=1
black (this PR) vs the reference as of #344 are clearly the same based on the ratio plots, e.g. in ttbar initialStep built tracks
If the change from #345 for e.g. this
initialStep
case was an improvement, I guess we'd be fine to pick it up. Since this is a regression (a clear increase in fakes), I propose to take this PR and then perhaps investigate if the non-BH solution can be improved (IIUC, it is more flexible).@osschar I've updated both the
run_OneIteration
andrunBtpCe_MultiIter
, but the CMSSW MTV test covers onlyrun_OneIteration
. Please check and if that seems correct, perhaps consider merging.