Join GitHub today
Stack Overflow in fault tree generation #1424
This occurs when there is an error path from an in propagation to an out propagation of an in out port.
in some cases the FTA of my AADL-model results in the following error in OSATE. The corresponding error log is attached as well as my model. As the error message isn't helpful at all I tried some fixes. If the error-flow "ef3" is removed the FTA works fine and as soon as it is implemented the error occurs. Right now this error path isn't used (ETH1 has no incoming propagations) but I want to be ready if the model needs to be extended. This is very important in my case of application so I want to predefine the possible error flows to add additional components without any effort. Is this possible with AADL or is there any error in my model? Maybe there is the option to enable or disable this flow if it's not connected as it is possible with the error-source above.