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
Finally, ROS is required. ROS 1 and ROS 2 are both supported.
19
-
20
-
## ROS 1
21
-
22
-
Follow the installation instructions here: https://wiki.ros.org/noetic/Installation/Ubuntu
23
-
24
-
Unfortunately, dependency management is difficult with this package due to its dependency on `ros2rust`, which requires the packages to be built locally. To make this package easier to compile, open `Cargo.toml` and remove the `ros2` feature and the dependencies listed for ROS 2. Also set the default features to ros1.
28
+
Finally, ROS is required. ROS 1 and ROS 2 are both supported. For ROS1, install Noetic as per [these installation instructions](https://wiki.ros.org/noetic/Installation/Ubuntu). For ROS2, we recommend using Kilted as the latest release ([installation instructions](https://docs.ros.org/en/kilted/Installation/Ubuntu-Install-Debs.html)), but earlier distros should also work.
25
29
26
-
Then, build the package by running:
30
+
In addition to base ROS, a websocket bridge server is required:
27
31
28
32
```bash
29
-
source /opt/ros/noetic/setup.bash
30
-
cargo build
33
+
sudo apt install ros-$ROS_DISTRO-rosbridge-suite
31
34
```
32
35
33
-
You can run the package with logging enabled using:
36
+
Build the package as follows:
34
37
35
38
```bash
36
-
RUST_LOG=debug cargo run
39
+
# Replace $ROS_DISTRO with the installed version of ROS
40
+
source /opt/ros/$ROS_DISTRO/setup.bash
41
+
# For debug mode:
42
+
cargo build
43
+
# For release mode:
44
+
cargo build --release
37
45
```
38
46
39
-
## ROS 2
40
-
41
-
Follow the installation instructions here: https://docs.ros.org/en/jazzy/Installation/Ubuntu-Install-Debs.html
42
-
43
-
Note that any distro of ROS 2 should be compatible, but only Jazzy has been tested so far.
44
-
45
-
Some extra installation is required for Rust-related build tooling:
47
+
The agent relies on rosbridge to relay ROS traffic. Run rosbridge as follows:
*Note that at present, all topics are hard-coded. You may need to check that the simulation is producing images on `/camera/image_raw` and adjust the source code if not. Similarly, the simulation may use Twist or TwistStamped messages for velocity commands, so if movement is not working, double-check the message type.*
84
88
85
-
*Note that cargo commands should be enabled, including cargo build and cargo run, but these did not work on the first system. It is a TODO to fix this build issue.*
0 commit comments