You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A CSTOverlay accumulates facts in the current sampling period. If enough facts match a composite state, it instantiates the composite state as a fact. If a composite state is instantiated, this means that all of its member are considered facts.
The problem is that, when Replicode is running in real time some times it will instantiate a composite state if it only accumulated a few matched facts. For example, if the composite state has four members, the CSTOverlay may only find facts which match two members, but will instantiate the composite state anyway. This means that the other members are also considered facts, even though they weren't checked and may not actually be facts. This never occurs in diagnostic time mode. It occurs as a side effect of multithreaded interaction which must be investigated.
(This was addressed in pull requests #79 by adding original_patterns_size_ and checking it before instantiating the cst. But since it never occurs in diagnostic mode, the pull request was reverted pending investigation of why the bug happens in real time.)
The text was updated successfully, but these errors were encountered:
A CSTOverlay accumulates facts in the current sampling period. If enough facts match a composite state, it instantiates the composite state as a fact. If a composite state is instantiated, this means that all of its member are considered facts.
The problem is that, when Replicode is running in real time some times it will instantiate a composite state if it only accumulated a few matched facts. For example, if the composite state has four members, the CSTOverlay may only find facts which match two members, but will instantiate the composite state anyway. This means that the other members are also considered facts, even though they weren't checked and may not actually be facts. This never occurs in diagnostic time mode. It occurs as a side effect of multithreaded interaction which must be investigated.
(This was addressed in pull requests #79 by adding
original_patterns_size_
and checking it before instantiating the cst. But since it never occurs in diagnostic mode, the pull request was reverted pending investigation of why the bug happens in real time.)The text was updated successfully, but these errors were encountered: