ogma VS nestjs-spelunker

[1] https://github.com/nasa/ogma

The changelog is available at: https://github.com/nasa/ogma/releases/tag/v1.0.8

https://space-ros.github.io/docs/rolling/Related-Projects/Ogma.html https://github.com/nasa/ogma

For more details, including videos of monitors being generated and flown in simulators, see: https://github.com/nasa/ogma

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.

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).

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).

NASA Ogma: generate hard-realtime C runtime monitoring applications\ (0 comments)

This absolutely isn't true. I'm both on the core team and a maintainer of several open source modules for Nest (nest-commander for CLI creation, ogma my own logger that has a really powerful interceptor, nestjs-spelunker which can print out an object representation of your Nest application and help with module debugging for dependency resolution, and a few more). The command module is even featured in the docs.