Add isaacsim pip with cache pkgs

[baconbrot]

Please add the following dependency to the rosdep database.

Package name:

Edit: In the newly released Isaac Sim 4.5.0, the package structure has changed. Packages are now installed via pip extras, and I propose adding the following extras to rosdep to replace the old ones:

python3-isaacsim-all-pip
python3-isaacsim-rl-pip
python3-isaacsim-ros-pip
python3-isaacsim-ros2-pip
python3-isaacsim-extscache-pip

python3-isaacsim-pip
python3-isaacsim-extscache-physics-pip
python3-isaacsim-extscache-kit-pip
python3-isaacsim-extscache-kit-sdk-pip

Package Upstream Source:

NA

Purpose of using this:

Simulating ROS integrated robots using NVIDIA Omniverse IsaacSim.
The main package isaacsim can be supplemented by any subset of the other three cache packages to accelerate first time startup.

Links to Distribution Packages

There are no special distribution packages, only pip.
pip:

• https://pypi.org/project/isaacsim/
• https://pypi.org/project/isaacsim-extscache-physics/
• https://pypi.org/project/isaacsim-extscache-kit/
• https://pypi.org/project/isaacsim-extscache-kit-sdk/

Edit: Available extras can be inspected in the isaacsim-4.5.0.0.tar.gz file available on PyPI.

Additional notes

Installation with rosdep might require the user to set the --as-root pip:false flag, e.g.
rosdep install -i -y --from-paths src --as-root pip:false

[github-actions]

Thanks for sending a pull request to ROS distro!

This is an automated tool that helps check your pull request for correctness.
This tool checks a number of attributes associated with your ROS package and generates a report that helps our reviewers merge your pull request in a timely fashion. Here are a few things to consider when sending adding or updating a package to ROS Distro.
ROS Distro includes a very helpful CONTRIBUTING.md file that we recommend reading if it is your first time submitting a package.
Please also read the ROS Distro review guidelines which summarizes this release process.

ROS Distro Considerations

• ROS Distributions are created using REP-134 Standards Track as a guide.
• Your package name should comply to REP-144 ROS Package Naming
• Your package must build for all platforms and architectures on the ROS buildfarm. See REP-2000 ROS Releases and Supported Platforms for all supported platforms for your ROS Distro.
• Your package must contain an OSI approved license. Your package.xml file must also include that license in a machine readable format. See REP-149 Package Manifest Format Three Specification for additional details.
• A publicly available, open source, repository for your ROS package.
• While not required, we recommend that you create an account for ROS Discourse and subscribe to the appropriate release topic.
• If you would like, you may join our Discord Server and ask questions in the #infra-help channel.

Package Considerations

Having your package included in a ROS Distro is a badge of quality, and we recommend that package developers strive to create packages of the highest quality. We recommend package developers review the following resources before submitting their package.

• REP-2004 Package Quality Declaration-- The ROS 2 TSC has created a quality rating system for ROS packages. These ratings should serve as a guide for package developers. We recommend package developers achieve a quality level of three or higher.
• Documentation -- it is recommended that ROS packages include an extensive README.md file, and API level documentation using the Sphinx documentation system.
• Maintainer Responsibilities -- the ROS 2 documentation includes a guide to ROS package maintainer responsibilities that summarizes your responsibilities as an open source maintainer. While we do not enforce these requirements on package maintainers they should be considered best practices.
• We recommend that your package should strive to conform to the ROS 2 Developer Guide and the ROS 2 Style Guide.

Need Help?

Please post your questions to Robotics Stack Exchange or refer to the #infra-help channel on our Discord server.

---

For changes related to rosdep:

• ✅ New rosdep keys are named appropriately

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks

[baconbrot]

This package is currently only available for python 3.10. Should the pip install be restricted to e.g. Ubuntu jammy (which has default python version 3.10.X)?

[baconbrot]

IsaacSim 4.5.0 was released during this PR.

The new version replaces isaacsim with isaacsim[all].
Since pip extras aren't supported yet (see ros-infrastructure/rosdep#900), I'll manually add each extra from isaacsim including the corresponding packages to python3-isaacsim-<extra>-pip, similar to how python-pytorch-pip installs both pytorch and torchvision.

[github-actions]

For changes related to rosdep:

• ✅ New rosdep keys are named appropriately

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks

[github-actions]

This PR hasn't been activity in 14 days. If you are still are interested in getting it merged please provide an update. Otherwise it will likely be closed by a rosdistro maintainer following our contributing policy. It's been labeled "stale" for visibility to the maintainers. If this label isn't appropriate, you can ask a maintainer to remove the label and add the 'persistent' label.

[baconbrot]

Still required

[cottsay]

I don't have any particular feedback here. The rules look really big but I think it makes sense to break out the full list of packages included in the extra like that.

This package is currently only available for python 3.10. Should the pip install be restricted to e.g. Ubuntu jammy (which has default python version 3.10.X)?

I don't think so. It would be different if we were talking about the system package manager, but you could absolutely use pip on one of those platforms with a different version of the interpreter. In any case, pip will give a graceful error if it finds that you're trying to install using an unsupported interpreter since isaacsim properly declares the constraint.

Standard disclaimer that rosdep keys backed by pip rules can't be used by packages which are built on the official buildfarm.