Fix the result of innerMaterial()
and outerMaterial()
depending on if the other is called first
#1414
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.
BEGINRELEASENOTES
innerMaterial()
andouterMaterial()
depending on if the other is called firstENDRELEASENOTES
Fix #1413.
I don't know exactly why this is happening for a few surfaces. What happens is that when getting the next boundary after
innerMaterial()
has been called is not the same as if it wasn't called (in this callDD4hep/DDRec/src/MaterialManager.cpp
Line 77 in 24fcc3e