$Id: Readme.txt 2305 2016-12-21 16:10:40Z lendl $

This directory contains a set of test files originating from real world 
"recorded" data. Use them for testing the various "timing quality" control 
algorithms implemented by the GIPPtools for processing Cube files.

Usually, files containing the input for the JUnit tests are denoted by >all< 
in their filename. Files with >bad< in the filename contain KNOWN bad time 
tags. "Timing quality" filter should always remove them from the input.
To save disk space, the time tags are read from plain text files instead of 
Cube files. 

Important! Depending on it's (configured) sensitivity, a filter may decide to 
remove even more time tags! But no matter what, it should remove at least the 
ones in the >bad< file!

The opposite is true for files containing >good< in their filename. The time 
tags in this selection are KNOWN to be good and should still be there after 
filtering. Again there may be additional >good< time tags in the input.

In other words:   "all" >=  "good" + "bad" !

         (All time tags not necessarily are the sum of good and bad time tags.) 


Note: Most test files in this directory only contain information required for 
      testing the "timing quality" algorithms (the sample ordinal number and 
      sample time). The other information time tags usually contain (such as
      file name and offset, geographic position and elevation) were omitted.


Test 001 -- Trond Ryberg's "D1" example data
--------------------------------------------

  The example data consists of about one week of time tags, one every second.
  It was recorded by Cube #612 in 2003 during an unknown campaign. The GPS 
  reception apparently was a little bit unreliable resulting in 55 outlier 
  time tags.
  
  The bad time tags were identified manually (they are easy to spot) using 
  the generated "detailed plot".
  
  Note: There is no special meaning in the "D1". Trond just called the example
        files that way for no particular reason and the name stuck.
  
  Files:
  
    001-D1.continuous.time ....... "all" time tags of this test case
    001-D1.bad.time .............. 55 known bad time tags
    
      The following files were generated from the "continuous" file mentioned 
      above. They simulated a Cube recording with "cyclic" GPS mode.
      
    001-D1.cycled.1-59-000.time .. 1min powered on every 59min, no time offset
    001-D1.cycled.1-59-123.time .. 1min powered on every 59min, 123s offset
    001-D1.cycled.1-59-186.time .. 1min powered on every 59min, 186s offset
    001-D1.cycled.1-59-843.time .. 1min powered on every 59min, 843s offset
    001-D1.cycled.5-30-000.time .. 5min powered on every 30min, no time offset
    001-D1.cycled.5-30-295.time .. 5min powered on every 30min, 295s offset
    001-D1.cycled.5-30-623.time .. 5min powered on every 30min, 623s offset
    001-D1.cycled.5-30-894.time .. 5min powered on every 30min, 894s offset
    001-D1.cycled.5-55-000.time .. 5min powered on every 55min, no time offset
    001-D1.cycled.5-55-175.time .. 5min powered on every 55min, 175s offset
    001-D1.cycled.5-55-353.time .. 5min powered on every 55min, 353s offset
    001-D1.cycled.5-55-933.time .. 5min powered on every 55min, 933s offset

    001-D1.bash .................. script used to generate PDF plots.
    001-D1.overview.pdf .......... single page test case overview plot
    001-D1.detail.pdf ............ 572 pages showing all time tag details.

