.. ...................................... .. UHDAS/CODAS restructured text document .. ...................................... Demos (Tutorials) --------------------------------- Introduction ***************** The examples that follow use two datasets for practice, one is :term:`UHDAS Data` and one is :term:`VmDAS Data`. UHDAS data includes two flavors: the entire raw single-ping data, stored in a directory structure with specific file names; and the pre-processed data from the at-sea UHDAS processing. which contains ocean velocities in earth coordinates. VmDAS also has single-ping data (ENR,N1R,N2R files) and averaged data in earth-coordinates (LTA or STA). A new program `adcp_database_maker.py <../adcp_database_maker_demos/ADM_adcp_database_maker_intro/index.html>`_ provides a graphical interface that leads the user through the steps getting the data into a form ready for post-processing. .. NOTE:: You should work through the post-processing demo because no matter what kind of data you have (VmDAS or UHDAS) ultimately you will need to work through the post-processing steps. **POSTPROCESSING** (1) postprocessing a dataset collected by UHDAS at sea **PRELIMINARY PROCESSING** Introduction to ``adcp_database_maker.py`` (2) **adcp_database_maker.py** a) UHDAS data b) VmDAS LTA (or STA) data c) VmDAS ENR (single-ping) processing d) VmDAS post-processing demo (because that's what naturally follows (b,c) (3) **commandline demos** a) UHDAS data using command-line steps b) "vmdas_quick_ltaproc.py" command-line c) LTA data using command-line steps d) ENR data using command-line steps There is also a rudimentary "PINGDATA" demo, using the original 1993 pingdata. The "original pingdata demo" has a very detailed manual, but the manual was written for Matlab processing (so some parts are different). The new Python pingdata demo exists in the text+directory form (no html documentation) alongside the other demos, and in ``quick_adcp.py --help``. There is not a web page for the pingdata demo. | The `glossary <../../../glossary/index.html>`_ describes some of the terminology. `This file <../../../txtfiles/directory-layout.txt>`_ and `this figure `_ describe the demos' directory structure and how they tie to the terminology. .. _Directory-Setup: Directory Setup **************** The ``adcp_py3demos`` directory is both an example (of what a final data processing directory looks like) and the source (of the data for these examples). If you start with the directory structure described below, your final processing directory should be nearly identical to ``adcp_py3demos/adcp_pyproc``. Before you start working with any of the demos, **make your own directory** to store the data and practice processing. The examples assume you have already set up a working directory such as below. The command-line examples are designed to copy-paste and use in the virtual computer. A graphical example is shown below. Check out the :term:`Glossary` for these terms, used below: - :term:`Project Directory` - :term:`Processing Directory` - :term:`UHDAS Data` - :term:`VmDAS Data` - :term:`UHDAS-style Data` ------ (1) make a directory called ``my_adcp_py3demos`` to hold **your practice demos** example: :: cd ls mkdir my_adcp_py3demos cd my_adcp_py3demos pwd ---- The result should be:: /home/adcpproc/my_adcp_py3demos (2) Copy the **uhdas_data** directory from the example into ``my_adcp_py3demos``, just as you would if you were getting the data from an at-sea disk example: :: cd ~/my_adcp_py3demos cp -a /home/adcpcode/programs/adcp_py3demos/uhdas_data . ls uhdas_data The result should be:: km1001c ---- (3) Copy the **vmdas_data** directory into ``my_adcp_py3demos`` example: :: cd ~/my_adcp_py3demos cp -a /home/adcpcode/programs/adcp_py3demos/vmdas_data . ls vmdas_data The result should be:: ps0918 ---- (4) Make a directory called **uhdas_style_data** (for converted VmDAS data) example: :: cd ~/my_adcp_py3demos mkdir uhdas_style_data ls The results should show 3 directories, all related to data:: uhdas_data uhdas_style_data vmdas_data ---- (5) Make a directory called ``adcp_pyproc`` (for **your UHDAS and VmDAS projects**) example: :: cd ~/my_adcp_py3demos mkdir adcp_pyproc cd adcp_pyproc pwd The result should be:: /home/adcpproc/my_adcp_py3demos/adcp_pyproc ---- (6) Make **one project directory for each dataset**. All your processing examples related to that dataset will be in the associated project directory. example: :: cd ~/my_adcp_py3demos cd adcp_pyproc pwd mkdir km1001c_uhdas mkdir ps0918_vmdas ls The result should show the two project directories:: km1001c_uhdas ps0918_vmdas ---- These steps are summarized `here <../../../txtfiles/make_dirs_for_demos.txt>`_ (copy-paste text suitable for the CODAS virtual computer). All the examples will refer to ``adcp_pyproc``. You will be building up your own version, but the directory structure and files of a finished version exist in your data source for the demos: `adcp_py3demos/adcp_pyproc <../../../../adcp_py3demos/adcp_pyproc>`_. Click the image below to enlarge .. image:: ../procfigs/demo_layout_dirs.png :alt: setting up to use demos :scale: 60 ---- .. toctree:: :maxdepth: 1