Obtaining recent single ping UHDAS data

If you are on a ship with a UHDAS computer, you can your computer to do your calculations. If you want to do your own codas processing, you can use the NFS or Samba export of the /home/data directory on the UHDAS computer to access the files, and do the work on your own computer.

Using pre-existing data

The easiest way to get fully navigated recent single-ping data is to

• mount the adcp_home share
• load the matlab file saved from the most recent 5-minute profile. The instrument name willl probably be one of the following: (wh300, nb150, os75bb, os75nb, os38bb, os38nb). The file will be a location like

For Mac or linux

/Volumes/adcp_home/cruise/proc/nb150/load/lastens.mat

For Windows

Q:\cruise\proc\nb150\load\lastens.mat

   - read the introduction to
     `single-ping adcp data <../../singleping_doc/index.html>`_
     structure:

Making your own files

You need to know what “rbin” and “gbin” files are. This file has a short explanation.

For step-by-step instructions on making rbin and gbin files, look at the UHDAS codas processing demo readme:

• (batch_setup.txt) for rbin and gbin generation
• (batch.txt) for averaging etc: single-ping processing from scratch

Keep in mind that the “rbin” files are continually updated on the UHDAS computer. Older versions of UHDAS (before April,2005) are hampered by a bug in python which may leave holes in the rbin files. You may want to make your own rbin files.

NOTE:

If you make your own rbin files, you should also make your own gbin files.

The gbin files are updated about every 5 minutes. If you need faster access to the gbin files or if you made your own rbin files, you’ll have to make your own.

Here’s a description of the setup described in this document:

• “currents” is the UHDAS computer on the ship
• “grantee” is a linux computer brought by a scientist. It has a matlab license and may have all the UH CODAS software installed (as per software and download instructions. The user has also mounted the data, programs, and adcp_home directories

This example uses np0507 for a cruise name.

• overview: on currents, all UHDAS logging and processing for np0507 occurs in /home/data/np0507. Subdirectories are
  • raw (all raw logging)
  • rbin (binary parsed versions of serial ascii streams)
  • gbin (same data as gbin, but gridded to match adcp ping times)

You need to recreate this directory tree on your computer (by a combination of mount, link, and computation). Then in matlab, you will use some configuration files which indicate where this directory tree is. A program will extract single-ping data from the raw directory, and add heading, position and time information from the gbin directory, giving you a little chunk of fully-navigated adcp data from whichever instrument you chose.

To set ths up,

On “grantee”, do the following:

• Mount the currents data directory as something like /mnt/currents_data (/mnt/currents_data will then have your cruise as a subdirectory, and will contain subdirectories raw, rbin, gbin, proc)

• Pick a working location on your computer, for example a subdirectory called “adcp”. Change directories to that location

• You are in a directory called “adcp“:

  • Make a UHDAS data directory: ‘mkdir np0507’

  • Make a directory called ‘config’, and copy the appropriate files from currents, as:

    mkdir config

    cp -p /mnt/currents_data/np0507/proc/nb150/config/np0507_*.m config

  • Link the mounted currents UHDAS raw logging directory to the data directory:

    ln -s /mnt/currents_data/np0507/raw np0507

  • Case (1) using raw data and gbins from currents

    ln -s /mnt/currents_data/np0507/rbin np0507

    ln -s /mnt/currents_data/np0507/gbin np0507

  • Case (2) use raw and rbin from currents, update your own gbin

    ln -s /mnt/currents_data/np0507/rbin np0507

    # see instructions below for making gbin

  • Case (3) use raw from currents, make your own rbin and gbin files

    # (see instructions below for making rbins)

    # (see instructions below for making gbins)

To access recent data: In matlab, get the UHDAS configuration for the instrument you want:

%----------------------
% eg nb150
nb150cfg = get_uhdascfg('cfgbase','np0507', ...
                      'cfgpath', 'config',...
                      'instname', 'nb150',...
                      'pingtype', 'nb',...
                      'logfpath', '.');
nbdata = getsome_adcp(nb150cfg, 'interval',200);

% eg os38 broadband mode
os38bbcfg = get_uhdascfg('cfgbase','np0507', ...
                      'cfgpath', 'config',...
                      'instname', 'os38',...
                      'pingtype', 'bb',...
                      'logfpath', '.');
osbbdata = getsome_adcp(os38bbcfg, 'interval',200);
%----------------------


   - To make rbins, in the "adcp" directory, type
     (assuming the np0507 data directory tree starts here)

::

mk_rbin.py –uhdas_dir np0507 –yearbase 2005

(This will make all rbins. Maybe I can add something to have it only do the last few)

To make gbins, in matlab, use the same “get_uhdascfg” command as above for the instrument of interest, eg:

%------------------
% get configuration info (paths, etc)
os38bbcfg = get_uhdascfg('cfgbase','np0507', ...
                       'cfgpath', 'config',...
                       'instname', 'os38',...
                       'pingtype', 'bb',...
                       'logfpath', '.');

% now update gbins
update_gbin(os38bbcfg,'whichones','all','redo',1)
%---------------