Please cite this release as:

Lendl, Christof (2021), GIPPtools, Version 2021.327, doi:10.5281/zenodo.5643357.

Changes since the previous GIPPtools 2021.168 release:

  • Fixed:

    • Correcting a sub-sample timing inaccuracy in the postprocessing (conversion) of Cube data streams.

      In order to use data acquired with Cube recorders, the data has to be converted from the proprietary internal data format, including interpretation of the timing information contained in the data stream. We were made aware that the recording time computation for the sample was imperfect.

      The necessary correction depends on the used sampling rate (sps) and can be computed as (0.199 / sps + 0.00030) seconds. For example a sampling rate of 100 samples per second requires an additional time correction of 2.29 milliseconds, which have not been considered so far.

      This (and all following) GIPPtool release(s) will automatically correct imperfect Cube timing during conversion to other data formats (using cube2mseed, cube2segy and cube2ascii).

      Note: As the timing error is only about a quarter of the sample period it is probably not a grave problem for most applications!

      Many thanks to Jake Anderson from Boise State University for reporting the problem and contributing to the fix.

    • Correctly warn the user about a missing JRE under Windows.

      Previously, Windows user were only receiving a rather misleading error message when no Java Runtime Environment (JRE) was found.

  • Added:

    • Extended the mseed2mseed utility to handle the timing quality field located in blockette #1001 (inside the miniSEED header).

      Use one or more of the command line options --equals-timing-quality, --less-than-timing-quality or --more-than-timing-quality as condition to select individual miniSEED records based on their respective timing quality. The --set-timing-quality command line option can be used to modify the timing quality field.

      Please see the manual page of the mseed2mseed utility for more details.

  • Changed:

    • Updated the internal leap seconds list. The new leap second list will expire June 28, 2022.

For more information see the ReleaseHistory.adoc file in the project source.