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

get_world_self_collision_distance_from_joints keep getting all zero result #430

Open
frankchan12138 opened this issue Nov 7, 2024 · 0 comments
Assignees

Comments

@frankchan12138
Copy link

Hello, @balakumar-s , I try to use VoxelGrid to check whether the robot_trajectory is valid as the code follow. But I keep getting d_world all zero even when I add obstables in the FOV of with realsense camera to generate collision scene. Is there any advice to figure out what's wrong?

rb_world_config = RobotWorldConfig.load_from_config(robot_dict, world_file, tensor_args,
            collision_checker_type = CollisionCheckerType.VOXEL, collision_activation_distance=0.0)
self.__curobo_fn = RobotWorld(rb_world_config)
...
voxel = [esdf_grid]
self.__curobo_fn.update_world(WorldConfig(
            sphere = sphere_list,
            cuboid = cuboid_list,
            cylinder = cylinder_list,
            mesh = mesh_list,
            voxel = voxel_list)
        )

array_data = []
for i in range(0, min(len(request.robot_trajectory.joint_trajectory.points), 10)):
    array_data.append(request.robot_trajectory.joint_trajectory.points[i].positions)

q_s = self.__tensor_args.to_device(np.array(array_data))
d_world, d_self = self.__curobo_fn.get_world_self_collision_distance_from_joints(q_s)
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

No branches or pull requests

2 participants