[Common] Add the mft muon matching with real data workflow #8562
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 is the first commitment to the MFT-MUON (MCH-MID) track matching for the Machine Learning technique with the real data.
Idea:
The training sample quality is extremely important to the ML and the real data is the most reliable for the training.
However, if we want to use the sample for the training, it is necessary to identify the "correct" sample and the "wrong" sample.
This workflow is used to make the tables of correct and wrong samples from data.
The wrong sample is produced by using the event mixing technique between MFT and MUON tracks.
The correct sample is produced by "tag-and-probe" method using J/psi peak.
First, the invariant mass of MUON track pair is calculated under the low MFT track multiplicity condition, and if the pair makes mass around J/psi the tracks are regarded as muon tracks.
If the higher momentum track passed tight selection of the MFT and MUON matching criteria, it is selected as "Tag".
The other track is regarded as "Probe" track.
The track is very likely to be muon and generated at the PV, which means there is an MFT track produced by the muon.
This workflow is the first attempt to check the above idea and check several points.
So, the code will be refined and finally extended to Pb-Pb collisions.
The UPC event is an excellent environment to make the tag track environment.