Empowering scientists to conduct reproducible, flexible, and MIQE best-practice compliant quantitative PCR analysis.
Quantitative Polymerase Chain Reaction (qPCR) is a highly adaptable experimental technique used across biology and medicine to measure the amounts of nucleic acids (DNA or RNA). tidyqpcr is a software package for qPCR data analysis that builds on the tidyverse collection of data science tools in the R programming language.
tidyqpcr combines a free, open-source qPCR analysis R package with online teaching materials.
We want our users to be able to know and understand what happens at every step of their analysis. Users are able to know what occurs at each step as all tidyqpcr tools are open source and follow the FAIR principles - Findable, Accessible, Interoperable, and Reusable. Users should also find each step understandable as we aim to produce educational resources as extensions of data carpentry workshops, such as Data Analysis and Visualization in R for Ecologists, accessible to beginner programmers.
tidyqpcr scripts produce paper-ready figures straight from raw data with identical results across computers.
We want to promote reproducible research so collaborators, reviewers or students can easily confirm and extend results and conclusions. tidyqpcr analysis will repeat exactly on different computers, enabling scientists to share raw data and analysis scripts rather than just processed figures. An R or R markdown script using tidyqpcr to analyse a set of qPCR data could be directly uploaded to a repository such as figshare, as encouraged by many journal publishers.
tidyqpcr follows the 'tidy' data paradigm to ensure scalability and adaptability.
We want to create a tool that is flexible enough to analyse high or low throughput experimental data whilst integrating easily into other data analyses. tidyqpcr uses powerful generic data science tools from the tidyverse R package, lightly overlaid with qPCR-specific scripts. As far as possible, every object in tidyqpcr is stored as a generic tibble / data frame. Manipulating and plotting qPCR data without creating bespoke data structures allows tidyqpcr scripts to be easily integrated and scaled according to the needs of your experiments.
tidyqpcr encourages standardised, reliable experimental design by prioritising MIQE-compliant best practices.
We want to make it easier for scientists to produce reliable and interpretable results. The final version of tidyqpcr will, by default, request the relevant experimental conditions and assay characteristics, as described in the MIQE guidelines, to allow reviewers/readers to rigorously assess the validity of a result. See "Future Priorities" below to get updates on tidyqpcr's MIQE compliant features.
As of July 2021, this software is in development. Edward Wallace wrote basic functions and documentation needed to do qPCR analysis in the Wallace lab, and is making them freely available. Sam Haynes is actively developing, initially as part of the eLife Open Innovation Leaders programme 2020.
- June 2021, tidyqpcr blogpost in eLife labs
- August 2020, relative quantification (delta delta Cq) added with function
calculate_deltadeltacq_bytargetid, and a vignette illustrationg this with small data from a 96-well plate. - June 2020, upgrades that break previous code. All function and variable names have been changed to snake case, i.e. lower case with underscore. Commits up to #ee6d192 change variable and function names. tidyqpcr now uses
sample_idfor nucleic acid sample (replaces Sample or SampleID),target_idfor primer set/ probe (replaces TargetID or Probe),prep_typefor nucleic acid preparation type (replaces Type), andcqfor quantification cycle (replaces Cq or Ct). It should be possible to upgrade old analysis code by (case-sensitive) search and replace.
Alternatively, pre-April 2020 analysis code should run from release v0.1-alpha, see releases.
tidyqpcr can be used to analyse qPCR data from any nucleic acid source - DNA for qPCR or ChIP-qPCR, RNA for RT-qPCR.
Currently tidyqpcr has functions that support relative quantification, but not yet absolute quantification.
- every object is a tibble / data frame, no special data classes to learn
- lay out and display 96/384-well plates for easy experimental setup (
label_plate_rowcol,create_blank_plate, ...) - flexible assignment of metadata to samples for visualisation with ggplot2 (see vignettes)
- read-in Cq and raw data from Roche LightCycler machines with single-channel fluorescence (
read_lightcycler_1colour_cq,read_lightcycler_1colour_raw) - calibration of primer sets including estimating efficiencies and visualization of curves (
calculate_efficiency, and see vignettes) - visualization of amplification and melt curves (
calculate_drdt_plate, and see vignettes) - delta Cq: normalization/ relative quantification of Cq data to one or more reference targets by delta count method (
calculate_normcq,calculate_deltacq_bysampleid) - delta delta Cq: normalization of delta Cq data across multiple samples (
calculate_deltadeltacq_bytargetid)
- including primer efficiencies in quantification
- an open-source and tested Cq calculation function, from amplification curves
- multi-colour (hydrolysis probe) detection
- extend to 1536-well plates
- metadata handling compatible with RDML format
- files for automatic plate loading with Opentrons and Labcyte Echo liquid handlers.
First install R.
Next, you need a working installation of Rtools.
Jeffrey Leek made slides on installation and testing of Rtools.
Install the devtools R package, see devtools installation instructions.
library(devtools)
devtools::install_github("ewallace/tidyqpcr",build_vignettes = TRUE) ## Vignettes require cowplot package
## Alternatively, install without building the vignetttes to remove cowplot dependency
## (Not recommended as vignettes contain the tutorials on using tidyqpcr)
devtools::install_github("ewallace/tidyqpcr")
Note older versions of the remote package automatically convert warnings to errors during installation. Please update your remotes package to >2.3.0 in order to remove this default.
Then load tidyqpcr as a standard package:
library(tidyqpcr)
Note tidyqpcr automatically imports and loads several external packages for basic functionality, including; tidy, dplyr and ggplot2. This allows tidyqpcr to be used immediately but may cause NAMESPACE clashes if the user already has many other package libraries loaded. Restarting the R session and loading tidyqpcr separately may solve such issues.
The best place to start is the vignettes, which offer tutorials and example data analyses including figures. Currently there are 4 vignettes:
- IntroDesignPlatesetup - Introduction to designing an experiment and setting up a plate plan in tidyqpcr.
- DeltaCq96wellExample - Example analysis of 96-well RT-qPCR data including relative quantification with delta Cq, from a real experiment.
- MultifactorialExample - Example design and analysis of a (real) multifactorial RT-qPCR experiment.
- PrimerCalibration - Example design and analysis of calibrating qPCR primer sets from a (real) experimental test
To find these from your R session, enter browseVignettes(package="tidyqpcr").
Individual R functions are also documented, use R's standard help system after loading the package, e.g. ?create_blank_plate. To see a list of all the functions and links to their help pages use help(package="tidyqpcr").
We would be delighted to work with you to answer questions, add features, and fix problems. Please file an issue or email Edward dot Wallace at his University email address, (ed.ac.uk).
We will be following the code of conduct from the tidyverse.
If you want to fix bugs or add features yourself, that's great. tidyqpcr development aims to follow best practices:
- first file an issue on the tidyqpcr github repository, then create a branch (in a fork) of the repository that references the issue number, e.g.
add-exciting-feature-55if it were issue 55. - add code in the branch, continue to ask questions on the issue ticket.
- follow the tidyverse style guide.
- document functions with roxygen2, as described in the R packages book.
- check the package with
R CMD check/devtools::check(), as explained in the R packages book. - including, check that all the vignettes run.
- put in a pull request to the main repository, we will review, then we will accept or suggest changes.