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

FTA treats multiple out propagation conditions for the same our propagation and type incorrectly #1961

Closed
reteprelief opened this issue Aug 20, 2019 · 1 comment · Fixed by #1969

Comments

@reteprelief
Copy link
Contributor

commented Aug 20, 2019

Example:
two out propagation conditions for the same out propagation and error type.
Each condition is based on an error state and an error event condition.
The result should be a OR of two PriorityAnd, each priority and representing the error event and the trigger event transitioning to the error state.
It puts the error event and error state transition trigger under the same PriorityAnd event.

ACCNoKnowledge-[mistakes{mistake2}]-> cmd{NoPilotAction};
AOADiscrepancyUnaware-[mistakes{mistake1}]-> cmd{NoPilotAction};

@reteprelief reteprelief added this to the 2.6.0 milestone Aug 20, 2019

@reteprelief reteprelief self-assigned this Aug 20, 2019

@reteprelief reteprelief modified the milestones: 2.6.0, 2.5.2 Aug 21, 2019

@reteprelief

This comment has been minimized.

Copy link
Contributor Author

commented Aug 21, 2019

Had to make sure FTA Event names are unique for different outgoing propagation conditions if these did not have a declarative name. My 737 example had such a situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.