Data conditioning for pems data
Various functions for the conditioning of
1 2 3 4 5
(Data series typically vector) The reference data series to consider when making a vector of subset markers/indices. See Details.
(Optional) Other arguments, currently passed on to
(Optional function) For
(Character vector) For
(Various managment arguments)
cutBy... functions generate a vector of subset markers or indices based
of the type of cut applied and the range/size of the reference,
ref. See Value regarding
cutBy is a wrapper for other
cutBy... functions. It provides additional options for
cutByRow assigns cut regions based in row number.
By default results are returned as
cut.marker vector generated by
can then be used to condition and subsample data in
Currently, no warnings.
hijack is an in-development argument, supplied to allow code developers to run multiple
functions in different function environments. When developers 'mix and match' code from
several sources it can become unstable, especially if functions are run within functions within
hijack = TRUE and associated code makes a function local to 'side-step'
this issue. This work by assuming/expecting all inputs to be local, i.e. supplied directly by
the code user.
cutBy... options can be very simply encoded.
References in preparation.
cut, etc. in the main R package.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
########### ##example 1 ########### #basic usage #working with a temporary pems temp <- pems.1 #cut into equal subsets temp$ref <- cutBy(velocity, n= 5, data=temp) pemsPlot(local.time, velocity, cond=ref, data=temp, type="l", layout=c(1,5)) #cut at three points temp <- pems.1 temp$ref <- cutBy(velocity, rows=c(180,410,700), data=temp) pemsPlot(local.time, velocity, cond=ref, data=temp, type="l", layout=c(1,5))
Want to suggest features or report bugs for rdrr.io? Use the GitHub issue tracker.