RDML
RDML
RDML file The file containing the data in xml-format. The file is zipped and renamed to .rdml, to view the data you can rename the file to .zip and extract the file.
Experiment ID The ID of the experiment is mandatory, can contain any characters and each experiment ID within an RDML file has to be unique.
Run ID The ID of a run, can contain any characters and each run ID within an experiment has to be unique.
Quantification file A tab delimited flat text file (*.txt) containing the quantification data (all numbers have to be written in point-notation) with one header row containing the following columns :
  • "reactionId"
notation : A1, B1, ... or integer number
  • "sampleId"
ID of the sample, this has to be the same ID as used in the sample annotation file.
  • "targetId"
ID of the target, this has to be the same ID as used in the target annotation file.
  • "cq"
the quantification cycle, has to be in point-notation.
  • "quantity"
Specifies the quantity of the target in the reaction. A unit can be specified as follows : 'value unit', possible units are "cop", "fold", "ng", "dil" and "nMol"
  • "excl"
indicates that this well should be excluded for data-analysis (e.g. bad replicate, suspicious melt curve). Possible values are "false", "true", "no" and "yes".
  • "exclExp"
explanation why a specific well had to be excluded.
  • "endFluor"
the end point fluorescence, has to be in point-notation.
  • "endPointFluor"
the background fluorescence, has to be in point-notation.
  • "quantFluor"
the quantification fluorescence, has to be in point-notation.


Only the headers "reactionId", "sampleId", "targetId" and "qc" are mandatory, the other headers are optional.
If this file has been given, then the sample annotation and target annotation files are mandatory.
Amplification curve fluorescence data file A tab delimited flat text file (*.txt) with the raw amplification curve fluorescence data (ie. values without baseline correction). All numbers have to be written in point-notation.
This file is optional, but if it is given, then the quantification, the sample annotation file and the target annotation file are mandatory.
The following columns are mandatory :
  •  "reactionId"
  •  "1" to "50" integer numbers for the cycle numbers
If multiple dyes have been used in the quantification file, an extra column with the header "targetId" has to be included.
Melting curve fluorescence data file A tab delimited flat text file (*.txt) with the raw melting curve fluorescence data (ie. values without baseline correction). All numbers have to be written in point-notation.
This file is optional, but if it is given, then the quantification, the sample annotation file and the target annotation file are mandatory.
The following columns are mandatory :
  •  "reactionId"
  •  "50" to "100" decimal numbers (.-notation) for the temperatures
If multiple dyes have been used in the quantification file, an extra column with the header "targetId" has to be included.
Run annotation file An optional tab delimited flat text file (*.txt) which contains the annotation of one run. All numbers have to be written in point-notation. The following headers can be used (but are all optional) :

  • "id"
ID of the run, has to be unique in the RDML file.
  • "description"
gives a description of the run.
  • "instrument"
name of the instrument used to perform the analysis.
  • "pcrFormat"
fomat used by the instrument. Possible values are "single-well 1x1", "48-well plate 8x6", "96-well plate 8x12", "384-well plate 16x24", "32-well rotor 1x32", "72-well rotor 1x72" and "100-well rotor 1x100".
  • "software"
name and version of the program used to collect/analyse the data, has to be written in the name:version format
  • "bgDeterminationMethod"
method used to determine the background noise.
  • "cqDetectionMethod"
method used to determine the cq-value. Possible values are "automated threshold and baseline settings", "manual threshold and baseline settings" and "second derivative maximum".
  • "runDate"
date when the run was performed (in YYYY-MM-DD notation).
  • "experimenter"
ID of the experimenter who participated in this run, has to be the same ID as used in the experimenters file.
  • "thermConditions"
ID of the thermal cycling conditions used for this run, has to be the same ID as used in the thermal cycling conditions file.
Sample annotation file A tab delimited flat text file (*.txt) which contains the annotations of all the samples in the experiment. All numbers have to be written in point-notation.
This file is mandatory if a quantification file has been given, otherwise it's optional.
The following headers can be used :

  • "id"
unique ID of the sample, mandatory header.
  • "type"
type of the sample, mandatory header. Possible values are "unkn", "std", "nac" and "ntc" (unkn = unknown, ntc = no template control, nac = no amplification control, std = standard).
  • "quantity"
mandatory header if the sample is part of a standard-curve.
  • "interRunCalibrator"
specifies if a sample has been used as an inter-run calibrator. Possible values are "false" and "true".
  • "calibrator"
specifies if a sample has been used as a calibrator. Possible values are "false", "true", "yes" and "no".
  • "description"
free description of the sample.
  • "dnaseTreatment"
specifies if a sample has been treated with DNase. Possible values are "true", "false", "yes" and "no".
  • "enzyme"
the enzyme used for the cDNA synthesis.
  • "primingMethod"
the method used for priming. Possible values are "oligo-dT", "random" and "target specific".
  • "thermConditions"
ID of the thermal cycling conditions used for the cDNA synthesis, has to be the same ID as used in the thermal cycling conditions file.
  • "rnaQuantity"
amount of RNA template, has to be in point-notation. A unit can be specified as folows : 'value unit'
  • "dnaQuantity"
amount of DNA template, has to be in point-notation. A unit can be specified as folows : 'value unit'
  • "rnaQualityMethod"
the method used for assessing the quality of the RNA template.
  • "dnaQualityMethod"
the method used for assessing the quality of the DNA template.
  • "rnaQualtity"
quality of the RNA template, has to be in point-notation. A unit can be specified as folows : 'value unit'
  • "dnaQualtity"
quality of the DNA template, has to be in point-notation. A unit can be specified as folows : 'value unit'
  • "xref"
reference ID of the target in a database, the followin format has to be used : name of the database(reference ID)


Only the headers "Id" and "type" are always mandatory. If the sample is part of a standard curve (STD-type), then the header "quantity" is also mandatory. All the other headers are always optional.
Target annotation file A tab delimited flat text file (*.txt) which contains the annotations of all the targets in the experiment. All numbers have to be written in point-notation.
This file is mandatory if a quantification file has been given, otherwise it's optional.
The following headers can be used :

  • "id"
unique ID of the target, mandatory header.
  • "type"
type of the target, mandatory header. Possible values are "ref" and "toi" (ref = reference target, toi = target of interest).
  • "dye"
name of the dye. This header is mandatory if multiple dyes have been used, otherwise it is optional.
  • "description"
free description of the target.
  • "amplificationEff"
target specific amplification efficiency (values between 0.5 and 1.5, 1=100% amplification efficiency), has to be in point-notation.
  • "forward"
nucleotide sequence of the forward primer. 3' and 5' tags can be specified as follows : 3'tag-sequence-5'tag
  • "reverse"
nucleotide sequence of the reverse primer. 3' and 5' tags can be specified as follows : 3'tag-sequence-5'tag
  • "probe"
nucleotide sequence of the probe. 3' and 5' tags can be specified as follows : 3'tag-sequence-5'tag
  • "amplicon"
nucleotide sequence of the amplicon. 3' and 5' tags can be specified as follows : 3'tag-sequence-5'tag
  • "commercialAssay"
company name and order number from which the kit with commercial primer and probe assays has been used, the following format has to be used : company:order number
  • "xref"
reference ID of the target in a database, the followin format has to be used : name of the database(reference ID)


Only the headers "Id" and "type" are always mandatory. If multiple dyes have been used, then the header "dye" is also mandatory. All the other headers are always optional.
List of experimenters A tab delimited flat text file (*.txt) which contains the personal information of the experimenters involved in the study.
The following headers can be used :

  • "id"
unique ID of the experimenter, mandatory header.
  • "firstName"
first name of the experimenter.
  • "lastName"
last name of the experimenter.
  • "email"
email address of the experimenter.
  • "labName"
name of the lab.
  • "labAddress"
address of the lab.
List of thermal cycling conditions A tab delimited flat text file (*.txt) which contains a list of all the thermal cycling conditions used during the study.
Each PCR program is written on a separate line in the file. The file contains no headers, but the values can be specified by the following identifiers :

  • "id"
unique ID of the PCR program, mandatory header.
  • "lidTemperature"
temperature of the lid.
  • "description"
description of the thermal cycling conditions.
  • "experimenter"
ID of the experimenter who created/used this protocol, the same ID as present in the thermal cycling conditions file has to be used.
  • "step step number"
Step identified by the step number in the header. All temperatures have to be entered in degrees celcius (°C) and durations in number of seconds. The type of step is identified by using the following notation :
  1. Normal step : normal(...)
    • temperature(value) : specifies the temperature of the step
    • duration(value) : specifies the duration of the step
    • tempChange(value) : specifies the temperature change of the step
    • durationChange(value) : specifies the duration change of the step
    • measure(value) : specifies the type of measurement performed during the step, possible values are "none", "real time" and "meltcurve"
    • ramp(value) : specifies the ramp of the step

    • All fields have to be separated from each other by a comma-point ";".
  2. Gradient step : gradient(...)
    • temperature(value-value) : specifies the lower- and upper temperature of the step
    • duration(value) : specifies the duration of the step
    • tempChange(value) : specifies the temperature change of the step
    • durationChange(value) : specifies the duration change of the step
    • measure(value) : specifies the type of measurement performed during the step, possible values are "none", "real time" and "meltcurve"
    • ramp(value) : specifies the ramp of the step

    • All fields have to be separated from each other by a comma-point ";".
  3. Loop step : loop(...)
    • goto(value) : specifies that on reaching the step, the program must go back and continue from the step identified by value
    • repeat(value) : specifies how many times the loop has to be repeated
  4. Pause step : pause(...)
    • temperature(value) : specifies the temperature of the step
  5. Lid open step : lidOpen
  6. Step example
    • gradient(temperature(50-70); duration(60); measure(meltcurve))