Description Usage Arguments Details Value Note Author(s) References See Also Examples
Joint segmentation of SNP array data resulting in piecewise constant curves with common break points for copy number data and B-allelle frequency data.
1 2 3 |
logR |
either a data frame or the name of a tab-separated file from which copy number data can be read. The rows of the data frame or file should represent the probes. Column 1 must hold numeric or character chromosome numbers, column 2 the numeric local probe positions, and subsequent columns the numeric copy number measurements for one or more samples. The header of copy number column(s) should give sample ID(s). |
BAF |
either a data frame or the name of a tab-separated file from which B-allelle frequency data can be read. Must be on the same format and size as |
pos.unit |
the unit used to represent the probe positions. Allowed options are "mbp" (mega base pairs), "kbp" (kilo base pairs) or "bp" (base pairs). By default assumed to be "bp". |
arms |
optional character vector containing chromosome arms (denoted 'p' and 'q') corresponding to the chromosomes and positions found in |
kmin |
minimum number of probes in each segment, default is 5. |
gamma |
penalty for each discontinuity in the curve, default is 40. |
baf.thres |
a numeric vector of length two giving the thresholds below and above which BAF probes are considered germline homozygous. Must be in the range 0 to 1, default is 0.1 and 0.9 for the lower and upper limit, respectively. |
skew |
a numeric value used to determine whether there is allelic skewness (one or two bands) in BAF. Default is 3. The larger the value the further the BAF measurements must be from 0.5 to imply two bands. |
assembly |
a string specifying which genome assembly version should be applied to determine chromosome arms. Allowed options are "hg19", "hg18", "hg17" and "hg16" (corresponding to the four latest human genome annotations in the UCSC genome browser). |
digits |
the number of decimals to be applied when reporting results. Default is 4. |
return.est |
logical value indicating whether a data frame holding LogR estimates should be returned along with the segments. Default is FALSE, which means that only segments are returned. |
save.res |
logical value indicating whether results should be saved in text files, default is FALSE. |
file.names |
optional character vector of length two giving the name of the files where the logR estimates and segments, respectively, should be saved in case |
verbose |
logical value indicating whether or not to print a progress message each time aspcf analysis is finished for a new chromosome arm. |
Piecewise constant curves are simultaneously fitted to the LogR and BAF data as described in Nilsen and Liestoel et al.(2012). This implies that break points will be the same for the LogR and BAF segmentation curves, while segment values differ. Segmentation is done separately on each chromosome arm in each sample.
If return.est = TRUE
a list with the following components:
logR_estimates |
a data frame where the first two columns give the chromosome numbers and probe positions, respectively, while subsequent column(s) give the LogR estimates for each sample. The estimate for a given probe equals the mean of the segment where the probe is located. |
segments |
a data frame describing each segment found. Each row represents a segment, and columns give the sample IDs, chromosome numbers, arms, local start positions, local end positions, number of probes in the segments, mean LogR values and mean BAF values, respectively. |
If return.est = FALSE
, only the data frame containing the segments is returned.
If save.res = TRUE
the results are also saved in text files with names as specified in file.names
. If file.names=NULL
, a folder named "aspcf_results" is created in the working directory, and the LogR estimates and the segmentation results are saved in this folder as tab-separated files named logR_estimates.txt and segments.txt, respectively.
It will usually be advisable to Winsorize the logR data before running aspcf
, see winsorize
on this. Missing values are not allowed in logR
, see imputeMissing
for imputation of missing copy number values.
Gro Nilsen, Knut Liestoel, Ole Christian Lingjaerde
Nilsen and Liestoel et al., "Copynumber: Efficient algorithms for single- and multi-track copy number segmentation", BMC Genomics 13:591 (2012), doi:10.1186/1471-2164-13-59
1 2 3 4 5 6 7 8 9 |
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.