As of April 2013, this version of the documentation is no longer maintained; however, it is consistent with the last (now retired) version of CODAS processing that used Matlab. We no longer update or fix the Matlab processing code, but we will maintain the Matlab code that reads CODAS Matlab output. Although the notes refer to both Python and Matlab processing, none of the code here will be maintained. This (now retired) documentation and code will remain available for awhile longer.

Python processing code is actively maintained and developed, and CODAS Python processing is documented here.

Python access to ADCP data

All these tools require a full Python+CODAS installation.

CODAS data a powerful graphical tool which allows viewing of data in a CODAS database.

get_profiles: getting all bins and all profiles from a CODAS database; follow this link

  • extract averaged data, every bin and every profile, including access to many variables (time, position, velocity, amplitude, temperature, heading)

single-ping or VmDAS data

Multiread read single-ping ADCP data follow this link

  • access to single-ping ADCP data

  • ancillary data (heading, navigation) depends on data type:
    • UHDAS *.raw, VmDAS ENR (beam coordinates, no navigation)
    • VmDAS *.ENS (beam coordinates, NO navigation)
    • VmDAS *.ENX (earth coordinates, with navigation)
    • VmDAS *.STA, *.LTA (earth coordinates, with navigation, averaged)

PingSuite read a chunk of single-ping UHDAS data with associated navigation This requires the a complete (raw + gbin) single-ping directory structure with consistent gbins, and a properly configured python configuration file. If you have a properly configured directory, try -p for a graphical interface to the CODAS database and the singleping data.

see examples