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.

GWASinspector: Comprehensive and Easy to Use Quality Control of GWAS Results

When evaluating the results of a genome-wide association study (GWAS), it is important to perform a quality control to ensure that the results are valid, complete, correctly formatted, and, in case of meta-analysis, consistent with other studies that have applied the same analysis. This package was developed to facilitate and streamline this process and provide the user with a comprehensive report.

Version: 1.7.1
Depends: R (≥ 3.2)
Imports: ini (≥ 0.3), futile.logger (≥ 1.4), data.table (≥ 1.12.8), hash (≥ 2.2), tools (≥ 3.0), ggplot2 (≥ 3.0), knitr (≥ 1.1), rmarkdown (≥ 2.17), gridExtra, grid, RSQLite, kableExtra (≥ 0.8), methods, R.utils, openxlsx (≥ 4.0)
Published: 2024-05-06
DOI: 10.32614/CRAN.package.GWASinspector
Author: Alireza Ani [aut, cre], Peter J. van der Most [aut], Ahmad Vaez [aut], Ilja M. Nolte [aut]
Maintainer: Alireza Ani <a.ani at umcg.nl>
License: GPL-3
URL: http://GWASinspector.com
NeedsCompilation: no
Citation: GWASinspector citation info
Materials: NEWS ChangeLog
CRAN checks: GWASinspector results

Documentation:

Reference manual: GWASinspector.pdf
Vignettes: Introduction to GWASinspector

Downloads:

Package source: GWASinspector_1.7.1.tar.gz
Windows binaries: r-devel: GWASinspector_1.7.1.zip, r-release: GWASinspector_1.7.1.zip, r-oldrel: GWASinspector_1.7.1.zip
macOS binaries: r-release (arm64): GWASinspector_1.7.1.tgz, r-oldrel (arm64): GWASinspector_1.7.1.tgz, r-release (x86_64): GWASinspector_1.7.1.tgz, r-oldrel (x86_64): GWASinspector_1.7.1.tgz
Old sources: GWASinspector archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=GWASinspector 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.