-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
11 changed files
with
182 additions
and
124 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,14 +8,14 @@ Authors@R: c( | |
comment = c(ORCID = "0000-0002-3913-153X")) | ||
) | ||
Maintainer: Michael Jahn <[email protected]> | ||
Description: The goal of 'ggcoverage' is to simplify the process of | ||
visualizing genome/protein coverage. It contains functions to load | ||
data from BAM, BigWig, BedGraph or txt/xlsx files, create | ||
genome/protein coverage plots, add various annotations to the coverage | ||
plot, including base and amino acid annotation, GC annotation, gene | ||
annotation, transcript annotation, ideogram annotation, peak | ||
annotation, contact map annotation, link annotation and protein | ||
feature annotation. | ||
Description: The goal of `ggcoverage` is to visualize coverage tracks from | ||
genomics, transcriptomics or proteomics data. It contains functions to | ||
load data from BAM, BigWig, BedGraph, txt, or xlsx files, create | ||
genome/protein coverage plots, and add various annotations including | ||
base and amino acid composition, GC content, copy number variation | ||
(CNV), genes, transcripts, ideograms, peak highlights, HiC contact | ||
maps, contact links and protein features. It is based on and | ||
integrates well with `ggplot2`. | ||
License: MIT + file LICENSE | ||
URL: https://showteeth.github.io/ggcoverage/, | ||
https://github.com/showteeth/ggcoverage | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.