Meaning of core libraries
Posted: Mon Jan 16, 2017 12:59 pm
Hi there,
from time to time players in the xUniverse want to know more about the interaction between so-called core components. I therefor provide a short list describing the meaning of those components:
Best regards Bernd
from time to time players in the xUniverse want to know more about the interaction between so-called core components. I therefor provide a short list describing the meaning of those components:
- DimaCtrl.dll: the job of the Dima Control is to maintain containers labeled as distance matrices. A distance matrix contains a large number of driving times and distances based on a specific routing option setting. The control creates / destroys the storage (single folder on the file system, usually /data/dima...), inserts, updates and deletes the content of the distance matrix and returns the content (byRoad) or approximations (byReference). Current versions of the Dima Control support both traditional and high performance routing.
Since the 64bit version of the control it is able to deal with DIMAs exceeding 20.000 rows (=400.000.000 routings!). The control is also able to import given relations / export calculated relations and it can handle a large number of DIMAs at a time. The Control is part of xDima, xTour, xCluster and xTerritory. - TimeCalc.dll: The TimeCalc control applies various time dependent rules on a given route based on
- the waypoints opening times
- the vehicles operating times
- the defined break- and rest rules (daily, weekly...).
- TourOpt.dll (xServer 1): The touropt dll is the function that determines
- optimal assignments of orders to tours
- optimal sequences of those assignments within a tour or chain
- ConstructionPhase
- SequenceOptimization
- ImprovementPhase
Best regards Bernd