load_cytoframe_from_fcs | R Documentation |
Similar to read.FCS
, this takes a filename for a single
FCS file and returns a cytoframe
.
load_cytoframe_from_fcs(
filename,
transformation = "linearize",
which.lines = NULL,
decades = 0,
is_h5 = NULL,
backend = get_default_backend(),
uri = NULL,
h5_filename = NULL,
min.limit = NULL,
truncate_max_range = TRUE,
dataset = NULL,
emptyValue = TRUE,
num_threads = 1,
ignore.text.offset = FALSE,
text.only = FALSE
)
filename |
The filename of the single FCS file to be read |
transformation |
A character string that defines the type of
transformation. Valid values are |
which.lines |
Numeric vector to specify the indices of the lines to be
read. If it is NULL, all the records are read. If it is of length 1, a random sample of
the size indicated by |
decades |
When scaling is activated, the number of decades to use for the output. |
is_h5 |
Logical indicating whether the data should be stored in h5 format |
h5_filename |
String specifying a name for the h5 file if |
min.limit |
The minimum value in the data range that is allowed. Some
instruments produce extreme artifactual values. The positive data range for
each parameter is completely defined by the measurement range of the
instrument and all larger values are set to this threshold. The lower data
boundary is not that well defined, since compensation might shift some
values below the original measurement range of the instrument. This can be
set to an arbitrary number or to |
truncate_max_range |
Logical. Default is TRUE. can be optionally turned off to avoid truncating the extreme positive value to the instrument measurement range, i.e. '$PnR'. |
dataset |
The FCS file specification allows for multiple data segments
in a single file. Since the output of |
emptyValue |
Logical indicating whether or not to allow empty values for keywords in TEXT segment. It affects how double delimiters are treated. If TRUE, double delimiters are parsed as a pair of start and end single delimiters for an empty value. Otherwise, double delimiters are parsed as one part of the string of the keyword value. The default is TRUE. |
num_threads |
Integer allowing for parallelization of the parsing operation by specifiying a number of threads |
ignore.text.offset |
Logical indicating whether to ignore the keyword values in TEXT segment when they don't agree with the HEADER. Default is FALSE, which throws the error when such a discrepancy is found. Users can turn it on to ignore the TEXT segment when they are sure of the accuracy of the HEADER segment so that the file still can be read. |
text.only |
whether to only parse text section of FCS (default is FALSE), it is sometime useful to skip loading data section for the faster loading meta data from FCS
|
The function load_cytoframe_from_fcs
works with the output of the FACS machine
software from a number of vendors (FCS 2.0, FCS 3.0 and List Mode Data LMD).
However, the FCS 3.0 standard includes some options that are not yet
implemented in this function. If you need extensions, please let us know.
The output of the function is an object of class cytoframe
.
For specifications of FCS 3.0 see http://www.isac-net.org and the file
../doc/fcs3.html in the doc
directory of the package.
The which.lines
arguments allow you to read a subset of the record as
you might not want to read the thousands of events recorded in the FCS file.
It is mainly used when there is not enough memory to read one single FCS
(which probably will not happen). It will probably take more time than
reading the entire FCS (due to the multiple disk IO).
An object of class
cytoframe
that contains the data, the parameters monitored,
and the keywords and values saved in the header of the FCS file.
Other cytoframe/cytoset IO functions:
cf_get_uri()
,
cf_write_disk()
,
cf_write_h5()
,
cs_get_uri()
,
load_cytoframe()
,
load_cytoset_from_fcs()
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.