ROS
ogma | ROS | |
---|---|---|
12 | 83 | |
320 | 2,635 | |
1.9% | 1.3% | |
9.1 | 2.6 | |
about 2 months ago | 3 months ago | |
Haskell | Python | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
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.
ogma
-
[ANN] Copilot 3.16
[1] https://github.com/nasa/ogma
-
[ANN] NASA's Ogma -- now with FPrime support
The changelog is available at: https://github.com/nasa/ogma/releases/tag/v1.0.8
-
More good news from the Ogma team -- Space ROS
https://space-ros.github.io/docs/rolling/Related-Projects/Ogma.html https://github.com/nasa/ogma
-
[ANN] NASA's Ogma 1.0.7
For more details, including videos of monitors being generated and flown in simulators, see: https://github.com/nasa/ogma
-
[ANN] Summer Internship at NASA Ames Research Center
The student, if selected, will be working on extending our capabilities to test cFS/ROS/FPrime applications, especially those using Ogma and/or Copilot for monitoring. Both Ogma and Copilot are open-source software written in Haskell.
-
[ANN] Copilot 3.12
Among others, Copilot has been used at the Safety Critical Avionics Systems Branch of NASA Langley Research Center for monitoring test flights of drones. It also serves as a runtime monitoring backend for the requirements elicitation tool FRET (https://github.com/NASA-SW-VnV/fret/), via Ogma (https://github.com/nasa/ogma).
- [ANN] Copilot 3.11
-
[ANN]: Copilot 3.10 - Runtime monitoring
Understanding these properties can get hard. Using a high level language as opposed to just C is very helpful (we review the code of flight systems with sometimes 4-5 people in the room and it's not trivial at all what it is doing or to show that it is correct). But even streams can sometimes be hard to understand for very complex monitors. We've also built Ogma (https://github.com/nasa/ogma) so that people can write properties in structured natural language, or transform other languages into Copilot (and then C/whatever).
-
Hacker News top posts: Dec 12, 2021
NASA Ogma: generate hard-realtime C runtime monitoring applications\ (0 comments)
- NASA Ogma: generate hard-realtime C runtime monitoring applications
ROS
- Google DeepMind's Aloha Unleashed is pushing the boundaries of robot dexterity
-
Linux market share passes 4% for first time; macOS dominance declines
I wonder if this could be related to M1/2/3 Macs being worse for x86 system software development than the old Intel Macs. I work on ROS[1] which runs on x86 Linux platforms, but usually develop on a Mac. I may have to move to a Linux laptop soon because there's not an easy path (that I'm aware of) to running x86 ROS code on an M3: compiling the entire system for arm would be a huge headache while running x86 code in a Linux VM under Rosetta has a lot of unknowns.
Obviously my case is a bit of an outlier, but once you add up enough outliers you might see a real impact.
[1] https://www.ros.org
-
Getting into Robotics as a Software Engineer
Robotics is a broad field and is a confluence of many specialties: mechanical engineering, hardware engineering, software engineering, control, machine learning, computer vision, anything in between is a good entrance.
Coming from software, if you are interested, I would suggest either:
- Backend platform development (Python, C++ as main programming languages with a strong focus on ROS[1]).
- Frontend development (nothing too different from what's out there).
As small projects I would suggest playing with ROS to learn it and getting a running simulation with a simple robot that you can teleoperate, most of the stack already exists, it's just connecting everything together [2].
Another venue is open source contribution [1] to get known within the community and potentially attract interest from companies. ROS has multiple packages, from cloud infrastructure to drivers and simulation, if you see anything there you could contribute to, they will gladly take contributions.
In general robotics greatly benefits of good technologies from other areas, if there is a tool we use you believe could be better or a lack of good tooling in a specific area, it will get noticed.
So this would be my suggested path: learn C++/Python if you're not familiar with, learn ROS and watch which specialties appear more often in robot related jos posts [3]. If you are really invested, maybe go to a robotics conference as ROSCon to meet other enthusiasts, which companies are engaged with the community, etc.
Good luck!
Note: not everything robot related is done in ROS, but it's almost a standard within the field save for a few exceptions.
[1]: https://www.ros.org/
-
How do I start robotics as a teen with no money?
ROS is an operating system designed for robotics (it can be run many different ways) it includes simulations for many robots (including sensors etc) and you can even design your own fully inside the software. https://www.ros.org/
-
C++ Project Ideas?
Robotics with ROS https://www.ros.org/ (You can do a lot with simulators and don't require actual HW)
-
[Career Advice] Transition from Software Engineer to Robotics
Hardware experience is useful, but not needed to get started working with robotics. With your software background, I recommend you look into learning ROS (Robot Operating System) fundamentals on a personal computer, you can simulate a robot using Gazebo. Good luck!
-
Best practices in creating a Rust API for a C++ library? Seeking advice from those who've done it before.
In Robotics, the Open Motion Planning Library (OMPL) is a popular library for multi-dimensional motion planning, and is used by ROS and other robotics-related software. There are no Rust bindings to OMPL (though there is Rust support for software like ROS), and the library is written almost exclusively in C++. There are Python bindings, but those are generated using Py++. The header files throughout OMPL are C++ header files, not C, as they contain namespaces, classes, etc.
-
[ANN] NASA's Ogma 1.0.9
[3] https://www.ros.org/
-
Newbie to Robotics (Question/Discussion)
ALSO - learn ROS. If you are interested in robotics as a career, this is one of the better things to have good experience for on your resume. There are also good tutorials on using ROS with simulated robots, so if you just want to focus on the software that's a good option :)
-
Real-time C++ on Linux
Roboticist here, have you heard of ROS?
What are some alternatives?
nestjs-monorepo-microservices-proxy - Example of how to implement a Nestjs monorepo with no shared folder
MRPT - :zap: The Mobile Robot Programming Toolkit (MRPT)
nestjs-spelunker - A NestJS Module for generating a NestJS Applications Module Dependency Graph.
Robotics Library (RL) - The Robotics Library (RL) is a self-contained C++ library for rigid body kinematics and dynamics, motion planning, and control.
semver - Nx plugin to automate semantic versioning and CHANGELOG generation.
yarp - YARP - Yet Another Robot Platform
fret - A framework for the elicitation, specification, formalization and understanding of requirements.
DART - DART: Dynamic Animation and Robotics Toolkit
cFS - The Core Flight System (cFS)
PCL - Point Cloud Library (PCL)
rust-brotli - Brotli compressor and decompressor written in rust that optionally avoids the stdlib
moveit - :robot: The MoveIt motion planning framework