[PWGDQ] add tag and probe method for dalitz selection

[glegras]

No description provided.

[github-actions]

O2 linter results: ❌ 23 errors, ⚠️ 232 warnings, 🔕 91 disabled

[alibuild]

Error while checking build/O2Physics/o2 for 8926f02 at 2026-04-26 02:46:

## sw/BUILD/O2Physics-latest/log
c++: fatal error: Killed signal terminated program cc1plus
ninja: build stopped: subcommand failed.

Full log here.

[vkucera]

How do these objects get deleted?

[glegras]

Since they are used in the AnalysisCut, they cannot be deleted until the end. But now I modified so that these TF1 are defined only when necessary

[vkucera]

You didn't answer my question.

[glegras]

I am not sure how they are deleted, maybe @iarsene you could check the PR and comment on that? Also I am using the standard coding of the PWGDQ framework, so if something is wrong about object deletions it should be modified in the entire framework.

[vkucera]

I'm asking because I don't see a single delete statement in the AnalysisCut class which would indicate that all the dynamically allocated objects with raw pointers leak, unless they are owned and handled by other classes.

[iarsene]

Hi Vit, in principle you are right. However, this function is allocated at init time, and then we need it until the end of the job. So this will not "leak" memory during the time the job is running. We can probably make the AnalysisCut to own this TF1 and then have an explicit delete when the cut gets destroyed at the end of the job.

[vkucera]

Hi Ionut, I don't know what you mean by "job" here, but I would expect the leak to live from the first call of ~AnalysisCut till the end of the program. Either the destructor should handle the deallocation or the raw pointers should be replaced with smart pointers.

[glegras]

I changed from TF1* to shared_ptr now