Please note that GPS Dancer will not run routine global solutions until its ITRF backbone network has been deployed and validated. Until that moment, feel free to download the latest software just to see what this is all about. It can already be used for various off-line applications, such as precise point positioning.

You can prepare a dancer test set-up for a GPS receiver of your choice via the following easy steps:

(1) Download one of the two available test data packages peer.tar.gz or These two files have exactly the same contents, but the first one can be unzipped with linux-style tools gzip and tar, while the second package can be unpacked with various windows-style zip programs like winzip or ark. The only reason why we provide the two alternatives is that some problems have occurred in the past with decompression tools on different platforms.     


                 unix-style peer.tar.gz                                         windows-style


(2) Unpack the peer data package anywhere in your system where you want to run a dancer peer. After unpacking, you should see the basic directory structure of the Figure below. You can rename the "peer" directory to reflect your particular receiver (using its RINEX station name), such as "algo", "mkea", "sydn", etc. This "peer" directory will be called the home directory of your dancer installation.

NOTE: if you or your system administrator are worried about security issues, you can create a separate "dancer" user account on your computer, and block read/write access for this user to the entire rest of your computer system. Each Dancer process only needs read/write access to its own home directory and the various sub-directories, it has no interest in the rest of your computer system.


(3) Download the latest version of the dancer.jar binary file. This file gets updated quite frequently, but it would be inefficient to always reinstall the complete peer set-up if only this single file gets modified. You can simply save this dancer.jar file in the home directory of your peer installation, overwriting the existing file of the same name.


                   latest version of dancer.jar  (Dancer v 0.9.018)


NOTE: if your Dancer process is on-line, its dancer.jar file will be updated automatically to the latest version without further action from your side

(4) You now need some RINEX observation data for the test campaign period, which covers the days 202 up to and including 210 of the year 2012. Most people who read this will be familiar with how to get RINEX observation files, but if not, you can find some help via the "RINEX data" menu option. If you have no specific preference for one site or another, try picking a proper IGS site at a location of the map where there are no other GPS Dancer stations yet. The currently active GPS Dancer stations are here.

(5) You now need to figure out how to launch a java application on your own system. Here, we can not help in full detail because there are some subtle syntax differences in different environments. Because the command line launches tend to be rather long and cumbersome, it is usually practical  to prepare a simple script, e.g. "dancer.bat" in windows, or "" in linux that contains the launch command. For the most common ways of running the software, some examples are given here:

  • in linux:             java -classpath ./dancer.jar:./jxta.jar:. dancer.Dancer
  • in windows:       java -classpath dancer.jar;jxta.jar;. dancer.Dancer

These commands will work from within the home directory, so if you put them in a script, you may want to preceed them with a line that changes the directory to your Dancer peer home directory, e.g. "cd  C:/Users/dancer/mkea" or something like that.

If you want to run multiple instances of dancer (preferrably on different computers), you can copy the entire "peer" directory across, renaming it to reflect some other GPS station, and obviously putting the correct RINEX observation files in the directory ~/peer/campaign/obs/. If you want to install multiple Dancer instances on a single file system you should always put them in completely separate home directories, otherwise some output files and scratch files will get overwritten by two or more instances simultaneously, with unpredictable results.

That's it, you are now ready to go. You may want to have a look at the short tutorial to get some idea how Dancer works.

Go to top