fprime
ikos
Our great sponsors
fprime | ikos | |
---|---|---|
73 | 14 | |
9,878 | 1,980 | |
0.7% | 1.2% | |
9.2 | 7.5 | |
1 day ago | 27 days ago | |
C++ | C++ | |
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.
fprime
- Fprime – A flight software and embedded systems framework by NASA
- F Prime – Flight software framework by NASA
- F': NASA Ingenuity Open-Source Flight Software Framework
-
Help finding flight software learning resources
Does anyone have any suggestions for learning to write flight software or have any resources to learn from? I'm not necessarily looking for a framework to learn either, unless you think I should be focusing on something like https://nasa.github.io/fprime/. At this point, I don't know what I don't know... what should I be focusing on?
-
What version of C++ does JPL use?
F´ (F Prime) is originally developed at JPL, which is written under the C++11 standard. The linked video should be based on JPL Institutional Coding Standard for the C Programming Language, which is a guideline for C. They should be using C++11 nowadays.
- GitHub - nasa/fprime: F' - A flight software and embedded systems framework
- Mars-Hubschrauber Ingenuity übertraf alle Erwartungen: Die kleine Helikopterdrohne begleitet den Rover Perseverance seit zwei Jahren – niemand hätte gedacht, dass er so lange durchhält
-
Mars Ingenuity helicopter breaks record for speed and altitude, NASA says
The navigation camera is something you can buy online, the other terrain camera is a Sony IMX 214, The flight software is on github, the altimeter is from sparkfun.
-
[ANN] NASA's Ogma -- now with FPrime support
[1] https://github.com/nasa/fprime
-
NASA should switch to Arch, bro 😎
Probes and satellites either user custom made os, or proprietary real time OS like VxWorks, or more recently open source fprime.
ikos
- Static analyzer IKOS 3.2 Released
- Static analyzer IKOS 3.2-rc1 published – Request for testers
-
The NSA advises move to memory-safe languages
I beg to differ: there are a few tools which are comparable.
Frama-C (https://www.frama-c.com) is an open source framework that has, among its analyzers, one based on abstract interpretation (https://www.frama-c.com/fc-plugins/eva.html) that is very similar in spirit to Astree.
MOPSA (https://mopsa.lip6.fr) is another open-source project (albeit more recent, and in a more "academic" stage) that also provides abstract interpretation to analyze C programs for flaws.
NASA also released IKOS (https://github.com/NASA-SW-VnV/ikos), on the same vein.
Of course they lack the polish of a product which costs tens of thousands of euros per license, but they are open source, and their purpose is the same: to ensure code safety via formal methods, in particular abstract interpretation.
It is possible to get these tools to analyze some code and generate no complaints, which ensures absence of several kinds of problems, such as memory safety issues.
Then again, it's hard to know exactly how much they differ from Astree, since you need a license to compare them, and I don't even know if you are allowed to publish such comparisons.
-
Does anyone use IKOS for static analysis?
I've been playing around with running IKOS (https://github.com/NASA-SW-VnV/ikos), it sounds very cool but doesn't seem to be super well maintained. I've managed to compile my project to llvm bit-code and run the IKSO on it, but the actual analysis seems to be buggy. There are open issues for the problems I encountered, but the make the analysis pretty useless (it thinks most functions are unreachable).
- Astrée Static Analyzer for C and C++
-
Checked C
> https://www.absint.com/astree/index.htm
This looks interesting. It's based on abstract interpretation which is more or less the most powerful approach for imperative code available. (Because the way it works it's likely slow as hell though, I guess).
But it's closed source. One of this kind of products where you need to asks for the price… I think we all know what this means: It'll be laughably expensive.
I don't see any offer for OpenSource projects frankly.
> https://github.com/NASA-SW-VnV/ikos
Also abstract interpretation based. Looks less polished than the first one at first glance.
It's under some questionable license. According to OSI it's OpenSource. According to the FSF it's not. (The FSF argument sounds strong. They're right in my opinion. This NASA license does not look like OpenSource).
But an OpenSource project could use it for free I assume.
> https://github.com/static-analysis-engineering/CodeHawk-C
Much more constrained in scope than the other ones. But looks a little bit "too academic" imho: Uses its own C parser and such.
At least it's OpenSource under MIT license.
Thanks for the links either way! Good to know about some tools in case one would need them at some point.
> I have planned to try using them on OpenZFS for a while, but I am still busy reviewing and fixing reports made by conventional static analyzers.
Stupid question about usual C development practices (as I don't have much contact with that):
Aren't analyzers today part of the build pipeline form the get go? Especially as C is known to be full of booby traps.
Imho it shouldn't be even possible to push anything that has issues discovered by tools.
This should be the lowest barrier as most code analyzers are at most able to spot quite obvious problems (the commercial one above is likely an exception to this "rule"). When even the usual "stupid analyzer" sees issues than the code is very likely in a very bad shape.
Adding such tools later on in the development is like activating warnings post factum: You'll get drowned in issues.
Especially in such critical domains as file-systems I would actually expect that the developers are using "the best tools money can buy" (or at least the best OpenSource tools available).
"Still fixing bugs found by some code analyzer" doesn't sound like someone should have much trust with their data in something like ZFS, to be honest… The statement sounds actually quite scary to me.
- NSA Cybersecurity Information Sheet remarks on C and C++.
-
IKOS: Static analyzer for C/C++ based on the theory of Abstract Interpretation
They have very unusual license which I have never seen before: https://github.com/NASA-SW-VnV/ikos/blob/master/LICENSE.txt
Is anyone familiar with it? Is it OSI certified? (it's not on the OSI's site).
- Is there a project like MIRI but for C++
-
(x-post) Why static analysis on C projects is not widespread already?
Yeah there are tools that require adding contracts as comments. But again, there are also friction-less tools that don't require any changes (for example a NASA one).
What are some alternatives?
ardupilot - ArduPlane, ArduCopter, ArduRover, ArduSub source
Triton - Triton is a dynamic binary analysis library. Build your own program analysis tools, automate your reverse engineering, perform software verification or just emulate code.
cFS - The Core Flight System (cFS)
Awesome-Linux-Software - 🐧 A list of awesome Linux softwares
IntegerAbsoluteDifferenceCpp - Computing the difference between two integer values in C++. Turns out this isn't trivial.
Visual Studio Code - Visual Studio Code
codechecker - CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy
seL4 - The seL4 microkernel
cppbestpractices - Collaborative Collection of C++ Best Practices. This online resource is part of Jason Turner's collection of C++ Best Practices resources. See README.md for more information.
Netdata - The open-source observability platform everyone needs
z3 - The Z3 Theorem Prover