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: docs/getting_started_gym.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ cd crisp_gym
8
8
Now, you should set a few things before installing everything.
9
9
Create a file `scripts/set_env.sh` which will be sourced every time that you run a command in your environment.
10
10
The script will not be tracked by git.
11
-
In this script you need to add a environment variables:
11
+
In this script you need to add the following environment variables:
12
12
13
13
-`ROS_DOMAIN_ID`**(Required)**: which is used to define nodes that should be able to see each other. In our [ROS2 nodes](getting_started_controllers.md) they are set to 100 as default.
14
14
-`CRISP_CONFIG_PATH`**(Optional)**: which should be the path to a config folder similar to [config path of CRISP_PY](https://github.com/utiasDSL/crisp_py/tree/main/config) or [config path of CRISP_GYM](https://github.com/utiasDSL/crisp_gym/tree/main/crisp_gym/config) but with your own custom configurations.
1. This will avoid downloading large files when cloning the repository. You can always download them later with `git lfs pull`.
27
27
2. This will remove logging from SVT codecs, which are used to create data in LeRobot format. The logs can be quite verbose.
28
28
29
-
If you want to work in a *multi-machine setup* (e.g. policy runs in a different machine as controllers/cameras), then check [how to setup multi-machine in ROS2](getting_started_multiple_machines.md).
29
+
If you want to work in a *multi-machine setup* (e.g. policy runs on a different machine than controllers/cameras), then check [how to set up multi-machine in ROS2](getting_started_multiple_machines.md).
30
30
31
31
!!! WARNING "Note on LeRobotDataset version"
32
32
Take a look at the `pixi.toml`. You can define your `lerobot` version there.
33
33
If you want to use later LeRobotDataset v3.0, you need to remove the `rerun` dependency/downgrade it in the `lerobot` like it is done [here](https://github.com/danielsanjosepro/lerobot/commit/b7aea681cda32eee21fa2b368af2119596f4e3ea) since it requires `numpy>=2.0` which is not compatible with the ROS2 versions of `numpy`.
34
34
This will require a small change in the `pixi.toml`:
0 commit comments