This is what I expect too. But I don't understand this part of the marouter document in which points to microscopic output: "One of the main usages of marouter is to compute a Demand/Dynamic_User_Assignment <https://sumo.dlr.de/docs/Demand/Dynamic_User_Assignment.html>. To this end it generates <flow> definitions with fully specified routes that can be loaded into sumo <https://sumo.dlr.de/docs/sumo.html> and sumo-gui <https://sumo.dlr.de/docs/sumo-gui.html>."
On Wed, Aug 18, 2021 at 7:05 PM Jakob Erdmann <[email protected]> wrote: > duaIterate determines travel times with a slow but precise microscopic > simulation whereas marouter uses a macroscopic capacity-constraint function > which is much faster but also less precise. > > > Am Mi., 18. Aug. 2021 um 15:50 Uhr schrieb ali mirzaei < > [email protected]>: > >> Hi everyone, >> What is the difference (relation) between the output generated by >> https://sumo.dlr.de/docs/Demand/Dynamic_User_Assignment.html#iterative_assignment_dynamic_user_equilibrium >> and the one created by >> https://sumo.dlr.de/docs/marouter.html#microscopic_outputs? >> Best, >> Ali >> _______________________________________________ >> 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
