Skip to content

PWGHF: Adding event selection in the correlatorDsHadrons task#5186

Merged
fgrosa merged 3 commits into
AliceO2Group:masterfrom
scattaru:CorrelationsME
Mar 15, 2024
Merged

PWGHF: Adding event selection in the correlatorDsHadrons task#5186
fgrosa merged 3 commits into
AliceO2Group:masterfrom
scattaru:CorrelationsME

Conversation

@scattaru

Copy link
Copy Markdown
Contributor

Dear all,
I've modified the correlator in order to select collisions with the sel8 flag

Cheers,
Samuele

@fgrosa

fgrosa commented Mar 15, 2024

Copy link
Copy Markdown
Collaborator

Dear all, I've modified the correlator in order to select collisions with the sel8 flag

Cheers, Samuele

Hi @scattaru, in principle the event selection can already be applied at the level of the CandidateCreator3Prong now (see the PRs by @mfaggin, see #5057 and for the counter #5141). Do you think you would still need to add it afterwards?

@scattaru

Copy link
Copy Markdown
Contributor Author

Dear all, I've modified the correlator in order to select collisions with the sel8 flag
Cheers, Samuele

Hi @scattaru, in principle the event selection can already be applied at the level of the CandidateCreator3Prong now (see the PRs by @mfaggin, see #5057 and for the counter #5141). Do you think you would still need to add it afterwards?

Hi @fgrosa, in my case I need to filter the collision table that is used for the event mixing in order to take only the collisions which satisfies the selection criteria. So the idea is to join the collision table with the one which provides the event selection information. As far as I've understood in the creator there are just histograms filled with the information of selected collisions not a table produced with that information.

@scattaru scattaru marked this pull request as draft March 15, 2024 14:38
@scattaru scattaru marked this pull request as ready for review March 15, 2024 14:58
@fgrosa

fgrosa commented Mar 15, 2024

Copy link
Copy Markdown
Collaborator

Dear all, I've modified the correlator in order to select collisions with the sel8 flag
Cheers, Samuele

Hi @scattaru, in principle the event selection can already be applied at the level of the CandidateCreator3Prong now (see the PRs by @mfaggin, see #5057 and for the counter #5141). Do you think you would still need to add it afterwards?

Hi @fgrosa, in my case I need to filter the collision table that is used for the event mixing in order to take only the collisions which satisfies the selection criteria. So the idea is to join the collision table with the one which provides the event selection information. As far as I've understood in the creator there are just histograms filled with the information of selected collisions not a table produced with that information.

Thanks for the reply! The creator also rejects candidates in events that do not fulfil the event selection, so you will not find Ds candidates in those events, but probably here you want to discard also the tracks in those events. If this is the case indeed it makes sense and we can merge it.

@scattaru

Copy link
Copy Markdown
Contributor Author

Dear all, I've modified the correlator in order to select collisions with the sel8 flag
Cheers, Samuele

Hi @scattaru, in principle the event selection can already be applied at the level of the CandidateCreator3Prong now (see the PRs by @mfaggin, see #5057 and for the counter #5141). Do you think you would still need to add it afterwards?

Hi @fgrosa, in my case I need to filter the collision table that is used for the event mixing in order to take only the collisions which satisfies the selection criteria. So the idea is to join the collision table with the one which provides the event selection information. As far as I've understood in the creator there are just histograms filled with the information of selected collisions not a table produced with that information.

Thanks for the reply! The creator also rejects candidates in events that do not fulfil the event selection, so you will not find Ds candidates in those events, but probably here you want to discard also the tracks in those events. If this is the case indeed it makes sense and we can merge it.

Yes, exactly. In the Event Mixing the problem we faced is the limit number of Ds meson selected per DF, so there are DFs with only one Ds reconstructed so it was impossible to do the event mixing. To avoid this issue we decided to use all collisions and to mix an event with a candidate reconstructed with particles coming from other events even if they have not a candidate reconstructed. For the moment this is the fastest way, however we are also exploring other attempts to do the event mixing.

@fgrosa fgrosa enabled auto-merge (squash) March 15, 2024 15:52
@fgrosa fgrosa merged commit 04d5bae into AliceO2Group:master Mar 15, 2024
@scattaru scattaru deleted the CorrelationsME branch March 16, 2024 06:55
wuctlby pushed a commit to wuctlby/O2Physics that referenced this pull request Mar 17, 2024
…2Group#5186)

* Adding event selection

* clang-format

* removing VARIABLE_WIDTH
christianreckziegel pushed a commit to christianreckziegel/O2Physics that referenced this pull request May 2, 2024
…2Group#5186)

* Adding event selection

* clang-format

* removing VARIABLE_WIDTH
hahassan7 pushed a commit to hahassan7/O2Physics that referenced this pull request May 17, 2024
…2Group#5186)

* Adding event selection

* clang-format

* removing VARIABLE_WIDTH
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