-
Notifications
You must be signed in to change notification settings - Fork 176
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
refactor: Refactor SurfaceReached
aborter
#2603
refactor: Refactor SurfaceReached
aborter
#2603
Conversation
SurfaceReached
aborterSurfaceReached
aborter
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2603 +/- ##
==========================================
- Coverage 49.64% 49.56% -0.08%
==========================================
Files 474 474
Lines 26946 26923 -23
Branches 12415 12422 +7
==========================================
- Hits 13376 13344 -32
- Misses 4747 4750 +3
- Partials 8823 8829 +6 ☔ View full report in Codecov by Sentry. |
there is some physmon diff for the gsf but it looks marginal to me. maybe @benjaminhuth can have a look. will not update the reference for now |
Seems to improve things actually, right? Maybe because the overstep limit is now properly propagated? |
…face-reached-aborter
…face-reached-aborter
Currently it is not possible to discover in which stage of propagation we are in the actors and aborters. By introducing a propagator stage enum, adding it to the state and setting it in the proagator loop this can be used in the actors and aborters. Pulled out of #2603
This does not cause any output changes in Athena. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think i like this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good from my side! (mainly looked at the multi stepper aborter)
Aimed to improve consistency and split surface and volume interactions into two logical parts pulled out of #2603
With these changes I try to decouple the navigator and surface reached aborter further. I don't believe that the navigator has to care about the target surface other than optimization reasons while the surface reached aborter should only care about the surface it is supposed to care about without looking at or touching the navigation state.
blocked by