Skip to content
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

fixes in TOF calibration workflow #7679

Merged
merged 2 commits into from
Nov 23, 2021
Merged

fixes in TOF calibration workflow #7679

merged 2 commits into from
Nov 23, 2021

Conversation

noferini
Copy link
Collaborator

No description provided.

@noferini
Copy link
Collaborator Author

WIP

@noferini
Copy link
Collaborator Author

@shahor02 -> this is now ready for the review (many fixes in TOF calibration workflow after running several tests on Beam Test data). Two comments:

  • only ITS-TPC tracks are used now (TPC only tracks have wrong track length to be fixed before to use in calibration)
  • added calibInfo clear when changing TF (this was missing, bug, and leading to a calibInfo size 50 times larger with CTF containing 100 TFs + some problems in calibration)

@njacazio -> once this PR will be merger you can open yours in O2Physics (adding EventTimeMaker moved from TOFReconstruction to TOFBase)

Copy link
Collaborator

@shahor02 shahor02 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @noferini

see one comment bellow. BTW, what about this question: #7610 (review) ?

*(mTimeSlewing[i]) = *(source.mTimeSlewing[i]);
(*(mChannelStart[i])) = (*(source.mChannelStart[i]));
*(mFractionUnderPeak[i]) = *(source.mFractionUnderPeak[i]);
*(mSigmaPeak[i]) = *(source.mSigmaPeak[i]);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't you need to copy also mGlobalOffset?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. I probably missed it when copy and paste (and workflow didn't complain also in execution).

About #7610
I implemented an autodetection for fill scheme in case it is not provided.
It will be automatically skipped once the fill scheme will be filled with the information of collision context (at the moment I didn't know how to retrieve that info from there).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@shahor02 shahor02 merged commit af8bd7f into AliceO2Group:dev Nov 23, 2021
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