Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow monitors to pass values to external handlers or in the message bus #219

Open
ivanperez-keera opened this issue Jan 27, 2025 · 0 comments

Comments

@ivanperez-keera
Copy link
Member

Currently, the monitor notifications to the rest of the system happen in one of two ways: as a call to a user-defined function, or as a notification in the message bus or via a port.

None of those messages carry any additional information: the occurrence of a property or requirement violation is implicit in the fact that the notification is present.

I'd like to change that so that monitors can have additional arguments that are passed to the handlers, to the receiver, or in the message placed in the bus.

This can be used in two ways: to diagnose the issue notified by the monitor, or to provide additional data (leveraging Copilot as a realtime programming language, rather than just a monitoring language).

It will also allow us to write cFS, ROS and F' applications entirely in with Copilot + Ogma, where all the outputs of the application are the result of a trigger call whose associated property could be just true (or some other clock).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant