-
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 direct navigator initialization #3183
refactor!: Refactor direct navigator initialization #3183
Conversation
📊: Physics performance monitoring for 11b3aaephysmon summary
|
7bfd0f0
to
522053f
Compare
522053f
to
cabfe79
Compare
cabfe79
to
9ce6967
Compare
95a67da
to
ee987f4
Compare
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 to me. I like that we can get rid of the initialization actor.
Can you add a few words on the intention of this change to the PR description (also for future reference)
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 to me. I like that we can get rid of the initialization actor this way.
Can you add a few words describing the change to the PR description?
|
After #3181 and #3182 we can properly initialize the
DirectNavigator
with the surface sequence without a specialActor
modifying the sequence at the right moment. This is directly applied for the KF and GSF.blocked by:
Navigator
#3190