Skip to content

[PWGCF,PWGHF] Add SigmaC(2455)-track femtoscopy to Charm+Track femtoscopy framework - #18692

Open
zhangbiao-phy wants to merge 6 commits into
AliceO2Group:masterfrom
zhangbiao-phy:codex/sigmac2455-track
Open

zhangbiao-phy wants to merge 6 commits into
AliceO2Group:masterfrom
zhangbiao-phy:codex/sigmac2455-track

Conversation

@zhangbiao-phy

@zhangbiao-phy zhangbiao-phy commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator

Extend the existing HFC producer and pairing task with SigmaC(2455) -> LambdaC pi candidates. Process neutral and doubly charged candidates together, preserving charge in the output tables and using the corresponding mass for each pair. Reject tracks shared with any of the four decay daughters.

Tag @mfaggin and @fgrosa

Extend the existing HFC producer and pairing task with SigmaC(2455) ->
LambdaC pi candidates, both LambdaC mass hypotheses, and data/MC modes.
Process neutral and doubly charged candidates together, preserving charge
in the output tables and using the corresponding mass for each pair.
Reject tracks shared with any of the four decay daughters.

Validate both tasks with syntax checks and synthetic regression tests for
legacy channels, output schemas, MC filters, charge-dependent kinematics,
and active workflow inputs. Real-AO2D and ONNX/CCDB inference were not run.
@github-actions

Copy link
Copy Markdown

O2 linter results: ❌ 0 errors, ⚠️ 47 warnings, 🔕 0 disabled

@zhangbiao-phy zhangbiao-phy changed the title [PWGHF] Add SigmaC(2455)-track femtoscopy to Charm+Track femtoscopy framework Add SigmaC(2455)-track femtoscopy to Charm+Track femtoscopy framework Nov 11, 2026
@github-actions github-actions Bot changed the title Add SigmaC(2455)-track femtoscopy to Charm+Track femtoscopy framework [PWGCF,PWGHF] Add SigmaC(2455)-track femtoscopy to Charm+Track femtoscopy framework Nov 11, 2026

@mfaggin mfaggin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks @zhangbiao-phy , please find my comments, they are mostly to better understand and eventually avoid some computations where they are not needed

zhangbiao-phy and others added 2 commits November 19, 2026 10:55
Use a fixed 0.135 GeV/c2 producer DeltaM lower bound and the common charm mass-window and histogram parameters in the pairing task. Remove the particle-sign selector and duplicate LambdaC mass selection while retaining charge information in the candidate output.

Apply the SigmaC review cleanup for redundant upstream checks and task selections.

Validation: O2 linter and diff checks; syntax checks for both workflows; SigmaC data/MC and legacy Lc, D+, D0, D*, Xic regression checks.
Please consider the following formatting changes to AliceO2Group#18692
@zhangbiao-phy

Copy link
Copy Markdown
Collaborator Author

Thanks @mfaggin for the comments and suggestions!

Resolve the HFC producer and task conflicts while retaining SigmaC(2455) reconstruction and the upstream D+ / D* generated-particle correlation workflows. Include all 14 process switches and qualify the new Gen output writers through ProducesGroup.

Hoist the Gen mixing histogram name outside the generic lambda for Clang compatibility without changing its contents.
@alibuild

Copy link
Copy Markdown
Collaborator

Error while checking build/O2Physics/code-check for a79cf1d at 2026-11-19 14:25:

## sw/BUILD/O2Physics-code-check-latest/log
--
========== List of issues found ==========
++ echo 'To reproduce the results below locally, run: '\''aliBuild build O2Physics-code-check -e ALIBUILD_BASE_HASH=upstream/master'\''.'
To reproduce the results below locally, run: 'aliBuild build O2Physics-code-check -e ALIBUILD_BASE_HASH=upstream/master'.
++ echo 'To apply all automatic fixes, add the '\''-e O2PHYSICS_CHECKER_FIX=1'\'' option.'
To apply all automatic fixes, add the '-e O2PHYSICS_CHECKER_FIX=1' option.
++ echo 'See the documentation for more details at: <https://aliceo2group.github.io/analysis-framework/docs/tools/#running-with-o2physics-code-check>.'
See the documentation for more details at: <https://aliceo2group.github.io/analysis-framework/docs/tools/#running-with-o2physics-code-check>.
++ echo 'Found 1 errors and 9 warnings.'
Found 1 errors and 9 warnings.
++ [[ 1 -gt 0 ]]
++ cat /sw/BUILD/30fe45380a2a8ded56dd969b6b58000a56e954e7/O2Physics-code-check/errors.txt
PWGHF/HFC/TableProducer/producerCharmHadronsTrackFemtoDream.cxx:1626:20: error: no header providing "std::size_t" is directly included [misc-include-cleaner,-warnings-as-errors]
++ [[ 9 -gt 0 ]]
++ cat /sw/BUILD/30fe45380a2a8ded56dd969b6b58000a56e954e7/O2Physics-code-check/warnings.txt
PWGCF/DataModel/FemtoDerived.h:141:18: warning: do not declare C-style arrays, use 'std::array' instead [modernize-avoid-c-arrays]
PWGCF/DataModel/FemtoDerived.h:143:18: warning: do not declare C-style arrays, use 'std::array' instead [modernize-avoid-c-arrays]
PWGCF/DataModel/FemtoDerived.h:155:18: warning: do not declare C-style arrays, use 'std::array' instead [modernize-avoid-c-arrays]
PWGCF/DataModel/FemtoDerived.h:829:18: warning: do not declare C-style arrays, use 'std::array' instead [modernize-avoid-c-arrays]
PWGCF/DataModel/FemtoDerived.h:856:18: warning: do not declare C-style arrays, use 'std::array' instead [modernize-avoid-c-arrays]
PWGCF/FemtoDream/Core/femtoDreamUtils.h:132:70: warning: repeated branch body in conditional chain [bugprone-branch-clone]
PWGHF/HFC/TableProducer/producerCharmHadronsTrackFemtoDream.cxx:210:58: warning: do not implicitly decay an array into a pointer; consider using gsl::array_view or an explicit cast instead [cppcoreguidelines-pro-bounds-array-to-pointer-decay]
PWGHF/HFC/TableProducer/producerCharmHadronsTrackFemtoDream.cxx:312:5: warning: do not declare C-style arrays, use 'std::array' instead [modernize-avoid-c-arrays]
PWGHF/HFC/Tasks/taskCharmHadronsTrackFemtoDream.cxx:1667:7: warning: switching on non-enum value without default case may not cover all cases [bugprone-switch-missing-default-case]
++ [[ 1 -gt 0 ]]
++ exit 1
--

Full log here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants