glidertools 2019.5

Tools and utilities for buoyancy glider data processing.

Glider tools is a Python 3.6+ package designed to process data from the first level of processing to a science ready dataset. The package is designed to easily import data to a standard column format (numpy.ndarray or pandas.DataFrame). Cleaning and smoothing functions are flexible and can be applied as required by the user. We provide examples and demonstrate best practices as developed by the SOCCO Group (http://socco.org.za/).

Please cite the original publication of this package and the version that you’ve used: Reference here with <#link_to_the_paper>

Installation

PyPI

To install the core package run: pip install glidertools.

GitLab

1. Clone glidertools to your local machine: git clone –depth 1 https://gitlab.com/socco/GliderTools (–depth 1 reduces the download size)

2. Change to the parent directory of GliderTools

3. Install glidertools with pip install -e ./GliderTools. This will allow changes you make locally, to be reflected when you import the package in Python

Recommended, but optional packages

There are some packages that are not installed by default, as these are large packages or can result in installation errors, resulting in failure to install GliderTools. These should install automatically with pip install package_name:

• gsw: accurate density calculation (may fail in some cases)

• pykrige: variogram plotting (installation generally works, except when bundled)

• plotly: interactive 3D plots (large package)

How you can contribute

• Error reporting with using GitLab (https://gitlab.com/socco/GliderTools/issues/new). Please copy the entire error message (even if it’s long).

• Detailed error reporting so users know where the fault lies.

• Oxygen processing is rudimentary as we do not have the expertise in our group to address this

Acknowledgements

• We rely heavily on ion_functions.data.flo_functions which was written by Christopher Wingard, Craig Risien, Russell Desiderio

• This work was initially funded by Pedro M Scheel Monteiro at the Council for Scientific and Industrial Research (where Luke was working at the time of writing the code).

• Testers for their feedback: SOCCO team at the CSIR and …