True, the scale parameter works perfectly fine. I am not sure if I was testing it on a nightly build version of 1.8.x, but now on 1.9.0 it works. However, the fromJunction - toJunction option for route files is not working, while it works perfectly fine in DUAROUTER. Moreover, for the output of MAROUTER I was under the impression that route costs are travel times (since the weight attribute is by default traveltime) but I get values that are much larger than traveltime, maybe distance in meters? Is this cost in MAROUTER modifiable i.e. to get travel time of each trip?
Best, Sasan On Mon, May 3, 2021 at 9:19 AM Jakob Erdmann <[email protected]> wrote: > Scaling route file input is supposed to work since 1.9.0 (and it's working > in our test). Can you send me a minimal failing example for 1.9 or later? > > Am Sa., 1. Mai 2021 um 14:46 Uhr schrieb Sasan Amini <[email protected]>: > >> Dear all, >> >> I am running MAROUTER on an extremely large network and have only 1% of >> the real demand, which means I have to scale it by a factor of 100. >> However, when I define demand as route file and apply the --scale option, >> it has no impact on the number of loaded vehicles. When I try to define >> demand as flows, no valid vehicles are loaded. Any suggestion on how to >> scale demand when using MAROUTER? or even a better way to downscale >> capacity (similar to MATSim)? >> >> Best, >> Sasan >> _______________________________________________ >> sumo-user mailing list >> [email protected] >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/sumo-user >> > _______________________________________________ > sumo-user mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user >
_______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
