Fix gbasf2 batch example for new basf2 releases: import ROOT #123
Conversation
This file contains 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
If ROOT is not explicitly imported, the example fails for the light-2106-rhea release, at least for me. Because the stdCharged packages try to import something from the ROOT namespace, but python complains that such a package does not exist. Explicitly importing ROOT fixes this. Not sure if that's also a problem for future basf2 releases or a bug in basf2.
meliache
deleted the
fixgbasf2-example-for-new-basf2-releases-by-explicitly-importing-ROOT
branch
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.
If ROOT is not explicitly imported, the example fails for the light-2106-rhea release, at least for me. Because the stdCharged packages try to import something from the ROOT namespace, but python complains that such a package does not exist. Explicitly importing ROOT fixes this. Not sure if that's also a problem for future basf2 releases or a bug in basf2.