Failure Manager: Difference between revisions

Jump to navigation Jump to search
Line 22: Line 22:
== Current Situation ==
== Current Situation ==


All systems and most instruments implemented in the C++ core support basic failure simulation by means of a "serviceable" property. Generally, when this "serviceable" property is set to false, the system will stop updating itself. Some of these systems may support additional, more elaborate types of failures.
All systems and most instruments implemented in the C++ core support basic failure simulation by means of a ''serviceable'' property. Generally, when this property is set to false, the system will stop updating itself. Some of these systems may support additional, more elaborate types of failures.


Other than this convention of using a "serviceable" property, there is no framework on the C++ side with regards to failure simulation. There is, however, a Nasal submodule that can generate random failures by taking user input from the GUI and controlling the relevant properties.
Other than this convention of using a ''serviceable'' property, there is no framework on the C++ side with regards to failure simulation. There is, however, a Nasal submodule that can generate random failures by taking user input from the GUI and controlling the relevant properties.


This approach good, but the main problem is that the supported types of failures are hardcoded both in the Nasal module and the GUI.
The approach is good, but the main problem is that the supported types of failures are hardcoded both in the Nasal module and the GUI.


=== Limitations ===
=== Limitations ===
60

edits

Navigation menu