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

Controls for tool initialization #5

Closed
kkevlar opened this issue Aug 7, 2018 · 2 comments
Closed

Controls for tool initialization #5

kkevlar opened this issue Aug 7, 2018 · 2 comments
Labels
enhancement New feature or request priority development priority

Comments

@kkevlar
Copy link
Contributor

kkevlar commented Aug 7, 2018

The user currently has no control as to how the tool is initialized. Cassie.xml and stepdata.bin are automatically loaded as soon as the executable is run as the model/trajectory.

The user should have control of at least the following initialization options:

  • Initialize the tool with any valid trajectory
  • Choose how many times the trajectory loops when the timeline is created
  • Initialize the tool with only a single pose
  • Clip a segment of an initial trajectory file to loop over

Best case, the user could also drag models/trajectories into the window as is implemented in the original simulate.cpp which is bundled with the MuJoCo library.

@kkevlar kkevlar added the enhancement New feature or request label Aug 7, 2018
@kkevlar
Copy link
Contributor Author

kkevlar commented Aug 8, 2018

Timeline initialization discussed here and this documentation will need to be updated through resolving this issue.

@kkevlar kkevlar added the priority development priority label Aug 8, 2018
This was referenced Aug 16, 2018
kkevlar added a commit that referenced this issue Aug 29, 2018
@kkevlar
Copy link
Contributor Author

kkevlar commented Aug 29, 2018

Merged in e90c1f7

@kkevlar kkevlar closed this as completed Aug 29, 2018
kkevlar added a commit that referenced this issue Aug 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority development priority
Projects
None yet
Development

No branches or pull requests

1 participant