-
Notifications
You must be signed in to change notification settings - Fork 70
Use Trajectory in BodyCentredBodyDirectionDynamicFrame #1296
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
Conversation
BodyCentredBodyDirectionDynamicFrame( | ||
not_null<Ephemeris<InertialFrame> const*> const ephemeris, | ||
not_null<MassiveBody const*> const primary, | ||
not_null<MassiveBody const*> const secondary) |
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 preferred the previous formatting...
DegreesOfFreedom<InertialFrame> const secondary_degrees_of_freedom = | ||
secondary_trajectory_->EvaluateDegreesOfFreedom(t); | ||
|
||
Vector<Acceleration, InertialFrame> const primary_acceleration = | ||
ephemeris_->ComputeGravitationalAccelerationOnMassiveBody(primary_, t); | ||
// TODO(egg): eventually we want to add the intrinsic acceleration here. | ||
primary_ == nullptr |
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.
This (rather ugly) test could be avoided by having another functor compute_gravitational_acceleration_on_primary
and setting it in the constructor.
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.
The arguments differ, in the second case we pass the position.
815f44e
to
31078a4
Compare
No intrinsic accelerations for now.