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

ExplicitPhase #97

Merged
merged 64 commits into from
Oct 20, 2018
Merged

ExplicitPhase #97

merged 64 commits into from
Oct 20, 2018

Conversation

robfalck
Copy link
Contributor

Adds ExplicitPhase to Dymos, which implements single, multiple, and hybrid shooting. This capability is still under development and is not yet documented for public use. Notable features to be added:

  • ExplicitPhase.simulate produces wrong results when called from within a trajectory
  • Need to support forward and backward integration, and correctly assess 'fix_initial' and 'fix_final' in those cases.

robfalck and others added 30 commits August 30, 2018 12:21
* Fixed embed-code calls to only use packages. Removed two burn orbit raise code while SNOPT is unavailable. Enabled doc-uploads.

* disabled two burn orbit raise test without SNOPT

* more fixes for doc building
…dymos (OpenMDAO#86)

* adding SNOPT and caching

* adding SNOPT and caching

* playing with pulling out nested ifs
changing to full anaconda due to miniconda recent weirdness
* fixed sign error when initial time or duration is unbounded.

* enable bumpversion automatic commits

* Bump version: 0.11.0 → 0.11.1

* missing run_model call in unbounded time test
robfalck and others added 24 commits October 2, 2018 16:36
…. stage_control_comp interpolates the controls within each segment to the stage nodes for the ODE calls.
…ch phase for initial and final constraints, which more generally works with phases where initial and final values arent in the same vector (like ExplicitPhase)
…nal constraints and is compatible with ExplicitPhase
…rue for set_state_options in ExplicitPhase now raises ValueError. Need to implement boundary constraints for ExplicitPhase in order to solve the brachistochrone problem.
…alues at nodes="steps". It is unable to return state values and ode outputs at any other node subset. simulate_phase works for the brachistochrone explicit test.
@coveralls
Copy link

coveralls commented Oct 20, 2018

Coverage Status

Coverage decreased (-0.3%) to 92.684% when pulling 0611137 on robfalck:nlrk into f8beec5 on OpenMDAO:develop.

@robfalck robfalck merged commit a519f7d into OpenMDAO:develop Oct 20, 2018
@robfalck robfalck mentioned this pull request Oct 20, 2018
@robfalck robfalck deleted the nlrk branch March 7, 2020 22:16
@robfalck robfalck restored the nlrk branch March 7, 2020 22:16
@robfalck robfalck deleted the nlrk branch September 10, 2020 13:45
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 this pull request may close these issues.

3 participants