By Emmanuel Bert
Real data sets are essential elements of an Aimsun Next model, but sometimes the quality of the data provided by the client or other data sources is less than perfect and may have gaps and inconsistencies that are often difficult to detect, especially in a large-scale, complex network with a high number of detectors.
Additionally, when using several sources of data, you are quite likely to observe variations, so you need to be sure that the different data sources are compatible in terms of data type and date/time.
Of course, trying to calibrate a model based on a real data set with inconsistent traffic values will make the process more difficult, error prone and even impossible – for instance, you cannot satisfy two inconsistent traffic values in the same section.
Congestion consistency: A congestion consistency message will appear when these two criteria are fulfilled simultaneously:
Spatial consistency (count or flow): The algorithm checks the difference between two measure points that have no interference in between (no merge/diverge nor centroid connections) or when the incoming vs outcoming flow differences in the node and applies the following criteria:
Things to note:
You’ll find more detail about these parameters in the User Manual: qthelp://aimsun.com.aimsun.8.4/doc/UsersManual/RealDataSetEditing.html#checking_real_data_consistency.
In the Consistency Parameters tab, modify the criteria for data consistency checks:
Click on the Check button to generate the list of inconsistencies in the Results tab.
To check with different time aggregations, just restore the RDS with a different time aggregation before performing the check.
Example of messages regarding individual consistency: They contain the line number, warning sign, the type of check (consistency type), the detector, the time of the record and the message explaining the issue detected.
Example of messages about spatial consistency: The following message shows an inconsistency between 2 detectors that have no interference in between:
And finally, consistency issues for a node: