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

Mixing collect-expression and collect-formula instructions #183

Open
rakhimov opened this Issue May 8, 2017 · 0 comments

Comments

@rakhimov
Owner

rakhimov commented May 8, 2017

It's not certain how to handle mixing expressions with formulas
in event-tree branches.
Some ideas/approaches:

  • The Ugly:
    Make it a special case across all the analyses,
    and multiply the expressions with the probability expressions
    of the collected formulas to find the sequence probabilities.

  • The Bad:
    Create 'phony' basic-events for event-tree functional event path states
    that are described by the collected expressions.
    However, these 'phony' events cannot show up in reports
    or fault tree analysis products.
    Moreover, since the functional event states are not constrained,
    the actual semantics of these basic events cannot be deduced.
    In other words, the analysis can end up with a non-coherent fault tree
    without even being capable of deducing it from the input alone.

  • The Good:
    (a) For qualitative analyses, force users to be explicit
    and to use concrete Boolean formulas or basic-events
    for functional-events and their states.
    (b) Perform only quantitative analyses assuming (testing?)
    that the collected formulas are conditionally independent in parallel paths;
    however, put a giant warning in the report.

rakhimov added a commit that referenced this issue May 11, 2017

Prohibit collect-formula & collect-expression mix
Mixing these instructions is not handled by the analysis,
so the initializer validates the input for this invalid setup.

Issue #183

@rakhimov rakhimov added this to To do in Status Jul 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment