UHDAS Overview
back (Other tabs)

UHDAS Control Files



All control or configuration files used by UHDAS (for logging or for subsequent processing) are stored in /home/adcp/config. Organizing these files by the programs that use them we have:


UHDAS Gui (logging and parsing)

If a serial port fails or an instrument is added or subtracted from the expected assemblage, that must be changed in the file "sensor_cfg.py". The other two (os_default.cmd and nb_default.cmd) should not be changed.


file (in /home/adcp/config)
 used for
 when to change it
sensor_cfg.py
 for each instrument, sets up
  • serial port, baud rate
  • message name (eg. "gga")
  • logging directory
  • filename specifics (prefix, format)
 Set up during an installation; change
when a serial port fails or instrument changes
os_default.cmd
 default values for 38KHz Ocean Surveyor ADCP
 probably never
nb_default.cmd
 default values for Narrowband 150KHz ADCP
 probably never


UHDAS (the gui and the underlying Python and C code) needs sensors_cfg.py to create the directories into which data recording occurs, and needs the *_default.cmd files to correctly initialize the ADCPs. The basic job of UHDAS is to reliably acquire serial data.

In addition, UHDAS preforms several useful steps in real-time, prepping the data streams for processing. So far, this is the end of what UHDAS does with the data. If all goes well, data are logged.


... the next stage: processing and plotting:

As the data are being logged, Matlab jobs are called to look at pieces of it and assemble it into meaningful numbers (ocean velocities, quality indicators, and backscatter strength). These matlab jobs may be spawned by UHDAS but they are fundamentally different, since they are not run in a real-time mode. This second stage is work in progress. If the processing fails, we apologize, but please DO NOT try to get it going: as long as logging is working, the raw data will be available for science after the cruise. DO NOT RISK THE DATA ACQUISITION. See troubleshooting.

The files below are used for processing (all done in Matlab) and plotting (python scripts drive matlab plotting routines).


UHDAS: setup for processing and plotting

file (in /home/adcp/config) used for when to change it
cruise_cfg.m__
  • template for regular matlab file (becomes lmg0406_cfg.m)
  • sets path information, year, cruise name, sensors and messages
 Set up during an installation; change
when a serial port fails or instrument changes
cruise_proc.m__
  • template for regular matlab file (becomes lmg0406_cfg.m)
  • sets transducer alignment and calibrations
 in a new installation or if a transducer is pulled
cruise_disp.m__
  • template for regular matlab file (becomes lmg0406_disp.m)
  • used for setting plotting parameters (under development)
 if the gps-aided attitude sensor changes
procsetup_onship.py
  • used to initialize Python with correct information for overview plots and email information
 in a new installation;


... and the overview: email status and tarball

file (in /home/adcp/config) used for when to change it
procsetup_onship.py
  • used to initialize Python with correct information for overview plots and email information
 in a new installation
et_email.txt
  • contents of email to ET (links to figures, mostly)
in a new installation



UHDAS Overview
back (Other tabs)