Event Tree Analysis #150
Milestone
Comments
rakhimov
added a commit
that referenced
this issue
Mar 25, 2017
rakhimov
added a commit
that referenced
this issue
Mar 25, 2017
Only collect expression instructions are added to support simple event trees. Issue #150
rakhimov
added a commit
that referenced
this issue
Mar 25, 2017
- Initial event_tree classes - Model - Initializer - Initialization tests Issue #150
rakhimov
added a commit
that referenced
this issue
Mar 25, 2017
This is an initial event tree instruction for sequences. Issue #150
rakhimov
added a commit
that referenced
this issue
Mar 31, 2017
Only 'collect-expression' instruction is implemented for use by Sequence. Issue #150
rakhimov
added a commit
that referenced
this issue
Apr 3, 2017
The addition of functional events is not yet made ordered. The approach needs to be coordinated with branch fork definitions and validations. Issue #150
rakhimov
added a commit
that referenced
this issue
Apr 29, 2017
Functional events cannot be referred outside of event trees. The model container does not store references to functional events. Issue #150
rakhimov
added a commit
that referenced
this issue
Apr 29, 2017
rakhimov
added a commit
that referenced
this issue
Apr 29, 2017
This is a schema error in the MEF. Issue #150
rakhimov
added a commit
that referenced
this issue
Apr 29, 2017
- Branch - Named Branch - Path - Fork - Initial State These classes are too coupled and interdependent to be introduced separately and incrementally. For this reason, the branch end-points or targets are implemented with algebraic datatypes (boost::variant) instead of a base class. Issue #150
rakhimov
added a commit
that referenced
this issue
Apr 29, 2017
Named branches can be referenced in fork definitions and may end up in invalid cycles. Issue #150
rakhimov
added a commit
that referenced
this issue
Apr 30, 2017
rakhimov
added a commit
that referenced
this issue
May 4, 2017
Event trees manage the order of functional events. The order implicitly deduced from the order of functional event addition into event trees. Issue #150
rakhimov
added a commit
that referenced
this issue
May 4, 2017
In event trees, the functional event order in fork paths matters. The order is deduced from the declaration of the functional events in event tree declaration element. This ordering is later used to validate the event tree paths. Issue #150
rakhimov
added a commit
that referenced
this issue
May 4, 2017
The states are allowed to be arbitrary, but they must be unique per fork. Issue #150
rakhimov
added a commit
that referenced
this issue
May 4, 2017
rakhimov
added a commit
that referenced
this issue
May 4, 2017
Simple event tree analysis with branch probabilities. The final sequence probabilities are given as analysis results. Since only "collect-expression" instruction is necessary, a simple 'quick-&-dirty' approach is taken upon walking the event tree; the expressions are multiplied during the walk expecting only the collect-expression (i.e., static downcast). To test the functionality, a simple event tree example is added into EvenTrees folder and tests. Issue #150
rakhimov
added a commit
that referenced
this issue
May 4, 2017
rakhimov
added a commit
that referenced
this issue
May 6, 2017
rakhimov
added a commit
that referenced
this issue
May 7, 2017
A warning message is produced in the report for unused:
- Sequences
- Functional events
- Branches
Issue #150
rakhimov
added a commit
that referenced
this issue
May 7, 2017
rakhimov
added a commit
that referenced
this issue
May 9, 2017
Analyses performed on event trees are uniquely identified by the initiating event and end-sequence. The report schema is changed to include the initiating-event attribute. Expression-only analyses are properly handled in report by not reporting quantitative analyses. Issue #150
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The initial basic analysis implementation without event tree chaining or fault tree linking
The text was updated successfully, but these errors were encountered: