Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sumo-user] Generating Demand from Counting Data

1. Can you paste the exact command line you are using to call flowrouter.py (including the python interpreter)?
2. You can let dfrouter write --detector-output, modify the types as you see fit and then use this file as --detector-files input
The discarded detectors are due to https://github.com/eclipse/sumo/issues/13020 (dfrouter was developed for scenarios where all entries to the network are covered by detectors).
Note, that dfrouter is no longer actively developed so it's unclear when / if this will be fixed.
I recommend taking a look at routeSampler since it has the best support and should be suitable for all uses cases involving counting data.



Am Mi., 12. Apr. 2023 um 10:36 Uhr schrieb Florian Schnepf <florian.schnepf97@xxxxxx>:
Hi Jakob,
 
thanks for the help. Still have the problem with flowrouter. Reinstalled it, but didn't helped
 
I have a question about how dfrouter sets the type of detectors. As i understood from the documentation, an edge is a source if there is no other before it, a sink if there is none after it and in between if there is another edge before and after it. When is it discarded?
I noticed that in my network it is not plausible for some detectors. Can I change this manually in the detector-file?
 
Gesendet: Mittwoch, 12. April 2023 um 08:59 Uhr
Von: "Jakob Erdmann" <namdre.sumo@xxxxxxxxx>
An: "Sumo project User discussions" <sumo-user@xxxxxxxxxxx>
Betreff: Re: [sumo-user] Generating Demand from Counting Data
correction:
it should be 
%SUMO_HOME%/tools/detector/flowrouter.py -n BAB.net.xml -d BAB_Zaehlstellen.add.xml -f DetectorFlows.csv -i 60 -o out2.add.xml -e out2.rou.xml
because flowrouter uses minutes (trying to be consistent with the flow input which also defines time in minutes).
 
Am Di., 11. Apr. 2023 um 16:32 Uhr schrieb Jakob Erdmann <namdre.sumo@xxxxxxxxx>:
- for dfrouter, set option --time-step 3600.   By default, the dfrouter expects inputs at 60s granularity. This is now documented at https://sumo.dlr.de/docs/Demand/Routes_from_Observation_Points.html#computing_flows
- for flowrouter,py, the following commandline worked fine on my end: %SUMO_HOME%/tools/detector/flowrouter.py -n BAB.net.xml -d BAB_Zaehlstellen.add.xml -f DetectorFlows.csv -i 3600 -o out2.add.xml -e out2.rou.xml
 
Am Mo., 3. Apr. 2023 um 09:18 Uhr schrieb Florian Schnepf <florian.schnepf97@xxxxxx>:
Hello,
 
input files are attached.
 
Adding 'python' at the beginning unfortunately changes nothing.
Gesendet: Donnerstag, 30. März 2023 um 17:33 Uhr
Von: "Jakob Erdmann" <namdre.sumo@xxxxxxxxx>
An: "Sumo project User discussions" <sumo-user@xxxxxxxxxxx>
Betreff: Re: [sumo-user] Generating Demand from Counting Data
- for dfrouter, this sounds a bit like an issue with how the input data is encoded. Can you provide examplary input files?
- for flowrouter try adding 'python' in front of the tool name. See https://sumo.dlr.de/docs/FAQ.html#the_python_scripts_do_not_accept_command_line_arguments_windows_only
 
 
Am Do., 30. März 2023 um 16:03 Uhr schrieb Florian Schnepf <florian.schnepf97@xxxxxx>:
Hello,
 
i am trying to generate vehicles for a section of highway. For the detectors, i have data for each hour. With dfrouter, the generated vehicles are generated only at the beginning of a new started hour. This makes the traffic uneven. Tried it with the --randomize-flows option, but that didn't make any difference. 

Now I wanted to test flowrouter.py. When I call it in the command line, I only get all options displayed (see picture).
 
Also tried to call it with %SUMO_HOME%/tools/detector/flowrouter.py with same results 
 
Thanks for all the support
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________ sumo-user mailing list sumo-user@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________ sumo-user mailing list sumo-user@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
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