# derfinder users guide

Leonardo Collado-Torres1,2*

1Lieber Institute for Brain Development, Johns Hopkins Medical Campus
2Center for Computational Biology, Johns Hopkins University

*lcolladotor@gmail.com

#### 26 April 2022

#### Package

derfinder 1.30.0

# 1 Asking for help

Please read the basics of using `derfinder` in the quick start guide. Thank you.

# 2 derfinder users guide

If you haven’t already, please read the quick start to using derfinder vignette. It explains the basics of using derfinder, how to ask for help, and showcases an example analysis.

The derfinder users guide goes into more depth about what you can do with derfinder. It covers the two implementations of the DER Finder approach (Frazee, Sabunciyan, Hansen, et al., 2014). That is, the (A) expressed regions-level and (B) single base-level F-statistics implementations. The vignette also includes advanced material for fine tuning some options, working with non-human data, and example scripts for a high-performance computing cluster.

# 3 Expressed regions-level

The expressed regions-level implementation is based on summarizing the coverage information for all your samples and applying a cutoff to that summary. For example, by calculating the mean coverage at every base and then checking if it’s greater than some cutoff value of interest. Contiguous bases passing the cutoff become a candidate Expressed Region (ER). We can then construct a matrix summarizing the base-level coverage for each sample for the set of ERs. This matrix can then be using with packages developed for feature counting (limma, DESeq2, edgeR, etc) to determine which ERs have differential expression signal. That is, to identify the Differentially Expressed Regions (DERs).

## 3.1 `regionMatrix()`

Commonly, users have aligned their raw RNA-seq data and saved the alignments in BAM files. Some might have chosen to compress this information into BigWig files. BigWig files are much faster to load than BAM files and are the type of file we prefer to work with. However, we can still identify the expressed regions from BAM files.

The function `regionMatrix()` will require you to load the data (either from BAM or BigWig files) and store it all in memory. It will then calculate the mean coverage across all samples, apply the cutoff you chose, and determine the expressed regions.

This is the path you will want to follow in most scenarios.

## 3.2 `railMatrix()`

Our favorite method for identifying expressed regions is based on pre-computed summary coverage files (mean or median) as well as coverage files by sample. Rail is a cloud-enabled aligner that will generate:

1. Per chromosome, a summary (mean or median) coverage BigWig file. Note that the summary is adjusted for library size and is by default set to libraries with 40 million reads.
2. Per sample, a coverage BigWig file with the un-adjusted coverage.

Rail does a great job in creating these files for us, saving time and reducing the memory load needed for this type of analysis with `R`.

If you have this type of data or can generate it from BAM files with other tools, you will be interested in using the `railMatrix()` function. The output is identical to the one from `regionMatrix()`. It’s just much faster and memory efficient. The only drawback is that BigWig files are not fully supported in Windows as of rtracklayer version 1.25.16.

We highly recommend this approach. Rail has also other significant features such as: scalability, reduced redundancy, integrative analysis, mode agnosticism, and inexpensive cloud implementation. For more information, visit rail.bio.

# 4 Single base-level F-statistics

The DER Finder approach was originally implemented by calculating t-statistics between two groups and using a hidden markov model to determine the expression states: not expressed, expressed, differentially expressed (Frazee, Sabunciyan, Hansen, et al., 2014). The original software works but had areas where we worked to improve it, which lead to the single base-level F-statistics implementation. Also note that the original software is no longer maintained.

This type of analysis first loads the data and preprocess it in a format that saves time and reduces memory later. It then fits two nested models (an alternative and a null model) with the coverage information for every single base-pair of the genome. Using the two fitted models, it calculates an F-statistic. Basically, it generates a vector along the genome with F-statistics.

A cutoff is then applied to the F-statistics and contiguous base-pairs of the genome passing the cutoff are considered a candidate Differentially Expressed Region (DER).

Calculating F-statistics along the genome is computationally intensive, but doable. The major resource drain comes from assigning p-values to the DERs. To do so, we permute the model matrices and re-calculate the F-statistics generating a set of null DERs. Once we have enough null DERs, we compare the observed DERs against the null DERs to calculate p-values for the observed DERs.

This type of analysis at the chromosome level is done by the `analyzeChr()` function, which is a high level function using many other pieces of derfinder. Once all chromosomes have been processed, `mergeResults()` combines them.

Which implementation of the DER Finder approach you will want to use depends on your specific use case and computational resources available. But in general, we recommend starting with the expressed regions-level implementation.

# 5 Example data

In this vignette we we will analyze a small subset of the samples from the BrainSpan Atlas of the Human Brain (BrainSpan, 2011) publicly available data.

We first load the required packages.

    ## Load libraries
    library("derfinder")
    library("derfinderData")
    library("GenomicRanges")

## 5.1 Phenotype data

For this example, we created a small table with the relevant phenotype data for 12 samples: 6 from fetal samples and 6 from adult samples. We chose at random a brain region, in this case the amygdaloid complex. For this example we will only look at data from chromosome 21. Other variables include the age in years and the gender. The data is shown below.

    library("knitr")
    ## Get pheno table
    pheno <- subset(brainspanPheno, structure_acronym == "AMY")

    ## Display the main information
    p <- pheno[, -which(colnames(pheno) %in% c(
        "structure_acronym",
        "structure_name", "file"
    ))]
    rownames(p) <- NULL
    kable(p, format = "html", row.names = TRUE)

| gender | lab | Age | group
--- | --- | --- | --- | ---
1 | F | HSB97.AMY | -0.4423077 | fetal
2 | M | HSB92.AMY | -0.3653846 | fetal
3 | M | HSB178.AMY | -0.4615385 | fetal
4 | M | HSB159.AMY | -0.3076923 | fetal
5 | F | HSB153.AMY | -0.5384615 | fetal
6 | F | HSB113.AMY | -0.5384615 | fetal
7 | F | HSB130.AMY | 21.0000000 | adult
8 | M | HSB136.AMY | 23.0000000 | adult
9 | F | HSB126.AMY | 30.0000000 | adult
10 | M | HSB145.AMY | 36.0000000 | adult
11 | M | HSB123.AMY | 37.0000000 | adult
12 | F | HSB135.AMY | 40.0000000 | adult

## 5.2 Load the data

derfinder offers three functions related to loading raw data. The first one, `rawFiles()`, is a helper function for identifying the full paths to the input files. Next, `loadCoverage()` loads the base-level coverage data from either BAM or BigWig files for a specific chromosome. Finally, `fullCoverage()` will load the coverage for a set of chromosomes using `loadCoverage()`.

We can load the data from derfinderData (Collado-Torres, Jaffe, and Leek, 2021) by first identifying the paths to the BigWig files with `rawFiles()` and then loading the data with `fullCoverage()`. Note that the BrainSpan data is already normalized by the total number of mapped reads in each sample. However, that won’t be the case with most data sets in which case you might want to use the `totalMapped` and `targetSize` arguments. The function `getTotalMapped()` will be helpful to get this information.

    ## Determine the files to use and fix the names
    files <- rawFiles(system.file("extdata", "AMY", package = "derfinderData"),
        samplepatt = "bw", fileterm = NULL
    )
    names(files) <- gsub(".bw", "", names(files))

    ## Load the data from disk
    system.time(fullCov <- fullCoverage(
        files = files, chrs = "chr21",
        totalMapped = rep(1, length(files)), targetSize = 1
    ))

Alternatively, since the BigWig files are publicly available from BrainSpan (see here), we can extract the relevant coverage data using `fullCoverage()`. Note that as of rtracklayer 1.25.16 BigWig files are not supported on Windows: you can find the `fullCov` object inside derfinderData to follow the examples.

    ## Determine the files to use and fix the names
    files <- pheno$file
    names(files) <- gsub(".AMY", "", pheno$lab)

    ## Load the data from the web
    system.time(fullCov <- fullCoverage(
        files = files, chrs = "chr21",
        totalMapped = rep(1, length(files)), targetSize = 1
    ))

Note how loading the coverage for 12 samples from the web was quite fast. Although in this case we only retained the information for chromosome 21.

The result of `fullCov` is a list with one element per chromosome. If no filtering was performed, each chromosome has a `DataFrame` with the number of rows equaling the number of bases in the chromosome with one column per sample.

    ## Lets explore it
    fullCov

    ## $chr21
    ## DataFrame with 48129895 rows and 12 columns
    ##          HSB97 HSB92 HSB178 HSB159 HSB153 HSB113 HSB130 HSB136 HSB126 HSB145 HSB123 HSB135
    ##          <Rle> <Rle>  <Rle>  <Rle>  <Rle>  <Rle>  <Rle>  <Rle>  <Rle>  <Rle>  <Rle>  <Rle>
    ## 1            0     0      0      0      0      0      0      0      0      0      0      0
    ## 2            0     0      0      0      0      0      0      0      0      0      0      0
    ## 3            0     0      0      0      0      0      0      0      0      0      0      0
    ## 4            0     0      0      0      0      0      0      0      0      0      0      0
    ## 5            0     0      0      0      0      0      0      0      0      0      0      0
    ## ...        ...   ...    ...    ...    ...    ...    ...    ...    ...    ...    ...    ...
    ## 48129891     0     0      0      0      0      0      0      0      0      0      0      0
    ## 48129892     0     0      0      0      0      0      0      0      0      0      0      0
    ## 48129893     0     0      0      0      0      0      0      0      0      0      0      0
    ## 48129894     0     0      0      0      0      0      0      0      0      0      0      0
    ## 48129895     0     0      0      0      0      0      0      0      0      0      0      0

If filtering was performed, each chromosome also has a logical `Rle` indicating which bases of the chromosome passed the filtering. This information is useful later on to map back the results to the genome coordinates.

## 5.3 Filter coverage

Depending on the use case, you might want to filter the base-level coverage at the time of reading it, or you might want to keep an unfiltered version. By default both `loadCoverage()` and `fullCoverage()` will not filter.

If you decide to filter, set the `cutoff` argument to a positive value. This will run `filterData()`. Note that you might want to standardize the library sizes prior to filtering if you didn’t already do it when creating the `fullCov` object. You can do so by by supplying the `totalMapped` and `targetSize` arguments to `filterData()`. Note: don’t use these arguments twice in `fullCoverage()` and `filterData()`.

In this example, we prefer to keep both an unfiltered and filtered version. For the filtered version, we will retain the bases where at least one sample has coverage greater than 2.

    ## Filter coverage
    filteredCov <- lapply(fullCov, filterData, cutoff = 2)

    ## 2022-04-26 18:22:16 filterData: originally there were 48129895 rows, now there are 130356 rows. Meaning that 99.73 percent was filtered.

The result is similar to `fullCov` but with the genomic position index as shown below.

    ## Similar to fullCov but with $position
    filteredCov

    ## $chr21
    ## $chr21$coverage
    ## DataFrame with 130356 rows and 12 columns
    ##                   HSB97              HSB92             HSB178            HSB159            HSB153           HSB113
    ##                   <Rle>              <Rle>              <Rle>             <Rle>             <Rle>            <Rle>
    ## 1      1.58000004291534 0.0700000002980232 0.0500000007450581 0.150000005960464 0.589999973773956 2.00999999046326
    ## 2      1.58000004291534 0.0700000002980232 0.0500000007450581 0.150000005960464 0.629999995231628 2.17000007629395
    ## 3      1.61000001430511  0.100000001490116 0.0500000007450581 0.150000005960464 0.670000016689301 2.21000003814697
    ## 4      1.64999997615814  0.129999995231628 0.0500000007450581 0.150000005960464 0.709999978542328 2.36999988555908
    ## 5      1.67999994754791  0.129999995231628  0.100000001490116              0.25              0.75 2.36999988555908
    ## ...                 ...                ...                ...               ...               ...              ...
    ## 130352 1.50999999046326   2.23000001907349    2.0699999332428  2.46000003814697  2.21000003814697             1.25
    ## 130353 1.50999999046326   2.23000001907349    2.0699999332428  2.46000003814697  2.21000003814697 1.21000003814697
    ## 130354 1.47000002861023   2.13000011444092   2.10999989509583  2.21000003814697  2.00999999046326 1.21000003814697
    ## 130355 1.47000002861023   2.13000011444092   2.10999989509583  2.10999989509583  2.00999999046326 1.16999995708466
    ## 130356 1.47000002861023   2.05999994277954   1.77999997138977  1.96000003814697  1.92999994754791 1.16999995708466
    ##                    HSB130            HSB136             HSB126            HSB145           HSB123            HSB135
    ##                     <Rle>             <Rle>              <Rle>             <Rle>            <Rle>             <Rle>
    ## 1      0.0399999991059303 0.129999995231628                  0                 0                0 0.230000004172325
    ## 2      0.0399999991059303 0.129999995231628                  0                 0                0 0.230000004172325
    ## 3      0.0399999991059303 0.129999995231628                  0                 0                0 0.230000004172325
    ## 4      0.0399999991059303 0.129999995231628                  0                 0                0 0.230000004172325
    ## 5      0.0399999991059303 0.129999995231628 0.0599999986588955                 0                0 0.230000004172325
    ## ...                   ...               ...                ...               ...              ...               ...
    ## 130352  0.790000021457672  1.37000000476837   2.04999995231628  1.02999997138977 1.27999997138977  1.62999999523163
    ## 130353  0.790000021457672  1.37000000476837   2.04999995231628  1.02999997138977 1.24000000953674  1.62999999523163
    ## 130354  0.790000021457672  1.27999997138977   1.92999994754791 0.730000019073486 1.20000004768372  1.62999999523163
    ## 130355  0.790000021457672  1.27999997138977   1.92999994754791 0.600000023841858 1.20000004768372  1.62999999523163
    ## 130356  0.790000021457672  1.01999998092651   1.87000000476837 0.560000002384186  1.0900000333786  1.54999995231628
    ##
    ## $chr21$position
    ## logical-Rle of length 48129895 with 3235 runs
    ##   Lengths: 9825448     149       2       9       2       2       6 ...     137    1446     172     740     598   45091
    ##   Values :   FALSE    TRUE   FALSE    TRUE   FALSE    TRUE   FALSE ...    TRUE   FALSE    TRUE   FALSE    TRUE   FALSE

In terms of memory, the filtered version requires less resources. Although this will depend on how rich the data set is and how aggressive was the filtering step.

    ## Compare the size in Mb
    round(c(
        fullCov = object.size(fullCov),
        filteredCov = object.size(filteredCov)
    ) / 1024^2, 1)

    ##     fullCov filteredCov
    ##        22.7         8.5

Note that with your own data, filtering for bases where at least one sample has coverage greater than 2 might not make sense: maybe you need a higher or lower filter. The amount of bases remaining after filtering will impact how long the analysis will take to complete. We thus recommend exploring this before proceeding.

# 6 Expressed region-level analysis

## 6.1 Via `regionMatrix()`

Now that we have the data, we can identify expressed regions (ERs) by using a cutoff of 30 on the base-level mean coverage from these 12 samples. Once the regions have been identified, we can calculate a coverage matrix with one row per ER and one column per sample (12 in this case). For doing this calculation we need to know the length of the sequence reads, which in this study were 76 bp long.

Note that for this type of analysis there is no major benefit of filtering the data. Although it can be done if needed.

    ## Use regionMatrix()
    system.time(regionMat <- regionMatrix(fullCov, cutoff = 30, L = 76))

    ## By using totalMapped equal to targetSize, regionMatrix() assumes that you have normalized the data already in fullCoverage(), loadCoverage() or filterData().

    ## 2022-04-26 18:22:17 regionMatrix: processing chr21

    ## 2022-04-26 18:22:17 filterData: normalizing coverage

    ## 2022-04-26 18:22:18 filterData: done normalizing coverage

    ## 2022-04-26 18:22:20 filterData: originally there were 48129895 rows, now there are 2256 rows. Meaning that 100 percent was filtered.

    ## 2022-04-26 18:22:20 findRegions: identifying potential segments

    ## 2022-04-26 18:22:20 findRegions: segmenting information

    ## 2022-04-26 18:22:20 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:20 findRegions: identifying region clusters

    ## 2022-04-26 18:22:20 getRegionCoverage: processing chr21

    ## 2022-04-26 18:22:20 getRegionCoverage: done processing chr21

    ## 2022-04-26 18:22:20 regionMatrix: calculating coverageMatrix

    ## 2022-04-26 18:22:20 regionMatrix: adjusting coverageMatrix for 'L'

    ##    user  system elapsed
    ##    2.67    0.13    2.79

    ## Explore results
    class(regionMat)

    ## [1] "list"

    names(regionMat$chr21)

    ## [1] "regions"        "coverageMatrix" "bpCoverage"

`regionMatrix()` returns a list of elements of length equal to the number of chromosomes analyzed. For each chromosome, there are three pieces of output. The actual ERs are arranged in a `GRanges` object named `regions`.

- regions is the result from filtering with `filterData()` and then defining the regions with `findRegions()`. Note that the metadata variable `value` represents the mean coverage for the given region while `area` is the sum of the base-level coverage (before adjusting for read length) from all samples.
- bpCoverage is a list with the base-level coverage from all the regions. This information can then be used with `plotRegionCoverage()` from derfinderPlot.
- coverageMatrix is the matrix with one row per region and one column per sample. The different matrices for each of the chromosomes can then be merged prior to using limma, DESeq2 or other packages. Note that the counts are generally not integers, but can easily be rounded if necessary.

    ## regions output
    regionMat$chr21$regions

    ## GRanges object with 45 ranges and 6 metadata columns:
    ##      seqnames            ranges strand |     value      area indexStart  indexEnd cluster clusterL
    ##         <Rle>         <IRanges>  <Rle> | <numeric> <numeric>  <integer> <integer>   <Rle>    <Rle>
    ##    1    chr21   9827018-9827582      * |  313.6717 177224.53          1       565       1      565
    ##    2    chr21 15457301-15457438      * |  215.0846  29681.68        566       703       2      138
    ##    3    chr21 20230140-20230192      * |   38.8325   2058.12        704       756       3      366
    ##    4    chr21 20230445-20230505      * |   41.3245   2520.80        757       817       3      366
    ##    5    chr21 27253318-27253543      * |   34.9131   7890.37        818      1043       4      765
    ##   ..      ...               ...    ... .       ...       ...        ...       ...     ...      ...
    ##   41    chr21 33039644-33039688      * |   34.4705 1551.1742       2180      2224      17       45
    ##   42    chr21 33040784-33040798      * |   32.1342  482.0133       2225      2239      18      118
    ##   43    chr21          33040890      * |   30.0925   30.0925       2240      2240      18      118
    ##   44    chr21 33040900-33040901      * |   30.1208   60.2417       2241      2242      18      118
    ##   45    chr21 48019401-48019414      * |   31.1489  436.0850       2243      2256      19       14
    ##   -------
    ##   seqinfo: 1 sequence from an unspecified genome

    ## Number of regions
    length(regionMat$chr21$regions)

    ## [1] 45

`bpCoverage` is the base-level coverage list which can then be used for plotting.

    ## Base-level coverage matrices for each of the regions
    ## Useful for plotting
    lapply(regionMat$chr21$bpCoverage[1:2], head, n = 2)

    ## $`1`
    ##   HSB97 HSB92 HSB178 HSB159 HSB153 HSB113 HSB130 HSB136 HSB126 HSB145 HSB123 HSB135
    ## 1 36.54 47.40  15.71   3.52  16.71  93.20   5.62  98.34  28.22   5.88   3.32 185.17
    ## 2 51.42 65.04  29.35   5.83  30.53 124.76  11.32 199.28  63.68  10.39   7.25 374.85
    ##
    ## $`2`
    ##     HSB97 HSB92 HSB178 HSB159 HSB153 HSB113 HSB130 HSB136 HSB126 HSB145 HSB123 HSB135
    ## 566 22.21 13.95   23.2   4.97  38.61  45.59  34.75 104.21  15.92  19.87   7.94 141.61
    ## 567 22.21 13.95   23.2   4.97  38.65  45.59  35.15 104.30  15.92  19.87   7.94 141.64

    ## Check dimensions. First region is 565 long, second one is 138 bp long.
    ## The columns match the number of samples (12 in this case).
    lapply(regionMat$chr21$bpCoverage[1:2], dim)

    ## $`1`
    ## [1] 565  12
    ##
    ## $`2`
    ## [1] 138  12

The end result of the coverage matrix is shown below. Note that the coverage has been adjusted for read length. Because reads might not fully align inside a given region, the numbers are generally not integers but can be rounded if needed.

    ## Dimensions of the coverage matrix
    dim(regionMat$chr21$coverageMatrix)

    ## [1] 45 12

    ## Coverage for each region. This matrix can then be used with limma or other pkgs
    head(regionMat$chr21$coverageMatrix)

    ##          HSB97       HSB92      HSB178     HSB159       HSB153       HSB113      HSB130      HSB136      HSB126
    ## 1 1325.9622371 1168.519079 1407.288552 297.939342 1461.2986829 3653.1093346 1106.722895 5570.221054 1397.068687
    ## 2  200.7834228  127.543553  193.695657  67.940131  313.8513139  333.3740816  267.354342 1162.313418  463.909476
    ## 3   20.4623685   23.758816   33.127368  28.145395   52.8756585   35.3828948   23.483947   17.168947   30.725394
    ## 4   28.2011836   29.546183   33.576974  31.244343   51.6146040   42.3398681   24.724736   19.309606   41.094474
    ## 5   35.5428946  100.085790   97.151316  78.069605   36.3046051   77.7402631  171.861974   93.503158  115.059342
    ## 6    0.3956579    1.136447    1.139079   1.000132    0.4221053    0.7988158    2.231053    1.007895    1.473421
    ##        HSB145     HSB123      HSB135
    ## 1 1330.158818 277.072106 8987.460401
    ## 2  257.114210  99.987237 1198.713552
    ## 3   22.895921  20.153553   16.786842
    ## 4   33.802632  29.931579   32.634080
    ## 5   90.950526 168.939342  180.638684
    ## 6    1.171316   1.770263    1.697368

We can then use the coverage matrix and packages such as limma, DESeq2 or edgeR to identify which ERs are differentially expressed.

### 6.1.1 Find DERs with DESeq2

Here we’ll use DESeq2 to identify the DERs. To use it we need to round the coverage data.

    ## Required
    library("DESeq2")

    ## Round matrix
    counts <- round(regionMat$chr21$coverageMatrix)

    ## Round matrix and specify design
    dse <- DESeqDataSetFromMatrix(counts, pheno, ~ group + gender)

    ## converting counts to integer mode

    ## Perform DE analysis
    dse <- DESeq(dse, test = "LRT", reduced = ~gender, fitType = "local")

    ## estimating size factors

    ## estimating dispersions

    ## gene-wise dispersion estimates

    ## mean-dispersion relationship

    ## final dispersion estimates

    ## fitting model and testing

    ## Extract results
    deseq <- regionMat$chr21$regions
    mcols(deseq) <- c(mcols(deseq), results(dse))

    ## Explore the results
    deseq

    ## GRanges object with 45 ranges and 12 metadata columns:
    ##      seqnames            ranges strand |     value      area indexStart  indexEnd cluster clusterL  baseMean
    ##         <Rle>         <IRanges>  <Rle> | <numeric> <numeric>  <integer> <integer>   <Rle>    <Rle> <numeric>
    ##    1    chr21   9827018-9827582      * |  313.6717 177224.53          1       565       1      565 2846.2872
    ##    2    chr21 15457301-15457438      * |  215.0846  29681.68        566       703       2      138  451.5196
    ##    3    chr21 20230140-20230192      * |   38.8325   2058.12        704       756       3      366   29.5781
    ##    4    chr21 20230445-20230505      * |   41.3245   2520.80        757       817       3      366   36.0603
    ##    5    chr21 27253318-27253543      * |   34.9131   7890.37        818      1043       4      765  101.6468
    ##   ..      ...               ...    ... .       ...       ...        ...       ...     ...      ...       ...
    ##   41    chr21 33039644-33039688      * |   34.4705 1551.1742       2180      2224      17       45 20.782035
    ##   42    chr21 33040784-33040798      * |   32.1342  482.0133       2225      2239      18      118  6.410542
    ##   43    chr21          33040890      * |   30.0925   30.0925       2240      2240      18      118  0.129717
    ##   44    chr21 33040900-33040901      * |   30.1208   60.2417       2241      2242      18      118  0.702291
    ##   45    chr21 48019401-48019414      * |   31.1489  436.0850       2243      2256      19       14  5.293293
    ##      log2FoldChange     lfcSE      stat      pvalue       padj
    ##           <numeric> <numeric> <numeric>   <numeric>  <numeric>
    ##    1     -1.3012037  0.900114   1.18752 2.75831e-01 1.00000000
    ##    2     -1.0635132  0.787523   2.66981 1.02268e-01 0.92041575
    ##    3     -0.5364640  0.307665  16.32623 5.33207e-05 0.00119972
    ##    4     -0.6256137  0.294302   8.96934 2.74547e-03 0.04118210
    ##    5     -0.0887821  0.344721   2.15124 1.42455e-01 0.94756226
    ##   ..            ...       ...       ...         ...        ...
    ##   41      -0.654517  0.326476  1.201039 2.73114e-01 1.0000e+00
    ##   42      -0.570137  0.475008  0.454718 5.00103e-01 1.0000e+00
    ##   43      -0.745914  3.116540 -0.033322 1.00000e+00 1.0000e+00
    ##   44      -0.646216  3.045577  0.260501 6.09776e-01 1.0000e+00
    ##   45      -0.320977  0.744647 29.167078 6.63979e-08 2.9879e-06
    ##   -------
    ##   seqinfo: 1 sequence from an unspecified genome

You can get similar results using edgeR using these functions: `DGEList()`, `calcNormFactors()`, `estimateGLMRobustDisp()`, `glmFit()`, and `glmLRT()`.

### 6.1.2 Find DERs with limma

Alternatively, we can find DERs using limma. Here we’ll exemplify a type of test closer to what we’ll do later with the F-statistics approach. First of all, we need to define our models.

    ## Build models
    mod <- model.matrix(~ pheno$group + pheno$gender)
    mod0 <- model.matrix(~ pheno$gender)

Next, we’ll transform the coverage information using the same default transformation from `analyzeChr()`.

    ## Transform coverage
    transformedCov <- log2(regionMat$chr21$coverageMatrix + 32)

We can then fit the models and get the F-statistic p-values and control the FDR.

    ## Example using limma
    library("limma")

    ##
    ## Attaching package: 'limma'

    ## The following object is masked from 'package:DESeq2':
    ##
    ##     plotMA

    ## The following object is masked from 'package:BiocGenerics':
    ##
    ##     plotMA

    ## Run limma
    fit <- lmFit(transformedCov, mod)
    fit0 <- lmFit(transformedCov, mod0)

    ## Determine DE status for the regions
    ## Also in https://github.com/LieberInstitute/jaffelab with help and examples
    getF <- function(fit, fit0, theData) {
        rss1 <- rowSums((fitted(fit) - theData)^2)
        df1 <- ncol(fit$coef)
        rss0 <- rowSums((fitted(fit0) - theData)^2)
        df0 <- ncol(fit0$coef)
        fstat <- ((rss0 - rss1) / (df1 - df0)) / (rss1 / (ncol(theData) - df1))
        f_pval <- pf(fstat, df1 - df0, ncol(theData) - df1, lower.tail = FALSE)
        fout <- cbind(fstat, df1 - 1, ncol(theData) - df1, f_pval)
        colnames(fout)[2:3] <- c("df1", "df0")
        fout <- data.frame(fout)
        return(fout)
    }

    ff <- getF(fit, fit0, transformedCov)

    ## Get the p-value and assign it to the regions
    limma <- regionMat$chr21$regions
    limma$fstat <- ff$fstat
    limma$pvalue <- ff$f_pval
    limma$padj <- p.adjust(ff$f_pval, "BH")

    ## Explore the results
    limma

    ## GRanges object with 45 ranges and 9 metadata columns:
    ##      seqnames            ranges strand |     value      area indexStart  indexEnd cluster clusterL     fstat
    ##         <Rle>         <IRanges>  <Rle> | <numeric> <numeric>  <integer> <integer>   <Rle>    <Rle> <numeric>
    ##    1    chr21   9827018-9827582      * |  313.6717 177224.53          1       565       1      565  0.377595
    ##    2    chr21 15457301-15457438      * |  215.0846  29681.68        566       703       2      138  3.557623
    ##    3    chr21 20230140-20230192      * |   38.8325   2058.12        704       756       3      366  4.570732
    ##    4    chr21 20230445-20230505      * |   41.3245   2520.80        757       817       3      366  1.709795
    ##    5    chr21 27253318-27253543      * |   34.9131   7890.37        818      1043       4      765  9.171222
    ##   ..      ...               ...    ... .       ...       ...        ...       ...     ...      ...       ...
    ##   41    chr21 33039644-33039688      * |   34.4705 1551.1742       2180      2224      17       45  17.13101
    ##   42    chr21 33040784-33040798      * |   32.1342  482.0133       2225      2239      18      118  19.69010
    ##   43    chr21          33040890      * |   30.0925   30.0925       2240      2240      18      118   4.77673
    ##   44    chr21 33040900-33040901      * |   30.1208   60.2417       2241      2242      18      118   4.82554
    ##   45    chr21 48019401-48019414      * |   31.1489  436.0850       2243      2256      19       14  60.94954
    ##           pvalue       padj
    ##        <numeric>  <numeric>
    ##    1   0.5541079  0.5798803
    ##    2   0.0918972  0.2067688
    ##    3   0.0612273  0.1530682
    ##    4   0.2234259  0.2957107
    ##    5   0.0142836  0.0565776
    ##   ..         ...        ...
    ##   41 2.52554e-03 0.03788308
    ##   42 1.62972e-03 0.03666877
    ##   43 5.66576e-02 0.15306825
    ##   44 5.56383e-02 0.15306825
    ##   45 2.68886e-05 0.00120999
    ##   -------
    ##   seqinfo: 1 sequence from an unspecified genome

In this simple example, none of the ERs have strong differential expression signal when adjusting for an FDR of 5%.

    table(limma$padj < 0.05, deseq$padj < 0.05)

    ##
    ##         FALSE TRUE
    ##   FALSE    40    2
    ##   TRUE      2    1

## 6.2 Via `railMatrix()`

If you have Rail output, you can get the same results faster than with `regionMatrix()`. Rail will create the summarized coverage BigWig file for you, but we are not including it in this package due to its size. So, lets create it.

    ## Calculate the mean: this step takes a long time with many samples
    meanCov <- Reduce("+", fullCov$chr21) / ncol(fullCov$chr21)

    ## Save it on a bigwig file called meanChr21.bw
    createBw(list("chr21" = DataFrame("meanChr21" = meanCov)),
        keepGR =
            FALSE
    )

Now that we have the files Rail creates for us, we can use `railMatrix()`.

    ## Identify files to use
    summaryFile <- "meanChr21.bw"
    ## We had already found the sample BigWig files and saved it in the object 'files'
    ## Lets just rename it to sampleFiles for clarity.
    sampleFiles <- files

    ## Get the regions
    system.time(
        regionMat.rail <- railMatrix(
            chrs = "chr21", summaryFiles = summaryFile,
            sampleFiles = sampleFiles, L = 76, cutoff = 30, maxClusterGap = 3000L
        )
    )

When you take into account the time needed to load the data (`fullCoverage()`) and then creating the matrix (`regionMatrix()`), `railMatrix()` is faster and less memory intensive.

The objects are not identical due to small rounding errors, but it’s nothing to worry about.

    ## Overall not identical due to small rounding errors
    identical(regionMat, regionMat.rail)

    ## Actual regions are the same
    identical(ranges(regionMat$chr21$regions), ranges(regionMat.rail$chr21$regions))

    ## When you round, the small differences go away
    identical(
        round(regionMat$chr21$regions$value, 4),
        round(regionMat.rail$chr21$regions$value, 4)
    )

    identical(
        round(regionMat$chr21$regions$area, 4),
        round(regionMat.rail$chr21$regions$area, 4)
    )

# 7 Single base-level F-statistics analysis

One form of base-level differential expression analysis implemented in derfinder is to calculate F-statistics for every base and use them to define candidate differentially expressed regions. This type of analysis is further explained in this section.

## 7.1 Models

Once we have the base-level coverage data for all 12 samples, we can construct the models. In this case, we want to find differences between fetal and adult samples while adjusting for gender and a proxy of the library size.

We can use `sampleDepth()` and it’s helper function `collapseFullCoverage()` to get a proxy of the library size. Note that you would normally use the unfiltered data from all the chromosomes in this step and not just one.

    ## Get some idea of the library sizes
    sampleDepths <- sampleDepth(collapseFullCoverage(fullCov), 1)

    ## 2022-04-26 18:22:24 sampleDepth: Calculating sample quantiles

    ## 2022-04-26 18:22:24 sampleDepth: Calculating sample adjustments

    sampleDepths

    ##  HSB97.100%  HSB92.100% HSB178.100% HSB159.100% HSB153.100% HSB113.100% HSB130.100% HSB136.100% HSB126.100% HSB145.100%
    ##    19.47733    19.55904    19.44252    19.24186    19.41285    19.82106    19.52017    19.97758    19.53045    19.49827
    ## HSB123.100% HSB135.100%
    ##    19.40505    20.33392

`sampleDepth()` is similar to `calcNormFactors()` from metagenomeSeq with some code underneath tailored for the type of data we are using. `collapseFullCoverage()` is only needed to deal with the size of the data.

We can then define the nested models we want to use using `makeModels()`. This is a helper function that assumes that you will always adjust for the library size. You then need to define the variable to test, in this case we are comparing fetal vs adult samples. Optionally, you can adjust for other sample covariates, such as the gender in this case.

    ## Define models
    models <- makeModels(sampleDepths,
        testvars = pheno$group,
        adjustvars = pheno[, c("gender")]
    )

    ## Explore the models
    lapply(models, head)

    ## $mod
    ##   (Intercept) testvarsadult sampleDepths adjustVar1M
    ## 1           1             0     19.47733           0
    ## 2           1             0     19.55904           1
    ## 3           1             0     19.44252           1
    ## 4           1             0     19.24186           1
    ## 5           1             0     19.41285           0
    ## 6           1             0     19.82106           0
    ##
    ## $mod0
    ##   (Intercept) sampleDepths adjustVar1M
    ## 1           1     19.47733           0
    ## 2           1     19.55904           1
    ## 3           1     19.44252           1
    ## 4           1     19.24186           1
    ## 5           1     19.41285           0
    ## 6           1     19.82106           0

Note how the null model (`mod0`) is nested in the alternative model (`mod`). Use the same models for all your chromosomes unless you have a specific reason to use chromosome-specific models. Note that derfinder is very flexible and works with any type of nested model.

## 7.2 Find candidate DERs

Next, we can find candidate differentially expressed regions (DERs) using as input the segments of the genome where at least one sample has coverage greater than 2. That is, the filtered coverage version we created previously.

The main function in derfinder for this type of analysis is `analyzeChr()`. It works at a chromosome level and runs behinds the scenes several other derfinder functions. To use it, you have to provide the models, the grouping information, how to calculate the F-statistic cutoff and most importantly, the number of permutations.

By default `analyzeChr()` will use a theoretical cutoff. In this example, we use the cutoff that would correspond to a p-value of 0.05. To assign p-values to the candidate DERs, derfinder permutes the rows of the model matrices, re-calculates the F-statistics and identifies null regions. Then it compares the area of the observed regions versus the areas from the null regions to assign an empirical p-value.

In this example we will use twenty permutations, although in a real case scenario you might consider a larger number of permutations.

In real scenario, you might consider saving the results from all the chromosomes in a given directory. Here we will use analysisResults. For each chromosome you analyze, a new directory with the chromosome-specific data will be created. So in this case, we will have analysisResults/chr21.

    ## Create a analysis directory
    dir.create("analysisResults")
    originalWd <- getwd()
    setwd(file.path(originalWd, "analysisResults"))

    ## Perform differential expression analysis
    system.time(results <- analyzeChr(
        chr = "chr21", filteredCov$chr21, models,
        groupInfo = pheno$group, writeOutput = TRUE, cutoffFstat = 5e-02,
        nPermute = 20, seeds = 20140923 + seq_len(20), returnOutput = TRUE
    ))

    ## 2022-04-26 18:22:25 analyzeChr: Pre-processing the coverage data

    ## 2022-04-26 18:22:28 analyzeChr: Calculating statistics

    ## 2022-04-26 18:22:28 calculateStats: calculating the F-statistics

    ## 2022-04-26 18:22:29 analyzeChr: Calculating pvalues

    ## 2022-04-26 18:22:29 analyzeChr: Using the following theoretical cutoff for the F-statistics 5.31765507157871

    ## 2022-04-26 18:22:29 calculatePvalues: identifying data segments

    ## 2022-04-26 18:22:29 findRegions: segmenting information

    ## 2022-04-26 18:22:29 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:29 findRegions: identifying region clusters

    ## 2022-04-26 18:22:30 calculatePvalues: calculating F-statistics for permutation 1 and seed 20140924

    ## 2022-04-26 18:22:30 findRegions: segmenting information

    ## 2022-04-26 18:22:30 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:30 calculatePvalues: calculating F-statistics for permutation 2 and seed 20140925

    ## 2022-04-26 18:22:30 findRegions: segmenting information

    ## 2022-04-26 18:22:30 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:30 calculatePvalues: calculating F-statistics for permutation 3 and seed 20140926

    ## 2022-04-26 18:22:31 findRegions: segmenting information

    ## 2022-04-26 18:22:32 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:32 calculatePvalues: calculating F-statistics for permutation 4 and seed 20140927

    ## 2022-04-26 18:22:32 findRegions: segmenting information

    ## 2022-04-26 18:22:32 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:32 calculatePvalues: calculating F-statistics for permutation 5 and seed 20140928

    ## 2022-04-26 18:22:32 findRegions: segmenting information

    ## 2022-04-26 18:22:33 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:33 calculatePvalues: calculating F-statistics for permutation 6 and seed 20140929

    ## 2022-04-26 18:22:33 findRegions: segmenting information

    ## 2022-04-26 18:22:33 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:33 calculatePvalues: calculating F-statistics for permutation 7 and seed 20140930

    ## 2022-04-26 18:22:33 findRegions: segmenting information

    ## 2022-04-26 18:22:33 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:33 calculatePvalues: calculating F-statistics for permutation 8 and seed 20140931

    ## 2022-04-26 18:22:33 findRegions: segmenting information

    ## 2022-04-26 18:22:34 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:34 calculatePvalues: calculating F-statistics for permutation 9 and seed 20140932

    ## 2022-04-26 18:22:34 findRegions: segmenting information

    ## 2022-04-26 18:22:34 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:34 calculatePvalues: calculating F-statistics for permutation 10 and seed 20140933

    ## 2022-04-26 18:22:34 findRegions: segmenting information

    ## 2022-04-26 18:22:34 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:34 calculatePvalues: calculating F-statistics for permutation 11 and seed 20140934

    ## 2022-04-26 18:22:35 findRegions: segmenting information

    ## 2022-04-26 18:22:35 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:35 calculatePvalues: calculating F-statistics for permutation 12 and seed 20140935

    ## 2022-04-26 18:22:35 findRegions: segmenting information

    ## 2022-04-26 18:22:35 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:35 calculatePvalues: calculating F-statistics for permutation 13 and seed 20140936

    ## 2022-04-26 18:22:35 findRegions: segmenting information

    ## 2022-04-26 18:22:35 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:35 calculatePvalues: calculating F-statistics for permutation 14 and seed 20140937

    ## 2022-04-26 18:22:36 findRegions: segmenting information

    ## 2022-04-26 18:22:36 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:36 calculatePvalues: calculating F-statistics for permutation 15 and seed 20140938

    ## 2022-04-26 18:22:36 findRegions: segmenting information

    ## 2022-04-26 18:22:36 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:36 calculatePvalues: calculating F-statistics for permutation 16 and seed 20140939

    ## 2022-04-26 18:22:36 findRegions: segmenting information

    ## 2022-04-26 18:22:36 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:36 calculatePvalues: calculating F-statistics for permutation 17 and seed 20140940

    ## 2022-04-26 18:22:36 findRegions: segmenting information

    ## 2022-04-26 18:22:37 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:37 calculatePvalues: calculating F-statistics for permutation 18 and seed 20140941

    ## 2022-04-26 18:22:37 findRegions: segmenting information

    ## 2022-04-26 18:22:37 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:37 calculatePvalues: calculating F-statistics for permutation 19 and seed 20140942

    ## 2022-04-26 18:22:37 findRegions: segmenting information

    ## 2022-04-26 18:22:37 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:37 calculatePvalues: calculating F-statistics for permutation 20 and seed 20140943

    ## 2022-04-26 18:22:37 findRegions: segmenting information

    ## 2022-04-26 18:22:38 findRegions: identifying candidate regions

    ## 2022-04-26 18:22:38 calculatePvalues: calculating the p-values

    ## 2022-04-26 18:22:38 analyzeChr: Annotating regions

    ## No annotationPackage supplied. Trying org.Hs.eg.db.

    ## Getting TSS and TSE.

    ## Getting CSS and CSE.

    ## Getting exons.

    ## Annotating genes.

    ## ...................

    ##    user  system elapsed
    ##  149.15    1.89  152.92

To speed up `analyzeChr()`, you might need to use several cores via the `mc.cores` argument. If memory is limiting, you might want to use a smaller `chunksize` (default is 5 million). Note that if you use too many cores, you might hit the input/output ceiling of your data network and/or hard drives speed.

Before running with a large number of permutations we recommend exploring how long each permutation cycle takes using a single permutation.

Note that analyzing each chromosome with a large number of permutations and a rich data set can take several hours, so we recommend running one job running `analyzeChr()` per chromosome, and then merging the results via `mergeResults()`. This process is further described in the advanced derfinder vignette.

## 7.3 Explore results

When using `returnOutput = TRUE`, `analyzeChr()` will return a list with the results to explore interactively. However, by default it writes the results to disk (one .Rdata file per result).

The following code explores the results.

    ## Explore
    names(results)

    ## [1] "timeinfo"     "optionsStats" "coveragePrep" "fstats"       "regions"      "annotation"

### 7.3.1 optionStats

`optionStats` stores the main options used in the `analyzeChr()` call including the models used, the type of cutoff, number of permutations, seeds for the permutations. All this information can be useful to reproduce the analysis.

    ## Explore optionsStats
    names(results$optionsStats)

    ##  [1] "models"          "cutoffPre"       "scalefac"        "chunksize"       "cutoffFstat"     "cutoffType"
    ##  [7] "nPermute"        "seeds"           "groupInfo"       "lowMemDir"       "analyzeCall"     "cutoffFstatUsed"
    ## [13] "smooth"          "smoothFunction"  "weights"         "returnOutput"

    ## Call used
    results$optionsStats$analyzeCall

    ## analyzeChr(chr = "chr21", coverageInfo = filteredCov$chr21, models = models,
    ##     cutoffFstat = 0.05, nPermute = 20, seeds = 20140923 + seq_len(20),
    ##     groupInfo = pheno$group, writeOutput = TRUE, returnOutput = TRUE)

### 7.3.2 coveragePrep

`coveragePrep` has the result from the `preprocessCoverage()` step. This includes the genomic position index, the mean coverage (after scaling and the log2 transformation) for all the samples, and the group mean coverages. By default, the chunks are written to disk in `optionsStats$lowMemDir` (chr21/chunksDir in this example) to help reduce the required memory resources. Otherwise it is stored in `coveragePrep$coverageProcessed`.

    ## Explore coveragePrep
    names(results$coveragePrep)

    ## [1] "coverageProcessed" "mclapplyIndex"     "position"          "meanCoverage"      "groupMeans"

    ## Group means
    results$coveragePrep$groupMeans

    ## $fetal
    ## numeric-Rle of length 130356 with 117984 runs
    ##   Lengths:        1        1        1        1        1        1 ...        1        1        1        1        1
    ##   Values : 0.741667 0.775000 0.798333 0.843333 0.880000 0.905000 ...  1.95500  1.94833  1.85667  1.83333  1.72833
    ##
    ## $adult
    ## numeric-Rle of length 130356 with 111765 runs
    ##   Lengths:         4         3         2         1         3 ...         1         1         1         1         1
    ##   Values : 0.0666667 0.0766667 0.0883333 0.1016667 0.1083333 ...   1.35833   1.35167   1.26000   1.23833   1.14667

### 7.3.3 fstats

The F-statistics are then stored in `fstats`. These are calculated using `calculateStats()`.

    ## Explore optionsStats
    results$fstats

    ## numeric-Rle of length 130356 with 126807 runs
    ##   Lengths:        1        1        1        1        1        1 ...        1        1        1        1        1
    ##   Values :  6.08556  6.07332  6.32563  6.39835  6.93078  7.20798 ... 3.500944 3.386907 4.095984 3.854257 4.071159

    ## Note that the length matches the number of bases used
    identical(length(results$fstats), sum(results$coveragePrep$position))

    ## [1] TRUE

### 7.3.4 regions

The candidate DERs and summary results from the permutations is then stored in `regions`. This is the output from `calculatePvalues()` which uses several underneath other functions including `calculateStats()` and `findRegions()`.

    ## Explore regions
    names(results$regions)

    ## [1] "regions"         "nullStats"       "nullWidths"      "nullPermutation"

For the null regions, the summary information is composed of the mean F-statistic for the null regions (`regions$nullStats`), the width of the null regions (`regions$nullWidths`), and the permutation number under which they were identified (`regions$nullPermutation`).

    ## Permutation summary information
    results$regions[2:4]

    ## $nullStats
    ## numeric-Rle of length 8868 with 8868 runs
    ##   Lengths:        1        1        1        1        1        1 ...        1        1        1        1        1
    ##   Values :  5.36984  5.90286  5.57047  6.02700  5.60038  5.40844 ...  6.29638  5.51568  7.25627  7.98296  7.22226
    ##
    ## $nullWidths
    ## integer-Rle of length 8868 with 7806 runs
    ##   Lengths:   1   1   1   1   1   1   1   1   1   1   1   1   1 ...   1   1   1   3   1   1   1   1   1   1   1   1   1
    ##   Values :   1  15   4  15  10   1  28   3  82   9   1   2   1 ...   3  16  26   1  22   5  16   8  24   2   7   2   4
    ##
    ## $nullPermutation
    ## integer-Rle of length 8868 with 20 runs
    ##   Lengths:  574  416  518 1160  606  176  644  242  262  178  308  236  114  752  648  798  460  324  158  294
    ##   Values :    1    2    3    4    5    6    7    8    9   10   11   12   13   14   15   16   17   18   19   20

The most important part of the output is the `GRanges` object with the candidate DERs shown below.

    ## Candidate DERs
    results$regions$regions

    ## GRanges object with 1912 ranges and 14 metadata columns:
    ##      seqnames            ranges strand |     value      area indexStart  indexEnd cluster clusterL meanCoverage
    ##         <Rle>         <IRanges>  <Rle> | <numeric> <numeric>  <integer> <integer>   <Rle>    <Rle>    <numeric>
    ##   up    chr21 48018861-48019420      * |   84.8778   47531.6     126383    126942     451      712     18.70725
    ##   up    chr21 40196060-40196788      * |   46.5093   33905.3      76025     76753     258     2186      1.33441
    ##   up    chr21 37444744-37445435      * |   45.8921   31757.3      62161     62852     214      692      3.82074
    ##   up    chr21 34001753-34003041      * |   21.8377   28148.7      32434     33722     126     2728      1.48913
    ##   up    chr21 45180666-45182147      * |   15.9280   23605.2      96597     98078     339     6589      3.11942
    ##   ..      ...               ...    ... .       ...       ...        ...       ...     ...      ...          ...
    ##   up    chr21          38525436      * |   5.31976   5.31976      65147     65147     228      301      2.74667
    ##   up    chr21          44473957      * |   5.31911   5.31911      88214     88214     310      677      1.56917
    ##   up    chr21          15753814      * |   5.31806   5.31806       4949      4949      10       17      2.06083
    ##   up    chr21          38525534      * |   5.31802   5.31802      65245     65245     228      301      2.00833
    ##   up    chr21          19161933      * |   5.31796   5.31796      11541     11541      29      306      0.65000
    ##      meanfetal meanadult log2FoldChangeadultvsfetal     pvalues significant    qvalues significantQval
    ##      <numeric> <numeric>                  <numeric>   <numeric>    <factor>  <numeric>        <factor>
    ##   up  1.002571  36.41193                    5.18263 0.000112752        TRUE 0.00589007            TRUE
    ##   up  0.331216   2.33759                    2.81918 0.000112752        TRUE 0.00589007            TRUE
    ##   up  1.498923   6.14255                    2.03491 0.000112752        TRUE 0.00589007            TRUE
    ##   up  0.654785   2.32347                    1.82719 0.000112752        TRUE 0.00589007            TRUE
    ##   up  1.755188   4.48366                    1.35305 0.000112752        TRUE 0.00589007            TRUE
    ##   ..       ...       ...                        ...         ...         ...        ...             ...
    ##   up  3.968333  1.525000                  -1.379724    0.997068       FALSE   0.682467           FALSE
    ##   up  2.233333  0.905000                  -1.303209    0.997970       FALSE   0.682727           FALSE
    ##   up  3.325000  0.796667                  -2.061306    0.999549       FALSE   0.682734           FALSE
    ##   up  3.015000  1.001667                  -1.589756    0.999549       FALSE   0.682734           FALSE
    ##   up  0.461667  0.838333                   0.860672    0.999549       FALSE   0.682734           FALSE
    ##   -------
    ##   seqinfo: 1 sequence from an unspecified genome; no seqlengths

The metadata columns are:

- value is the mean F-statistics for the candidate DER.
- area is the sum of the F-statistics for the candidate DER.
- indexStart Relates the genomic start coordinate with the filtered genomic index start coordinate.
- indexEnd Similarly as above but for the end coordinates.
- cluster The cluster id to which this candidate DER belongs to.
- clusterL The length of the cluster to which this candidate DER belongs to.
- meanCoverage The base level mean coverage for the candidate DER.
- meanfetal In this example, the mean coverage for the fetal samples.
- meanadult In this example, the mean coverage for the adult samples.
- log2FoldChangeadultvsfetal In this example, the log2 fold change between adult vs fetal samples.
- pvalues The p-value for the candidate DER.
- significant By default, whether the p-value is less than 0.05 or not.
- qvalues The q-value for the candidate DER calculated with qvalue.
- significantQval By default, whether the q-value is less than 0.10 or not.

Note that for this type of analysis you might want to try a few coverage cutoffs and/or F-statistic cutoffs. One quick way to evaluate the results is to compare the width of the regions.

    ## Width of potential DERs
    summary(width(results$regions$regions))

    ##    Min. 1st Qu.  Median    Mean 3rd Qu.    Max.
    ##    1.00    1.00    5.00   31.49   25.00 1482.00

    sum(width(results$regions$regions) > 50)

    ## [1] 342

    ## Width of candidate DERs
    sig <- as.logical(results$regions$regions$significant)
    summary(width(results$regions$regions[sig]))

    ##    Min. 1st Qu.  Median    Mean 3rd Qu.    Max.
    ##     7.0    73.5    95.0   139.0   137.0  1482.0

    sum(width(results$regions$regions[sig]) > 50)

    ## [1] 307

### 7.3.5 Nearest annotation

`analyzeChr()` will find the nearest annotation feature using `matchGenes()` from bumphunter (version >= 1.7.3). This information is useful considering that the candidate DERs were identified without relying on annotation. Yet at the end, we are interested to check if they are inside a known exon, upstream a gene, etc.

    ## Nearest annotation
    head(results$annotation)

    ##    name
    ## 1 S100B
    ## 2  ETS2
    ## 3  CBR1
    ## 4 SYNJ1
    ## 5  PDXK
    ## 6 OLIG1
    ##                                                                                                                                                                                                                                                                                                                                                                                                            annotation
    ## 1                                                                                                                                                                                                                                                                                                                                                                       NM_006272 NP_006263 XM_017028424 XP_016883913
    ## 2                                                                                                                                                                                                                                                                                                                   NM_001256295 NM_005239 NP_001243224 NP_005230 XM_005260935 XM_017028290 XP_005260992 XP_016883779
    ## 3                                                                                                                                                                                                                                                                                                                                                                       NM_001286789 NM_001757 NP_001273718 NP_001748
    ## 4 NM_001160302 NM_001160306 NM_003895 NM_203446 NP_001153774 NP_001153778 NP_003886 NP_982271 XM_017028494 XM_017028495 XM_017028496 XM_017028497 XM_017028498 XM_017028499 XM_017028500 XM_017028501 XM_017028502 XM_017028503 XM_017028504 XM_017028505 XP_016883983 XP_016883984 XP_016883985 XP_016883986 XP_016883987 XP_016883988 XP_016883989 XP_016883990 XP_016883991 XP_016883992 XP_016883993 XP_016883994
    ## 5                                                                                                                   NM_001331030 NM_003681 NM_021941 NP_001317959 NP_003672 XM_005261195 XM_005261196 XM_005261199 XM_011529758 XM_011529760 XM_011529761 XM_011529762 XM_017028483 XM_017028484 XP_005261252 XP_005261253 XP_005261256 XP_011528060 XP_011528062 XP_011528063 XP_011528064 XP_016883972 XP_016883973
    ## 6                                                                                                                                                                                                                                                                                                                                                                                                 NM_138983 NP_620450
    ##              description region distance              subregion insideDistance exonnumber nexons            UTR strand
    ## 1 overlaps exon upstream inside     5615 overlaps exon upstream              0          4      4 overlaps 3'UTR      -
    ## 2            inside exon inside    18305            inside exon              0         10     10          3'UTR      +
    ## 3            inside exon inside     2459            inside exon              0          3      3          3'UTR      +
    ## 4            inside exon inside    97310            inside exon              0         33     33          3'UTR      -
    ## 5            inside exon inside    41688            inside exon              0         10     10          3'UTR      +
    ## 6            inside exon inside      837            inside exon              0          1      1 overlaps 3'UTR      +
    ##   geneL codingL Geneid subjectHits
    ## 1  6504      NA   6285       51509
    ## 2 19123      NA   2114       17340
    ## 3  3179      NA    873       67646
    ## 4 99282      NA   8867       68102
    ## 5 43210      NA   8566       67104
    ## 6  2278      NA 116448        8622

For more details on the output please check the bumphunter package.

Check the section about non-human data (specifically, using annotation different from hg19) on the advanced vignette.

### 7.3.6 Time spent

The final piece is the wallclock time spent during each of the steps in `analyzeChr()`. You can then make a plot with this information as shown in Figure 1.

    ## Time spent
    results$timeinfo

    ##                      init                     setup                  prepData                  savePrep
    ## "2022-04-26 18:22:25 EDT" "2022-04-26 18:22:25 EDT" "2022-04-26 18:22:28 EDT" "2022-04-26 18:22:28 EDT"
    ##            calculateStats                 saveStats             saveStatsOpts          calculatePvalues
    ## "2022-04-26 18:22:29 EDT" "2022-04-26 18:22:29 EDT" "2022-04-26 18:22:29 EDT" "2022-04-26 18:22:38 EDT"
    ##                  saveRegs                  annotate                  saveAnno
    ## "2022-04-26 18:22:38 EDT" "2022-04-26 18:24:58 EDT" "2022-04-26 18:24:58 EDT"

    ## Use this information to make a plot
    timed <- diff(results$timeinfo)
    timed.df <- data.frame(Seconds = as.numeric(timed), Step = factor(names(timed),
        levels = rev(names(timed))
    ))
    library("ggplot2")
    ggplot(timed.df, aes(y = Step, x = Seconds)) +
        geom_point()

Figure 1: Seconds used to run each step in analyzeChr()

## 7.4 Merge results

Once you have analyzed each chromosome using `analyzeChr()`, you can use `mergeResults()` to merge the results. This function does not return an object in R but instead creates several Rdata files with the main results from the different chromosomes.

    ## Go back to the original directory
    setwd(originalWd)

    ## Merge results from several chromosomes. In this case we only have one.
    mergeResults(
        chrs = "chr21", prefix = "analysisResults",
        genomicState = genomicState$fullGenome,
        optionsStats = results$optionsStats
    )

    ## 2022-04-26 18:25:00 mergeResults: Saving options used

    ## 2022-04-26 18:25:00 Loading chromosome chr21

    ## 2022-04-26 18:25:00 mergeResults: calculating FWER

    ## 2022-04-26 18:25:00 mergeResults: Saving fullNullSummary

    ## 2022-04-26 18:25:00 mergeResults: Re-calculating the p-values

    ## 2022-04-26 18:25:00 mergeResults: Saving fullRegions

    ## 2022-04-26 18:25:00 mergeResults: assigning genomic states

    ## 2022-04-26 18:25:00 annotateRegions: counting

    ## 2022-04-26 18:25:00 annotateRegions: annotating

    ## 2022-04-26 18:25:00 mergeResults: Saving fullAnnotatedRegions

    ## 2022-04-26 18:25:00 mergeResults: Saving fullFstats

    ## 2022-04-26 18:25:00 mergeResults: Saving fullTime

    ## Files created by mergeResults()
    dir("analysisResults", pattern = ".Rdata")

    ## [1] "fullAnnotatedRegions.Rdata" "fullFstats.Rdata"           "fullNullSummary.Rdata"      "fullRegions.Rdata"
    ## [5] "fullTime.Rdata"             "optionsMerge.Rdata"

- fullFstats.Rdata contains a list with one element per chromosome. Per chromosome it has the F-statistics.
- fullNullSummary.Rdata is a list with the summary information from the null regions stored for each chromosome.
- fullTime.Rdata has the timing information for each chromosome as a list.

### 7.4.1 optionsMerge

For reproducibility purposes, the options used the merge the results are stored in `optionsMerge`.

    ## Options used to merge
    load(file.path("analysisResults", "optionsMerge.Rdata"))

    ## Contents
    names(optionsMerge)

    ## [1] "chrs"            "significantCut"  "minoverlap"      "mergeCall"       "cutoffFstatUsed" "optionsStats"

    ## Merge call
    optionsMerge$mergeCall

    ## mergeResults(chrs = "chr21", prefix = "analysisResults", genomicState = genomicState$fullGenome,
    ##     optionsStats = results$optionsStats)

### 7.4.2 fullRegions

The main result from `mergeResults()` is in `fullRegions`. This is a `GRanges` object with the candidate DERs from all the chromosomes. It also includes the nearest annotation metadata as well as FWER adjusted p-values (fwer) and whether the FWER adjusted p-value is less than 0.05 (significantFWER).

    ## Load all the regions
    load(file.path("analysisResults", "fullRegions.Rdata"))

    ## Metadata columns
    names(mcols(fullRegions))

    ##  [1] "value"                      "area"                       "indexStart"                 "indexEnd"
    ##  [5] "cluster"                    "clusterL"                   "meanCoverage"               "meanfetal"
    ##  [9] "meanadult"                  "log2FoldChangeadultvsfetal" "pvalues"                    "significant"
    ## [13] "qvalues"                    "significantQval"            "name"                       "annotation"
    ## [17] "description"                "region"                     "distance"                   "subregion"
    ## [21] "insideDistance"             "exonnumber"                 "nexons"                     "UTR"
    ## [25] "annoStrand"                 "geneL"                      "codingL"                    "Geneid"
    ## [29] "subjectHits"                "fwer"                       "significantFWER"

Note that `analyzeChr()` only has the information for a given chromosome at a time, so `mergeResults()` re-calculates the p-values and q-values using the information from all the chromosomes.

### 7.4.3 fullAnnotatedRegions

In preparation for visually exploring the results, `mergeResults()` will run `annotateRegions()` which counts how many known exons, introns and intergenic segments each candidate DER overlaps (by default with a minimum overlap of 20bp). `annotateRegions()` uses a summarized version of the genome annotation created with `makeGenomicState()`. For this example, we can use the data included in derfinder which is the summarized annotation of hg19 for chromosome 21.

    ## Load annotateRegions() output
    load(file.path("analysisResults", "fullAnnotatedRegions.Rdata"))

    ## Information stored
    names(fullAnnotatedRegions)

    ## [1] "countTable"     "annotationList"

    ## Take a peak
    lapply(fullAnnotatedRegions, head)

    ## $countTable
    ##   exon intergenic intron
    ## 1    1          0      0
    ## 2    1          0      0
    ## 3    1          0      1
    ## 4    1          0      0
    ## 5    1          0      0
    ## 6    1          0      0
    ##
    ## $annotationList
    ## GRangesList object of length 6:
    ## $`1`
    ## GRanges object with 1 range and 4 metadata columns:
    ##        seqnames            ranges strand |   theRegion         tx_id               tx_name          gene
    ##           <Rle>         <IRanges>  <Rle> | <character> <IntegerList>       <CharacterList> <IntegerList>
    ##   4986    chr21 48018531-48019416      - |        exon   73464,73465 uc002zju.1,uc002zjv.1           227
    ##   -------
    ##   seqinfo: 1 sequence from hg19 genome
    ##
    ## $`2`
    ## GRanges object with 1 range and 4 metadata columns:
    ##        seqnames            ranges strand |   theRegion         tx_id               tx_name          gene
    ##           <Rle>         <IRanges>  <Rle> | <character> <IntegerList>       <CharacterList> <IntegerList>
    ##   1189    chr21 40194598-40196878      + |        exon   72757,72758 uc002yxf.3,uc002yxg.4            77
    ##   -------
    ##   seqinfo: 1 sequence from hg19 genome
    ##
    ## $`3`
    ## GRanges object with 2 ranges and 4 metadata columns:
    ##        seqnames            ranges strand |   theRegion                 tx_id                              tx_name
    ##           <Rle>         <IRanges>  <Rle> | <character>         <IntegerList>                      <CharacterList>
    ##    834    chr21 37444113-37445464      + |        exon           72703,72704                uc002yvb.1,uc010gmy.1
    ##   3843    chr21 37442784-37447178      - |      intron 73230,73231,73233,... uc002yuu.3,uc002yux.2,uc002yuy.3,...
    ##                 gene
    ##        <IntegerList>
    ##    834           282
    ##   3843         4,206
    ##   -------
    ##   seqinfo: 1 sequence from hg19 genome
    ##
    ## ...
    ## <3 more elements>

# 8 ChIP-seq differential binding

As of version 1.5.27 derfinder has parameters that allow smoothing of the single base-level F-statistics before determining DERs. This allows finding differentially bounded regions (peaks) using ChIP-seq data. In general, ChIP-seq studies are smaller than RNA-seq studies which means that the single base-level F-statistics approach is well suited for differential binding analysis.

To smooth the F-statistics use `smooth = TRUE` in `analyzeChr()`. The default smoothing function is `bumphunter::locfitByCluster()` and all its parameters can be passed specified in the call to `analyzeChr()`. In particular, the `minNum` and `bpSpan` arguments are important. We recommend setting `minNum` to the minimum read length and `bpSpan` to the average peak length expected in the ChIP-seq data being analyzed. Smoothing the F-statistics will take longer but not use significantly more memory than the default behavior. So take this into account when choosing the number of permutations to run.

# 9 Visually explore results

Optionally, we can use the addon package derfinderPlot to visually explore the results.

To make the region level plots, we will need to extract the region level coverage data. We can do so using `getRegionCoverage()` as shown below.

    ## Find overlaps between regions and summarized genomic annotation
    annoRegs <- annotateRegions(fullRegions, genomicState$fullGenome)

    ## 2022-04-26 18:25:01 annotateRegions: counting

    ## 2022-04-26 18:25:01 annotateRegions: annotating

    ## Indeed, the result is the same because we only used chr21
    identical(annoRegs, fullAnnotatedRegions)

    ## [1] FALSE

    ## Get the region coverage
    regionCov <- getRegionCoverage(fullCov, fullRegions)

    ## 2022-04-26 18:25:01 getRegionCoverage: processing chr21

    ## 2022-04-26 18:25:01 getRegionCoverage: done processing chr21

    ## Explore the result
    head(regionCov[[1]])

    ##   HSB97 HSB92 HSB178 HSB159 HSB153 HSB113 HSB130 HSB136 HSB126 HSB145 HSB123 HSB135
    ## 1  0.10     0      0   0.05      0      0   0.39   1.10   0.54   1.24   1.60   2.24
    ## 2  0.10     0      0   0.10      0      0   0.50   1.15   0.60   1.24   1.68   2.58
    ## 3  0.10     0      0   0.10      0      0   0.54   1.10   0.54   1.24   1.64   2.69
    ## 4  0.10     0      0   0.10      0      0   0.57   1.10   0.48   1.29   1.75   2.73
    ## 5  0.14     0      0   0.10      0      0   0.61   1.10   0.48   1.29   1.82   2.73
    ## 6  0.14     0      0   0.10      0      0   0.64   1.02   0.48   1.29   1.75   2.73

With this, we are all set to visually explore the results.

    library("derfinderPlot")

    ## Overview of the candidate DERs in the genome
    plotOverview(
        regions = fullRegions, annotation = results$annotation,
        type = "fwer"
    )

    suppressPackageStartupMessages(library("TxDb.Hsapiens.UCSC.hg19.knownGene"))
    txdb <- TxDb.Hsapiens.UCSC.hg19.knownGene

    ## Base-levle coverage plots for the first 10 regions
    plotRegionCoverage(
        regions = fullRegions, regionCoverage = regionCov,
        groupInfo = pheno$group, nearestAnnotation = results$annotation,
        annotatedRegions = annoRegs, whichRegions = 1:10, txdb = txdb, scalefac = 1,
        ask = FALSE
    )

    ## Cluster plot for the first region
    plotCluster(
        idx = 1, regions = fullRegions, annotation = results$annotation,
        coverageInfo = fullCov$chr21, txdb = txdb, groupInfo = pheno$group,
        titleUse = "fwer"
    )

The quick start to using derfinder has example plots for the expressed regions-level approach. The vignette for derfinderPlot has even more examples.

# 10 Interactive HTML reports

We have also developed an addon package called regionReport available via Bioconductor.

The function `derfinderReport()` in regionReport basically takes advantage of the results from `mergeResults()` and plotting functions available in derfinderPlot as well as other neat features from knitrBootstrap. It then generates a customized report for single-base level F-statistics DER finding analyses.

For results from `regionMatrix()` or `railMatrix()` use `renderReport()` from regionReport. In both cases, the resulting HTML report promotes reproducibility of the analysis and allows you to explore in more detail the results through some diagnostic plots.

We think that these reports are very important when you are exploring the resulting DERs after changing a key parameter in `analyzeChr()`, `regionMatrix()` or `railMatrix()`.

Check out the vignette for regionReport for example reports generated with it.

# 11 Miscellaneous features

In this section we go over some other features of derfinder which can be useful for performing feature-counts based analyses, exploring the results, or exporting data.

## 11.1 Feature level analysis

Similar to the expressed region-level analysis, you might be interested in performing a feature-level analysis. More specifically, this means getting a count matrix at the exon-level (or gene-level). `coverageToExon()` allows you to get such a matrix by taking advantage of the summarized annotation produced by `makeGenomicState()`.

In this example, we use the genomic state included in the package which has the information for chr21 TxDb.Hsapiens.UCSC.hg19.knownGene annotation.

    ## Get the exon-level matrix
    system.time(exonCov <- coverageToExon(fullCov, genomicState$fullGenome, L = 76))

    ## class: SerialParam
    ##   bpisup: FALSE; bpnworkers: 1; bptasks: 0; bpjobname: BPJOB
    ##   bplog: FALSE; bpthreshold: INFO; bpstopOnError: TRUE
    ##   bpRNGseed: ; bptimeout: NA; bpprogressbar: FALSE
    ##   bpexportglobals: FALSE; bpexportvariables: FALSE; bpforceGC: FALSE; bpfallback: FALSE
    ##   bplogdir: NA
    ##   bpresultdir: NA
    ## class: SerialParam
    ##   bpisup: FALSE; bpnworkers: 1; bptasks: 0; bpjobname: BPJOB
    ##   bplog: FALSE; bpthreshold: INFO; bpstopOnError: TRUE
    ##   bpRNGseed: ; bptimeout: NA; bpprogressbar: FALSE
    ##   bpexportglobals: FALSE; bpexportvariables: FALSE; bpforceGC: FALSE; bpfallback: FALSE
    ##   bplogdir: NA
    ##   bpresultdir: NA

    ## 2022-04-26 18:25:09 coverageToExon: processing chromosome chr21

    ## class: SerialParam
    ##   bpisup: FALSE; bpnworkers: 1; bptasks: 0; bpjobname: BPJOB
    ##   bplog: FALSE; bpthreshold: INFO; bpstopOnError: TRUE
    ##   bpRNGseed: ; bptimeout: NA; bpprogressbar: FALSE
    ##   bpexportglobals: FALSE; bpexportvariables: FALSE; bpforceGC: FALSE; bpfallback: FALSE
    ##   bplogdir: NA
    ##   bpresultdir: NA

    ## 2022-04-26 18:25:12 coverageToExon: processing chromosome chr21

    ##    user  system elapsed
    ##    8.86    0.36    9.22

    ## Dimensions of the matrix
    dim(exonCov)

    ## [1] 2658   12

    ## Explore a little bit
    tail(exonCov)

    ##            HSB97       HSB92    HSB178      HSB159     HSB153    HSB113      HSB130       HSB136      HSB126
    ## 4983  0.44605264  0.03986842 0.1289474  0.04934211  0.1052632 0.1173684   0.0000000   0.03947368   0.0000000
    ## 4985 10.87723678  1.65184211 7.3119736  4.39013167 10.4906578 4.6542105   0.7798684   0.72986842   1.6034210
    ## 4986  6.23315790 11.40447366 4.9807895 10.64368415  4.5310526 7.1510526 152.1905258 263.63486853 252.4892106
    ## 4988  0.00000000  0.05644737 0.0000000  0.00000000  0.0000000 0.0000000   0.2639474   0.37657895   0.7223684
    ## 4990  1.96131579  3.98013159 0.9542105  2.67486840  1.2284210 2.3064474  35.5769737  76.96736838  69.6584212
    ## 4992  0.07473684  0.66907895 0.2601316  0.73039474  0.2402632 0.1652632   2.4193421  14.41013157   9.7538158
    ##            HSB145      HSB123       HSB135
    ## 4983 5.263158e-03   0.1382895   0.07894737
    ## 4985 9.964474e-01   1.4557895   1.29592103
    ## 4986 2.345414e+02 291.0205261 439.69500020
    ## 4988 6.156579e-01   0.7063158   0.48657895
    ## 4990 5.978842e+01  64.9423686 101.76394746
    ## 4992 5.325658e+00   8.1834211  10.08618420

With this matrix, rounded if necessary, you can proceed to use packages such as limma, DESeq2, edgeR among others.

## 11.2 Compare results visually

We can certainly make region-level plots using `plotRegionCoverage()` or cluster plots using `plotCluster()` or overview plots using `plotOveview()`, all from derfinderPlot.

First we need to get the relevant annotation information.

    ## Annotate regions as exonic, intronic or intergenic
    system.time(annoGenome <- annotateRegions(
        regionMat$chr21$regions,
        genomicState$fullGenome
    ))

    ## 2022-04-26 18:25:14 annotateRegions: counting

    ## 2022-04-26 18:25:14 annotateRegions: annotating

    ##    user  system elapsed
    ##    0.31    0.00    0.31

    ## Note that the genomicState object included in derfinder only has information
    ## for chr21 (hg19).

    ## Identify closest genes to regions
    suppressPackageStartupMessages(library("bumphunter"))
    suppressPackageStartupMessages(library("TxDb.Hsapiens.UCSC.hg19.knownGene"))
    txdb <- TxDb.Hsapiens.UCSC.hg19.knownGene
    genes <- annotateTranscripts(txdb)

    ## No annotationPackage supplied. Trying org.Hs.eg.db.

    ## Getting TSS and TSE.

    ## Getting CSS and CSE.

    ## Getting exons.

    ## Annotating genes.

    system.time(annoNear <- matchGenes(regionMat$chr21$regions, genes))

    ##    user  system elapsed
    ##    2.83    0.00    2.83

Now we can proceed to use derfinderPlot to make the region-level plots for the top 100 regions.

    ## Identify the top regions by highest total coverage
    top <- order(regionMat$chr21$regions$area, decreasing = TRUE)[1:100]

    ## Base-level plots for the top 100 regions with transcript information
    library("derfinderPlot")
    plotRegionCoverage(regionMat$chr21$regions,
        regionCoverage = regionMat$chr21$bpCoverage,
        groupInfo = pheno$group, nearestAnnotation = annoNear,
        annotatedRegions = annoGenome, whichRegions = top, scalefac = 1,
        txdb = txdb, ask = FALSE
    )

However, we can alternatively use epivizr to view the candidate DERs and the region matrix results in a genome browser.

    ## Load epivizr, it's available from Bioconductor
    library("epivizr")

    ## Load data to your browser
    mgr <- startEpiviz()
    ders_dev <- mgr$addDevice(
        fullRegions[as.logical(fullRegions$significantFWER)], "Candidate DERs"
    )
    ders_potential_dev <- mgr$addDevice(
        fullRegions[!as.logical(fullRegions$significantFWER)], "Potential DERs"
    )
    regs_dev <- mgr$addDevice(regionMat$chr21$regions, "Region Matrix")

    ## Go to a place you like in the genome
    mgr$navigate(
        "chr21", start(regionMat$chr21$regions[top[1]]) - 100,
        end(regionMat$chr21$regions[top[1]]) + 100
    )

    ## Stop the navigation
    mgr$stopServer()

## 11.3 Export coverage to BigWig files

derfinder also includes `createBw()` with related functions `createBwSample()` and `coerceGR()` to export the output of `fullCoverage()` to BigWig files. These functions can be useful in the case where you start with BAM files and later on want to save the coverage data into BigWig files, which are generally smaller.

    ## Subset only the first sample
    fullCovSmall <- lapply(fullCov, "[", 1)

    ## Export to BigWig
    bw <- createBw(fullCovSmall)

    ## See the file. Note that the sample name is used to name the file.
    dir(pattern = ".bw")

    ## Internally createBw() coerces each sample to a GRanges object before
    ## exporting to a BigWig file. If more than one sample was exported, the
    ## GRangesList would have more elements.
    bw

# 12 Advanced arguments

If you are interested in using advanced arguments in derfinder, they are described in the manual pages of each function. Some of the most common advanced arguments are:

- `chrsStyle` (default is `UCSC`)
- `verbose` (by default `TRUE`).

`verbose` controls whether to print status updates for nearly all the functions. `chrsStyle` is used to determine the chromosome naming style and is powered by GenomeInfoDb. Note that `chrsStyle` is used in any of the functions that call `extendedMapSeqlevels()`. If you are working with a different organism than Homo sapiens set the global `species` option using `options(species = 'your species')` with the syntax used in `names(GenomeInfoDb::genomeStyles())`. If you want to disable `extendedMapSeqlevels()` set `chrsStyle` to `NULL`, which can be useful if your organism is not part of GenomeInfoDb.

The third commonly used advanced argument is `mc.cores`. It controls the number of cores to use for the functions that can run with more than one core to speed up. In nearly all the cases, the maximum number of cores depends on the number of chromosomes. One notable exception is `analyzeChr()` where the maximum number of cores depends on the `chunksize` used and the dimensions of the data for the chromosome under study.

Note that using the `...` argument allows you to specify some of the documented arguments. For example, you might want to control the `maxClusterGap` from `findRegions()` in the `analyzeChr()` call.

# 13 Non-human data

If you are working with data from an organism that is not Homo sapiens, then set the global options defining the `species` and the `chrsStyle` used. For example, if you are working with Arabidopsis Thaliana and the NCBI naming style, then set the options using the following code:

    ## Set global species and chrsStyle options
    options(species = "arabidopsis_thaliana")
    options(chrsStyle = "NCBI")

    ## Then proceed to load and analyze the data

Internally derfinder uses `extendedMapSeqlevels()` to use the appropriate chromosome naming style given a species in all functions involving chromosome names.

Further note that the argument `txdb` from `analyzeChr()` is passed to `bumphunter::annotateTranscripts(txdb)`. So if you are using a genome different from hg19 remember to provide the appropriate annotation data or simply use `analyzeChr(runAnnotation = FALSE)`.

So, in the Arabidopsis Thaliana example, your `analyzeChr()` call would look like this:

    ## Load transcript database information
    library("TxDb.Athaliana.BioMart.plantsmart28")

    ## Set organism options
    options(species = "arabidopsis_thaliana")
    options(chrsStyle = "NCBI")

    ## Run command with more arguments
    analyzeChr(txdb = TxDb.Athaliana.BioMart.plantsmart28)

You might find the discussion Using bumphunter with non-human genomes useful.

# 14 Functions that use multiple cores

Currently, the following functions can use multiple cores, several of which are called inside `analyzeChr()`.

- `calculatePvalues()`: 1 core per chunk of data to process.
- `calculateStats()`: 1 core per chunk of data to process.
- `coerceGR()`: 1 core per chromosome. This function is used by `createBw()`.
- `coverageToExon()`: 1 core per strand, then 1 core per chromosome.
- `loadCoverage()`: up to 1 core per tile when loading the data with GenomicFiles. Otherwise, no parallelization is used.
- `fullCoverage()`: 1 core per chromosome. In general, try to avoid using more than 10 cores as you might reach your maximum network speed and/or hard disk input/output seed. For the case described in `loadCoverage()`, you can specify how many cores to use per chromosome for the tiles using the `mc.cores.load` argument effectively resulting in `mc.cores` times `mc.cores.load` used (otherwise it’s `mc.cores` squared).
- `getRegionCoverage()`: 1 core per chromosome.
- `regionMatrix()`: 1 core per chromosome.
- `railMatrix()`: 1 core per chromosome.

All parallel operations use `SnowParam()` from BiocParallel when more than 1 core is being used. Otherwise, `SerialParam()` is used. Note that if you prefer to specify other types of parallelization you can do so by specifying the `BPPARAM.custom` advanced argument.

Because `SnowParam()` requires `R` to load the necessary packages on each worker, the key function `fstats.apply()` was isolated in the derfinderHelper package. This package has much faster loading speeds than derfinder which greatly impacts performance on cases where the actual step of calculating the F-statistics is fast.

You may prefer to use `MulticoreParam()` described in the BiocParallel vignette. In that case, when using these functions use `BPPARAM.custom = MulticoreParam(workers = x)` where `x` is the number of cores you want to use. Note that in some systems, as is the case of the cluster used by derfinder’s developers, the system tools for assessing memory usage can be misleading, thus resulting in much higher memory loads when using `MulticoreParam()` instead of the default `SnowParam()`.

# 15 Loading data details

## 15.1 Controlling loading from BAM files

If you are loading data from BAM files, you might want to specify some criteria to decide which reads to include or not. For example, your data might have been generated by a strand-specific protocol. You can do so by specifying the arguments of `scanBamFlag()` from Rsamtools.

You can also control whether to include or exclude bases with `CIGAR` string `D` (deletion from the reference) by setting the advanced argument `drop.D = TRUE` in your `fullCoverage()` or `loadCoverage()` call.

## 15.2 Unfiltered base-level coverage

Note that in most scenarios, the `fullCov` object illustrated in the introductory vignette can be large in memory. When making plots or calculating the region-level coverage, we don’t need the full information. In such situations, it might pay off to create a smaller version by loading only the required data. This can be achieved using the advanced argument `which` to `fullCoverage()` or `loadCoverage()`.

However, it is important to consider that when reading the data from BAM files, a read might align partially inside the region of interest. By default such a read would be discarded and thus the base-level coverage would be lower than what it is in reality. The advanced argument `protectWhich` extends regions by 30 kbp (15 kbp each side) to help mitigate this issue.

We can illustrate this issue with the example data from derfinder. First, we load in the data and generate some regions of interest.

    ## Find some regions to work with
    example("loadCoverage", "derfinder")

    ##
    ## ldCvrg> datadir <- system.file("extdata", "genomeData", package = "derfinder")
    ##
    ## ldCvrg> files <- rawFiles(
    ## ldCvrg+     datadir = datadir, samplepatt = "*accepted_hits.bam$",
    ## ldCvrg+     fileterm = NULL
    ## ldCvrg+ )
    ##
    ## ldCvrg> ## Shorten the column names
    ## ldCvrg> names(files) <- gsub("_accepted_hits.bam", "", names(files))
    ##
    ## ldCvrg> ## Read and filter the data, only for 2 files
    ## ldCvrg> dataSmall <- loadCoverage(files = files[1:2], chr = "21", cutoff = 0)

    ## 2022-04-26 18:25:37 loadCoverage: finding chromosome lengths

    ## 2022-04-26 18:25:37 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009101_accepted_hits.bam

    ## 2022-04-26 18:25:37 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009102_accepted_hits.bam

    ## 2022-04-26 18:25:37 loadCoverage: applying the cutoff to the merged data

    ## 2022-04-26 18:25:37 filterData: originally there were 48129895 rows, now there are 454 rows. Meaning that 100 percent was filtered.

    ##
    ## ldCvrg> ## Not run:
    ## ldCvrg> ##D ## Export to BigWig files
    ## ldCvrg> ##D createBw(list("chr21" = dataSmall))
    ## ldCvrg> ##D
    ## ldCvrg> ##D ## Load data from BigWig files
    ## ldCvrg> ##D dataSmall.bw <- loadCoverage(c(
    ## ldCvrg> ##D     ERR009101 = "ERR009101.bw", ERR009102 =
    ## ldCvrg> ##D         "ERR009102.bw"
    ## ldCvrg> ##D ), chr = "chr21")
    ## ldCvrg> ##D
    ## ldCvrg> ##D ## Compare them
    ## ldCvrg> ##D mapply(function(x, y) {
    ## ldCvrg> ##D     x - y
    ## ldCvrg> ##D }, dataSmall$coverage, dataSmall.bw$coverage)
    ## ldCvrg> ##D
    ## ldCvrg> ##D ## Note that the only difference is the type of Rle (integer vs numeric) used
    ## ldCvrg> ##D ## to store the data.
    ## ldCvrg> ## End(Not run)
    ## ldCvrg>
    ## ldCvrg>
    ## ldCvrg>
    ## ldCvrg>

    example("getRegionCoverage", "derfinder")

    ##
    ## gtRgnC> ## Obtain fullCov object
    ## gtRgnC> fullCov <- list("21" = genomeDataRaw$coverage)
    ##
    ## gtRgnC> ## Assign chr lengths using hg19 information, use only first two regions
    ## gtRgnC> library("GenomicRanges")
    ##
    ## gtRgnC> regions <- genomeRegions$regions[1:2]
    ##
    ## gtRgnC> seqlengths(regions) <- seqlengths(getChromInfoFromUCSC("hg19",
    ## gtRgnC+     as.Seqinfo = TRUE
    ## gtRgnC+ ))[
    ## gtRgnC+     mapSeqlevels(names(seqlengths(regions)), "UCSC")
    ## gtRgnC+ ]
    ##
    ## gtRgnC> ## Finally, get the region coverage
    ## gtRgnC> regionCov <- getRegionCoverage(fullCov = fullCov, regions = regions)

    ## extendedMapSeqlevels: sequence names mapped from NCBI to UCSC for species homo_sapiens

    ## 2022-04-26 18:25:38 getRegionCoverage: processing chr21

    ## 2022-04-26 18:25:38 getRegionCoverage: done processing chr21

Next, we load the coverage again using `which` but without any padding. We can see how the coverage is not the same by looking at the maximum coverage for each sample.

    ## Illustrate reading data from a set of regions
    test <- loadCoverage(
        files = files, chr = "21", cutoff = NULL, which = regions,
        protectWhich = 0, fileStyle = "NCBI"
    )

    ## extendedMapSeqlevels: sequence names mapped from UCSC to NCBI for species homo_sapiens

    ## 2022-04-26 18:25:38 loadCoverage: finding chromosome lengths

    ## 2022-04-26 18:25:38 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009101_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009102_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009105_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009107_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009108_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009112_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009115_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009116_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009131_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009138_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009144_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009145_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009148_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009151_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009152_accepted_hits.bam

    ## 2022-04-26 18:25:39 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009153_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009159_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009161_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009163_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009164_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009167_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031812_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031835_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031867_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031868_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031900_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031904_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031914_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031936_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031958_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031960_accepted_hits.bam

    ## 2022-04-26 18:25:40 loadCoverage: applying the cutoff to the merged data

    ## 2022-04-26 18:25:41 filterData: originally there were 48129895 rows, now there are 48129895 rows. Meaning that 0 percent was filtered.

    ## Some reads were ignored and thus the coverage is lower as can be seen below:
    sapply(test$coverage, max) - sapply(genomeDataRaw$coverage, max)

    ## ERR009101 ERR009102 ERR009105 ERR009107 ERR009108 ERR009112 ERR009115 ERR009116 ERR009131 ERR009138 ERR009144 ERR009145
    ##         0         0         0         0        -1         0        -1        -2        -2        -2        -1        -1
    ## ERR009148 ERR009151 ERR009152 ERR009153 ERR009159 ERR009161 ERR009163 ERR009164 ERR009167 SRR031812 SRR031835 SRR031867
    ##        -3        -3         0        -3        -3        -3        -1        -3        -3         0        -1         0
    ## SRR031868 SRR031900 SRR031904 SRR031914 SRR031936 SRR031958 SRR031960
    ##         0         0        -1         0         0         0         0

When we re-load the data using some padding to the regions, we find that the coverage matches at all the bases.

    ## Illustrate reading data from a set of regions

    test2 <- loadCoverage(
        files = files, chr = "21", cutoff = NULL,
        which = regions, protectWhich = 3e4, fileStyle = "NCBI"
    )

    ## extendedMapSeqlevels: sequence names mapped from UCSC to NCBI for species homo_sapiens

    ## 2022-04-26 18:25:41 loadCoverage: finding chromosome lengths

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009101_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009102_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009105_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009107_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009108_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009112_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009115_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009116_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009131_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009138_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009144_accepted_hits.bam

    ## 2022-04-26 18:25:41 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009145_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009148_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009151_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009152_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009153_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009159_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009161_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009163_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009164_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/ERR009167_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031812_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031835_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031867_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031868_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031900_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031904_accepted_hits.bam

    ## 2022-04-26 18:25:42 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031914_accepted_hits.bam

    ## 2022-04-26 18:25:43 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031936_accepted_hits.bam

    ## 2022-04-26 18:25:43 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031958_accepted_hits.bam

    ## 2022-04-26 18:25:43 loadCoverage: loading BAM file F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08/derfinder/extdata/genomeData/SRR031960_accepted_hits.bam

    ## 2022-04-26 18:25:43 loadCoverage: applying the cutoff to the merged data

    ## 2022-04-26 18:25:43 filterData: originally there were 48129895 rows, now there are 48129895 rows. Meaning that 0 percent was filtered.

    ## Adding some padding to the regions helps get the same coverage
    identical(sapply(test2$coverage, max), sapply(genomeDataRaw$coverage, max))

    ## [1] TRUE

    ## A more detailed test reveals that the coverage matches at every base
    all(mapply(function(x, y) {
        identical(x, y)
    }, test2$coverage, genomeDataRaw$coverage))

    ## [1] TRUE

How much padding you need to use will depend on your specific data set, and you might be comfortable getting approximately the same coverage values for the sake of greatly reducing the memory resources needed.

## 15.3 Input files in a different naming style

If you are under the case where you like to use a specific chromosome naming style but the raw data files use another one, you might need to use the `fileStyle` argument.

For example, you could be working with Homo sapiens data and your preferred naming style is UCSC (chr1, chr2, …, chrX, chrY) but the raw data uses NCBI style names (1, 2, …, X, Y). In that case, use `fullCoverage(fileStyle = 'NCBI')` or `loadCoverage(fileStyle = 'NCBI')` depending if you are loading one chromosome or multiple at a time.

## 15.4 Loading data in chunks

If you prefer to do so, `fullCoverage()` and `loadCoverage()` can load the data of a chromosome in chunks using GenomicFiles. This is controlled by whether you specify the `tilewidth` argument.

Notice that you might run into slight coverage errors near the borders of the tiles for the same reason that was illustrated previously when loading specific regions.

This approach is not necessarily more efficient and can be significantly time consuming if you use a small `tilewidth`.

## 15.5 Large number of samples

If you have a large number of samples (say thousands), it might be best to submit cluster jobs that run `loadCoverage()` or `fullCoverage()` for only one chromosome at a time.

In the case of working with Rail output, you can either use `railMatrix()` with the argument `file.cores` greater than 1 or specify the advanced argument `BPPARAM.railChr` to control the parallel environment used for loading the BigWig files. Doing so, you can then submit cluster jobs that run `railMatrix()` for one chromosome at a time, yet read in the data fast. You can do all of from R by using `BPPARAM.custom` and `BPPARAM.railChr` at the same time where you use a `BatchJobsParam()` for the first one.

Another option when working with Rail output is to simply load the summary BigWig data (mean, median), then define the ERs using `findRegions()` and write them to a BED file. You can then use bwtool to create the coverage matrix.

# 16 Flow charts

## 16.1 DER analysis flow chart

Figure 2 illustrates how most of derfinder’s functions interact when performing a base-level differential expression analysis by calculating base-level F-statistics.

Figure 2: derfinder F-statistics flow chart

Flow chart of the different processing steps (black boxes) that can be carried out using derfinder and the functions that perform these actions (in red). Input and output is shown in green boxes. Functions in blue are those applied to the results from multiple chromosomes (`mergeResults()` and `derfinderReport`). regionReport functions are shown in orange while derfinderPlot functions are shown in dark purple. Purple dotted arrow marks functions that require unfiltered base-level coverage.

## 16.2 `analyzeChr()` flow chart

Figure 3: analyzeChr() flow chart

Figure 3 shows in more detail the processing flow in `analyzeChr()`, which is the main function for identifying candidate differentially expressed regions (DERs) from the base-level F-statistics.

Many fine-tunning arguments can be passed to `analyzeChr()` to feed into the other functions. For example, you might want to use a smaller `chunksize` when pre-processing the coverage data (the default is 5 million): specially if you have hundreds of samples.

Another useful argument is `scalefac` (by default it’s 32) which controls the scaling factor to use before the log2 transformation.

Furthermore, you might want to specify `maxClusterGap` to control the maximum gap between two regions before they are considered to be part of the same cluster.

## 16.3 `regionMatrix()` flow chart

Figure 4: regionMatrix() flow chart

Figure 4 shows the functions used internally by `regionMatrix()` and processing steps for identifying expressed regions. Overall, it is much simpler than `analyzeChr()`. The flow is even simpler in `railMatrix()`.

# 17 Base-level F-statistics projects

For each project where you will calculating base-level F-statistics, we recommend the following organization. You might be interested in a similar structure when using `regionMatrix()` if you have BAM files. The notable exception is when you are analyzing output data from Rail in which case you won’t be needing this type of organization. Remember that `railMatrix()` is much less computationally intensive than `analyzeChr()`.

## 17.1 File organization

This is our recommended file organization when using `analyzeChr()`.

    ProjectDir
    |-derCoverageInfo
    |-derAnalysis
    |---analysis01
    |---analysis02

We start with a main project directory that has two initial directories. One for storing the coverage data, and one for storing each analysis: you might explore different models, cutoffs or other parameters.

You can then use `fullCoverage()`, save the result and also save the filtered coverage information for each chromosome separately. Doing so will result in the following structure.

    ProjectDir
    |-derCoverageInfo
    |---Chr1Cov.Rdata
    |---Chr2Cov.Rdata
    ...
    |---ChrYCov.Rdata
    |---fullCov.Rdata
    |-derAnalysis
    |---analysis01
    |---analysis02

Next, you can use `analyzeChr()` for each of the chromosomes of a specific analysis (say analysis01). Doing so will create several Rdata files per chromosome as shown below. `bash` scripts can be useful if you wish to submit one cluster job per chromosome. In general, you will use the same model and group information for each chromosome, so saving the information can be useful.

    ProjectDir
    |-derCoverageInfo
    |---Chr1Cov.Rdata
    |---Chr2Cov.Rdata
    ...
    |---ChrYCov.Rdata
    |---fullCov.Rdata
    |-derAnalysis
    |---analysis01
    |-----models.Rdata
    |-----groupInfo.Rdata
    |-----chr1/
    |-------chunksDir/
    |-------logs/
    |-------annotation.Rdata
    |-------coveragePrep.Rdata
    |-------fstats.Rdata
    |-------optionsStats.Rdata
    |-------regions.Rdata
    |-------timeinfo.Rdata
    |-----chr2/
    ...
    |-----chrY/
    |---analysis02

Then use `mergeResults()` to pool together the results from all the chromosomes for a given analysis (here analysis01).

    ProjectDir
    |-derCoverageInfo
    |---Chr1Cov.Rdata
    |---Chr2Cov.Rdata
    ...
    |---ChrYCov.Rdata
    |---fullCov.Rdata
    |-derAnalysis
    |---analysis01
    |-----logs/
    |-----fullAnnotatedRegions.Rdata
    |-----fullFstats.Rdata
    |-----fullNullSummary.Rdata
    |-----fullRegions.Rdata
    |-----fullTime.Rdata
    |-----optionsMerge.Rdata
    |-----chr1/
    |-------chunksDir/
    |-------logs/
    |-------annotation.Rdata
    |-------coveragePrep.Rdata
    |-------fstats.Rdata
    |-------optionsStats.Rdata
    |-------regions.Rdata
    |-------timeinfo.Rdata
    |-----chr2/
    ...
    |-----chrY/
    |---analysis02

Finally, you might want to use `derfinderReport()` from regionReport to create a HTML report of the results.

## 17.2 bash scripts

If you are following our recommended file organization for a base-level F-statistics DER finding analysis, you might be interested in the following `bash` scripts templates. Note that there are plenty of other solutions, such as writing a master `R` script and using BiocParallel to submit jobs and administer them for you. Check out the `BatchJobsParam()` for more information. If you want to use `bash` scripts, take a look below.

For interacting between `bash` and `R` we have found quite useful the getopt package. Here we include an example `R` script that is controlled by a `bash` script which submits a job for each chromosome to analyze for a given analysis.

The two files, derfinderAnalysis.R and derAnalysis.sh should live under the derAnalysis directory.

    ProjectDir
    |-derCoverageInfo
    |---Chr1Cov.Rdata
    |---Chr2Cov.Rdata
    ...
    |---ChrYCov.Rdata
    |---fullCov.Rdata
    |-derAnalysis
    |---derfinder-Analysis.R
    |---derAnalysis.sh
    |---analysis01
    |---analysis02

Then, you can simply use:

    cd /ProjectDir/derAnalysis
    sh derAnalysis.sh analysis01

to run `analyzeChr()` on all your chromosomes.

### 17.2.1 derfinder-analysis.R

    ## Run derfinder's analysis steps with timing info

    ## Load libraries
    library("getopt")

    ## Available at http:/bioconductor.org/packages/derfinder
    library("derfinder")

    ## Specify parameters
    spec <- matrix(c(
        "DFfile", "d", 1, "character", "path to the .Rdata file with the results from loadCoverage()",
        "chr", "c", 1, "character", "Chromosome under analysis. Use X instead of chrX.",
        "mcores", "m", 1, "integer", "Number of cores",
        "verbose", "v", 2, "logical", "Print status updates",
        "help", "h", 0, "logical", "Display help"
    ), byrow = TRUE, ncol = 5)
    opt <- getopt(spec)

    ## Testing the script
    test <- FALSE
    if (test) {
        ## Speficy it using an interactive R session and testing
        test <- TRUE
    }

    ## Test values
    if (test) {
        opt <- NULL
        opt$DFfile <- "/ProjectDir/derCoverageInfo/chr21Cov.Rdata"
        opt$chr <- "21"
        opt$mcores <- 1
        opt$verbose <- NULL
    }

    ## if help was asked for print a friendly message
    ## and exit with a non-zero error code
    if (!is.null(opt$help)) {
        cat(getopt(spec, usage = TRUE))
        q(status = 1)
    }

    ## Default value for verbose = TRUE
    if (is.null(opt$verbose)) opt$verbose <- TRUE

    if (opt$verbose) message("Loading Rdata file with the output from loadCoverage()")
    load(opt$DFfile)

    ## Make it easy to use the name later. Here I'm assuming the names were generated using output='auto' in loadCoverage()
    eval(parse(text = paste0("data <- ", "chr", opt$chr, "CovInfo")))
    eval(parse(text = paste0("rm(chr", opt$chr, "CovInfo)")))

    ## Just for testing purposes
    if (test) {
        tmp <- data
        tmp$coverage <- tmp$coverage[1:1e6, ]
        library("IRanges")
        tmp$position[which(tmp$pos)[1e6 + 1]:length(tmp$pos)] <- FALSE
        data <- tmp
    }

    ## Load the models
    load("models.Rdata")

    ## Load group information
    load("groupInfo.Rdata")

    ## Run the analysis with lowMemDir
    analyzeChr(
        chr = opt$chr, coverageInfo = data, models = models,
        cutoffFstat = 1e-06, cutoffType = "theoretical", nPermute = 1000,
        seeds = seq_len(1000), maxClusterGap = 3000, groupInfo = groupInfo,
        subject = "hg19", mc.cores = opt$mcores,
        lowMemDir = file.path(tempdir(), paste0("chr", opt$chr), "chunksDir"),
        verbose = opt$verbose, chunksize = 1e5
    )

    ## Done
    if (opt$verbose) {
        print(proc.time())
        print(sessionInfo(), locale = FALSE)
    }

Remember to modify the the script to fit your project.

### 17.2.2 derAnalysis.sh

    #!/bin/sh

    ## Usage
    # sh derAnalysis.sh analysis01

    # Directories
    MAINDIR=/ProjectDir
    WDIR=${MAINDIR}/derAnalysis
    DATADIR=${MAINDIR}/derCoverageInfo

    # Define variables
    SHORT='derA-01'
    PREFIX=$1

    # Construct shell files
    for chrnum in 22 21 Y 20 19 18 17 16 15 14 13 12 11 10 9 8 X 7 6 5 4 3 2 1
    do
        echo "Creating script for chromosome ${chrnum}"

        if [[ ${chrnum} == "Y" ]]
        then
            CORES=2
        else
            CORES=6
        fi

        chr="chr${chrnum}"
        outdir="${PREFIX}/${chr}"
        sname="${SHORT}.${PREFIX}.${chr}"
        cat > ${WDIR}/.${sname}.sh <<EOF
    #!/bin/bash
    #$ -cwd
    #$ -m e
    #$ -l mem_free=8G,h_vmem=10G,h_fsize=10G
    #$ -N ${sname}
    #$ -pe local ${CORES}

    echo "**** Job starts ****"
    date

    # Create output directory
    mkdir -p ${WDIR}/${outdir}
    # Make logs directory
    mkdir -p ${WDIR}/${outdir}/logs

    # run derfinder-analysis.R
    cd ${WDIR}/${PREFIX}/

    # specific to our cluster
    # see http://www.jhpce.jhu.edu/knowledge-base/environment-modules/
    module load R/3.3.x
    Rscript ${WDIR}/derfinder-analysis.R -d "${DATADIR}/${chr}Cov.Rdata" -c "${chrnum}" -m ${CORES} -v TRUE

    # Move log files into the logs directory
    mv ${WDIR}/${sname}.* ${WDIR}/${outdir}/logs/

    echo "**** Job ends ****"
    date
    EOF
        call="qsub .${sname}.sh"
        $call
    done

Your cluster might specify memory requirements differently and you might need to use fewer or more cores depending on your data set.

# 18 Expressed regions-level projects

If you are using `regionMatrix()`, an organization similar to the one we mentioned for the single base-level F-statistics implementation is recommended. If you have a very large number of samples, it might be best to store the coverage data separately by chromosome instead of a single `fullCov` object. This is help with the memory load since you can then write a script for loading the coverage data for the chromosome of interest and running `regionMatrix()` on it. Once all your jobs are done, merge the results from them.

If you are using `railMatrix()`, you don’t need any fancy setup. You only need the paths to the summary files and the sample files, all of which are assumed to be BigWig files.

# 19 Summary

We have illustrated how to identify candidate differentially expressed regions without using annotation by using `analyzeChr()`. Furthermore, we covered how to perform the expressed region-level matrix analysis with `regionMatrix()` or `railMatrix()`. We also highlighted other uses of the derfinder package.

Latter sections of this vignette covered the most commonly used advanced arguments, details on how to load data, flow charts explaining the relationships between the functions, the recommended output organization, and example shell scripts for running the analysis.

# 20 Reproducibility

This package was made possible thanks to:

- R (R Core Team, 2022)
- AnnotationDbi (Pagès, Carlson, Falcon, et al., 2017)
- BiocParallel (Morgan, Wang, Obenchain, et al., 2022)
- bumphunter (Jaffe, Murakami, Lee, et al., 2012) and (Jaffe, Murakami, Lee, et al., 2012)
- derfinderHelper
- GenomeInfoDb (Arora, Morgan, Carlson, et al., 2017)
- GenomicAlignments (Lawrence, Huber, Pagès, et al., 2013)
- GenomicFeatures (Lawrence, Huber, Pagès, et al., 2013)
- GenomicFiles (Bioconductor Package Maintainer, Obenchain, Love, et al., 2022)
- GenomicRanges (Lawrence, Huber, Pagès, et al., 2013)
- Hmisc (Harrell Jr, 2022)
- IRanges (Lawrence, Huber, Pagès, et al., 2013)
- qvalue (Storey, Bass, Dabney, et al., 2022)
- Rsamtools (Morgan, Pagès, Obenchain, et al., 2022)
- rtracklayer (Lawrence, Gentleman, and Carey, 2009)
- S4Vectors (Pagès, Lawrence, and Aboyoun, 2017)
- derfinderData (Collado-Torres, Jaffe, and Leek, 2021)
- sessioninfo (Wickham, Chang, Flight, et al., 2021)
- ggplot2 (Wickham, 2016)
- knitr (Xie, 2014)
- BiocStyle (Oleś, 2022)
- RefManageR (McLean, 2017)
- rmarkdown (Allaire, Xie, McPherson, et al., 2022)
- testthat (Wickham, 2011)
- TxDb.Hsapiens.UCSC.hg19.knownGene (Carlson and Maintainer, 2015)

Code for creating the vignette

    ## Create the vignette
    library("rmarkdown")
    system.time(render("derfinder-users-guide.Rmd", "BiocStyle::html_document"))

    ## Extract the R code
    library("knitr")
    knit("derfinder-users-guide.Rmd", tangle = TRUE)

    ## Clean up
    file.remove("derfinderUsersGuideRef.bib")

    ## Warning in file.remove("derfinderUsersGuideRef.bib"): cannot remove file 'derfinderUsersGuideRef.bib', reason 'No such
    ## file or directory'

    ## [1] FALSE

    unlink("analysisResults", recursive = TRUE)
    file.remove("HSB113.bw")

    ## Warning in file.remove("HSB113.bw"): cannot remove file 'HSB113.bw', reason 'No such file or directory'

    ## [1] FALSE

    file.remove("meanChr21.bw")

    ## Warning in file.remove("meanChr21.bw"): cannot remove file 'meanChr21.bw', reason 'No such file or directory'

    ## [1] FALSE

Date the vignette was generated.

    ## [1] "2022-04-26 18:25:43 EDT"

Wallclock time spent generating the vignette.

    ## Time difference of 3.482 mins

`R` session information.

    ## ─ Session info ───────────────────────────────────────────────────────────────────────────────────────────────────────
    ##  setting  value
    ##  version  R version 4.2.0 RC (2022-04-19 r82224 ucrt)
    ##  os       Windows Server x64 (build 20348)
    ##  system   x86_64, mingw32
    ##  ui       RTerm
    ##  language (EN)
    ##  collate  C
    ##  ctype    English_United States.utf8
    ##  tz       America/New_York
    ##  date     2022-04-26
    ##  pandoc   2.7.3 @ C:/PROGRA~1/Pandoc/ (via rmarkdown)
    ##
    ## ─ Packages ───────────────────────────────────────────────────────────────────────────────────────────────────────────
    ##  package                           * version  date (UTC) lib source
    ##  annotate                            1.74.0   2022-04-26 [2] Bioconductor
    ##  AnnotationDbi                     * 1.58.0   2022-04-26 [2] Bioconductor
    ##  AnnotationFilter                    1.20.0   2022-04-26 [2] Bioconductor
    ##  assertthat                          0.2.1    2019-03-21 [2] CRAN (R 4.2.0)
    ##  backports                           1.4.1    2021-12-13 [2] CRAN (R 4.2.0)
    ##  base64enc                           0.1-3    2015-07-28 [2] CRAN (R 4.2.0)
    ##  Biobase                           * 2.56.0   2022-04-26 [2] Bioconductor
    ##  BiocFileCache                       2.4.0    2022-04-26 [2] Bioconductor
    ##  BiocGenerics                      * 0.42.0   2022-04-26 [2] Bioconductor
    ##  BiocIO                              1.6.0    2022-04-26 [2] Bioconductor
    ##  BiocManager                         1.30.17  2022-04-22 [2] CRAN (R 4.2.0)
    ##  BiocParallel                        1.30.0   2022-04-26 [2] Bioconductor
    ##  BiocStyle                         * 2.24.0   2022-04-26 [2] Bioconductor
    ##  biomaRt                             2.52.0   2022-04-26 [2] Bioconductor
    ##  Biostrings                          2.64.0   2022-04-26 [2] Bioconductor
    ##  biovizBase                          1.44.0   2022-04-26 [2] Bioconductor
    ##  bit                                 4.0.4    2020-08-04 [2] CRAN (R 4.2.0)
    ##  bit64                               4.0.5    2020-08-30 [2] CRAN (R 4.2.0)
    ##  bitops                              1.0-7    2021-04-24 [2] CRAN (R 4.2.0)
    ##  blob                                1.2.3    2022-04-10 [2] CRAN (R 4.2.0)
    ##  bookdown                            0.26     2022-04-15 [2] CRAN (R 4.2.0)
    ##  BSgenome                            1.64.0   2022-04-26 [2] Bioconductor
    ##  bslib                               0.3.1    2021-10-06 [2] CRAN (R 4.2.0)
    ##  bumphunter                        * 1.38.0   2022-04-26 [2] Bioconductor
    ##  cachem                              1.0.6    2021-08-19 [2] CRAN (R 4.2.0)
    ##  checkmate                           2.1.0    2022-04-21 [2] CRAN (R 4.2.0)
    ##  cli                                 3.3.0    2022-04-25 [2] CRAN (R 4.2.0)
    ##  cluster                             2.1.3    2022-03-28 [2] CRAN (R 4.2.0)
    ##  codetools                           0.2-18   2020-11-04 [2] CRAN (R 4.2.0)
    ##  colorspace                          2.0-3    2022-02-21 [2] CRAN (R 4.2.0)
    ##  crayon                              1.5.1    2022-03-26 [2] CRAN (R 4.2.0)
    ##  curl                                4.3.2    2021-06-23 [2] CRAN (R 4.2.0)
    ##  data.table                          1.14.2   2021-09-27 [2] CRAN (R 4.2.0)
    ##  DBI                                 1.1.2    2021-12-20 [2] CRAN (R 4.2.0)
    ##  dbplyr                              2.1.1    2021-04-06 [2] CRAN (R 4.2.0)
    ##  DelayedArray                        0.22.0   2022-04-26 [2] Bioconductor
    ##  derfinder                         * 1.30.0   2022-04-26 [1] Bioconductor
    ##  derfinderData                     * 2.13.1   2021-11-23 [2] Bioconductor
    ##  derfinderHelper                     1.30.0   2022-04-26 [2] Bioconductor
    ##  derfinderPlot                     * 1.30.0   2022-04-26 [2] Bioconductor
    ##  DESeq2                            * 1.36.0   2022-04-26 [2] Bioconductor
    ##  dichromat                           2.0-0    2013-01-24 [2] CRAN (R 4.2.0)
    ##  digest                              0.6.29   2021-12-01 [2] CRAN (R 4.2.0)
    ##  doRNG                               1.8.2    2020-01-27 [2] CRAN (R 4.2.0)
    ##  dplyr                               1.0.8    2022-02-08 [2] CRAN (R 4.2.0)
    ##  ellipsis                            0.3.2    2021-04-29 [2] CRAN (R 4.2.0)
    ##  ensembldb                           2.20.0   2022-04-26 [2] Bioconductor
    ##  evaluate                            0.15     2022-02-18 [2] CRAN (R 4.2.0)
    ##  fansi                               1.0.3    2022-03-24 [2] CRAN (R 4.2.0)
    ##  farver                              2.1.0    2021-02-28 [2] CRAN (R 4.2.0)
    ##  fastmap                             1.1.0    2021-01-25 [2] CRAN (R 4.2.0)
    ##  filelock                            1.0.2    2018-10-05 [2] CRAN (R 4.2.0)
    ##  foreach                           * 1.5.2    2022-02-02 [2] CRAN (R 4.2.0)
    ##  foreign                             0.8-82   2022-01-16 [2] CRAN (R 4.2.0)
    ##  Formula                             1.2-4    2020-10-16 [2] CRAN (R 4.2.0)
    ##  genefilter                          1.78.0   2022-04-26 [2] Bioconductor
    ##  geneplotter                         1.74.0   2022-04-26 [2] Bioconductor
    ##  generics                            0.1.2    2022-01-31 [2] CRAN (R 4.2.0)
    ##  GenomeInfoDb                      * 1.32.0   2022-04-26 [2] Bioconductor
    ##  GenomeInfoDbData                    1.2.8    2022-04-21 [2] Bioconductor
    ##  GenomicAlignments                   1.32.0   2022-04-26 [2] Bioconductor
    ##  GenomicFeatures                   * 1.48.0   2022-04-26 [2] Bioconductor
    ##  GenomicFiles                        1.32.0   2022-04-26 [2] Bioconductor
    ##  GenomicRanges                     * 1.48.0   2022-04-26 [2] Bioconductor
    ##  GGally                              2.1.2    2021-06-21 [2] CRAN (R 4.2.0)
    ##  ggbio                               1.44.0   2022-04-26 [2] Bioconductor
    ##  ggplot2                           * 3.3.5    2021-06-25 [2] CRAN (R 4.2.0)
    ##  glue                                1.6.2    2022-02-24 [2] CRAN (R 4.2.0)
    ##  graph                               1.74.0   2022-04-26 [2] Bioconductor
    ##  gridExtra                           2.3      2017-09-09 [2] CRAN (R 4.2.0)
    ##  gtable                              0.3.0    2019-03-25 [2] CRAN (R 4.2.0)
    ##  highr                               0.9      2021-04-16 [2] CRAN (R 4.2.0)
    ##  Hmisc                               4.7-0    2022-04-19 [2] CRAN (R 4.2.0)
    ##  hms                                 1.1.1    2021-09-26 [2] CRAN (R 4.2.0)
    ##  htmlTable                           2.4.0    2022-01-04 [2] CRAN (R 4.2.0)
    ##  htmltools                           0.5.2    2021-08-25 [2] CRAN (R 4.2.0)
    ##  htmlwidgets                         1.5.4    2021-09-08 [2] CRAN (R 4.2.0)
    ##  httr                                1.4.2    2020-07-20 [2] CRAN (R 4.2.0)
    ##  IRanges                           * 2.30.0   2022-04-26 [2] Bioconductor
    ##  iterators                         * 1.0.14   2022-02-05 [2] CRAN (R 4.2.0)
    ##  jpeg                                0.1-9    2021-07-24 [2] CRAN (R 4.2.0)
    ##  jquerylib                           0.1.4    2021-04-26 [2] CRAN (R 4.2.0)
    ##  jsonlite                            1.8.0    2022-02-22 [2] CRAN (R 4.2.0)
    ##  KEGGREST                            1.36.0   2022-04-26 [2] Bioconductor
    ##  knitr                             * 1.38     2022-03-25 [2] CRAN (R 4.2.0)
    ##  labeling                            0.4.2    2020-10-20 [2] CRAN (R 4.2.0)
    ##  lattice                             0.20-45  2021-09-22 [2] CRAN (R 4.2.0)
    ##  latticeExtra                        0.6-29   2019-12-19 [2] CRAN (R 4.2.0)
    ##  lazyeval                            0.2.2    2019-03-15 [2] CRAN (R 4.2.0)
    ##  lifecycle                           1.0.1    2021-09-24 [2] CRAN (R 4.2.0)
    ##  limma                             * 3.52.0   2022-04-26 [2] Bioconductor
    ##  locfit                            * 1.5-9.5  2022-03-03 [2] CRAN (R 4.2.0)
    ##  lubridate                           1.8.0    2021-10-07 [2] CRAN (R 4.2.0)
    ##  magick                              2.7.3    2021-08-18 [2] CRAN (R 4.2.0)
    ##  magrittr                            2.0.3    2022-03-30 [2] CRAN (R 4.2.0)
    ##  Matrix                              1.4-1    2022-03-23 [2] CRAN (R 4.2.0)
    ##  MatrixGenerics                    * 1.8.0    2022-04-26 [2] Bioconductor
    ##  matrixStats                       * 0.62.0   2022-04-19 [2] CRAN (R 4.2.0)
    ##  memoise                             2.0.1    2021-11-26 [2] CRAN (R 4.2.0)
    ##  munsell                             0.5.0    2018-06-12 [2] CRAN (R 4.2.0)
    ##  nnet                                7.3-17   2022-01-16 [2] CRAN (R 4.2.0)
    ##  org.Hs.eg.db                      * 3.15.0   2022-04-21 [2] Bioconductor
    ##  OrganismDbi                         1.38.0   2022-04-26 [2] Bioconductor
    ##  pillar                              1.7.0    2022-02-01 [2] CRAN (R 4.2.0)
    ##  pkgconfig                           2.0.3    2019-09-22 [2] CRAN (R 4.2.0)
    ##  plyr                                1.8.7    2022-03-24 [2] CRAN (R 4.2.0)
    ##  png                                 0.1-7    2013-12-03 [2] CRAN (R 4.2.0)
    ##  prettyunits                         1.1.1    2020-01-24 [2] CRAN (R 4.2.0)
    ##  progress                            1.2.2    2019-05-16 [2] CRAN (R 4.2.0)
    ##  ProtGenerics                        1.28.0   2022-04-26 [2] Bioconductor
    ##  purrr                               0.3.4    2020-04-17 [2] CRAN (R 4.2.0)
    ##  qvalue                              2.28.0   2022-04-26 [2] Bioconductor
    ##  R6                                  2.5.1    2021-08-19 [2] CRAN (R 4.2.0)
    ##  rappdirs                            0.3.3    2021-01-31 [2] CRAN (R 4.2.0)
    ##  RBGL                                1.72.0   2022-04-26 [2] Bioconductor
    ##  RColorBrewer                        1.1-3    2022-04-03 [2] CRAN (R 4.2.0)
    ##  Rcpp                                1.0.8.3  2022-03-17 [2] CRAN (R 4.2.0)
    ##  RCurl                               1.98-1.6 2022-02-08 [2] CRAN (R 4.2.0)
    ##  RefManageR                        * 1.3.0    2020-11-13 [2] CRAN (R 4.2.0)
    ##  reshape                             0.8.9    2022-04-12 [2] CRAN (R 4.2.0)
    ##  reshape2                            1.4.4    2020-04-09 [2] CRAN (R 4.2.0)
    ##  restfulr                            0.0.13   2017-08-06 [2] CRAN (R 4.2.0)
    ##  rjson                               0.2.21   2022-01-09 [2] CRAN (R 4.2.0)
    ##  rlang                               1.0.2    2022-03-04 [2] CRAN (R 4.2.0)
    ##  rmarkdown                           2.14     2022-04-25 [2] CRAN (R 4.2.0)
    ##  rngtools                            1.5.2    2021-09-20 [2] CRAN (R 4.2.0)
    ##  rpart                               4.1.16   2022-01-24 [2] CRAN (R 4.2.0)
    ##  Rsamtools                           2.12.0   2022-04-26 [2] Bioconductor
    ##  RSQLite                             2.2.12   2022-04-02 [2] CRAN (R 4.2.0)
    ##  rstudioapi                          0.13     2020-11-12 [2] CRAN (R 4.2.0)
    ##  rtracklayer                         1.56.0   2022-04-26 [2] Bioconductor
    ##  S4Vectors                         * 0.34.0   2022-04-26 [2] Bioconductor
    ##  sass                                0.4.1    2022-03-23 [2] CRAN (R 4.2.0)
    ##  scales                              1.2.0    2022-04-13 [2] CRAN (R 4.2.0)
    ##  sessioninfo                       * 1.2.2    2021-12-06 [2] CRAN (R 4.2.0)
    ##  stringi                             1.7.6    2021-11-29 [2] CRAN (R 4.2.0)
    ##  stringr                             1.4.0    2019-02-10 [2] CRAN (R 4.2.0)
    ##  SummarizedExperiment              * 1.26.0   2022-04-26 [2] Bioconductor
    ##  survival                            3.3-1    2022-03-03 [2] CRAN (R 4.2.0)
    ##  tibble                              3.1.6    2021-11-07 [2] CRAN (R 4.2.0)
    ##  tidyselect                          1.1.2    2022-02-21 [2] CRAN (R 4.2.0)
    ##  TxDb.Hsapiens.UCSC.hg19.knownGene * 3.2.2    2022-04-21 [2] Bioconductor
    ##  utf8                                1.2.2    2021-07-24 [2] CRAN (R 4.2.0)
    ##  VariantAnnotation                   1.42.0   2022-04-26 [2] Bioconductor
    ##  vctrs                               0.4.1    2022-04-13 [2] CRAN (R 4.2.0)
    ##  withr                               2.5.0    2022-03-03 [2] CRAN (R 4.2.0)
    ##  xfun                                0.30     2022-03-02 [2] CRAN (R 4.2.0)
    ##  XML                                 3.99-0.9 2022-02-24 [2] CRAN (R 4.2.0)
    ##  xml2                                1.3.3    2021-11-30 [2] CRAN (R 4.2.0)
    ##  xtable                              1.8-4    2019-04-21 [2] CRAN (R 4.2.0)
    ##  XVector                             0.36.0   2022-04-26 [2] Bioconductor
    ##  yaml                                2.3.5    2022-02-21 [2] CRAN (R 4.2.0)
    ##  zlibbioc                            1.42.0   2022-04-26 [2] Bioconductor
    ##
    ##  [1] F:/biocbuild/bbs-3.15-bioc/tmpdir/RtmpmwLNde/Rinst39ec7b966f08
    ##  [2] F:/biocbuild/bbs-3.15-bioc/R/library
    ##
    ## ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

# 21 Bibliography

This vignette was generated using BiocStyle (Oleś, 2022) with knitr (Xie, 2014) and rmarkdown (Allaire, Xie, McPherson, et al., 2022) running behind the scenes.

Citations made with RefManageR (McLean, 2017).

[1] J. Allaire, Y. Xie, J. McPherson, et al. rmarkdown: Dynamic Documents for R. R package version 2.14. 2022. URL: https://github.com/rstudio/rmarkdown.

[2] S. Arora, M. Morgan, M. Carlson, et al. GenomeInfoDb: Utilities for manipulating chromosome and other ‘seqname’ identifiers. 2017. DOI: 10.18129/B9.bioc.GenomeInfoDb.

[3] Bioconductor Package Maintainer, V. Obenchain, M. Love, et al. GenomicFiles: Distributed computing by file or by range. R package version 1.32.0. 2022.

[4] BrainSpan. “Atlas of the Developing Human Brain [Internet]. Funded by ARRA Awards 1RC2MH089921-01, 1RC2MH090047-01, and 1RC2MH089929-01.” 2011. URL: http://www.brainspan.org/.

[5] M. Carlson and B. P. Maintainer. TxDb.Hsapiens.UCSC.hg19.knownGene: Annotation package for TxDb object(s). R package version 3.2.2. 2015.

[6] L. Collado-Torres, A. Jaffe, and J. Leek. derfinderData: Processed BigWigs from BrainSpan for examples. R package version 2.13.1. 2021. URL: https://github.com/leekgroup/derfinderData.

[7] A. C. Frazee, S. Sabunciyan, K. D. Hansen, et al. “Differential expression analysis of RNA-seq data at single-base resolution”. In: Biostatistics 15 (3) (2014), pp. 413-426. DOI: 10.1093/biostatistics/kxt053. URL: http://biostatistics.oxfordjournals.org/content/15/3/413.long.

[8] F. Harrell Jr. Hmisc: Harrell Miscellaneous. R package version 4.7-0. 2022. URL: https://CRAN.R-project.org/package=Hmisc.

[9] A. E. Jaffe, P. Murakami, H. Lee, et al. “Bump hunting to identify differentially methylated regions in epigenetic epidemiology studies”. In: International journal of epidemiology 41.1 (2012), pp. 200–209. DOI: 10.1093/ije/dyr238.

[10] A. E. Jaffe, P. Murakami, H. Lee, et al. “Bump hunting to identify differentially methylated regions in epigenetic epidemiology studies”. In: International Journal of Epidemiology (2012).

[11] M. Lawrence, R. Gentleman, and V. Carey. “rtracklayer: an R package for interfacing with genome browsers”. In: Bioinformatics 25 (2009), pp. 1841-1842. DOI: 10.1093/bioinformatics/btp328. URL: http://bioinformatics.oxfordjournals.org/content/25/14/1841.abstract.

[12] M. Lawrence, W. Huber, H. Pagès, et al. “Software for Computing and Annotating Genomic Ranges”. In: PLoS Computational Biology 9 (8 2013). DOI: 10.1371/journal.pcbi.1003118. URL: http://www.ploscompbiol.org/article/info%3Adoi%2F10.1371%2Fjournal.pcbi.1003118}.

[13] M. W. McLean. “RefManageR: Import and Manage BibTeX and BibLaTeX References in R”. In: The Journal of Open Source Software (2017). DOI: 10.21105/joss.00338.

[14] M. Morgan, H. Pagès, V. Obenchain, et al. Rsamtools: Binary alignment (BAM), FASTA, variant call (BCF), and tabix file import. R package version 2.12.0. 2022. URL: https://bioconductor.org/packages/Rsamtools.

[15] M. Morgan, J. Wang, V. Obenchain, et al. BiocParallel: Bioconductor facilities for parallel evaluation. R package version 1.30.0. 2022. URL: https://github.com/Bioconductor/BiocParallel.

[16] A. Oleś. BiocStyle: Standard styles for vignettes and other Bioconductor documents. R package version 2.24.0. 2022. URL: https://github.com/Bioconductor/BiocStyle.

[17] H. Pagès, M. Carlson, S. Falcon, et al. AnnotationDbi: Annotation Database Interface. 2017. DOI: 10.18129/B9.bioc.AnnotationDbi.

[18] H. Pagès, M. Lawrence, and P. Aboyoun. S4Vectors: S4 implementation of vector-like and list-like objects. 2017. DOI: 10.18129/B9.bioc.S4Vectors.

[19] R Core Team. R: A Language and Environment for Statistical Computing. R Foundation for Statistical Computing. Vienna, Austria, 2022. URL: https://www.R-project.org/.

[20] J. D. Storey, A. J. Bass, A. Dabney, et al. qvalue: Q-value estimation for false discovery rate control. R package version 2.28.0. 2022. URL: http://github.com/jdstorey/qvalue.

[21] H. Wickham. ggplot2: Elegant Graphics for Data Analysis. Springer-Verlag New York, 2016. ISBN: 978-3-319-24277-4. URL: https://ggplot2.tidyverse.org.

[22] H. Wickham. “testthat: Get Started with Testing”. In: The R Journal 3 (2011), pp. 5–10. URL: https://journal.r-project.org/archive/2011-1/RJournal_2011-1_Wickham.pdf.

[23] H. Wickham, W. Chang, R. Flight, et al. sessioninfo: R Session Information. R package version 1.2.2. 2021. URL: https://CRAN.R-project.org/package=sessioninfo.

[24] Y. Xie. “knitr: A Comprehensive Tool for Reproducible Research in R”. In: Implementing Reproducible Computational Research. Ed. by V. Stodden, F. Leisch and R. D. Peng. ISBN 978-1466561595. Chapman and Hall/CRC, 2014. URL: http://www.crcpress.com/product/isbn/9781466561595.