Skip to content

Methodology

This page explains the engineering and editorial rules every BioSyn calculator follows. The goal is simple: you should be able to trust a result, see exactly how it was produced, and check the source yourself. The same rules apply to every tool, from themolarity calculator to the DNA and protein tools we add next.

A calculation engine separate from the interface

All maths lives in typed functions that know nothing about the web page. A function such assolveMolarity() takes numbers, validates them, computes a result and returns it. The widget on the page only collects input and renders output — it never contains a formula. This separation is what lets us unit-test every calculation, reuse the logic across tools and audit a method by reading one small file instead of digging through markup.

Canonical unit handling

Inputs arrive in many units — grams, milligrams, microlitres, millimolar. Rather than write a conversion for every pair, the engine converts each input to a single canonical unit, does the arithmetic there, then converts back for display. The canonical units are:

QuantityCanonical unitCommon inputs accepted
Massgram (g)g, mg, µg, ng
Volumelitre (L)L, mL, µL
Amount of substancemole (mol)mol, mmol, µmol, nmol, pmol
Concentrationmolar (mol/L)M, mM, µM, nM, pM
Lengthmetre (m)bp, kb, nt

Converting to one canonical unit removes an entire class of rounding and ordering bugs, and it means a new tool only has to declare its units — the conversion factors are already proven by tests.

Input validation

Every field is checked before a result is produced. The engine rejects non-finite numbers, negative masses and volumes, non-positive reaction counts and sequences containing characters outside the expected alphabet. Errors name the offending field and the reason — for example "Mass must be greater than 0 g" — so you can fix the input rather than stare at a blank or impossible result. Validation runs in the engine, not the browser UI, so it cannot be bypassed by a malformed value.

Source tiers

Each constant and method is backed by a source, graded so you can see how authoritative it is. The full definitions are on the about page; in short:

  • Tier 1 — NIST, NIH, NCBI, PubMed-indexed peer-reviewed papers. Required for physical constants.
  • Tier 2 — NEB, Thermo Fisher, Promega, IDT, Bio-Rad, Sigma/Merck technical documentation. Used for protocol conventions.
  • Tier 3 — established educational resources. Used only to cross-check or explain.

We never ship a number that rests on a Tier 3 source alone. Where a citation is an external link it opens in a new tab and carries rel="nofollow".

Scientific constants

The shared constants used across tools, with the version recorded for each. These come from a single data layer so a value is defined once and reused consistently.

ConstantValueSourceVersion
Avogadro constant6.02214076e+23 mol⁻¹NIST CODATA 20181.0
Average dsDNA molecular weight per base pair660 g/molPromega Biomath / NEB NEBioCalculator1.0
Average ssDNA molecular weight per nucleotide330 g/molPromega Biomath / NEB NEBioCalculator1.0
Average RNA molecular weight per nucleotide330 g/molPromega Biomath / NEB NEBioCalculator1.0
A260 conversion — dsDNA (µg/mL per OD)50Promega Biomath / Thermo Fisher1.0
A260 conversion — ssDNA (µg/mL per OD)33Promega Biomath / Thermo Fisher1.0
A260 conversion — RNA (µg/mL per OD)40Promega Biomath / Thermo Fisher1.0

Accuracy, method version and review date

Each calculator records its method, the formula used, the constants applied, the version and the month it was last reviewed. That metadata is shown at the bottom of the tool. When we revise a method we increment the version and re-run the worked examples; a review date is never changed without re-checking the underlying content.

Known limitations

Calculators give estimates, not guarantees. Real reagents have purity below 100%, solution volume changes with temperature, and manufacturer protocols can differ from a textbook formula. Each page lists the specific limitations that apply to that tool, and the standing rule is the same everywhere: your protocol and your manufacturer's guidance take precedence over any number on this site. Where a result is physically implausible — for example a molarity above 100 M — the tool shows a warning rather than presenting the value as final.