Hello Frederic, thank you for reporting this problem. It is fixed in revision 15251. see http://sumo-sim.org/trac.wsgi/changeset/15251 regards, Jakob
2013/12/2 Frédéric Drouhin <[email protected]> > Dear Jakob, > > Following your correction, I found again a strange behaviour (not related > to it). > > I run the command: > $> /home/frederic/Sumo/sumo/tools/bin/traceExporter.py --fcd-input > test.fcdoutput.xml --ns2config-output test60.config.tcl > --ns2activity-output test60.activity.tcl --ns2mobility-output > test60.ns2mobility.xml --penetration 1 --begin 0 --end 60 > > Then if I make a check on NS2 node 7, I found two entries for the same > time with the same node number: > $> grep "$node_(7)" test60.ns2mobility.xml | grep "at 13.0" > $ns_ at 13.0 "$node_(7) setdest 730.18 124.29 0" > $ns_ at 13.0 "$node_(7) setdest 143.88 261.15 0" > > The problem did not come from test.fcdoutput.xml but from the file > generated (here test60.ns2mobility.xml). > > Output from (in traceExporter.py - just a print out of time with v.id): > At 13.0 vehicle 1 added > At 13.0 vehicle 13 added > At 13.0 vehicle 2 added > At 13.0 vehicle 5 added > At 13.0 vehicle 6 added > At 13.0 vehicle 7 added > At 13.0 vehicle 8 added > At 13.0 vehicle 9 added > > Output from fcd2ns2mobility (in ns2.py - just a print of time together > with NS2 node and v.id) : > $ns_ at 13.0 "$node_(0) setdest 594.91 743.64 0 " # for vehicle ID 1 > $ns_ at 13.0 "$node_(7) setdest 730.18 124.29 0 " # for vehicle ID 13 > $ns_ at 13.0 "$node_(1) setdest 329.14 699.29 0 " # for vehicle ID 2 > $ns_ at 13.0 "$node_(3) setdest 438.81 696.59 0 " # for vehicle ID 5 > $ns_ at 13.0 "$node_(4) setdest 462.49 793.37 0 " # for vehicle ID 6 > $ns_ at 13.0 "$node_(5) setdest 854.27 648.09 0 " # for vehicle ID 7 > $ns_ at 13.0 "$node_(6) setdest 178.68 798.67 0 " # for vehicle ID 8 > $ns_ at 13.0 "$node_(7) setdest 143.88 261.15 0 " # for vehicle ID 9 > > You see that two nodes has the same NS2 node (v.id 9 and v.id 13). We are > just coming one after the other (not in the same order than the print). > > I think the v.id is converted to NS2 node, here is the problem (_Running > class). > > The difference is coming that an entry in my case v.id=3 is deleted by > writeMissing (ns2.py) since the vehicule 3 is present at time 9 and > disapear at time=10. > > I just move the NS2 id to a simple counter in Running class and it works > but dunno if it's the correct solution. > > let me know, > > Thanks, best regards > > Frederic > > -- > Frédéric Drouhin > Maître de Conférence, Laboratoire MIPS, Equipe GRTC > Université de Haute-Alsace, IUT de COLMAR > 34 rue du Grillenbreit > BP 50568 > F-68008 COLMAR > Tél. : +33 (0)3 89 20 23 73 Fax +33 (0)3 89 20 23 > 84http://www.iutcolmar.uha.fr/rt > > ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
