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
Expression->Built-in->Periodic-test #69
Labels
Milestone
Comments
rakhimov
added a commit
that referenced
this issue
Feb 22, 2017
This introduces PeriodicTest in general: - Schema - Initializer - Analysis - Tests Issue #69
rakhimov
added a commit
that referenced
this issue
Feb 22, 2017
This test intended to test periodic-test and system integrity levels. The initial test is only for probability with periodic-test. Issue #69
rakhimov
added a commit
that referenced
this issue
Feb 22, 2017
rakhimov
added a commit
that referenced
this issue
Feb 22, 2017
- Rewrite the formula to compute a geometric sum instead of a loop. Issue #69
rakhimov
added a commit
that referenced
this issue
Feb 22, 2017
- DRY for Validation code - Move the code out of line - Simplify Min/Max for probability expressions Issue #69
rakhimov
added a commit
that referenced
this issue
Feb 22, 2017
This is a special case due to the current solution divisor having (lambda - mu). The fail-after-repair probability integral changes due to this and produces a different formula. Issue #69
rakhimov
added a commit
that referenced
this issue
Feb 22, 2017
The result should be close to PeriodicTest with 4 args. Issue #69
rakhimov
added a commit
that referenced
this issue
Mar 3, 2017
- The Expression tests are refactored to support the 11 arg beast. Issue #69
rakhimov
added a commit
that referenced
this issue
Mar 3, 2017
The implementation assumes that the repair is also conducted upon the test phase failure. This assumption effectively merges the multi-phase Markov chains into one. As a result, the model becomes much more complex, requiring analysis of multiple 2, 3 - consecutive Poisson processes. This implementation unnecessarily complicates the model, which is effectively covered by 5 argument periodic-test, i.e., instant test. Unsurprisingly, this implementation/approach does not pass benchmark tests. However, the only reason this implementation is committed is for historical/future information. Should anyone need "crazy" 3-consecutive Poisson-process Markov chain formulas, it would be in this commit. Issue #69
rakhimov
added a commit
that referenced
this issue
Mar 3, 2017
Even in not-available-at-test configuration, if the system enters in repair, it can be made available since no tests are conducted. In other words, the probability of unavailability at test time is not always 1. Issue #69
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describes periodically tested components:
The text was updated successfully, but these errors were encountered: