adp
.read.adp(file, from=0, to, by=1,
type=c("rdi", "nortek", "sontek"),
debug=getOption("oce.debug"), monitor=TRUE, log.action)
read.adp.rdi(file, from=0, to, by=1,
type=c("workhorse"),
debug=getOption("oce.debug"), monitor=TRUE, log.action)
read.adp.nortek(file, from=0, to, by=1,
type=c("aquadopp high resolution"),
debug=getOption("oce.debug"), monitor=TRUE, log.action)
read.adp.sontek(file, from=0, to, by=1,
type=c("adp"),
withHeader=FALSE,
debug=getOption("oce.debug"), monitor=TRUE, log.action)
tz
argument.by-1
profiles are skipped between each pair of profiles that is read. If
this is a string representing a time interval, in colTRUE
to provide an indication
(with numbers and dots) of every profile read.class
"adp"
, which
contains measurements made with an ADP device. The value of
metadata$coordinate
is set to "beam"
, a fact that is
used in other steps in processing. For information on data stored in
the object, see read.adp
may also work on other RDI
units, but this has not been tested. It definitely does not work on
other NorTek units, because the binary format is different for each. There are three types of element stored in the result's data
,
namely space-series, time-series, and matrix. These are contained
within lists named data$ss
, data$ts
and data$ma
,
and their contents are as follows.
[object Object],[object Object],[object Object]
In addition to the data
entry, the metadata
entry holds
general information about such things as beam geometry, etc.
Information on the Nortek profiler is available at
read.oce
provides an
alternative to this. An adp
object may be summarized with
summary.adp
, and plotted with plot.adp
. Several functions are provided to manipulate adp
objects. For
example, in many research applications, the records are stored in beam
coordinates, instead of the further-processed forms such as instrument
or enu coordinates. Accordingly, adp.beam2xyz
is
provided, convert the velocity portions of adp
objects from
beam coordinates to xyz-based (also called ship-based or
instrument-based) coordinates. Similarly,
adp.xyz2enu
converts from xyz to enu
coordinates, taking into account the varying orientation of an
instrument attached to a ship or a mobile mooring. For applications
in which enu-based coordinates are not desired (e.g. if a coordinate
is to be aligned with the local coastline or a mean current),
adp.enu2other
is provided, to convert from enu
coordinates to another coordinate system.
Another convenience
function is adp.beam.attenuate
, which performs a
correction for $r^2$ beam spreading.
library(oce)
# A day sampled at 1/2 hour interval. Note the timezone.
d <- read.oce("~/SL08F001.000",
from=as.POSIXct("2008-06-26", tz="UTC"),
to=as.POSIXct("2008-06-27", tz="UTC"),
by="30:00")
summary(d)
plot(d)
Run the code above in your browser using DataLab