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
-
New Features
slow down optimized trajectories. Use
MotionGenPlanConfig.time_dilation_factor<1.0
to slow down aplanned trajectory. This is more robust than setting
velocity_scale<1.0
and also allows forchanging the speed of trajectories between planning calls
curobo.util.logger
addslogger_name
as an input, enabling use of logging api with otherpackages.
Changes in default behavior
CudaRobotModelState
fromcurobo.cuda_robot_model.types
tocurobo.cuda_robot_model.cuda_robot_model
small range of joint limits when
velocity_scale<0.1
.TrajResult
is renamed toTrajOptResult
to be consistent with other solvers.get_batch_interpolated_trajectory
has changed.MpcSolverConfig.load_from_robot_config
usesworld_model
instead ofworld_cfg
to beconsistent with other wrappers.
BugFixes & Misc.
MotionGen.plan_batch_env
where graph planner was being set to True. This also fixesisaac sim example
batch_motion_gen_reacher.py
.min_dt
as a parameter toMotionGenConfig
andTrajOptSolverConfig
to improve readabilityand allow for having smaller
interpolation_dt
.epsilon
tomin_dt
to make sure after time scaling, joint temporal values are not exactlyat their limits.
max_joint_vel
andmax_joint_acc
inTrajOptSolver
1/limit_range**2
whenlimit_range<1.0
to 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.
Beta Was this translation helpful? Give feedback.
All reactions