lines
methods for drawing of
filter
boundaries. They allow for
multiple dispatch, since not all filter
types need to be evaluated for plotting, but this decision should be
made internally. filter
. This is used as the
default when no more explicit method is found. It tries to find
the plotted parameters from the internal flowViz.state
environment. This only works if the flow data has been plotted
using the plot
or xyplot
methods provided by this
flowViz
package. filterResult
object. This basically extracts the
filter
from the
filterResult
and
dispatches on that. filter
types we need the raw
data to re-evaluate the filter. filterResult
or the raw
data as a flowFrame
for
curv1Filter
. filterResult
or the raw
data as a flowFrame
for
curv2Filter
.kmeansFilter
, hence we
warn. filterResult
or the raw
data as a flowFrame
for
norm2Filter
.polygonGate
directly from the gate
definition. quadGate
directly from the gate
definition. rectangleGate
directly from the gate
definition. rectangleGate
directly from the gate
definition. flowFrames
using the
plot
or xyplot
methods provided by flowViz
, the
plotted parameters are recorded, which makes it possible to correctly
overlay the outlines of filter
assuming that they are defined for the respective parameters. Warnings
and error will be cast for the cases where the parameters are
non-distinct or ambigious. The flow parameters plotted can be passed on to any of the methods
through the optional channels
argument, which always gets
precedence over automatically detected parameters.
The methods support all plotting parameters that are available for the
base
lines
functions.
filter
,
flowFrame
,
gpoints