You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+29-26Lines changed: 29 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
# Isaac Launchable
4
4
5
-
Isaac Launchable offers a simplified approach to installing and using [Isaac Lab](https://isaac-sim.github.io/IsaacLab/main/index.html) and [Isaac Sim](https://github.com/isaac-sim/IsaacSim).
5
+
Isaac Launchable offers a simplified approach to trying [Isaac Lab](https://isaac-sim.github.io/IsaacLab/main/index.html) and [Isaac Sim](https://github.com/isaac-sim/IsaacSim) in a web browser.
6
6
7
7
Through this project, users can interact with Isaac Sim and Isaac Lab purely from a web browser, with one tab running Visual Studio Code for development and command execution, and another tab providing the streamed user interface for Isaac Sim.
8
8
@@ -15,12 +15,11 @@ The installation steps for Isaac Lab are automated via Docker, such that it can
15
15
16
16
The project includes:
17
17
- a Visual Studio Code container
18
-
- Isaac Lab pre-installed
19
-
- Isaac Sim pre-installed
18
+
- Isaac Lab 2.3 container
19
+
- Isaac Sim 5.1 container
20
20
- an Omniverse Kit App Streaming client, based on the [web-viewer-sample](https://github.com/NVIDIA-Omniverse/web-viewer-sample) project.
21
21
22
22
23
-
24
23
## Quickstart Guide
25
24
This guide will get you started with a Visual Studio Code instance with Isaac Lab preinstalled, and an in-browser user interface provided by Kit App Streaming.
26
25
@@ -31,16 +30,16 @@ This guide will get you started with a Visual Studio Code instance with Isaac La
31
30
> Please note that Brev instances are pay-by-the hour. To make the best use of credits, stop instances when they are not in use. Stopped instances have a smaller storage charge.
32
31
33
32
### Deploy
34
-
1. Click this Deploy Now button
35
-
[](https://brev.nvidia.com/launchable/deploy?launchableID=env-31ezDWyp4LvtDQr5rUhAWOUMFhn)
36
-
2.Click the Deploy Launchable button to spin up the instance.
33
+
1. Click this Deploy Now button ->
34
+
[](https://brev.nvidia.com/launchable/deploy/now?launchableID=env-35JP2ywERLgqtD0b0MIeK1HnF46)
35
+
2.In Brev, click the Deploy Launchable button to spin up the instance.
37
36
3. Wait for the instance to be fully ready on Brev: running, built, and the setup script has completed (first launch can take a while)
38
-
4.On the Brev instance page, scroll to the TCP/UDP ports section.
39
-
5.Click the link for port 80 (HTTP) to open Visual Studio Code Server.
40
-
6.The default password is `password`. This can be modified.
41
-
- To change the password, modify the `PASSWORD` environment variable in this [docker-compose.yml](https://github.com/isaac-sim/isaac-launchable/blob/main/isaac-lab/docker-compose.yml) file.
42
-
7. Inside Visual Studio Code, continue with the [README.md](https://github.com/isaac-sim/isaac-launchable/blob/main/isaac-lab/vscode/README.md) instructions. A summary is provided below.
43
-
8. Now you're in the Visual Studio Code dev environment!
37
+
4.Open the `Logs` tab to view the setup script output. At the end of this output, a password will be printed. This is the password for the Visual Studio Code server. Save this somewhere safe.
38
+
5.On the Brev instance page, scroll to the TCP/UDP ports section.
39
+
6.Click the link for port 80 (HTTP) to open Visual Studio Code Server.
40
+
7. Enter the password from the Logs tab in step 4.
41
+
8. Inside Visual Studio Code, continue with the [README.md](https://github.com/isaac-sim/isaac-launchable/blob/main/isaac-lab/vscode/README.md) instructions. A summary is provided below.
42
+
9. Now you're in the Visual Studio Code dev environment!
44
43
45
44
### Running Isaac Sim and Isaac Lab - the quick version
46
45
In short, the commands to run Isaac Lab and Isaac Sim are similar to workstation installs, except when you need the UI. Then we add a few arguments for streaming to the normal commands.
@@ -54,7 +53,7 @@ The top-level README.md file in the dev environment contains a shortened version
Note how this is similar to the workstation command for launching Isaac Sim, but uses additional arguments for streaming.
60
59
@@ -65,11 +64,10 @@ Note how this is similar to the workstation command for launching Isaac Sim, but
65
64
5. After a few seconds you should see the UI in the viewer tab. The first launch may take much longer as shaders are cached.
66
65
6. On subsequent relaunches, simply refresh this tab to see the UI.
67
66
68
-
69
67
### Running Isaac Lab Commands - Detailed Guide
70
68
To run an Isaac Lab command, first consider if it requires the UI. If it doesn't, such as during policy training, simply run the command as normal.
71
69
72
-
If you need to see the Isaac Sim UI, just append these additional arguments to the Isaac Lab command: `--kit_args="--no-window --enable omni.kit.livestream.webrtc"`.
70
+
If you need to see the Isaac Sim UI, just append these additional arguments to the Isaac Lab command: `--livestream 2`.
73
71
74
72
Let's try out the Ant walking task as a demo. We chose this task because it trains quickly.
75
73
@@ -81,7 +79,7 @@ This is essentially the same command you would run for a workstation install of
81
79
82
80
2. Once the training script is complete, test the policy behavior by running:
8. Under "Do you want a Jupyter Notebook experience" select "No, I don't want Jupyter".
130
-
9. Select the TCP/UDP ports tab.
131
-
10. Expose the following ports (for Visual Studio Code Server and Kit App Streaming) to a specific public IP address that will be using this service.
127
+
7. The VSCode container expects a password to be set via the $VSCODE_PASSWORD environment variable. Add the following environment variable to the setup script. Replace `your_password` with your desired password, or generate it securely.
128
+
```bash
129
+
export VSCODE_PASSWORD=your_password
130
+
```
131
+
132
+
8. Click Next.
133
+
9. Under "Do you want a Jupyter Notebook experience" select "No, I don't want Jupyter".
134
+
10. Select the TCP/UDP ports tab.
135
+
11. Expose the following ports (for Visual Studio Code Server and Kit App Streaming) to a specific public IP address that will be using this service.
132
136
```
133
137
80
134
138
1024
135
139
47998
136
140
49100
137
141
```
138
-
11. Click Next.
139
-
12. Choose your desired compute.
142
+
12. Click Next.
143
+
13. Choose your desired compute.
140
144
141
145
> [!NOTE]
142
146
> GPUs with RT cores are required for Kit App Streaming.
143
147
> The compute specs and driver versions provided also need to be compatible with [Isaac Sim](https://docs.isaacsim.omniverse.nvidia.com/latest/installation/requirements.html). The available drivers are not exposed on this Brev page currently.
144
148
145
149
> [!IMPORTANT]
146
150
> The project is not currently compatible with Crusoe instances. AWS has been tested and is used for the example launchable.
147
-
13. Choose disk storage, then click Next.
148
-
14. Enter a name, then select **Create Launchable**
151
+
14. Choose disk storage, then click Next.
152
+
15. Enter a name, then select **Create Launchable**
149
153
150
154
Congratulations! You now have a custom launchable.
151
155
@@ -155,7 +159,6 @@ This project can also be used to run a containerized version of Isaac Sim and Is
155
159
156
160
To use this project locally, you'll need a workstation that meets [Isaac Sim](https://docs.isaacsim.omniverse.nvidia.com/latest/installation/requirements.html)'s requirements.
157
161
158
-
159
162
1. Install the NVIDIA Container Toolkit: `sudo install nvidia-container-toolkit`
160
163
2. Inside [this docker-compose file](https://github.com/isaac-sim/isaac-launchable/blob/main/isaac-lab/docker-compose.yml), change the `ENV=brev` line to `ENV=localhost`.
161
164
3. Inside the folder `isaac-lab`, run `docker compose up -d`.
0 commit comments