DMRforPairs (version 1.8.0)

regionfinder: IDENTIFICATION OF PROBE DENSE REGIONS

Description

Identifies genomic regions with sufficient probe density, i.e. a high number of probes positioned closely together.

Usage

regionfinder(targetID,chr,position,pclass,r_excl,u_pclass,d=200,m.v,beta.v,n_min=4, debug=FALSE,gs)

Arguments

targetID

See DMRforPairs parameters

chr

See DMRforPairs parameters

position

See DMRforPairs parameters

pclass

See merge_classes output

r_excl

See merge_classes output ($no.pclass). If a probe is not annotated to one of the classes of interest in the recoding scheme, that probe is discarded.

u_pclass

See merge_classes output

d

See DMRforPairs parameters

m.v

See DMRforPairs parameters

beta.v

See DMRforPairs parameters

n_min

See DMRforPairs parameters

debug

See DMRforPairs parameters

gs

See DMRforPairs parameters

Value

List of objects containing

$boundaries

information about the regions identified (chr, start and end bp position, length of region, n of probes in region and information about the functional class(es) the region is associated to.

$perprobe

m x p matrix with region IDs. Rows represent the valid probes (see below) and there is one column per functional class (see u_pclass parameter). Each probe can be associated to one region within each class. Region IDs are specific to a dataset and to a set of DMRforPairs parameters. They are not interchangeable between datasets/experiments and serve mainly as an identifier during exploration of the dataset.

$valid.m

m x n matrix with M values for all samples. Only probes associated with at least one class of interest are included (=valid probes).

$valid.beta

see valid.m. This matrix contains the beta values.

Details

Regions are identified (per unique functional class) based on a minimal number of probes that lay in close proximity to each other. This can lead to identical (start to end) regions in different classes due to overlapping annotations. regionfinder() merges such regions to prevent duplications. These regions can be identified by a combined class name (e.g. "tss;island").

See Also

DMRforPairs, merge_classes.

Examples

#regionfinder() is an integrated part of the DMRforPairs() wrapper and is 
#not usually called by the user directly. Please see DMRforPairs() for 
#an example.