Merged
Conversation
bugfix: add setter for charge field
lubynets
added a commit
to lubynets/AnalysisTree
that referenced
this pull request
Jul 31, 2025
due to changes introduced in HeavyIonAnalysis#132
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: In some pieces of code based on AnalysisTree (e.g. CbmRoot interface, PFSimple, Pid etc) the charge could be set as a user-defined field. Now it should be fixed, and a default field should be used. Check described in item (2) will help to localize these places.