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

Fault trace has unnecessary events when outgoing propagation is specified #1882

reteprelief opened this issue Jul 9, 2019 · 1 comment


Copy link

@reteprelief reteprelief commented Jul 9, 2019

When the top level component instance has an outgoing propagation specification with a multi element condition then not only the condition is reflected in the fault trace but also each of the elements in the condition as top level event. It should only be the condition.

@reteprelief reteprelief added this to the 2.5.1 milestone Jul 9, 2019
@reteprelief reteprelief self-assigned this Jul 9, 2019
Copy link
Contributor Author

@reteprelief reteprelief commented Jul 9, 2019

It also results in an incorrect fault tree.
All our examples sofar had a single element as condition for the out propagation condition (OPC) of the top-level component..
My MAX example uses logical expression on multiple engines in an OPC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

1 participant