cellHTS object.## S3 method for class 'cellHTS':
configure(object, descripFile, confFile, logFile,
path, descFunArgs=NULL, confFunArgs=NULL, logFunArgs=NULL)cellHTS object.read.table
function, so any of the valid argument types for
read.table are valid here, too. Must contain one row
for each well and each batch. Alternatively this can be a
function. See details.read.table function, so any of the valid argument
types for read.table are valid here,
too. Alternatively this can be a function. See details.descripFile, confFile or logFile are functions
rather than file names. See details.cellHTS ,
which is obtained by copying object and updating
the following slots:confFile (except the first two header rows).logFile.character containing what was read from input file descripFile.cellHTS object is updated in to state["configured"]=TRUE.controlStatus is updated taking into account the well annotation given by the plate configuration file.MIAME containing descriptions of
the
experiment, constructed from the screen description file.Plate, Well and Content. Columns
Plate and Well are allowed to contain regular
expressions. Data from wells that are configured as empty will
be ignored and are set to NA in the data slot xraw. For
an example, and for more details, please read the accompanying
vignette. logFile: This optional file allows to flag certain measurements
as invalid. It is expected to be a tab-delimited file with at least
three columns, and column names Plate, Well, and
Flag. If there are multiple samples (replicates or conditions),
a column called Sample should also be given. If there are
multiple channels, a column called Channel must be
given. Further columns are allowed.
descripFile: The screen description file contains general
information about the screen.
Alternatively, any of the three arguments can also be a user-defined
function returning data frames similar to those produced by
read.table from the respective files. If confFile is a
function, it has to return a list, where the first list item is an
integer vector of length 2 giving the total number of plates and
wells, and the second list item is the data.frame of the actual
plate configuration. Additional parameters can be passed on to these
functions via the descFunArgs, confFunArgs and
logFunArgs arguments. This design allows for instance to
import the necessary information directly from a data base rather than
using flat files.
readPlateList
templateDescriptionFiledatadir <- system.file("KcViabSmall", package = "cellHTS2")
x <- readPlateList("Platelist.txt", name="KcViabSmall", path=datadir)
x <- configure(x, "Description.txt", "Plateconf.txt", "Screenlog.txt", path=datadir)Run the code above in your browser using DataLab