Versions Compared

Old Version 12

changes.mady.by.user Zafar Gilani

Saved on

compared with

New Version 13

changes.mady.by.user Les Cottrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. User enters the URL with target to be geolocated.
  2. The TULIP visualization GUI on the client calls the Java code. The Java code calls the reflector RTT server with the target and information on the selection of landmarks .  The reflector calls the enabled landmarks from the set of selected  landmarks. The landmarks measure the ping RTTs  to the target and return the results of the pings to the reflector, that in turn returns those results to the client. The client then massages the results and computes the answer. Meanwhile the client sends a query string via a web service/remote routine (Perl or CGI script) to the Matlab server. Detail below:
    1. The TULIP client gets the active landmarks list from the reflector as before.
    2. Client massages/adjusts the results and computes the answer for the target that needs to be geolocated.
    3. Client needs to send this active landmark and target list to Matlab as well. To accomplish this, the client (which is written in Java) writes a file.
    4. A perl script can then use sockets to establish a connection to the Matlab server and send this file.
    5. Another perl script running on the Matlab server receives the file via sockets and writes it in local directory.
    6. Matlab CBG code then needs to read this file and provide the contents as input to the geolocateall method.
  3. The Matlab server computes an answer from data provided in the query string. Matlab server sends back a reply in the form of a dataset. Detail below:
    1. Matlab CBG code computes an answer from the list of landmarks and target.
    2. Matlab CBG code writes the result to a file.
    3. This file is sent to the TULIP client using perl script. This will be the same script running on Matlab server which was used to receive the active landmarks and target list.
    4. The file will be received at TULIP client by perl script.
    5. The TULIP Java code will be modified to read this file and put the CBG results on the map.
  4. The Java code receives the reply and merges this to other results to create a standardized XML file.
  5. This XML file is then read by TULIP visualization GUI to display the result on Google map. Each algorithm's result is represented in a distinct fashion.

...