I am currently hardcoding the path to python.sh. Is there any way I can dynamically get the path to it, independently of the user and the Isaac Sim version being used?
I’ve unsuccessfully tried using the omni.isaac.version library, but imports will fail in my ROS2 launchfile since it is not aware of those libraries. However, the ideal solution would return the absolute path to the aforementioned python.sh file.
@martinho_crespo We have a new ROS2 isaacsim package that will allow you to launch isaac sim. Using this package you can pass in theversion or install_path along with standalone ros launch configs to the launch file which I believe will solve what you are trying to do!
However, one drawback of that solution is that the user is forced to specify the Isaac Sim version, as long as it is not 4.0.0. Based on the assumption that most of the users only have a single Isaac Sim version installed, wouldn’t it be better to use whatever version is installed if the user does not specify any? In case the user has several versions installed, simply use the most recent one.
This way, people using ROS2 launch files with isaacsim would find it easier to use, since no version argument would need to be specified.
If that makes sense to you, I can open a ticket here.