Skip to content

[PWGHF] Patches for first Xic autoencoder study #10813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

macamerl
Copy link

Minimal changes in XicToPKPi specific files (task and selector) to evaluate the MSE between input (externally scaled) and internal scaled output of autoencoder. At moment, one can not run Autoencoder and BDT at the same time since they competitively fill candidate.mlProbXicToPKPi()[0].

@github-actions github-actions bot added the pwghf PWG-HF label Apr 10, 2025
@github-actions github-actions bot changed the title Patches for first Xic autoencoder study [PWGHF] Patches for first Xic autoencoder study Apr 10, 2025
Please consider the following formatting changes to AliceO2Group#10813
@zhangbiao-phy
Copy link
Collaborator

Hi @macamerl, Thanks for the development! First of all, let me ping the code owner to see if they have any comments on this implementation. @mfaggin @cterrevo and @phymanshu. Then I only have a few comments, see the review. Then could you also fix magalinter errors since they come from this PR?

changes to fix megalinter check
changes to fix megalinter checks
Changes to fix the PR checks
@phymanshu
Copy link
Contributor

Hi @macamerl @zhangbiao-phy
Since you are adding a configurable for these studies, I have no problem as long as it is not conflicting with the standard BDT analysis.
Best wishes

@macamerl
Copy link
Author

Thanks @phymanshu. Yes, I locally checked that the BDT inference has no problem after the changes that I made. The flags "applyMSE" and "applyMinMax" are set false/0 by default. In any case, I will privately send you the config file that I used for the check.

Comment on lines +281 to +285
if (applyMSE) {
hfMlXicToPKPiCandidate(outputMSEXicToPKPi, outputMSEXicToPiKP);
} else {
hfMlXicToPKPiCandidate(outputMlXicToPKPi, outputMlXicToPiKP);
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you not avoid all the branching and just make the decision once?

@vkucera
Copy link
Collaborator

vkucera commented May 6, 2025

@macamerl Is there any progress?

@macamerl
Copy link
Author

macamerl commented May 7, 2025

Hi, I'm implementing the comment received by @fgrosa . However, we had Italian national holidays as soon as after Easter and I had to replace one of my colleagues for other more urgent tasks of the project. Then, I have slowed down the debugging of the new version. I will give you an update next week.

@vkucera vkucera marked this pull request as draft May 22, 2025 16:38
@vkucera
Copy link
Collaborator

vkucera commented Jun 19, 2025

@macamerl Is there any activity on this?

@macamerl
Copy link
Author

macamerl commented Jun 23, 2025

@vkucera Yes, I implemented the ideas (and small adjustment) in the offline mail in the old O2Physics version. it worked at the beginning of June. Now, I think to see some conflicts btw the onnx versions (see error below). Then, I decide to update my local O2Physics version and to arrive at the point that my branch works again.

I also attached an example of the error: "Schema error: Trying to register schema with name Abs (domain: version: 1) from file /local/workspace/DailyBuilds/DailyO2Physics-slc9/daily-tags.uO7Ig4H9DC/SOURCES/onnx/v1.17.0-alice2/v1.17.0-alice2/onnx/defs/math/old.cc line 2729, but it is already registered from file /local/workspace/DailyBuilds/DailyO2Physics-slc9/daily-tags.uO7Ig4H9DC/SOURCES/onnx/v1.17.0-alice2/v1.17.0-alice2/onnx/defs/math/old.cc

@vkucera
Copy link
Collaborator

vkucera commented Jun 23, 2025

@macamerl Your current branch does not show any development.

@macamerl
Copy link
Author

What do you prefer? You want to close this commit request and open a new one when I solve the error (in the previous comment) in my local branch?

@vkucera
Copy link
Collaborator

vkucera commented Jun 23, 2025

What do you prefer? You want to close this commit request and open a new one when I solve the error (in the previous comment) in my local branch?

Please do not open a new PR. Just resolve the conflicts, address the comments and push the commits in your branch to update this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pwghf PWG-HF
Development

Successfully merging this pull request may close these issues.

6 participants