Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sumo-user] Question regarding routeSampler methodology for demand reduction scenarios

Thank you for the problem report.
The easiest way to scale demand is to use vType attribute 'scale' which will selective drop/add vehicles to match the given scaling quota (i.e. 0.5 for dropping half of the vehicles of this type).

The option --total-count was mainly designed to make use of routes which are not restricted by any counting locations (to "fill up" the route file to some expected number of cars).
It's application for down-scaling of counting data has not been systematically tested.
Your report indicates that the current sampling methodology introduces an ordering bias that becomes apparent when stopping the sampling process early (which is what a lower total-count does).
A potential work-around would be to apply scaling to the input counts instead (which would require a new routeSampler option but would otherwise be trivial).
regards,
Jakob

Am Di., 21. Apr. 2026 um 15:41 Uhr schrieb Nikiforos Mpotzoris via sumo-user <sumo-user@xxxxxxxxxxx>:
Dear SUMO support team,

I am currently working on a traffic simulation study, in which I have developed a calibrated baseline scenario using turn counts imported from an Excel file and routeSampler.
Based on this baseline scenario, I am now attempting to develop alternative scenarios involving demand reductions for specific vehicle classes. According to the desired reduction percentages, I have calculated the corresponding target number of vehicles for each category.
During the generation of the new route files, I tested the use of the --total-count option for each vehicle type in order to impose the reduced demand. However, I observed that the performance of routeSampler decreases compared to the baseline scenario.
In addition, it seems that this reduction is not being applied uniformly across the network. More specifically, it appears to affect mainly the secondary roads rather than the main corridor, particularly in the parts of the network with more complex geometric characteristics.
I would therefore like to ask whether this behavior could be related to the way routeSampler handles demand reduction when --total-count is imposed for each vehicle class.
More generally, I would greatly appreciate your advice on the most appropriate methodology for reducing demand by vehicle class in a uniform manner, while preserving, as far as possible, the proportions reflected in the original turn counts.
Thank you very much for your time and support.
Kind regards,
Nikiforos Botzoris



_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

Back to the top