Skip to content

Methods

Decimal comma and point: what Clarida reads

Enter 0.5 or 0,5: Clarida reads one separator as the decimal and always shows a point. A typed 1,234.5 is refused.

On this page

A threshold of zero point five is written 0.5 in the United Kingdom and 0,5 in Belgium. Both are correct. Neither is a rounding, an approximation, or a matter of taste: they are the same number under two conventions.

In a letter this is cosmetic. In software holding standard-curve concentrations, efficiency values and quality-control thresholds, it is not: a separator misread by one character silently changes a scientific result, and the change is invisible because the wrong number still looks like a number.

Clarida handles this with an asymmetry. When you type, either separator is accepted. When Clarida shows you a number, or exports one, it is always a point.

Why typing and display follow two rules

It is tempting to make everything follow the reader's language: show 0,5 to a reader in Belgium, 0.5 to one in Britain. Clarida does not, and the reason is what happens to the number after it leaves the screen.

The text shown in a table is the text you get when you copy it. A results table copied into Excel, a value pasted into an email, a figure caption quoted in a manuscript: all carry whatever separator was on screen. If that separator followed the viewer's browser language, the same experiment copied by two colleagues would produce two different files, and one of them would be misread on paste. Scientific data interchange assumes a point, and formats like RDML are specified that way.

So the output side is pinned to a point everywhere: tables, charts, reports, clipboard, and file exports. This is not a setting, and there is nothing to configure. It is a property of how the numbers are rendered.

Entry is a genuinely different problem, because what reaches the field is outside Clarida's control:

  • The keyboard may not match the country. A scientist on a comma locale may work on a US-layout keyboard, and a numeric keypad can emit a point regardless of the operating system's setting.
  • Copied values may already use a point. RDML files use one, and so can instrument exports and vendor spreadsheets. Someone copying 0.0001 out of a supplier's file should not be told it is invalid.
  • A field is not a document. When you type into a single numeric box, there is no surrounding context to make a comma mean anything other than a decimal point.

Rejecting the comma would punish people for their hardware. Accepting it costs nothing, provided the rule is narrow.

The rule

In a field you type into: exactly one separator character. It is always the decimal separator. The number of digits after it is irrelevant.

You typeClarida storesWhy
1.231.23one separator, read as decimal
1,231.23one separator, read as decimal
1,2341.234one separator, read as decimal
0,00010.0001one separator, read as decimal
1,234.5refusedtwo separators: implies digit grouping
1.234,5refusedtwo separators: implies digit grouping
1 234refusedspace grouping

Whatever you type, a point is stored. The comma never reaches the database, the calculations, or an export.

Note the third row: 1,234 is read as one point two three four, not as one thousand two hundred thirty-four. That follows directly from the rule: there is one separator, so it is the decimal separator. Digit count plays no part.

This matters more than it looks. The obvious alternative (treat three digits after a comma as grouping) would mean someone on a comma locale could type two decimal places but not three, with nothing on screen to explain why. An arbitrary cliff in the middle of ordinary entry is worse than a rule that is occasionally strict.

What Clarida refuses when you type

Digit grouping is not accepted in a field you type into. Not 1,234,567, not 1 234 567, not 1.234.567.

This is the one place where a general rule is impossible. 1,234 means one thousand two hundred thirty-four to one reader and one point two three four to another, and nothing in a single field settles it. Rather than guess, Clarida applies the single-separator rule and refuses anything that implies grouping.

The consequence: if you type 1,234 intending one thousand two hundred thirty-four, you will get 1.234. Two things limit the damage. A number that carries both a grouping separator and a decimal one (1,234.5) is refused rather than misread. And where a field has a defined valid range, an out-of-range result is refused regardless of how it was typed.

A refused entry is always visible: the field reverts to its previous value rather than storing something unexpected.

How imported files are read

An instrument's Cq table follows the file's own convention in its Cq and quantity columns. A lone comma marks the decimal. With both a comma and a point, the last of the two is the decimal one and the other groups digits, so 1,234.5 and 1.234,5 each read as 1234.5. Several commas group thousands: 1,234,567 reads as 1234567.

Where you will see a point

Everywhere Clarida writes a number for you:

  • Tables and charts in the analysis workflow, including axis labels and tooltips
  • Copied and exported data: clipboard, spreadsheet export, and the electronic lab notebook
  • Reports, both on screen and in the exported artifact
  • RDML export, where the format itself requires it

Alongside the separator, Clarida follows the %g convention used by Python, R, MATLAB and printf for deciding when to switch to scientific notation, at six significant digits by default, so 0.00123 stays readable while 0.0000123 becomes 1.23e-05. Quantities with an established convention keep it: Cq to two decimals, geNorm M to three.

Reporting a case we handle badly

If a number you typed was stored differently from what you meant, or a field refuses an entry that looks reasonable, that is worth telling us about. The rule above is intended to cover ordinary scientific entry without exception, and a case it handles badly is a defect rather than a limitation.

About the author

  • Jan Hellemans

    Co-founder, Clarida

    Leads the science and the methods at Clarida. Published the qBase method in 2007 and co-authored the MIQE guidelines.

Type numbers the way your keyboard writes them.

In a field you type into, one separator is read as the decimal; tables, reports and exports show a point.

Related methods

All methods
  • Importing qPCR run files and Cq (Ct) tables

    Which run files and Cq (Ct) tables Clarida reads, and why an import takes one step without a design and three with one.

    Published
    By
    Jan Hellemans
    Reading time
    10 min read
  • Connecting instruments with Porta

    How to set up Porta on the instrument PC, so its export folders and LightCycler 480 runs open inside Clarida.

    Published
    By
    Jan Hellemans
    Reading time
    11 min read
  • Exploring qPCR data

    How Clarida keeps exploring relative quantities apart from statistical tests, and how a view worth keeping becomes an annotated snapshot.

    Published
    By
    Jan Hellemans
    Reading time
    4 min read