Skip to content

Commit 74f729c

Browse files
Merge pull request #608 from ARISE-Initiative/fix-doc-links
Fix doc links
2 parents 359cfbc + b0cddaa commit 74f729c

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

docs/modules/controllers.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The "WholeBodyIK" composite controller takes in end effector targets, and conver
3333
***********************
3434

3535
Third-party controllers integrate custom or external control algorithms into robosuite. Examples include https://github.com/kevinzakka/mink. We provide
36-
an example of adding a third part controller in https://robosuite.ai/docs/tutorials/add_controller.html.
36+
an example of adding a third-party controller in https://robosuite.ai/docs/tutorials/add_controller.html.
3737

3838

3939
Workflow of Loading Configs

docs/tutorials/add_environment.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
## Building Your Own Environments
22

3-
**robosuite** offers great flexibility in creating your own environments. A [task](modeling/task) typically involves the participation of a [robot](modeling/robot_model) with [grippers](modeling/robot_model.html#gripper-model) as its end-effectors, an [arena](modeling/arena) (workspace), and [objects](modeling/object_model) that the robot interacts with. For a detailed overview of our design architecture, please check out the [Overview](modules/overview) page in Modules. Our Modeling APIs provide methods of composing these modularized elements into a scene, which can be loaded in MuJoCo for simulation. To build your own environments, we recommend you take a look at the [Environment classes](simulation/environment) which have used these APIs to define robotics environments and tasks and the [source code](https://github.com/ARISE-Initiative/robosuite/tree/master/robosuite/environments) of our standardized environments. Below we walk through a step-by-step example of building a new tabletop manipulation environment with our APIs.
3+
**robosuite** offers great flexibility in creating your own environments. A [task](../modeling/task) typically involves the participation of a [robot](../modeling/robot_model) with [grippers](../modeling/robot_model.html#gripper-model) as its end-effectors, an [arena](../modeling/arena) (workspace), and [objects](../modeling/object_model) that the robot interacts with. For a detailed overview of our design architecture, please check out the [Overview](../modules/overview) page in Modules. Our Modeling APIs provide methods of composing these modularized elements into a scene, which can be loaded in MuJoCo for simulation. To build your own environments, we recommend you take a look at the [Environment classes](../simulation/environment) which have used these APIs to define robotics environments and tasks and the [source code](https://github.com/ARISE-Initiative/robosuite/tree/master/robosuite/environments) of our standardized environments. Below we walk through a step-by-step example of building a new tabletop manipulation environment with our APIs.
44

5-
**Step 1: Creating the world.** All mujoco object definitions are housed in an xml. We create a [MujocoWorldBase](source/robosuite.models) class to do it.
5+
**Step 1: Creating the world.** All mujoco object definitions are housed in an xml. We create a [MujocoWorldBase](../source/robosuite.models) class to do it.
66
```python
77
from robosuite.models import MujocoWorldBase
88

@@ -28,7 +28,7 @@ mujoco_robot.set_base_xpos([0, 0, 0])
2828
world.merge(mujoco_robot)
2929
```
3030

31-
**Step 3: Creating the table.** We can initialize the [TableArena](source/robosuite.models.arenas) instance that creates a table and the floorplane
31+
**Step 3: Creating the table.** We can initialize the [TableArena](../source/robosuite.models.arenas) instance that creates a table and the floorplane
3232
```python
3333
from robosuite.models.arenas import TableArena
3434

@@ -37,7 +37,7 @@ mujoco_arena.set_origin([0.8, 0, 0])
3737
world.merge(mujoco_arena)
3838
```
3939

40-
**Step 4: Adding the object.** For details of `MujocoObject`, refer to the documentation about [MujocoObject](modeling/object_model), we can create a ball and add it to the world.
40+
**Step 4: Adding the object.** For details of `MujocoObject`, refer to the documentation about [MujocoObject](../modeling/object_model), we can create a ball and add it to the world.
4141
```python
4242
from robosuite.models.objects import BallObject
4343
from robosuite.utils.mjcf_utils import new_joint
@@ -50,7 +50,7 @@ sphere.set('pos', '1.0 0 1.0')
5050
world.worldbody.append(sphere)
5151
```
5252

53-
**Step 5: Running Simulation.** Once we have created the object, we can obtain a `mujoco_py` model by running
53+
**Step 5: Running Simulation.** Once we have created the object, we can obtain a `mujoco.MjModel` model by running
5454
```python
5555
model = world.get_model(mode="mujoco")
5656
```

0 commit comments

Comments
 (0)