2.5. Demos: Commandline Demos


Directory Strategy

To simplify the documentation, these instructions assume you have set up your directories as in Directory Setup and you are doing your processing demos in my_adcp_py3demos/adcp_pyproc

your practice directory                 source
-----------------------                -----------

my_adcp_py3demos/adcp_pyproc                 (new, WORKING IN HERE)
my_adcp_py3demos/uhdas_data                  copy of adcp_py3demos/uhdas_data
my_adcp_py3demos/vmdas_data                  copy of adcp_py3demos/vmdas_data
my_adcp_py3demos/uhdas_style_data            (new, empty, for VmDAS conversion)

The 4 demos with commandline instructions are:

  1. UHDAS Single-ping: You need to reprocess UHDAS data and adcp_database_maker.py is not sufficient for some reason. For example, you need to alter a configuration file in a way that is not supported in the GUI.

  2. LTA automated: You have a large historical collection of VmDAS data LTA data and you want to quickly loop through the cruises and get a quick look at the data (to see what else needs to be done, and which cruises are worth saving).

  3. LTA manual: You want to know what is going on behind the scenes in (2)

  4. ENR manual: You have VmDAS data and need to reprocess it from single-ping files (ENR) but something isn’t working with adcp_database_maker.py

Other resources

This diagram shows the split between what happens before the data are in the CODAS database (acquisition + averaging + loading the database) and the steps that operate on the CODAS database itself (which can be repeated). The latter steps are called Post-Processing

This page shows a schematic about how CODAS processing fits with LTA and UHDAS datasets.

This detailed ascii chart shows (most of) the steps quick_adcp.py performs, the directory in which it does the work, the input files it generates, the programs it runs, and the output files it generates.