One last thing that I noticed now, is that the NODE IDs in the generated ns2 mobility TCL file are not sequential.
Is this by design?

Best,
Nicholas.

On 02/25/2014 12:03 PM, Nicholas Loulloudes wrote:
Ok updating the above file sorted out
my problem.

Thanks Jacob!

On 02/24/2014 09:09 AM, Jakob Erdmann wrote:
Did you also update the file http://sumo-sim.org/trac.wsgi/browser/trunk/sumo/tools/sumolib/__init__.py ? Regarding revision numbers. I noticed that some of these files were wrongly tagged in the repositoy and did therefore not updated their $Id.
regards,
Jakob


2014-02-22 15:07 GMT+01:00 Nicholas Loulloudes <[email protected] <mailto:[email protected]>>:

    Hi Jacob, all,

    Even after updating to the latest revision of ns2.py module, the
    problem persists.

    Any suggestions are highly welcome

    Btw, the @version tag for (ns2.py, traceExporter.py) do not
    provide information for the actual version. It only includes
    the $id directive and nothing else. Example below.

    """
    A script for converting SUMO's fcd-output into files readable by
    PHEM and communication simulators.

    @file   traceExporter.py
    @author  Daniel Krajzewicz
    @date   2013-01-15
    @version $Id$

    Regards,
    Nicholas

    On 21 Feb 2014, at 16:02, Jakob Erdmann
    <[email protected] <mailto:[email protected]>>
    wrote:

    Every file contains the revision number among the first few
    comment lines. look for @version $Id: ....



    2014-02-21 12:43 GMT+01:00 Nicholas Loulloudes
    <[email protected] <mailto:[email protected]>>:

        I updated the ns2.py, to the latest, but wasn't aware about
        the init.py.

        I will update this module and try again....and let you know.

        Btw, is there any way of finding the revision number I have
        on my local SUMO installation?

        - Nicholas

        On 21 Feb 2014, at 13:03, Jakob Erdmann
        <[email protected]
        <mailto:[email protected]>> wrote:

        Hello,
        what revision of
http://sumo-sim.org/trac.wsgi/changeset/15251/trunk/sumo/tools/sumolib/__init__.py
        and
http://sumo-sim.org/trac.wsgi/browser/trunk/sumo/tools/sumolib/output/convert/ns2.py
        are you using?
        both need to be updated to patch known bugs
        (see
http://sumo-sim.org/wiki/FAQ#traceExporter.py_fails_to_work_properly_in_verson_0.19.0)
        regards,
        Jakob


        2014-02-21 8:47 GMT+01:00 Nicholas Loulloudes
<[email protected] <mailto:[email protected]>>:

            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_400

            Unless 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 <tel:%2B357-22892676>
            Email: loulloudes.n[at]cs.ucy.ac.cy <http://cs.ucy.ac.cy/>
            Web: www.cs.ucy.ac.cy/~nickl
            <http://www.cs.ucy.ac.cy/%7Enickl>
            <http://www.cs.ucy.ac.cy/%7Enickl>
            LINC: linc.ucy.ac.cy <http://linc.ucy.ac.cy/>
            <http://linc.ucy.ac.cy <http://linc.ucy.ac.cy/>>
            CELAR: www.celarcloud.eu <http://www.celarcloud.eu/>
            <http://www.celarcloud.eu/>
________________________________________________________


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






    ________________________________________________________
    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 <tel:%2B357-22892676>
    Email: loulloudes.n[at]cs.ucy.ac.cy <http://cs.ucy.ac.cy>
    Web:www.cs.ucy.ac.cy/~nickl <http://www.cs.ucy.ac.cy/%7Enickl>
    VSense:vsense.cs.ucy.ac.cy <http://vsense.cs.ucy.ac.cy/>
    LINC:linc.ucy.ac.cy <http://linc.ucy.ac.cy/>
    ________________________________________________________





------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk


_______________________________________________
sumo-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sumo-user

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
sumo-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sumo-user

Reply via email to