Calculator quality checks

See how the calculator checks units before showing an answer.

Eight synthetic cases let educators, developers, and QA teams independently reproduce the calculator's concentration, conversion, volume, capacity, and rejection behavior. No compound names, protocols, or personalized recommendations are included.

Educational content only. Not medical advice.

Published by PeptideSchool Team · Published and reviewed August 11, 2026

How the calculator is checked

Math that fails safely

Valid paths
5 arithmetic checks
Rejection paths
3 fail-closed checks
Unit handling
Mass and volume stay explicit
Capacity limit
Flags without rewriting math

Method

Every answer must pass four repeatable math checks.

Each synthetic example starts with a total quantity, liquid volume, requested quantity, unit, and measuring capacity. Valid examples calculate exact numeric outputs before display rounding. Invalid combinations stop safely instead of forcing an answer.

Concentration

total quantity ÷ liquid volume

Output volume

requested quantity ÷ concentration

U-100 scale equivalent

output volume in mL × 100

Quantities per container

total quantity ÷ requested quantity

The activity-unit row is intentionally a rejection case. It verifies that a numeric value cannot cross incompatible unit families. The dataset does not assign an amount to a person or make a real-world use decision.

Vector map

Five arithmetic paths and three fail-closed checks.

VectorResultConcentrationVolumeBehavior
mass-mg-basicValid5 mg/mL0.2 mLDirect mass path
mass-mcg-conversionValid2.5 mg/mL0.1 mLMetric conversion
mass-decimalValid2.5 mg/mL0.2 mLDecimal input
small-mass-conversionValid0.5 mg/mL0.1 mLSmall mass conversion
capacity-flagValid + flag2 mg/mL1 mLCapacity boundary
zero-liquid-volumeRejected00Zero denominator
mass-activity-unit-mismatchRejected00Unit mismatch
negative-requested-quantityRejected00Negative input
Technical files for researchers and developers

Most visitors do not need these files. They allow independent arithmetic and rejection-path verification.

Reproduction contract

What a conforming implementation should prove.

Parse every input as a number and preserve its unit before any conversion.

Convert micrograms to milligrams exactly once when the total quantity is mass-labeled in milligrams.

Compare numeric results within an absolute tolerance of 1 × 10⁻⁹, before display rounding.

Reject non-positive inputs and incompatible unit families with the expected error code.

Flag a result that exceeds the stated measuring capacity without rewriting the arithmetic result.

A passing arithmetic test does not validate a label, product, protocol, substance, or personal decision. Implementations may use different display formatting while still conforming to the numeric and rejection contract.

Method, license, and citation

A stable record built for verification and citation.

The technical files preserve a stable reproducibility record. A later correction receives a new file set while prior releases remain available for independent verification.

The dataset is licensed under CC BY 4.0. Suggested citation: PeptideSchool Team. PeptideSchool Calculator Test Vectors, version 1.0.0. August 11, 2026. Link to this canonical page so readers retain the scope and limitations.

Sources

The measurement framework behind the vectors.

National Institute of Standards and Technology

SI Units: Mass

Defines the SI basis for mass and the metric prefixes used in the conversion vectors.

Open source

OpenStax Chemistry 2e

Molarity

Explains the amount-per-volume relationship used by the concentration equation.

Open source

OpenStax Chemistry 2e

Measurements

Provides the measurement, significant-figure, and dimensional-analysis context.

Open source

NCBI Bookshelf

Dimensional Analysis

Describes the factor-label method used to verify that unwanted units cancel.

Open source

Continue the research path

Read the math, then inspect the real calculator interface.

The public guide explains the unit checks in context. The preview shows the actual product surface while keeping usable output and profile-specific depth inside the workspace.