v0.7.2 Re-timing post-processing improves motion generation quality at slow speeds, API documentation #240
balakumar-s
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
New Features
slow down optimized trajectories. Use
MotionGenPlanConfig.time_dilation_factor<1.0to slow down aplanned trajectory. This is more robust than setting
velocity_scale<1.0and also allows forchanging the speed of trajectories between planning calls
curobo.util.loggeraddslogger_nameas an input, enabling use of logging api with otherpackages.
Changes in default behavior
CudaRobotModelStatefromcurobo.cuda_robot_model.typestocurobo.cuda_robot_model.cuda_robot_modelsmall range of joint limits when
velocity_scale<0.1.TrajResultis renamed toTrajOptResultto be consistent with other solvers.get_batch_interpolated_trajectoryhas changed.MpcSolverConfig.load_from_robot_configusesworld_modelinstead ofworld_cfgto beconsistent with other wrappers.
BugFixes & Misc.
MotionGen.plan_batch_envwhere graph planner was being set to True. This also fixesisaac sim example
batch_motion_gen_reacher.py.min_dtas a parameter toMotionGenConfigandTrajOptSolverConfigto improve readabilityand allow for having smaller
interpolation_dt.epsilontomin_dtto make sure after time scaling, joint temporal values are not exactlyat their limits.
max_joint_velandmax_joint_accinTrajOptSolver1/limit_range**2whenlimit_range<1.0to be robust to smalljoint limits.
curobo.util.logger,curobo.wrap.reacher.motion_gen,curobo.wrap.reacher.mpc, andcurobo.wrap.reacher.trajopt.instead of raising an exception.
torch.cuda.synchronize()now only synchronizes specified cuda device withtorch.cuda.synchronize(device=self.tensor_args.device)This discussion was created from the release Re-timing post-processing improves motion generation quality at slow speeds, API documentation.
All reactions