Closed bschilder closed 2 years ago
Now implemented as compute_consensus_peaks
using one of two strategies:
consensusSeekeR
, which does some modelling to approximate the range of "true" peaks. Can read more here. consensusSeekeR
can also be sped up using parallelization. By default, all GRanges object in the named list are used to compute consensus peaks. However, users can also supply the groups
argument which lets them compute sets of consensus peaks based on element groupings (e.g. C&T, C&R, or whatever other grouping you want).
I think it makes the most sense to keep this as a prestep before running EpiCompare::EpiCompare
. That way users can inspect the consensus peaks, and tweak the hyperparameters if needed, before proceeding.
Full documentation found here: https://neurogenomics.github.io/EpiCompare/reference/compute_consensus_peaks.html
Group multiple files in a peak list into consensus peak files. This will both help reduce the number of samples being plotted (especially important for single-cell data), and make peak files more comparable to "Replicated peak" files generated by ENCODE from multiple replicates. @NathanSkene