wrapyfi
evarobot
wrapyfi | evarobot | |
---|---|---|
4 | 2 | |
70 | 2 | |
- | - | |
9.6 | 0.0 | |
20 days ago | over 2 years ago | |
Python | Python | |
GNU General Public License v3.0 or later | 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.
wrapyfi
-
Wrapyfi for distributing LLaMA by Meta on different machines
The authors present an example of combining Wrapyfi (https://github.com/fabawi/wrapyfi), a Python wrapper for message-oriented and robotics middleware, with LLaMA (https://github.com/facebookresearch/llama), a series of large language models from Meta AI. They demonstrate how Wrapyfi can enable running LLaMA on multiple mid-range machines with high inference speed and low cost. They also provide links to their GitHub repository (https://github.com/modular-ml/wrapyfi-examples_llama) and paper (https://arxiv.org/abs/2302.09648) for more details. They state that this example can revolutionize natural language processing tasks such as text generation, summarization, question answering, sentiment analysis, etc. without having to buy new hardware and use their existing infrastructure!
- Wrapify is a middleware communication wrapper for running the same script on multiple machines. Run the Python script everywhere and choose where each method executes by simply declaring it as a publisher or a listener [currently supports YARP; ROS and ROS2 coming soon]
evarobot
-
Is ROS only about packages?
I am sorry if the question sounds a little aggressive but I want it to be direct. I was just messing around with ROS and was comparing Neuronbot (Noetic) and Evarobot. I have tried both and Neuronbot is better for dynamic environment (and faster as well). I compared their file structures and some navigation files, and found the only difference to be the larger range of planners Neuronbot was using. There were no custom nodes or services publishing goals, optimizing paths, global planner, etc., in either of them.
-
What's next? After ROS tutorials
Now I want to do the fun stuff and actually write my own code for a robot. I found evabot which seems to be perfect (it's just a simulation with a 2d navigation tool that doesn't work for dynamic environments). I know a little bit of C++ but prefer developing on Python (hopefully 100% Python). My goal is to make 2d navigation work in a dynamic environment.
What are some alternatives?
nmea_navsat_driver - ROS package containing drivers for NMEA devices that can output satellite navigation data (e.g. GPS or GLONASS).
ur3 - ROS-based UR3/UR3e controller with simulation in Gazebo. Adaptable to other UR robots
aztarna - aztarna, a footprinting tool for robots.
Pyluos - A Python library to program a Luos based network through a high level interface.
interbotix_ros_toolboxes - Support-level ROS Packages for Interbotix Robots
interbotix_ros_manipulators - ROS Packages for Interbotix Arms
linorobot2 - Autonomous mobile robots (2WD, 4WD, Mecanum Drive)
zeroros - Python-only dependency-free middleware that resembles ROS using ZeroMQ
Dstar-lite-pathplanner - Implementation of the D* lite algorithm in Python for "Improved Fast Replanning for Robot Navigation in Unknown Terrain"