Hi all,I think I come across a possible bug with traceExporter.py while generating ns-2 output trace.
Specifically, I am trying to generate ns-2 traces out of the TAPAS cologne scenario. For you information, I am using SUMO v.19.0 for the TAPAS cologne scenario and traceExporter.py (rev #15433).
After the fcd-output data processing, the "config.tcl" file reports the generation of around 75000 node-traces. However, when looking into the "acitivity.tcl" file, the largest ns2 node_ID I could find was around 10000.
I examined the activity file in depth and found that several SUMO nodes are reported with the same ns2 node_ID, and often their presence in the trace (in terms of time) is overlapping. Example below for ns2 node with ID: 6916
$ns_ at 24168.0 "$g(6916) start"; # SUMO-ID: 115011_115011_403 $ns_ at 24568.0 "$g(6916) stop"; # SUMO-ID: 115011_115011_403 $ns_ at 24075.0 "$g(6916) start"; # SUMO-ID: 127584_127584_407 $ns_ at 24634.0 "$g(6916) stop"; # SUMO-ID: 127584_127584_407 $ns_ at 24166.0 "$g(6916) start"; # SUMO-ID: 132184_132184_410 $ns_ at 24312.0 "$g(6916) stop"; # SUMO-ID: 132184_132184_410 $ns_ at 24080.0 "$g(6916) start"; # SUMO-ID: 104574_104574_397 $ns_ at 25037.0 "$g(6916) stop"; # SUMO-ID: 104574_104574_397 $ns_ at 24078.0 "$g(6916) start"; # SUMO-ID: 112052_112052_401 $ns_ at 24846.0 "$g(6916) stop"; # SUMO-ID: 112052_112052_401 $ns_ at 24167.0 "$g(6916) start"; # SUMO-ID: 123312_123312_406 $ns_ at 24733.0 "$g(6916) stop"; # SUMO-ID: 123312_123312_406 $ns_ at 24169.0 "$g(6916) start"; # SUMO-ID: 102491_102491_396 $ns_ at 25068.0 "$g(6916) stop"; # SUMO-ID: 102491_102491_396 $ns_ at 28665.0 "$g(6916) start"; # SUMO-ID: 218770_218770_446 $ns_ at 28800.0 "$g(6916) stop"; # SUMO-ID: 218770_218770_446 $ns_ at 24076.0 "$g(6916) start"; # SUMO-ID: 118187_118187_405 $ns_ at 24635.0 "$g(6916) stop"; # SUMO-ID: 118187_118187_405 $ns_ at 24163.0 "$g(6916) start"; # SUMO-ID: 123240_123240_406 $ns_ at 24633.0 "$g(6916) stop"; # SUMO-ID: 123240_123240_406 $ns_ at 24165.0 "$g(6916) start"; # SUMO-ID: 131705_131705_410 $ns_ at 24492.0 "$g(6916) stop"; # SUMO-ID: 131705_131705_410 $ns_ at 24164.0 "$g(6916) start"; # SUMO-ID: 121001_121001_405 $ns_ at 25202.0 "$g(6916) stop"; # SUMO-ID: 121001_121001_405 $ns_ at 24077.0 "$g(6916) start"; # SUMO-ID: 100928_100928_396 $ns_ at 24640.0 "$g(6916) stop"; # SUMO-ID: 100928_100928_396 $ns_ at 24160.0 "$g(6916) start"; # SUMO-ID: 107246_107246_400 $ns_ at 24596.0 "$g(6916) stop"; # SUMO-ID: 107246_107246_400Unless it is by design, I believe, that there must be a problem with the ns2 node_ID generation that causes
the reuse of previously generated IDs. - Nicholas -- ________________________________________________________ Nicholas Loulloudes PhD Candidate, LINC - Laboratory for Internet Computing Department of Computer Science, University of Cyprus PO Box 20537, 1678 Nicosia, Cyprus Tel: +357-22892676 Email: loulloudes.n[at]cs.ucy.ac.cy Web: www.cs.ucy.ac.cy/~nickl <http://www.cs.ucy.ac.cy/%7Enickl> LINC: linc.ucy.ac.cy <http://linc.ucy.ac.cy> CELAR: www.celarcloud.eu <http://www.celarcloud.eu/> ________________________________________________________
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
