The more complex the AI is the more likely it is to be buggy. One should ask the question: "Has this AI been implemented with the least amount of nodes necessary?". A simple solution should be preferred over a complex one leading to the same or very similar results. The size of an AI has a significant effect on the error rate. If its not possible to prevent duplicate nodes in the first place one can try to move them to sub AIs. Sometimes duplicate nodes can be prevented by using bot specific filters or additional conditions. One should consider to align nodes to the grid.Īvoid using the exact same set of nodes in several places. AIs should have meaningful names revealing their purpose. Overlapping nodes, links crossing each other and great distances between linked nodes are difficult to read and should be avoided. The complexity is reduced leading to a better maintainability.ĪIs are written once, but read many times. In Gladiabots this could be done by creating sub-AIs for each sub-problem. Complex sub-problems can again be divided. The following rules can help improve the quality of AIs, enhancing both the initial development and subsequent maintenance of the AI.īreak down a problem into two or more sub-problems and solve each of them separately. Some best coding practices from software development also apply to AIs in Gladiabots.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |