Question about the MotionGen about curobo HOT 8 CLOSED

If you are trying to use the motion generation on obstacles that are represented as meshes or primitives, you can use CollisionCheckerType.Mesh instead of CollisionCheckerType.BLOX. Note that when changing to a different collision checker type, change the world config to collision_table.yml to load an appropriate set of obstacles.

If you are trying to use obstacles from a depth camera, try one of the below:

1. you might need to compile glog from source following instructions from : https://curobo.org/source/getting_started/1_install_instructions.html#installing-nvblox-with-isaac-sim
2. If that doesn't work, you can follow instructions from dockerfile here:

   curobo/docker/isaac_sim.dockerfile

   Line 186 in 21d434f

   RUN cd /pkgs && git clone https://github.com/sqlite/sqlite.git -b version-3.39.4 && \

We found nvblox to work reliably inside the provided dockerfiles. When using outside docker, you might have to make sure the glog library is correctly linked to avoid getting a segfault.

We found compiling nvblox with statically linked glog following these instructions (

from curobo.

I have also encountered the same problem described above and it happens when the warmup() is called. You can remove warmup() and continue to use the motion_gen planning but without the speedup that the warmup provides. I'll update this thread if I get to the bottom of this

from curobo.

We have a fix for this issue, will push an update before Monday.

from curobo.

I have also encountered the same problem described above and it happens when the warmup() is called. You can remove warmup() and continue to use the motion_gen planning but without the speedup that the warmup provides. I'll update this thread if I get to the bottom of this

I get the exact same, but commenting the warmup did not solve. I will wait for the next release then

from curobo.

We just pushed a new release that works better with nvblox. Can you try it now and close this issue if it's resolved?

from curobo.

We just pushed a new release that works better with nvblox. Can you try it now and close this issue if it's resolved?

Thanks! @balakumar-s
I pulled the new code and reinstalled it, but it seems that the issue has not been resolved.
But this issue did not occur when running in the docker you provided(Even in the old version curobo).
Is this an issue with the PyTorch version? The pytorch version in the docker is 2.1.0a0+29c30b1, but in my conda environment, the pytorch version is 1.13.1+cu117
I will try installing a new version of pytorch later to see if the problem is resolved.😄

from curobo.

Did you also remove nvblox (uninstall any files from system path as well) and reinstall it with the new instructions?

from curobo.

Did you also remove nvblox (uninstall any files from system path as well) and reinstall it with the new instructions?

Thank you. I have reinstalled Curobo according to the latest installation documentation and it can now run successfully. I will close this issue.😄

from curobo.