pop_add: Add populations to a GatingHierarchy

In RGLab/flowWorkspace: Infrastructure for representing and interacting with gated and ungated cytometry data sets.

Add populations to a GatingHierarchy

Description

Add populations to a GatingHierarchy

Usage

pop_add(gate, gh, ...)

## S3 method for class 'filter'
pop_add(gate, gh, ...)

## S3 method for class 'filters'
pop_add(gate, gh, names = NULL, ...)

## S3 method for class 'quadGate'
pop_add(gate, gh, names = NULL, ...)

## S3 method for class 'logical'
pop_add(gate, gh, parent, name, recompute, cluster_method_name = NULL, ...)

## S3 method for class 'factor'
pop_add(gate, gh, name = NULL, ...)

## S3 method for class 'logicalFilterResult'
pop_add(gate, gh, ...)

## S3 method for class 'multipleFilterResult'
pop_add(gate, gh, name = NULL, ...)

gh_pop_remove(gh, node, ...)

Arguments

gate	a gate object that extends flowCore::filter or flowCore::filters
gh	GatingHierarchy
...	other arguments
names	a character vector of length four,which specifies the population names resulted by adding a quadGate.The order of the names is clock-wise starting from the top left quadrant population.
parent	a character scalar to specify the parent node name where the new gate to be added to, by default it is NULL,which indicates the root node
name	the population name
recompute	whether to recompute the gates
cluster_method_name	when adding the logical vectors as the gates, the name of the cluster method can be used to tag the populations as the extra meta information associated with the gates.
node	population name/path

RGLab/flowWorkspace documentation built on March 17, 2024, 2:24 p.m.