-
Notifications
You must be signed in to change notification settings - Fork 173
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: Move actor state into propagator state #2552
refactor: Move actor state into propagator state #2552
Conversation
…pagator-result-state-restart
📊: Physics performance monitoring for f069ea4physmon summary
|
@paulgessinger @benjaminhuth @asalzburger do you have some early feedback on this? |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2552 +/- ##
==========================================
- Coverage 49.03% 49.03% -0.01%
==========================================
Files 492 492
Lines 28526 28542 +16
Branches 13477 13487 +10
==========================================
+ Hits 13989 13995 +6
Misses 4819 4819
- Partials 9718 9728 +10 ☔ View full report in Codecov by Sentry. |
…pagator-result-state-restart
…pagator-result-state-restart
…pagator-result-state-restart
6467460
to
5c9aa03
Compare
…pagator-result-state-restart
…pagator-result-state-restart
…pagator-result-state-restart
…pagator-result-state-restart
…pagator-result-state-restart
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.
There are a number of cases where I wonder if you need to supply the explicit template parameters of you could let the compiler figure them out. Did you try this out?
Other than that, do you need the template
if you don't supply explicit arguments? I thought this is just needed to disambiguate what <>
means syntactically.
big thanks for your comments @paulgessinger ! I am cleaning this out |
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 am happy with it now.
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.
Found one more case, but not critical
Co-authored-by: Paul Gessinger <hello@paulgessinger.com>
I propose to move the actor state into the propagator state. This allows us to copy the whole propagator state and to start the propagation from a specific state after it stopped before. Intention of this change is that algorithms may want to steer the propagation from the outside rather than from within by using an actor.
I propose to move the actor state into the propagator state. This allows us to copy the whole propagator state and to start the propagation from a specific state after it stopped before.
Intention of this change is that algorithms may want to steer the propagation from the outside rather than from within by using an actor.