SEa-EXPLORER data format

[laurcopp]

Hello

Does Pyglider allow conversion of recent SeaExplorer datasets? The example cited here seems to work only for older data formats. Do you know of any recent examples demonstrating the use of the Pyglider toolbox?

https://pyglider.readthedocs.io/en/latest/getting-started-seaexplorer.html

[jklymak]

Hi @laurcopp

I'm sure it could be made to work with whatever the new format is. Do you have an example that doesn't work? Perhaps @callumrollo knows more.

[richardsc]

Hi!

We (@clayton33 and I) have been using it successfully for some time (not quite at full production yet). There are a few tweaks we are working on based on our needs, but most are handled using the yaml rather than code base changes.

I think our firmware is pretty recent, so our files should look a lot like yours. It would help to have an example file or two (e.g. pld, gli, and also associated sub files).

Clark

[laurcopp]

Hello

Basically, I have a few SeaExplorer files that I’d like to import using PyGlider (to convert them to .nc) and then use Glidertools for plotting and corrections (especially for optical sensors). On GitHub, I can only find examples for VOTO gliders, which don’t fit our latest SeaExplorer dataset. How do you proceed on your side ?

sea091.9.gli.sub.1.gz
sea091.9.gli.sub.2.gz
sea091.9.gli.sub.3.gz

[jklymak]

Hi Laurent, do you have the .pld1. files and also what deployment.yml are you trying to use? .gli. are just the navigation files, so there is no instrument data in there to use. Finally, where does your processing fail?

Merci!

[laurcopp]

Hi Jody

Yes indeed my mistake. Find here some delayed mode data for SEA091. For the deployment.yml we used this one in attachment. So I understand we have to fill ourselves this file with metadata...correct ?

sea091.9.pld1.raw.1.gz
sea091.9.pld1.raw.2.gz
sea091.9.pld1.raw.3.gz
deployment.txt

[jklymak]

Yes, you should rewrite the deployment.yaml and make sure in particular that the "source" for netcdf data matches the columns in the pld1 or gli files. I note you have two CTDs, but that should not be an issue - just make two temperature netcdf variables eg:

 temperature_gpctd:
    source:       GPCTD_TEMPERATURE
    long_name:    water temperature
    standard_name: sea_water_temperature
    units:        Celsius
    coordinates:  time depth latitude longitude
    instrument:   instrument_ctd
    valid_min:    -5
    valid_max:    50
    observation_type: "measured"
    accuracy:      0.002
    precision:     0.001
    resolution:    0.0002

 temperature_legato:
    source:       LEGATO_TEMPERATURE
    long_name:    water temperature
    standard_name: sea_water_temperature
    units:        Celsius
    coordinates:  time depth latitude longitude
    instrument:   instrument_ctd
    valid_min:    -5
    valid_max:    50
    observation_type: "measured"
    accuracy:      0.002
    precision:     0.001
    resolution:    0.0002

I'm a little uncertain if you need to assign two different long_name to duplicate variables like that, but I don't think there is any reason your files should not work.