13.4.8 Debugging

An important step after running a model is debugging. This is the process in which coding errors are identified and addressed. Coding within the network is typically checked so that it conforms to best practices and results in simulated conditions that are consistent with observed field conditions.
The debugging process is recommended to focus on checking the quality of big picture items such as the number of lanes, the RBCs used, and the location and type of DSD. The recommended method for debugging is to complete an initial review of the network prior to running the simulation, observe the model during the simulation, and/or review the error log file that may appear in a pop-up window. It is best practice to document the items checked while debugging.
Common coding errors are typically found in the following model objects:
  • Signal timing/Signal Head assignments;
  • Conflict Areas;
  • DSD;
  • Unusual vehicle behaviors due to errors in coding on network; and
  • Types of Vehicle Inputs on Links
A checklist for debugging models is provided in
Appendix N, Section 1 – Model Debugging Checklist.