Boundary detection: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<div class="pageexperimental">''This page documents an '''experimental''' feature. You can help out by '''testing it''' and <span class="plainlinks">[http:// | <div class="pageexperimental">''This page documents an '''experimental''' feature. You can help out by '''testing it''' and <span class="plainlinks">[http://bugs.ascend4.org reporting]</span> your experiences.''</div> | ||
Boundary detection works under [[IDA]] to detect when, as moving forward in time, a point comes when a conditional expression changes value. | Boundary detection works under [[IDA]] to detect when, as moving forward in time, a point comes when a conditional expression changes value. | ||
Latest revision as of 01:34, 26 November 2017
This page documents an experimental feature. You can help out by testing it and reporting your experiences.
Boundary detection works under IDA to detect when, as moving forward in time, a point comes when a conditional expression changes value.
Possible boundaries include
- real-valued relations, such as t < t_1 or T > T_sat
- boolean-valued relations, such as motor_running = (have_power AND motor_switch_on)
As integration time progresses, logic-valued relations can only change value when somehow triggered by changes in real-valued relations. Boolean-valued relations at that point then be re-evaluated using LRSlv to precedence-order the logical relations from the current model state.
Boolean-valued relations case use the truth-value of real-valued relations using the SATISFIED(relname,tolerance) function.
See also