Failure Manager: Difference between revisions

Jump to navigation Jump to search
(→‎Examples: trigger renamed as suggested by Galvedro)
Line 25: Line 25:
Design a framework to unify and simplify failure simulation, both from the system modeler and end user perspective.
Design a framework to unify and simplify failure simulation, both from the system modeler and end user perspective.


== Status (07/2014) ==
== Status (12/2014) ==


* A first stable version of the framework is committed to git and will be publicly available on 3.2. See the project sidebar for pointers to the code.
* A first stable version of the framework is available since 3.2. See the project sidebar for pointers to the code.
* Necolattis is working on a more capable Canvas based GUI to replace the old one.
* Necolattis is working on a more capable Canvas based GUI to replace the old one.
* Galvedro is revising the architecture to support aircraft provided wear/damage/failure models.
* Galvedro is revising the architecture to support aircraft provided wear/damage/failure models.
{{FGCquote
  |I have a brand new and quite thourough nasal model for electrical and hydraulic system and I think I will submit it to peer review to see if I can crawl it in the C++ code in order to model its relation to the engine driven accessories (plus corresponding failures and power drain).
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33055004/
    |title=<nowiki>Re: [Flightgear-devel] Features for 3.4 please</nowiki>
    |author=<nowiki>flying.toaster</nowiki>
    |date=<nowiki>2014-11-19</nowiki>
  }}
}}


== Current Situation (3.1 and earlier) ==
== Current Situation (3.1 and earlier) ==
60

edits

Navigation menu