Mercurial > repos > zzhou > spp_phantompeak
comparison spp/man/get.binding.characteristics.Rd @ 6:ce08b0efa3fd draft
Uploaded
author | zzhou |
---|---|
date | Tue, 27 Nov 2012 16:11:40 -0500 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
5:608a8e0eac56 | 6:ce08b0efa3fd |
---|---|
1 \name{get.binding.characteristics} | |
2 \alias{get.binding.characteristics} | |
3 %- Also NEED an '\alias' for EACH other topic documented here. | |
4 \title{ Calculate characteristics of observed DNA-binding signal from | |
5 cross-correlation profiles } | |
6 \description{ | |
7 The methods calculates strand cross-correlation profile to determine binding | |
8 peak separation distance and approximate window size that should be used | |
9 for binding detection. If quality scores were given for the tags, | |
10 which quality bins improve the cross-correlation pattern. | |
11 } | |
12 \usage{ | |
13 get.binding.characteristics(data, srange = c(50, 500), bin = 5, cluster = NULL, debug = F, min.tag.count = 1000, acceptance.z.score = 3, remove.tag.anomalies = T, anomalies.z = 5,accept.all.tags=F) | |
14 } | |
15 %- maybe also 'usage' for other objects documented here. | |
16 \arguments{ | |
17 \item{data}{ Tag/quality data: output of \code{read.eland.tags} or similar function } | |
18 \item{srange}{ A range within which the binding peak separation is | |
19 expected to fall. Should be larger than probe size to avoid artifacts. } | |
20 \item{bin}{ Resolution (in basepairs) at which cross-corrrelation | |
21 should be calculated. bin=1 is ideal, but takes longer to calculate. } | |
22 \item{cluster}{ optional snow cluster for parallel processing } | |
23 \item{debug}{ whether to print debug messages } | |
24 \item{min.tag.count}{ minimal number of tags on the chromosome to be | |
25 considered in the cross-correlation calculations } | |
26 \item{acceptance.z.score}{ A Z-score used to determine if a given tag | |
27 quality bin provides significant improvement to the strand cross-correlation } | |
28 \item{remove.tag.anomalies}{ Whether to remove singular tag count peaks prior to | |
29 calculation. This is recommended, since such positions may distort the | |
30 cross-correlation profile and increase the necessary computational time. } | |
31 \item{anomalies.z}{ Z-score for determining if the number of tags at a | |
32 given position is significantly higher about background, and should be | |
33 considered an anomaly.} | |
34 \item{accept.all.tags}{ Whether tag alignment quality calculations | |
35 should be skipped and all available tags should be accepted in the | |
36 downstream analysis.} | |
37 } | |
38 \value{ | |
39 \item{cross.correlation }{ Cross-correlation profile as an $x/$y data.frame} | |
40 \item{peak }{Position ($x) and height ($y) of automatically detected | |
41 cross-correlation peak.} | |
42 \item{whs} { Optimized window half-size for binding detection (based | |
43 on the width of the cross-correlation peak) } | |
44 \item{quality.bin.acceptance} { A list structure, describing the | |
45 effect of inclusion of different tag quality bins on | |
46 cross-correlation, and a resolution on which bins should be | |
47 considered. | |
48 \item{informative.bins} { A boolean vector indicating whether the | |
49 inclusion of tags from the tag quality bin specified in the name | |
50 attribute significantly increases cross-correlation profile near | |
51 the peak.} | |
52 \item{quality.cc} { A list giving the cross-correlation profile | |
53 after the inclusion of the tags from different quality bins } | |
54 } | |
55 } |