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
When I added a float attribute with a range I could not get Visual Soar to accept it as correct. Here is the example showing the float attribute definition (I had said -0.99 and -0.01 and VS gets something approximate), then the line under referring to that that caused an error, and then the error messages (there were two of them for this line):
threshold-neg: float [ -0.9900000095367432 - -0.009999999776482582 ]
^threshold-neg -0.1
...\find-my-neighbors(38): could not match constraint (<op>,threshold-neg,0) in production
...\find-my-neighbors(38): could not match constraint (<op>,threshold-neg,0.1) in production
In addition, in defining the float attribute it insisted that the left value had to be less than, or more negative in this case, than the right value. This is probably reasonable.
When I deleted the attribute and redefined it with no limits it worked fine.
The text was updated successfully, but these errors were encountered:
elaborate*goal-message: elaborations/top-state(10): could not match constraint (<s>,foo,0) in production
elaborate*goal-message: elaborations/top-state(10): could not match constraint (<s>,foo,0.1) in production
It seems like a production parsing error to me; I think that V-S thinks there are two floats here: -0 and .1. Or maybe it interpreted the - as something else and read the floats 0 and .1. Either one is wrong.
The Soar syntax looks good to me. I can't see what you have in the datamap, but those errors seem like part of the problem for this issue, as shown in the errors in the original issue.
When I added a float attribute with a range I could not get Visual Soar to accept it as correct. Here is the example showing the float attribute definition (I had said -0.99 and -0.01 and VS gets something approximate), then the line under referring to that that caused an error, and then the error messages (there were two of them for this line):
In addition, in defining the float attribute it insisted that the left value had to be less than, or more negative in this case, than the right value. This is probably reasonable.
When I deleted the attribute and redefined it with no limits it worked fine.
The text was updated successfully, but these errors were encountered: