You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

RDI Time Series

Data files for Teledyne RDI ADCPs are described here. Ancillary data (e.g., temperature, pitch, roll) are also available independently.

Revision History

  1. Date: Beta product released
  2. Date: Second release (beta designation removed)

Formats

This data is available in RDI and MAT formats. Content descriptions and example files are provided below.

RDI

This binary format is specific to the manufacturer. When using Teledyne-RDI data acquisition software, data is normally stored in this way. Although we use custom-built drivers to communicate with our instruments, we can use the raw data in the log file to produce the PRF file which can be interpreted by Teledyne-RDI post-processing software.

To produce the file, the following requirements apply:

  • A new RDI file is started at the beginning of each day, when the maximum records per file is exceeded, or when the driver is restarted (this should account for configuration changes, site changes, etc).
  • Only records with valid checksums are included.
  • The instrument date/time field is replaced using the NEPTUNE timestamp at the beginning of the log file (since this timestamp is more accurate than the instrument clock), and the checksum is recalculated.

This format is further described in the manufacturer's documentation.

Example:

MAT

MAT files (v7) can be opened using MathWorks MATLAB 7.0 or later. Each file is limited to a maximum of 5 days time series. The file contains two structures, meta and neptune.

meta: structure containing the following metadata fields.

  • deviceID: A unique identifier to represent the instrument within the NEPTUNE Canada observatory.
  • creationDate:Date and time (using ISO8601 format) that the data product was produced. This is a valuable indicator for comparing to other revisions of the same data product.
  • deviceHeading: Obtained at time of deployment (exception: for Device ID 13051, this field is NaN since this ADCP is on a mooring and does not have a fix heading).
  • siteName: Name corresponding to its latitude, longitude, depth position.
  • deviceName: A name given to the instrument.
  • deviceCode: A unique string for the instrument which is used to generate data product filenames.
  • locationName: The node of the NEPTUNE Canada observatory. Each location contains many sites.
  • samplingPeriod: Sampling rate of the instrument in seconds.
  • depth: Obtained at time of deployment.
  • lat: Obtained at time of deployment.
  • lon: Obtained at time of deployment.
  • dataProductVer: Version of data product.

adcp: structure containing the ADCP data, having the following fields.

  • range: vector of distance to each bin
  • corr: 3D matrix, correlation time-series for each bin
  • intens: 3D matrix, intensity time-series for each bin
  • velocity: 3D matrix
  • percentGood: 3D matrix, percent good time-series for each bin
  • ens: vector, ensemble number
  • compassHeading: vector, magnetic compass heading time-series
  • pitch: vector, pitch time-series
  • roll: vector, roll time-series
  • time: vector, timestamp in datenum format (obtained from time the reading reached the shore station)
  • temperature: vector, temperature time-series
  • salinity: vector, salinity time-series
  • pressure: vector, pressure time-series
  • depth: vector, calculated from range and deployment depth
  • soundSpeed: vector or constant (depending if configured to be fixed or computed)
  • uMagnetic (optional): 2D matrix
  • vMagnetic (optional): 2D matrix
  • u: 2D matrix
  • v: 2D matrix
  • w: 2D matrix
  • velocityError: 2D matrix
  • backscatter: 3D matrix

config: structure containing ADCP configuration details, where some field names are appended with '_XX' to represent the corresponding configuration command (beneficial for experienced RDI ADCP users).

  • fwVer: firmware version
  • fwRev: firmware revision
  • sysCfg:
  • freq: frequency
  • beamPattern:
  • orient: orientation (e.g.,'Up' indicates transducers are looking upward)
  • beamAngle:
  • janusCfg:
  • lagLength:
  • nbeams:
  • nbins_WN:
  • npings_WP
  • cellSize_WS
  • profilingMode
  • corrThresh_WC
  • codeReps
  • percentGoodMin_WG
  • errVelThreshold_WE
  • timePing_TP
  • coord_EX
  • coordSys
  • headingAlign_EA
  • headingBias_EB
  • sensorSrc_EZ
  • sensorAvail
  • bin1Dist
  • transmitLength_WT
  • falseTrgt_WA
  • transmitLagDistance
  • cpuSN
  • sysBndwdth_WB
  • sysPower_CQ
  • instSN
  • ensInterval
  • soundAbsorptionCoefficient
  • ambiguityVelocity_WV

units: structure containing unit of measure for fields in structures above. For instance, units.pressure='decibar'.

For details about the configuration parameters, refer to the manufacturer documentation (especially the WorkHorse Commands and Output Data Format manual).

Example:

Discussion

To comment on this product, click Add Comment below.

  • No labels