Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

This page lists all the tasks related to TULIP. The page is characterized in the following sections

Section 1 and 2 deals with the pre start of TULIP project.

  1. Understanding of the existing code and model of TULIP developed by Faran
  2. Disintegration of  Code from GUI.
    1. A separate command line tool is needed so that it can run this from cronjob for larger set of data
    2. Structuring of code so that classes can be found according to functionalities they diliver.
      1. Current Structure of code is :
      2. Code Block
        `-- tulip
            |-- core
            |   |-- AutomateTest.java
            |   |-- GetPingDataPL-08-27-2008
            |   |-- GetPingDataPL.java
            |   |-- Locate.java
            |   `-- PhysicalDistance.java
            `-- util
                |-- AnalyzeLog.java
                |-- Conversions.java
                |-- JScience.java.bak
                |-- LatLngToXYZ.java
                |-- LatLontoXY.java
                |-- Normalize.java
                |-- PingParser.java
                |-- Point.java
                |-- SAXParserTulip.java
                |-- Sites.java
                |-- XYtoLatLon.java
                |-- sites.xml
                `-- test.java.bak
        
      3. To solve the compilation problems and running of large number of java files, the code was made complaint to 'ANT' package management tool
        1. Single command explained here is used to compile the entire code.
        2. Binaries files are generarted for every compile in a separate folder. This helps us to upload code on SVN
        3. Document the code[here].
      4.  Code is scalable and portable , /afs/slac/pakage/pinger/tulip/src contains the client which can be shifted without any further problems.

Utility Perl Scripts for TULIP:

TULIP results depends upon landmarks, and there is greater need to manage these landmarks through some platform. These perl scripts are generally divided into two categories

  •  Scripts to generate XML which is used by reflector to decide which landmarks to probe these scripts are located at
  • Code Block
    /afs/slac/package/pinger/tulip/insert_sites-xml.pl (Script used to update landmarks from pinger Nodedetails)
    

Still in Process

TULIP Algorithm

TULIP Algorithm is still under-development, the algorithm works on multilateration and is considering 4 landmarks to calculate the position of target.