However, AnyLogic complains about the name in the code. The modeler’s intention here was to add the time that the agents had spent going through the flowchart to the histogram. Sometimes, at first glance, there seems to be no typos, so there’s a trick that helps you make it right. Misspelling is one of the hardest things to catch. įixing misspelling in an AnyLogic model (click to enlarge) Try this yourself with the Error demo – name resolution example. Now if you press Build model (or F7) again, you’ll see that you’ve resolved the error. So, here you can just delete mypopulation and, from the drop-down menu, select the suggested population name – Customers. The modeler’s intention was that the Source block should refer to the agent population called Customers. The error indicates there’s a problem with the name of the population that is referred to. Name resolution: the name of the referred element is wrongįixing the wrong name of the element (click to enlarge) Here are some scenarios for dealing with this error. It is usually caused by misspelling or renaming an object without refactoring.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |