DFROUTER only builds routes from the source detectors by default. If you want routes to also start at the in-between detectors, use option --routes-for-all
The total number of cars at any one time depends on not only on the flow values but also on the time each vehicle spends in the network and as such is not easily predicted. 2016-01-11 22:02 GMT+01:00 Nguyen Nguyen <[email protected]>: > Hi Jakob, > > Thanks for your reply. I have one more questions related to the type > generation part. Could you please help me clarify? > > In the example included with SUMO, dfrouter only generate routes coming > from the "source" detectors. Should defroster also generate routes for > "between" & "sink" detectors also? At such a time, the total number of cars > is the total number of vehicles passing by all the detectors > (source/between/sink detectors) in the network, isn't it? > > Thank you. > > Best regards, > > Tran > > > On Friday, January 8, 2016 10:51 AM, Nguyen Nguyen < > [email protected]> wrote: > > > Hi Jakob, > > Thanks for your reply. I have one more questions related to the type > generation part. Could you please answer me? > > In the input_tri_flows.txt example provided by SUMO, MQ_beg read 40, > MQ_middle read 10, MQ_1toR read 10, etc.. at time = 0. It means that at > that time, there were 40 cars passing by detector MQ_beg, 10 cars > passing by detector MQ_middle,... Why does dfrouter only recognize MQ_beg > as the source type, all others are sink and between type, and finally the > generated route files only has 40 routes coming from the source MQ_beg? I > think I misunderstand somewhere. Could you please help me correct it? > > Thank you so much. > > Best, > > Tran > > > On Tuesday, January 5, 2016 3:30 AM, Jakob Erdmann < > [email protected]> wrote: > > > Does your file input_tri.det.xml contain 'type' information (i.e. > source,sink,between)? If not see > > http://sumo.dlr.de/wiki/Demand/Routes_from_Observation_Points#Computing_Detector_Types > for how to compute these types. > Otherwise, follow the advice given in the previous answer. > Missing flow values are interpreted as 0. > > 2016-01-05 11:20 GMT+01:00 Nguyen Nguyen <[email protected]>: > > Hi Jakob, > > Thanks for your reply. I am trying to run the dfrouter examples provided > by SUMO source code to understand how to use dfrouter to generate needed > outputs as following: > > dfrouter -n input_tri.net.xml -d input_tri.det.xml --measure-files > input_tri_flows.txt --routes-output routes.rou.xml --emitters-output > emitters.rou.xml --validation-output validation.xml > > There are total 40 routes in emitters.rou.xml. However, in the > input_tri_flows.txt, there are total 40+10+10+..=180 cars at time = 0. When > I check the validation files, there are still many sensors with 0 values. > Did I make mistake somewhere? > > Morover, the flow file that I provided miss some flow values at some time > slot. Will that still be allowed for dfrouter? > > Thank you, > > Best regards, > > Tran > > > > > On Monday, January 4, 2016 11:44 PM, Jakob Erdmann < > [email protected]> wrote: > > > Check the total number of vehicles that were generated (in the output file > of option --emitters-output) against your expectations. > The warnings could indicate why not all of the desired routes (and thus > vehicles) have been generated. They are typical for networks that have > insufficient sink detectors declared. > See the options documented at > http://sumo.dlr.de/wiki/Demand/Routes_from_Observation_Points#Computing_Routes > for working around these warnings. > regards, > Jakob > > 2016-01-05 8:30 GMT+01:00 Nguyen Nguyen <[email protected]>: > > Hi All, > I figured it out that I can use the validation.xml as an additional file > while I run the simulation to generate validation_dets.xml. However, most > of the sensors have 0 counts, which is very different from the real > information (failed validation). When I use dfrouter, I still got a lot of > warnings like "Quitting checking for being a source for detector ... due to > seen edge limit." and "Could not close route for...". Did these warning > cause the problems? And how should I get rid of these warnings? > Thank you very much. > Best, > Tran > > On Monday, January 4, 2016 10:54 PM, Nguyen Nguyen < > [email protected]> wrote: > > > Hello All, > I performed dfrouter to import sensor information and want to validate the > simulation. I put detectors at those locations and retrieve the vehicle > counts and speed for validation but most of the sensors read 0. Could I do > this for validation? Is there anything wrong with this? > Moreover, I also saw that we can perform validation > by --validation-output validation.xml, but when I ran the simulation, I > got an xml file with some information like: > <e1Detector id="validation_10113" lane="-121939397#30_0" pos="104.24" > freq="60" friendlyPos="1" file="validation_dets.xml"/> > > There is no validation_dets.xml created, and I do not how to use this file > for validation. > Could you please explain more clearly how I should validate my simulation > using dfrouter.. > Thank you very much. > Best regards, > Tran > > > > ------------------------------------------------------------------------------ > _______________________________________________ > sumo-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sumo-user > > > > > > > > > > ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
