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 > > > > > ------------------------------------------------------------------------------ _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
