handle case when non-identity and no flux term #683
Merged
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.
@stefan-schnake
The flux term should always be at position
0
in theactive_terms
as this is the one that doesn't get split into upper/lower part. Active term0
does not require completeness of the hierarchy, the rest of directions can be given in any order.This fixes the case when we have a term that is a mass term (no flux) but is not identity. We should also double-check the logic in
get_flux_direction()
.