Skip to content

Commit 1e21daa

Browse files
fix grammar
1 parent d814b6e commit 1e21daa

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

docs/getting_started_gym.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ cd crisp_gym
88
Now, you should set a few things before installing everything.
99
Create a file `scripts/set_env.sh` which will be sourced every time that you run a command in your environment.
1010
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:
1212

1313
- `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.
1414
- `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.
@@ -26,17 +26,17 @@ export CRISP_CONFIG_PATH=/path/to/config1/folder:/path/to/config2/folder # opti
2626
1. This will avoid downloading large files when cloning the repository. You can always download them later with `git lfs pull`.
2727
2. This will remove logging from SVT codecs, which are used to create data in LeRobot format. The logs can be quite verbose.
2828

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).
3030

3131
!!! WARNING "Note on LeRobotDataset version"
3232
Take a look at the `pixi.toml`. You can define your `lerobot` version there.
3333
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`.
3434
This will require a small change in the `pixi.toml`:
3535
```toml title="pixi.toml" hl_lines="11-12"
3636
[feature.lerobot.pypi-dependencies]
37-
# Commnet this line:
37+
# Comment this line:
3838
# lerobot = { git = "https://github.com/huggingface/lerobot", rev = "dacd1d7f5c719c3e56d7b7154a751bef6d5bd23c", extras = ["smolvla"]}
39-
# Add use your fixed fork:
39+
# Add your fixed fork:
4040
lerobot = { git = "https://github.com/your-fork/lerobot" }
4141
# Or if present locally:
4242
# lerobot = { path = "../lerobot/", editable = true }

0 commit comments

Comments
 (0)