You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).The text was updated successfully, but these errors were encountered: