6 Bugs

At present, the software is not memory and speed optimized. Tip if you are short of memory: After you have completed the network design, delete your background maps with Edit/ Map/ Delete and safe this version under a different name. Then run the simulation. The results will be the same, but your computer does not have to deal with the memory of the maps. You can also much quicker zoom in and out without maps.

In any case, for larger networks it is recommended to run the simulation in command-line mode or as a script, without graphical support. This will reduce the used memory and make the simulations roughly 5 times faster, see Sec 4.3 and Sec 4.2.

Some ``minor'' problems have been discovered and will be improved in future versions:

• There may be problems with reloading already simulation files.Sometimes it cannot be seen immediately, but during the simulation when various WARNING messages do occur on the terminal.

  Please keep always a copy of the unactivated track as backup. This will always work. From there it is quick to reconstruct the simulation by adding different numbers of vehicles and users.

• Vehicles crash into each other at a certain merge points. The reason why this can happen is that there is no design rule checker. Most likely one of the branches of your merge element is too short in order to allow vehicles to adapt their speed.

  The only solution is to extend the input lines or to lower the line speed on the input sections (and on previous section in order to guarantee that the vehicles enter the merge at the desired speed.). In general one would set the same line-velocity for both input sections of a merge element (first two sections on the Section page of the control-panel).

• The deviation rate (number of deviation divided by the total number of switch operation $\times 100$ ) on the track management control-panel can show 101% instead of 100%.

• It has been observed that vehicles stop inside stations and refuse to load passengers. This can occurs if stations are over-congested. Try to avoid over-congested networks. Add station or bypass or reduce the number of vehicles.

• Some error messages may occur after running and re-editing a simulation. But this should be avoided in any case: edit only unactivated tracks, save the network, activate it and then run the simulation.

• In some cases, a discontinuity can occur when connecting track elements. Usually this happens when the connecting algorithms cannot straighten the angle between both elements because it is too big.

  Workaround: just move the track elements apart with Edit/ Module/ Move and reconnect them. When still problems, try to change relative angle or position element or position of nodes. Or use flexible elements instead of curve elements or lines. If this still does not help it can be that you ask for a too small curve radius, which would also be a problem of the real system: Consider a different network-layout.

• Some track elements show ``strange'' stretch properties when placed with certain angles.

  Workaround: move (Edit/ Module/ Move) and turn the track element slightly if possible. When still problems, consider using alternative track elements.