Introducing 2D mode #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
use `python policy_compression_train.py --dim=2 --num_obstacles=<n_obs>`
* adjusted ActionManager so it can also handle actions with number of trajectories other than the given one
Jannes Develop Version
…(dim=2, n_obstacles=1)
janneshb
force-pushed
the
master
branch
7 times, most recently
from
5031c65 to
650a69e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introducing 2D mode as discussed with @jtorde.
Mainly:
solver_ipopt.cppnow uses dynamically sized Eigen vectors to be independent of dimensionsmain.mcorrectly generates CasADi files for either 2D or 3D depending on the parameterdim_posFOV tracking is untested in 2D.