Unexplained Method Not Found error message_fixed
Discussion:A careful examination of the name specified in the “Message” action and that in the actual method reveals the number “0” in the former and a letter “O” in the latter. Spelling counts!
AgentCubes has a better capability for preventing this kind of spelling error, but it is not infallible. Once a method name or variable name (agent attribute or simulation property) is defined via certain actions, such as the “set” first operand or the “message” second operand, the user has a menu from which to choose the name in subsequent actions. The “method” name field (the second operand field of the “message” action, and the first operand field of the “set” action) display a menu of existing defined names for messages, methods and variables, as shown in the image below. The final entry in the list provides the ability to define a new name.
Note that in this example there are actually two method names, V0 and Vo. These can be seen by using the pull-down menu on either the message action name or the method name, as shown in the example to the left. In this case, the user at some point must have selected the “Add new method” option and created each one. An attentive user will notice the existence of the first created name and, hopefully, continue to select it in subsequent references in “message” and “broadcast” actions, thus making this problem less likely.
However, the “test” condition operands and second operand of the “set” action, for example, permit free-form input, in which the user has the “opportunity” for misspelling! This kind of problem is more difficult to detect. After the simulation has run, using the pull-down menu of the “set” action may display the current list of agent attribute and simulation property names, which will reveal names that are similarly spelled. However, this is not guaranteed if the additional name is not actually modified via a “set” action.
One final note: AgentCubes ignores upper/lower case when defining and referring to variable names and method names.
| Data | |
|---|---|
| Created: | May 28, 2015 |
| Played: | 112 |
| Agent: | 13 |
| Rules: | 36 |
| Methods: | 16 |
false
Settings
New Project Name
Rename
Copy
Download
Show Project Report
Flag Project
Delete
Discussion:A careful examination of the name specified in the “Message” action and that in the actual method reveals the number “0” in the former and a letter “O” in the latter. Spelling counts!
AgentCubes has a better capability for preventing this kind of spelling error, but it is not infallible. Once a method name or variable name (agent attribute or simulation property) is defined via certain actions, such as the “set” first operand or the “message” second operand, the user has a menu from which to choose the name in subsequent actions. The “method” name field (the second operand field of the “message” action, and the first operand field of the “set” action) display a menu of existing defined names for messages, methods and variables, as shown in the image below. The final entry in the list provides the ability to define a new name.
Note that in this example there are actually two method names, V0 and Vo. These can be seen by using the pull-down menu on either the message action name or the method name, as shown in the example to the left. In this case, the user at some point must have selected the “Add new method” option and created each one. An attentive user will notice the existence of the first created name and, hopefully, continue to select it in subsequent references in “message” and “broadcast” actions, thus making this problem less likely.
However, the “test” condition operands and second operand of the “set” action, for example, permit free-form input, in which the user has the “opportunity” for misspelling! This kind of problem is more difficult to detect. After the simulation has run, using the pull-down menu of the “set” action may display the current list of agent attribute and simulation property names, which will reveal names that are similarly spelled. However, this is not guaranteed if the additional name is not actually modified via a “set” action.
One final note: AgentCubes ignores upper/lower case when defining and referring to variable names and method names.
Edit Description
Design