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

Error event in FTA sometimes does not show an error type even when one is defined #1962

Closed
reteprelief opened this issue Aug 20, 2019 · 0 comments

Comments

@reteprelief
Copy link
Contributor

@reteprelief reteprelief commented Aug 20, 2019

In the example below the error type is not included in the FTA event representing the error type.
It is included if the out propagation does not have a type or the out propagation type is contained in the constraint{mistake1} of the error event condition

events
mistakes: error event {mistake1, mistake2};
propagations
degraded-[mistakes{mistake1}]-> controlsurfacecmd{NoPilotAction};

@reteprelief reteprelief added this to the 2.6.0 milestone Aug 20, 2019
@reteprelief reteprelief self-assigned this Aug 20, 2019
@lwrage lwrage removed this from the 2.6.0 milestone Aug 21, 2019
@lwrage lwrage added this to the 2.5.2 milestone Aug 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants