The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
Implementation of the empirical method to derive log2 counts per million (CPM) cutoff to filter out lowly expressed genes using ERCC spike-ins as described in Goll and Bosinger et.al (2022)<doi:10.1101/2022.06.23.497396>. This package utilizes the synthetic mRNA control pairs developed by the External RNA Controls Consortium (ERCC) (ERCC 1 / ERCC 2) that are spiked into sample pairs at known ratios at various absolute abundances. The relationship between the observed and expected fold changes is then used to empirically determine an optimal log2 CPM cutoff for filtering out lowly expressed genes.
Version: | 1.0.0 |
Depends: | R (≥ 3.6) |
Imports: | stats, graphics |
Suggests: | spelling, testthat (≥ 3.0.0) |
Published: | 2022-09-13 |
DOI: | 10.32614/CRAN.package.CpmERCCutoff |
Author: | Tyler Grimes [aut], Travis L. Jensen [aut], Kristen Steenbergen [ctb, cre], The Emmes Company LLC [cph] (Copyright holder of CpmERCCutoff package (Copyright (C) 2022)), Johannes B. Goll [aut] |
Maintainer: | Kristen Steenbergen <ksteenbergen at emmes.com> |
License: | GPL (≥ 3) |
NeedsCompilation: | no |
Language: | en-US |
CRAN checks: | CpmERCCutoff results |
Reference manual: | CpmERCCutoff.pdf |
Package source: | CpmERCCutoff_1.0.0.tar.gz |
Windows binaries: | r-devel: CpmERCCutoff_1.0.0.zip, r-release: CpmERCCutoff_1.0.0.zip, r-oldrel: CpmERCCutoff_1.0.0.zip |
macOS binaries: | r-release (arm64): CpmERCCutoff_1.0.0.tgz, r-oldrel (arm64): CpmERCCutoff_1.0.0.tgz, r-release (x86_64): CpmERCCutoff_1.0.0.tgz, r-oldrel (x86_64): CpmERCCutoff_1.0.0.tgz |
Please use the canonical form https://CRAN.R-project.org/package=CpmERCCutoff to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.