The first step is to determine whether the problem originates within the Intent system, or from an external source. For example, if a database returns incorrect results, changing rules cannot correct the problem.
The dependencies for all evaluations are recorded. That is, if Rule A references Rule B, after Rule A is evaluated, the dependency on B is recorded. If B is changed, then the system knows to unbind A. you can traverse and inspect the entire recorded dependency tree to find problems.
In Formula, the formula for the selected node in the tree displays. In this case, "diameter" is a simple numeric parameter, and it depends on no other rules. The selected modelSelf rule depends on diameter, but indirectly. The rule is an internal function call that references Radius, not Diameter. But the Group rule diameter_only is triggered to obtain the Radius for the Arc.
Inthe following image, the left window shows both the direct and hidden references that were made during evaluation. It requires the center, radius, start, and end angles, and some other information. With one exception, they are the arguments to the function.