Skip to content
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

Trajectory link_phases method should support arguments of add_linkage_constraint. #855

Closed
robfalck opened this issue Nov 9, 2022 · 0 comments · Fixed by #858
Closed
Assignees

Comments

@robfalck
Copy link
Contributor

robfalck commented Nov 9, 2022

Proposed feature.

The link_phases method is a simpler wrapper for the more complex but more capable add_linkage_constraint method.
In order to allow the user to control things like the scaling factors for the imposed constraints, link_phases should support the following options and pass them to add_linkage_constraint.

  • units
  • scaler
  • adder
  • ref0
  • ref
  • linear

If connected is specified, then the above options will have no effect.

Note sign_a and sign_b are explicitly left out here, since the intent of link_phases is to provide continuity in value.

Example


traj.link_phases(
    phases=['ascent', 'descent'],
    vars=['time', 'r', 'h', 'gam'],
    scaler=1.0E-3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant