Skip to content

Commit

Permalink
Merge pull request #58 from NVIDIA-ISAAC-ROS/release-dp3
Browse files Browse the repository at this point in the history
Isaac ROS 0.30.0 (DP3)
  • Loading branch information
hemalshahNV authored Apr 6, 2023
2 parents c2aa5bb + 30caa26 commit c6c4595
Show file tree
Hide file tree
Showing 159 changed files with 9,310 additions and 4,166 deletions.
3 changes: 3 additions & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -1,3 +1,6 @@
# Ignore Python files in linguist
*.py linguist-detectable=false

# Images
*.gif filter=lfs diff=lfs merge=lfs -text
*.jpg filter=lfs diff=lfs merge=lfs -text
Expand Down
207 changes: 93 additions & 114 deletions README.md

Large diffs are not rendered by default.

143 changes: 0 additions & 143 deletions ci/Jenkinsfile

This file was deleted.

3 changes: 0 additions & 3 deletions ci/copy_results.sh

This file was deleted.

147 changes: 0 additions & 147 deletions ci/nvblox_nightly.jenkinsfile

This file was deleted.

11 changes: 11 additions & 0 deletions docs/linux-people-isaac-sim-workaround.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# Workaround for running People Animation on Linux

Currently, python scripts for animation can only run if the usd is on the same filesystem as the script. This means that it is required to upload the scripts next to where the usd is stored:

1. To retrieve where the scripts are stored, click Window -> Extensions and search for `omni.anim.people`. Then in the extension details click on the folder icon. This will open a window in your browser showing where the extension is stored.

<div align="center"><img src="../resources/isaac_sim_anim_people_scripts.png" width=700px/></div>

2. You now need to upload the `scripts` folder from the `omni/anim/people` folder into a `people_anim_scripts` folder next to the scene usd. To do so, you can right-click on the *Content* tab on the bottom then select *Upload files and folders* to upload the scripts folder.

3. This step will need to be done each time a new version of the extension is released.
Loading

0 comments on commit c6c4595

Please sign in to comment.