Could the official tutorials or documentation include a section describing how, if at all, UXsim can be configured to approximate a point-queue + FIFO model — i.e., a setting in which each link has a single bottleneck at its downstream end and no spillback to upstream links?
Comparing UXsim with point-queue DTA solvers conflates the difference in routing principle with the bias from spillback, which the point-queue side does not model.
A documented "reduced" mode would help in two situations:
- Cross-method benchmarking, by placing UXsim and point-queue solvers on the same physical footing so the routing component of any gap can be isolated.
- Quantifying spillover bias by running the same scenario in standard mode and in reduced mode and comparing the results.
If such a reduction is not intended to be supported, a brief note to that effect would also be useful, so that users do not invent ad hoc parameter recipes that may not match the model's design intent.
Could the official tutorials or documentation include a section describing how, if at all, UXsim can be configured to approximate a point-queue + FIFO model — i.e., a setting in which each link has a single bottleneck at its downstream end and no spillback to upstream links?
Comparing UXsim with point-queue DTA solvers conflates the difference in routing principle with the bias from spillback, which the point-queue side does not model.
A documented "reduced" mode would help in two situations:
If such a reduction is not intended to be supported, a brief note to that effect would also be useful, so that users do not invent ad hoc parameter recipes that may not match the model's design intent.