Data-quality flags are stored in the
oce-class objects in a
The present function (a generic that has specialized versions
for various data classes) provides a way to
manipulate the core data based on
the data-quality flags. For example, a common operation is to replace suspicious
or erroneous data with
metadata$flags in the object supplied as the first argument
is empty, then that object is returned, unaltered.
handleFlags analyses the data-quality flags within
the object, in relation to the
flags argument, and interprets
action argument to select an action to be applied to mached
Reasonable defaults are used if
are not supplied (see ‘Details’),
but different schemes are used in different
data archives, so it is risky to rely on these defaults.
It is usually necessary to tailor
to the data and the analysis goals.
An object of
actions are not provided, the
default is to use ARGO flags , in which the
value 1 indicates good data, and other values indicate either unchecked,
suspicious, or bad data. Any data not flagged as good are set
NA in the returned value. Since Argo flag codes run
from 0 to 4, this default is equivalent to
flags=list(c(0, 2:4)) along with
handleFlags is a new function as of March 2016,
and it will probably continue to evolve through the rest of 2016.
Users are asked to be patient, and to provide help by
looking at the documentation and telling the developers
whether the planned functioning seems reasonable.
Other functions that handle data-quality flags:
Other things related to
1 2 3 4 5 6 7 8 9 10 11 12
## Not run: library(oce) data(argo) # 1. Default: anything not flagged as 1 is set to NA, to focus # solely on 'good', in the Argo scheme. argoNew <- handleFlags(argo) # 2. A less restrictive case: include also 'questionable' data, # and only apply this action to salinity. argoNew <- handleFlags(argo, flags=list(salinity=4)) ## End(Not run)
Want to suggest features or report bugs for rdrr.io? Use the GitHub issue tracker.