nucleosomeDynamics: Run nucleosomeDynamics to compare two sets.

Description Usage Arguments Details Value Author(s)

Description

This is the main function in nucleosomeDynamics. It allows to compare the reads of two NGS experiments of nucleosome coverage.

Usage

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
nucleosomeDynamics(setA, setB, maxLen = 170, equalSize = FALSE,
  readSize = 140, maxDiff = 74, minDiff = 10, mc.cores = 1)

## S4 method for signature 'IRanges,IRanges'
nucleosomeDynamics(setA, setB, maxLen = 170,
  equalSize = FALSE, readSize = 140, maxDiff = 74, minDiff = 10)

## S4 method for signature 'RangedData,RangedData'
nucleosomeDynamics(setA, setB, maxLen = 170,
  equalSize = FALSE, readSize = 140, maxDiff = 74, minDiff = 10,
  mc.cores = 1)

## S4 method for signature 'GRanges,GRanges'
nucleosomeDynamics(setA, setB, maxLen = 170,
  equalSize = FALSE, readSize = 140, maxDiff = 74, minDiff = 10,
  mc.cores = 1)

Arguments

setA

Reads of the first experiment in IRanges, RangedData, or GRanges. The format should the same of the one in setB.

setB

Reads of the second experiment in IRanges, RangedData, or 'GRanges. The format should the the same of the one in setA.

maxLen

Reads longer than this number will be filtered out.

equalSize

If set to TRUE, all sets will be set to the same length, conserving their original dyad position. Use it if the reads in your sets have differences in length (ie, due to differences in the digestion) that you are not interested in.

readSize

Length to which all reads will be set in case equalSize is TRUE. It is ignored when equalSize is set to FALSE.

maxDiff

Maximum distance between the dyads of two reads that allows them to still be considered a "shift".

minDiff

Minimum distance between the dyads of two reads that allows them to still be considered a "shift".

mc.cores

If parallel support, the number of cores available. This option is only used if the provided sets are from more than one chromosome.

Details

The aim of NucleosomeDynamics is to infer "movement" (with direction and magnitude) of the reads between two reference nucleosome maps. In contrast with a simple coverage difference, NucleosomeDynamics can tell how the reads change between two different experiments. This is useful to analyze regions where fine regulatory role of the nucleosomes is suspected to happen.

This method is based on the idea that reads in a reference state (ref1) should match those in another reference state (ref2) after applying a few shifts and/or indels. Both ref1 and ref2 need to be experimental nucleosome maps, either from the same sample with different conditions or from different samples.

Then, we look for a match to each read in ref1 in another read of ref2 using a specific deffinition for what a "match" is. After all possible matches have been found, we set those reads apart and we look for matches in the remaining reads using a different definition for what a "match" is. Then, to account for the possibility that one sample has a higher coverage than the other, randomly picked reads are removed from the dataset with more reads to that they are the same size. After this, all the remaining reads are considered indels.

Since they are tried sequentially, the definition of each type of match implies that the previous definitions tried are do not hold. The different types of matches, in the order in which they are tried are:

If equalSize=TRUE, all reads are forced to the same size, to the match types "Same start", "Same end" and "Contained" do not apply.

In an attempt to find the optimum pairing for the shifts, we use dynamic programming approach. It is done in such a way that the score is inversely proportional to the dyad distance (to favor shortest possible distance), but with a very high gap penalty (to favor more pairs at longer distance rather than less closer pairs) and a penalty of -Inf for distances higher than maxDist so that those don't happen at all.

Value

An object of class NucDyn.

Author(s)

Ricard Illa ricard.illa@irbbarcelona.org


gthar/NucleosomeDynamics documentation built on May 17, 2019, 8:56 a.m.