ros2_rust
r2r
| ros2_rust | r2r | |
|---|---|---|
| 6 | 3 | |
| 809 | 267 | |
| 2.5% | 3.0% | |
| 8.3 | 8.6 | |
| 3 days ago | 6 days ago | |
| Rust | Rust | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ros2_rust
-
Rapier is a set of 2D and 3D physics engines written in Rust
I want to make this happen ! Do you know of any good robotics framework in Rust, as of today ? I heard that ROS2 was slowly including Rust [1], not sure at how did it go. Ros would be a good entry door to sensor fusion, mapping and localization. Because all of the hardware integration / abstraction is already done (in C++). I'm curious to know if company are using this.
[1] https://github.com/ros2-rust/ros2_rust
-
Help with rosrust crate.
The rosrust crate is for ROS1. You either want to switch to that instead or use a crate meant for ROS2 (I think the main crate for that is ros2_rust).
-
Is C++ better for ROS2?
How about: https://github.com/ros2-rust/ros2_rust/blob/main/docs/writing-your-first-rclrs-node.md
-
Announcing ros2-rust (aka rclrs) 0.3
We're happy to announce a new release of of ros2-rust!
-
Announcing ros2-rust 0.2.0
After many months of hard work we're happy to announce [a new release](https://github.com/ros2-rust/ros2_rust/releases/tag/0.2.0) of ros2-rust. This new release includes lots of improvements and features, some of them are:
-
Why Rust for Robots?
ros2-rust: Bindings, a code generator and code examples for ROS2
r2r
-
Rapier is a set of 2D and 3D physics engines written in Rust
You can also check https://github.com/sequenceplanner/r2r for ROS2 bindings (using in production at work for a couple of ROS nodes).
But TBH, in a Rust world, it’s worth revisiting the assumptions behind the ROS node architecture, since Rust is so strong at scaling to large monolithic applications (due to the strict hierarchical code patterns it encourages).
A transitional Rust approach, that doesn't try to reimplement everything from scratch, could do something like a strangler pattern: Take each ROS node, run them separately in “jails” with a Rust API around each one, then implement the plumbing/management logic in pure Rust.
-
Announcing ros2-rust 0.2.0
Nice to see async support! I've been following along with r2r which seems further along (action, parameter support), which has been converted to async-only a while ago. However, it hasn't seen activity since February,
-
Does anyone use rust here for robotics?
ros2 bindings (not the one you get as the first search result, ros2_rust) are far nicer than ros1 ones, mostly because ros2's design of having one library (rcl) designed for bindings is far better. This one even has full async/await support, and because of Rust's flexible design for that, rcl's runtime is plugged into Rust's so it's really efficient.
What are some alternatives?
openrr - Open Rust Robotics
rosrust - Pure Rust implementation of a ROS client library
optimization-engine - Nonconvex embedded optimization: code generation for fast real-time optimization
syact - A library to control motors (mainly stepper motors) and components, read data from sensors and more
example-robot-docker - An example docker container for running the Transitive agent on a robot
sybot - Rust library for coordinating components, defining robotic systems and their communication
rustros_tf - A port of ROS's TF library to rust
petgraph - Graph data structure library for Rust.
dora - low latency, composable, and distributed dataflow for AI and robotic application
bonsai - Rust implementation of AI behavior trees.
nphysics - 2 and 3-dimensional rigid body physics engine for Rust.