Now let’s remember that for an agent to move from one node to the other, both nodes have to belong to the same network, and separating the networks in different agents, will generate as many networks as agents. Still a lot of paths, but nothing problematic.įigure 5 – paths, nodes and rectangular nodes moved to a new agent
#ANYLOGIC SOFTWARE MEMORY CHANGE FULL#
Turned into this, which can only be created in the Pro or University versions, since the PLE is limited to 10 agents.Īnd the purple area full of nodes in figure 2 ends up being a solitaire set of paths in one of the new agents. So this set of agents that fit into the PLE version of AnyLogic (figure 3)
As you can see in figure 2, all the paths belong to an area that has a particular color, so what needed to be done was to restructure the model and generate a new agent containing the paths associated with an area of a particular color. The second solution, which is much more elegant and useful but much more difficult, is to separate your model into several agents. Nevertheless the solution may help you move forward and continuing the development of the model. You can save a few bytes doing that, but saving the project, making changes or moving things around will be very slow, and also you may have so many variables that reducing the size may not be enough for you. The first solution is to reduce the size of your variables names (for instance changing path1503 to p1503). There are two solutions for this problem. It may be a rare situation, but it can happen. This is just a small piece of the model, but you can already see a ridiculous amount of paths!!!! I don’t know what other business cases you can have in which you end up having so many things in an agent. This can easily be seen in the figure.įigure 2 – presentation with several spacial markup elements Figure 2 shows part of the presentation in main where the number of paths, nodes and areas was crazy high. In this business case, several machines need to follow some paths in a very precise order to do some work in different areas. And you are not only in trouble because continuing building the model is impossible, but also because making changes to the model when you are close to the 65535 bytes limit becomes slow and tedious, even when you have a great computer.
If you open the Main agent with the java editor, you will see something like figure 1.īasically, there can be hundreds of variables that can be embedded inside this method, and if the string of variables exceeds 65535 bytes, then you are in trouble.
#ANYLOGIC SOFTWARE MEMORY CHANGE CODE#
The error thrown by AnyLogic is “The code of method doCreate() is exceeding the 65535 bytes limit”. Up to this date with AnyLogic 8.3, there is a bug that doesn’t let you generate an agent that has too many elements. The error is caused by the code generation mechanism creating a large constructor of presentation of Main, violating the Java limitation on the method size.
0 kommentar(er)
