ADCP cruise directory contents

The data for the present cruise is in the network share data directory under the generic name “current_cruise”, and under the cruise name used for logging. During a cruise, all logging and processing take place in this directory. Figures and data accessible through the web interface are generated using these data. After the ADCP Operator has stopped ADCP data acquisition and clicked “end cruise” the archived figures are copied to this directory, and it then contains all pertinent data from the ADCP.

Data for Scientists

There are three categories of data, all located in the logging directory, /home/data/CRUISEID. The cruise DVD shoule contain the entire /home/data/CRUISEID directory. This table is a short description of the contents:

subdirectory	contents	importance	back up for ...
raw	all raw data	critical	archiving
rbin	intermediate files	nice to have	anyone who gets ‘raw’
gbin	intermediate files	nice to have	anyone who gets ‘raw’
proc	processed data codas database underway figure archive matlab files	final at-sea product	science CD after cruise

Cruise Directory Details

If the cruise name is “vg0810” :

• Data logs under /home/data/vg0810 on the ADCP linux computer “currents”. The active UHDAS cruise directory contains the following subdirectories (link shows expanded tree format)
• raw: logging goes on here in directories named by instrument
  • ADCP (wh300, nb150, os150, os75, os38)
  • ancillary (gpsnav, gyro, ashtech, posmv, seapath, mahrs, phins...)
  • config (configuration directory)
  • log (diagnostics directory)
• rbin: intermediate version of ancillary ascii data in “raw” subdirectory, stored as binary.
  • ancillary only (gpsnav, gyro, ashtech, posmv, seapath, mahrs, phins...)
• gbin: time-matched ADCP, navigation, attitude; time in UTC
• proc : one processing directory for each instrument+pingtype possible; CODAS processing
  • standard CODAS processing subdirectories
  • config (instrument configurations used at sea)
  • png_archive (figures from the web site)

Accessing data in the cruise directory

1. ADCP data in raw can be accessed using Matlab and the UH program read.m These data, with no other information, will have values of velocity, amplitude, and correlation (or spectral width) for each beam. The time is the instrument time, which was set to the computer time when logging was started.
2. ADCP data in raw and gbin can be combined using Matlab and the UH program get_xfraw.m. This will result in a file that includes earth coordinates, heading, position, and an estimate of ocean velocity over the time range of the raw data file.
3. The proc directory contains the processing tree for each instrument. One codas database (and supporting files) exists for each instrument+pingtype combination. In each processing directory (eg vg0810/proc/os75nb) these may be of interest:

data	files to use
coarse resolution averaged ocean velocity	vector/vect*.mat
moderate resolution averaged ocean velocity	contour/cont*.mat
every bin and every profile	contour/allbins_*.mat
figures from the cruise	png_archive
the database (for manual extraction)	adcpdb/a*.blk

Matlab tools to access to ADCP data

Tip

Follow this link