LinRegPCR

Download: LinRegPCR: analysis of qPCR data

If you wish to receive mails regarding important updates/bugs, please enter your email address below and press submit. The address will not be used for any other purpose

LinRegPCR is a program for the analysis of quantitative RT-PCR (qPCR) data resulting from monitoring the PCR reaction with SYBR green or similar fluorescent dyes. The program determines a baseline fluorescence and does a baseline subtraction. Then a Window-of-Linearity is set and PCR efficiencies per sample are calculated. With the mean PCR efficiency per amplicon, the Cq value per sample and the fluorescence threshold set to determnine the Cq, the starting concentration per sample, expressed in arbitrary fluorescence units, is calculated. See: Ramakers et al., NeuroSci Lett 2003; Ruijter et al., Nucleic Acids Research 2009.

Go to the FAQ
Go to the references
Go to the version history

FAQs

I tried to import a file into LinRegPCR : the error message was "invalid variant type conversion".
This error message indicates that the program is trying to convert a text that is not a number into a number. This most often happens because: 1: you gave the wrong input range or 2: the decimal separator in Excel is different from the one in Windows. LinRegPCR works with the decimal separator in Windows, so you have to set Excel to use the system separator (in Excel: options menu - international Tab in the options dialog).
After importing data I get the error message "floating point division by zero".
This error occurs when there are not enough data per sample to fit a straight line. This may be because no positive values are left after baseline subtraction by your PCR apparatus. Check your input file and remove the rows or columns with these 'empty' samples. Better still: leave the baseline correction to LinRegPCR (see: Ruijter et al. NAR 2009)
I did run LinRegPCR but in the output all the starting concentrations are 0.
This is because Excel only displays three decimal places. When you increase the number of decimal places or switch to scientific format you will see the starting concentrations are above 0. Except when no baseline can be determined or no amplification is present, then the program reports -999.
Why does LinRegPCR use the word 'baseline' in stead of 'background'?
We use the word baseline to describe the fluorescence that is observed before the amplicon specific fluorescence can be detected. Most PCR systems already use the word background for the fluorescence of a reference fluorochrome that is used to correct for experimental variations in sample volumes and well characteristics. In these systems baseline is used as we use it.
What is the unit of the N0 value?
The starting concentrations (N0) per sample are calculated in the unit of the Y-axis of the PCR amplification plot which are arbitrary fluorescence units. To convert this unit to a RNA concentration you need a calibration line of known concentration of the amplicon you are producing in the PCR.
LinRegPCR reports PCR efficiency values that range between 1 and 2. How must I interpret these values?
You are probably used to describe efficiency as a value between 0 and 1. To get these values you just subtract 1 from the efficiency that LinRegPCR reports. An efficiency of 1.85 reported by LinRegPCR can be read as an efficiency of 0.85 or 85%. We use PCR efficiencies between 1 and 2 because it makes the equations a lot easier to handle.
How is the starting concentration in LinRegPCR calculated?
LinRegPCR calculates a starting concentration (N0) per sample with the formula: N0 = Nq / (Emean^Cq) with the ^ symbol meaning 'to the power'. In this formula Nq stands for the fluorescence threshold set to determine Cq, which is the number of cycles needed to reach Nq. Emean is the mean PCR efficiency for the amplicon that is amplified in the current sample. The mean efficiency is used because the efficiency per sample is too variable to give reliable results. (see Karlen et al., 2007; Cikos et al., 2007)
I have always used the comparative Ct method to calculate the expression of a target relative to a reference gene. How do I do that with the results of LinRegPCR?
LinRegPCR gives you the starting concentrations (N0) of the target and the reference genes. When you have replicates per biological sample you first take the average of the N0 values in the target wells and in the reference wells. Then the relative expression is the ratio of these two averages. When you have only one measurement per amplicon, you calculate the ratio directly from the N0 values. You do not need to use the efficiency values and the Cq values to do this. These are only displayed in the output to give you a chance to do a comparative Ct calculation. The result will be the same. See the Equations in Box 1 in Ruijter et al., NAR 2009.
LinRegPCR gives a warning about 'noisy samples'. How do I recognise a noisy sample?
A noisy sample is defined as a sample in which the data points do not show a continuous increase in the Window-of-Linearity. You recognise a noisy sample because in the W-o-L they have a point c that is above -or at the same level as- point c+1. Noisy samples are excluded from the calculation of the mean efficiency.
LinRegPCR reports a lot of baseline errors but the amplification curves show a straight log-linear phase.
LinRegPCR reports a baseline error when it is not possible to find a baseline value that leads to a straight continuous set of data points in the log-linear phase. However, the program also reports a baseline error when the remaining log-linear phase is to short. This may be because measurement noise causes the lower data points to be discontinuous: the fluorescence in cycle c is larger than that in cycle c+1. The baseline estimation only uses data in which Fc < Fc+1. In version 11.3 you can 'relax' this continuity criterion and allow jumps, as long as all data in the log-linear phase are around a straight line. This leads to less baseline-error samples but also leads to more variation between individual efficiency values.
I am wondering whether you can apply your window of linearity methodology to qPCR data obtained using a Taqman probe assay rather than the SYBR green assay? I can't think of any, as both result in fluorescence values but perhaps I have missed something?
The kinetics of the fluorescence of the Taqman probe is different from SYBR green. SYBR green is binding to dsDNA and is freed again at heating. So the fluorescence you see is proportional to the amount of DNA present at the end of each cycle. The Taqman probe binds to ssDNA, is digested by the polymerase and then becomes fluorescent. And stays fluorescent. So the fluorescence you see is an accumulation of the probe that has ever bound to the ssDNA. Therefore, this fluorescence increases more rapidly than the SYBR green fluorescence. However, on a log-fluorescence scale this amplifiaction curve becomes parallel to the curve that would have been observed when the reporter fluorescence was not cumulative. Therefore, the derived PCR efficiency is correct. Because the values in the Taqman curve are higher, its Cq value is too low. However, this bias is only dependent on the PCR efficiency and can thus be corrected. (see Tuomi et al. , Methods 2010)
I try to read data into LinRegPCR and always get the error message “Variant or safe index out of bounds”.
This is the error message that occurs when you try to read only 1 sample. LinRegPCR expects data for at least 2 samples.
Q.
A.

Go to top

References

Ramakers et al. Assumption-free analysis of quantitative real-time PCR data. Neurosci Letters 339: 62-66, 2003
Ruijter et al. Amplification efficiency: linking baseline and bias in the analysis of quantitative PCR data. Nucleic Acids Research 37: e45, 2009
Tuomi et al. Bias in the Cq value observed with hydrolysis probe based quantitative PCR can be corrected with the estimated PCR efficiency value. Methods 50: 313-322, 2010
Ruijter et al. Evaluation of qPCR curve analysis methods for reliable biomarker discovery: bias, resolution, precision, and implications. Methods 59: 32-46, 2013
Karlen et al. Statistical significance of quantitative PCR. BMC Bioinformatics 8: 131, 2007
Cikos et al. Relative quantification of mRNA: comparison of methods currently used for real-time PCR data analysis. BMC Mol Biol 8: 113, 2007

Go to top

Version History

LinRegPCR version 2013.0 released March 2013

In this version the input format for the PikoReal system of Thermo Scientific was added in the Read-from-Excel dialog. Export the raw data, resulting in an Aquired_dat_1 sheet in Excel. Ommit the 10 lines header and read only the range of data, including the header row with well identifiers and the 3 leading columns, labelled Channel, Cycle and Temp.

These changes have no effect on the analysis results.

LinRegPCR version 2012.3 released December 2012

In this version the input from RDML was updated to enable import of RDML files that use comma as decimal separator. The definition of RDML states that floating point values have to be written with a point as decimal separator. Therefore, the analysis results will always be written with decimal points to maintain compatibility with downstream analysis programs that use RDML. RDML files containing decimal commas can be read by LinRegPCR, but results will be saved to a new RDML file with decimal points. To avoid having to save to a new file: set your computer system to decimal points when you use RDML files.

These changes have no effect on the analysis results.

LinRegPCR version 2012.2 released October 2012

In this version the input from RDML was updated to enable import of RDML version 1.1 and version 1.0. The analysis results will always be saved in RDML version 1.1 to maintain compatibility with downstream analysis programs.

Other corrections made in this version of the program are:

Note that the XML file in an RDML file is essentially a text file. Therefore it is very important that the decimal separator of the qPCR apparatus is the same as the decimal separator of the computer on which the data analysis is performed.
Zip files that cannot be handled will be captured. The online Help and the Manual tell you how to re-zip those files.
Formatting of results in Excel is now conditional upon checking a box in the Save-to-Excel dialog. In some computer configurations formatting should be turned off.

These changes have no effect on the analysis results.

LinRegPCR version 2012.1 uploaded October 2012

In this upload only a few lay-out errors were corrected

LinRegPCR version 2012.1 released August 2012

In this version the input format for the Illumina Eco system was added

Export 'Component data' from the Eco system
Start the input range with the 'Well' cell
The sample name will be composed of the entries in the Well and the Dye columns
Excluded and Empty wells will be ignored

The ViiA7 format was added to the Step-One Plus format option

Note that ViiA7 has a different number of header rows

LinRegPCR version 2012.0 released April 2012

In this version the following features have been implemented:

This version is fully RDML compatible
Data can be read from an RDML file
Results can be saved to an RDML (version 1.1) file
Saved results can be imported in qbasePLUS for normalisation and statistical analysis

NOTE:

For RDML input into LinRegPCR it is very important that the qPCR machine is using the decimal separator that is set with the Regional Settings of Windows
Keep in mind that also the RDML export of the qPCR machine should contain raw, not baseline-corrected, data
The RDML output of the BioRad CFX software is based on RDML, version 1.0, and can therefore not be handled (yet)

LinRegPCR version 12.18 released March 2012

Release in preparation of the full RDML compatible release
Added tab page for assignment of Tissue Samples per reaction
Added option to read amplicon group, tissue sample and baseline from Excel
Note that spaces will be removed from the given identifiers
Moved user choices to separate tab page 'User Settings'
Note that the LinRegPCR_help.pdf is not yet updated
When you want to test the RDML input and output: please contact us at info@linregpcr.nl

LinRegPCR earlier versions

A full update history (versions released since March 2008) can be found in the file UpdateHistroy.pdf that is distributed with the program

Go to top

LinRegPCR (automated content)