Skip to content
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

LCRelationNavigator: add methods to return both max weight and object #171

Merged
merged 4 commits into from
Jun 13, 2023

Conversation

Zehvogel
Copy link
Contributor

As a result from discussion in iLCSoft/MarlinReco#114 (comment)

I was also thinking of changing getRelatedToMaxWeight and friends to call this and to then just return the respective entry of the tuple to have less of a logic duplication but I have no idea how this will affect the performance...

BEGINRELEASENOTES

  • LCRelationNavigator: add methods getRelatedToMaxWeightAndObject and getRelatedFromMaxWeightAndObject returning both the object and the weight in a tuple

ENDRELEASENOTES

@tmadlener
Copy link
Contributor

I think the performance overhead is pretty negligible and I would like the reduced duplication that could be achieved with that.

@Zehvogel
Copy link
Contributor Author

Ok, I made the change

@Zehvogel
Copy link
Contributor Author

Ugh I just noticed that the order of the return values in the tuple is the opposite of the method name, let me fix that

@tmadlener tmadlener merged commit 723f3c2 into iLCSoft:master Jun 13, 2023
@Zehvogel Zehvogel deleted the lcrelationnavigator branch June 13, 2023 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants