FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Provisionary fix for ITS fit with B=0 by shahor02 · Pull Request #10261 · AliceO2Group/AliceO2 · GitHub

Provisionary fix for ITS fit with B=0 - #10261

Closed
shahor02 wants to merge 1 commit into
AliceO2Group:devfrom
shahor02:pr_itsfitB0
Closed

Provisionary fix for ITS fit with B=0#10261
shahor02 wants to merge 1 commit into
AliceO2Group:devfrom
shahor02:pr_itsfitB0

Conversation

Copy link
Copy Markdown
Collaborator

Hi @mpuccio @davidrohr

The ITS tracking with B=0 produces a weird q/pT spectrum instead of fixed (modulo e.loss) "most probable" q2pt:

The reason is that in the

track::TrackParCov TrackerTraits::buildTrackSeed(const Cluster& cluster1, const Cluster& cluster2, const Cluster& cluster3, const TrackingFrameInfo& tf3, float resolution)
you are initializing the cov.matrix with non-0 non-diagonal elements while with B=0 all correlations with q/pT must be 0.
This PR attempts to fix this, but I don't understand the way you build the cov. matrix in general: should not it correspond to the matrix updated only at cluster3, i.e. only diag. errors in Y and Z set to resolution^2, other diagonal errors "as large as possible" and non-diagonal ones set to 0?
With this fix the result of the fit becomes:

and the final covariances of q/pT with other parameters are 0 within ~10^-7

@davidrohr, for the TPC I see something different: the mean q/pt corresponds to conventional "most probable" but then there are huge tails on both sides

and also I see a significant correlation between the q/pT error and e.g. y, this cannot happen with B=0.

Could you please check if you are not initializing with the covariance with some non-diagonal elements?

It seems that currently all fits with B=0 are wrong.

mpuccio commented Nov 13, 2022

Copy link
Copy Markdown
Contributor

Hi @shahor02, it looks good to me. I copied the code from the Cooked matrix long ago, so I cannot exclude that I did some mistakes in the process. However, we can even remove this part of the code and do a full fit of the candidate by providing a reasonable set of parameters and a very large covariance as starting conditions.

Copy link
Copy Markdown
Collaborator Author

@mpuccio starting from large diagonal cov matrix would be the right choice later you fit through the all clusters, but I was not sure if you do this: I see that you make a piecewise fit

fitSuccess = fitTrack(temporaryTrack, 0, mTrkParams[0].NLayers, 1, mTrkParams[0].FitIterationMaxChi2[0]);
if (!fitSuccess) {
continue;
}
CA_DEBUGGER(backpropagatedCounters[nClusters - 4]++);
temporaryTrack.getParamOut() = temporaryTrack;
temporaryTrack.resetCovariance();
fitSuccess = fitTrack(temporaryTrack, mTrkParams[0].NLayers - 1, -1, -1, mTrkParams[0].FitIterationMaxChi2[1], 50.);

Does it fit through all clusters contiguously, including the cluster3 ?

Copy link
Copy Markdown
Collaborator Author

Superseded by #10271

shahor02 closed this Nov 15, 2022
shahor02 deleted the pr_itsfitB0 branch April 26, 2023 16:00
This file contains hidden or 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL