getImages | R Documentation |
Return a list of paired DNA and fluorescent images
appropriate for parseImages
.
getImages(
source,
type = "tiff",
which.images = c(1, 2, 2),
pattern = NULL,
verbose = FALSE
)
source |
A character vector identifying the source of images.
The source can be a directory with subdirectories, each of which
contains images organized as specified by |
type |
A character string identifying the type of image files to parse ("tif", tiff", jpeg", jpg or png"). |
which.images |
An integer of length 2 or 3 or |
pattern |
Optional grep pattern as character string used by
|
verbose |
If |
Images specified in source
will be evaluated with the same logic in
checkImages
to determine if the proper number of files are
present. The order required by parseImages
is the DNA
image first and the fluorescent viral target second. The position of
the DNA image and the target image within each set of images can be changed
with the which.images
argument.
Images associated with each multiplicity of infection can be individual
files in a single directory where each directory named as the well such as
A1
, A2
, etc. and the files within are identified as
A1/file001.tif
, A1/file002.tif
, etc. The well identifier
can be in upper or lower case and can contain leading zeros such as
c0003/file12.tif
as well as a numeric prefix such as 1A3
.
Alternatively, each group of images associated with a given moi can be
a multi-layered tiff file where the sequence of images in the file is
specified by the argument which.images
.
If 'source'
is one or more zip files, files in the temporary directory
(tempdir
) will be deleted in order to receive the compressed
files.
A list of two named lists containing the nuclear and target images.
Each well or file will be represented as an element in the lists nuc
and tgt
. Diagnostic messages are provided if verbose
is TRUE
.
# Example with data organized by folder or well
path.by.folder <- system.file("extdata", "by_folder", package = "virustiter")
getImages(path.by.folder)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.