ros2_rust
petgraph
ros2_rust | petgraph | |
---|---|---|
6 | 7 | |
809 | 2,655 | |
2.5% | 1.7% | |
8.3 | 7.0 | |
3 days ago | 8 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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
petgraph
-
Borrow Checking, RC, GC, and the Eleven () Other Memory Safety Approaches
Are you just trying to throw shade on Rust?
https://doc.rust-lang.org/std/collections/struct.LinkedList....
> NOTE: It is almost always better to use Vec or VecDeque because array-based containers are generally faster, more memory efficient, and make better use of CPU cache.
https://docs.rs/petgraph 78 M downloads
-
The Hunt for the Missing Data Type
I used to think that since graphs are such a broad datastructure that can be represented in different ways depending on requirements that it just made more sense to implement them at a domain-ish level.
Then I saw Petgraph [0] which is the first time I had really looked at a generic graph library. It's very interesting, but I still have implemented graphs at a domain level.
[0] https://github.com/petgraph/petgraph
-
Many of the typical "Algorithms" as plain Rust implementation
For graph algorithms specifically, also consider looking at the implementations in petgraph.
-
2-way Weak
Take a look at: https://github.com/petgraph/petgraph
-
autograph v0.1.0
Render the backward "graph" using petgraph for visualization and debugging purposes.
-
Another graph library :)
I second the need for quickcheck-style tests. I implemented a matching algorithm in petgraph, and quickcheck discovered so many bugs on non-trivial graphs. Thanks to it, I am now much more confident that it is indeed correct.
-
Why Rust for Robots?
petgraph: Graph data structure library, compatible with Rust
What are some alternatives?
openrr - Open Rust Robotics
rosrust - Pure Rust implementation of a ROS client library
autograph - Machine Learning Library for Rust
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
prepona - A graph crate with simplicity in mind
example-robot-docker - An example docker container for running the Transitive agent on a robot
nphysics - 2 and 3-dimensional rigid body physics engine for Rust.
sybot - Rust library for coordinating components, defining robotic systems and their communication