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

Resolve time optimization issues #217

Closed
wants to merge 1 commit into from

Conversation

scharalambous-sony
Copy link
Contributor

@scharalambous-sony scharalambous-sony commented Apr 11, 2024

  • Decouples interpolation dt from the minimum dt in retiming operation which are independent
  • Resolves issue where trajectory evaluation will fail after retiming operation
  • Resolves issues where the solver dt will not be restored to its original value
  • Resolves minor bug where the multiplication with finetune_dt_scale was missing

Possibly resolves issues mentioned in #210

@@ -1946,8 +1954,8 @@ def _plan_js_from_solve_state(
og_solve_time = traj_result.solve_time

scaled_dt = torch.clamp(
torch.max(traj_result.optimized_dt[traj_result.success]),
self.trajopt_solver.interpolation_dt,
torch.max(traj_result.optimized_dt[traj_result.success]) * self.finetune_dt_scale,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is I think a minor fix as finetune_dt_scale must have been applied

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, we only use finetune_dt_scale only for pose planning. Joint space planning was implemented to facilitate going to a home configuration after doing manipulation tasks.

The finetune attempts could be implemented in plan_single_js as well. Thanks for bring this up.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I remove this from the PR?

Copy link
Collaborator

@balakumar-s balakumar-s Apr 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have forked your changes, I have a few more changes to make to get this working correctly. I will push these changes and other adjustments before the end of this week.
This way, we don't duplicate efforts.

@scharalambous-sony
Copy link
Contributor Author

One of the issues has been already fixed in the latest release so I removed the corresponding changes from my PR

curobo/CHANGELOG.md

Lines 49 to 50 in d6e600c

- Fix dt update in `MotionGen.plan_single_js()` where dt was not reset after finetunestep, causing
joint space planner to fail often.

@balakumar-s
Copy link
Collaborator

This has been added to v0.7.2

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.

2 participants