General

The GPSdancer software was written in JAVA and should therefore run without modification on any computer platform with an appropriate JAVA Run-time Environment. The executable consists of a single file dancer.jar, if desired it is of course possible to wrap this in a JNI environment for creating a stand-alone executable.

The source code consists of a few different packages (see the JAVAdoc information) that are more or less independent and suitable for reuse, although most of them will also require some lower level packages, such as the objectbase infrastructure, various storage classes and generic utility classes.

Authors

The current source code was entirely written by Henno Boomkamp, mainly for keeping the coding conventions homogeneous but also because he wants to make sure to understand every detail. However, writing source code and developing software are not the same thing. During the development, many inputs and code examples have been provided by people from science and industry, or were simply found somewhere in the public domain. Please refer to the credits page for a (probably incomplete) overview of known contributors.

Dependencies

GPSdancer software no longer has any dependencies on third-party libraries, such as (in the earlier versions) JXTA, for the peer-to-peer network, or the Bouncy Castle encryption binaries. The advantage of having only native software are of course that there cannot be IPR issues or (e.g.) limitations on distribution under GPL license or similar.

Configuration control and maintenance

Classic CVS configuration control is used on the full source code, its makefile and the various resources (such as images) that are archived in the jar file itself. Most work on the software is done in a SuSE linux environment, which in turn runs inside a VMware virtual machine on a Windows laptop. This allows quick testing of everything in Linux and Windows, and so far no incompatibilities have ever been observed between the two environments, other than minor differences in the graphics, as can be expected.

Graphics

The graphics package can be replaced by stubs to significantly reduce the size of the jar file from about 1.6 MB to about 300 kB. This is mainly aimed at possible use in web applets and other tiny-footprint environments (remember, we originally aimed at embedding GPSdancer on a GPS receiver).

Validation

GPSdancer has a variety of built-in unit tests, for instance for most IERS Class-1 models of the 2010 conventions, and other critical elements. These tests require access to some standard input files (e.g. the DE421 JPLEPH file) but can normally be executed in any standard dancer run-time environment, where these files are typically available.

At system level, a full validation campaign of dancer-in-the-cloud (including web portal) is foreseen as part of the deployment of the Geodetic Cloud Computing Service (GCCS), which is effectively the operational branch of the GPSdancer project. This validation will be done at and by the IGS Analysis Centre of the European Space Operations Centre in Darmstadt, Germany. results will be published via the typical IGS and IAG channels, but also on-line (e.g. through this website) to remain transparent on what GPSdancer can and cannot do.

 

Project details

Ultimate Browsers SupportThe GPS Dancer project started in 2007 as a voluntary project of a working group of the International Association of Geodesy.

Read more ...

Square dance algorithm

Great Docs and SupportThe GPS Dancer system was named after its "square dance" exchange algorithm. Of course, it also wants to to make the GPS reference frame denser.

Read more...

Here, there be pirates

The Dancer on-line network became immune against internet connection problems by leaving the US marines, and becoming a pirate.

Read more ...

Go to top