Skip to content

Conversation

@singhra1994
Copy link
Collaborator

I have modified the block trigger SigmaCPPK in such a way that both SigmaCPPK and SigmaCP can be filled in the same block

Added parameters for Sigma_C trigger selection and updated event tagging logic for SigmaC candidates.
Added support for SigmaC particle selection in the HfFilterHelper class.
[Trigger,PWGHF] Please consider the following formatting changes to AliceO2Group#14786
Copy link
Collaborator

@fgrosa fgrosa left a comment

Choose a reason for hiding this comment

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

Hi @singhra1994 I still didn't look into the helper functions, but I already spotted several issues in the logic of the filter itself. Please implement the suggestions, and then I will take a look at the helper functions as well.

Copy link
Collaborator

@fgrosa fgrosa left a comment

Choose a reason for hiding this comment

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

Hi @singhra1994, thanks for addressing my comments! The code looks correct to me now, but I would like to ask @mfaggin also to check that I didn't overlook any other bug that might affect the SigmaC-K triggers.
Please also address my remaining comments and then as discussed in the trigger meeting, verify that the output of the task is identical for the other triggers before and after your changes, so that we can then merge it. Thanks!


// array of BDT thresholds
std::array<LabeledArray<double>, kNCharmParticles> thresholdBDTScores;
std::array<LabeledArray<double>, kNCharmParticles + 1> thresholdBDTScores;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please put it separately

Copy link
Collaborator

Choose a reason for hiding this comment

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

I agree with this comment: leave your BDT fully independent from the others which are general for the triggers.

Copy link
Collaborator

@mfaggin mfaggin left a comment

Choose a reason for hiding this comment

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

Hi @fgrosa @singhra1994 I tried to go through the modifications and I posted some comments. It looks to me that the already existing trigger Sc-K is not affected by the proposed modifications, but I have a couple of warnings/comments for the Sc-p part.


// array of BDT thresholds
std::array<LabeledArray<double>, kNCharmParticles> thresholdBDTScores;
std::array<LabeledArray<double>, kNCharmParticles + 1> thresholdBDTScores;
Copy link
Collaborator

Choose a reason for hiding this comment

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

I agree with this comment: leave your BDT fully independent from the others which are general for the triggers.

singhra1994 and others added 4 commits February 7, 2026 03:10
Updated PID cuts and added new parameters for SigmaC-pr correlation. Adjusted track selection criteria and improved comments for clarity.
[Trigger,PWGHF] Please consider the following formatting changes to AliceO2Group#14786
}
float deltaEta = std::abs(RecoDecay::eta(pVecSigmaC) - track.eta());
if (!keepEvent[kSigmaCPr] && (isTrackProton && deltaEta < 1.0)) {
auto tagBDT = helper.isBDTSelected(scores[2], thresholdBDTScoreScLcToPiKP.value);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Move this cut as suggested in the previous round of review

singhra1994 and others added 5 commits February 10, 2026 00:49
Updated configurable parameters for SigmaCPr trigger and added logic for SigmaC-proton correlation. Enhanced event tagging and BDT score handling for SigmaC candidates.
[Trigger,PWGHF] Please consider the following formatting changes to AliceO2Group#14786
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

4 participants