Film creditsChanging the unit. Keep the quantity.
A transformation method for combining scientific records without converting unlike quantities or losing the original measurement basis.
Proposed evidence-engineering direction | External sources and defined methods; scope, rights and delivery capacity to be agreed.
A clean axis can conceal a broken comparison
Confirm that records describe the same physical quantity before a shared axis or standard unit makes their values look comparable.
A graph looks more coherent when all its values use one unit. That visual improvement is useful only if the records measure the same quantity. Converting milligrams per millilitre to a consistent mass concentration is different from converting a preparation dose into purified-polymer concentration. Converting seconds to hours is different from treating an endpoint as a kinetic rate. The proposed transformation ledger would begin with dimensional identity and preserve original units, denominators and source wording. It would then identify which conversions are exact, which require measured inputs and which should remain prohibited for the intended comparison.
Examine the development decision
Changing the unit. Keep the quantity.
Open the sequence to examine what a development decision needs.
Identify the exact preparation, its source, and the properties a second laboratory must be able to reproduce.
Explanatory geometry · no simulated or measured performance
Kinetic units need their concentration basis
Preserve the kinetic concentration convention when changing units, keeping numerical transformations separate from changes in parameter interpretation.
A catalytic-efficiency parameter contains an inverse concentration unit as well as an inverse time unit. Nemergut et al. (2023) report values using micromolar concentration. A standardised export can convert those units while keeping the original table untouched, but the resulting numerical magnitude changes with the concentration unit. STRENDA explicitly asks for parameter definitions and units (STRENDA Commission, 2021). The proposed ledger would test the conversion on known examples, attach the formula and prevent a unit-normalised parameter from being interpreted as brightness, binding affinity or a first-order transport coefficient simply because its value fits a convenient model.
Changing the concentration unit changes the numerical magnitude, not the measured kinetic quantity.
- Molar concentration unitmol L⁻¹
- Micromolar concentration unit10⁻⁶ mol L⁻¹
Model conditions. Same defined catalytic-efficiency quantity and time unit No change in parameter model or concentration convention
Viscosity and stress remain different measurands
Derive apparent viscosity from measured stress and positive shear rate while retaining the original quantities and their experimental context.
The new Woodbridge et al. (2025) flow files contain shear rate in inverse seconds and shear stress in pascals. Dividing stress by a positive measured shear rate yields an apparent viscosity in pascal seconds. That arithmetic is a derived quantity, not another independently measured row. It also does not turn oscillatory modulus into steady viscosity. The proposed data export would label the transformation and retain the original stress and rate, giving a formulator a reproducible comparison across the measured flow domain. A zero, negative or unavailable denominator would produce an explicit invalid state rather than an infinite viscosity presented as useful material behaviour.
Keep the conditions attached to the result.
Make scientific records useful through source-linked comparisons, explicit units and a reproducible decision trail.
Dimensionless does not mean interchangeable
Pair dimensionless values with their endpoint definitions so that ratios, coefficients and percentages are never joined on units alone.
Friction coefficient, loss factor, percentage response and a normalised activity ratio can all be dimensionless while answering different questions. The proposed schema would therefore pair units with endpoint definitions rather than using units as the sole criterion for joining records. A percentage also needs its denominator and uncertainty basis. A ratio relative to a reference preparation is not an absolute response, and a chemical-assay percentage cannot be averaged with retained-water percentage. This is a practical safeguard when a buyer wants a compact dashboard: the display can be concise without stripping away the definitions that make its comparisons scientifically meaningful.
Measured inputs make some conversions uncertain
Identify density, moisture or purity inputs required for a conversion, then expose the uncertainty those measured quantities introduce.
A mass-to-volume conversion requires density, while a wet-to-dry conversion requires water content and possibly a purity basis. Those inputs may vary by temperature, preparation or lot. JCGM’s measurement model treats an output as a function of inputs whose uncertainties and dependencies matter (JCGM, 2008). The proposed ledger would retain the measured input record and distinguish it from an assumed scenario value. A reader could then see whether the comparison is robust to the conversion or whether the apparent difference comes mainly from an uncertain correction. Missing inputs would not be replaced by a generic literature value without explicit justification.
A transformation should be testable
Use dimensional and source-row checks to catch transformations that produce technically valid numbers with the wrong scientific meaning.
The proposed software check would use dimensional tests, finite-value rules, round-trip conversions where appropriate and source-exact reference rows. It would preserve the source’s significant figures rather than giving transformed values an implied extra experimental precision. A failed transformation would be visible and would not silently drop the record. The ledger could also record a known source-header inconsistency separately from the decision about how to parse it. These checks matter to an API or exported collection because a technically valid response can still carry a scientifically wrong quantity if the unit and endpoint assumptions are not tested together.
The deliverable is more than a cleaned spreadsheet
Deliver original values, conversions and exceptions together so that a receiving scientist can reproduce the comparison rather than trust its formatting.
A prospective partner would receive the original record, standardised fields, conversion expressions, required inputs and an exception log. The acceptance task would ask another scientist to reproduce representative transformed rows from the source. That makes the service useful for an internal evidence collection, a model comparison or a development meeting where conclusions may be challenged. The proposed scope would specify which quantities are included and which remain incomparable. A fee or recurring integration would need a separately agreed delivery arrangement; a tidy dataset alone does not establish demand, laboratory readiness or scientific performance.
The next proposed comparison.
A dimensional conversion ledger and testable data export
Fix the quantity before expanding the collection
Trial the conversion rules on difficult records before multiplying an unresolved denominator or unit error across a larger collection.
The next commitment should test a small set of difficult records rather than ingesting more sources immediately. Include a concentration conversion, a derived rheology quantity, a dimensionless endpoint and a record with missing inputs. If the schema cannot represent these without losing meaning, a larger collection will multiply the ambiguity. Once the rules are clear, additional records can enter with an explicit version and transformation history. The buyer should be able to answer what changed numerically, what remained measured and what assumptions were required. That is the foundation for a comparison worth using beyond the website.
Evidence engineering · Proposed development discussion
A development path
for this research.
The unit transformations a comparison can legitimately use
The people this could serve.Formulation, application-science and research-data teams.
The decision behind the project.
Your intended application, present alternative and the constraint behind “Units and dimensional checks”. A useful starting point is the change that would justify another development step.
A proposed scope centred on a dimensional conversion ledger and testable data export.
Agree the comparison, acceptance basis and responsible expertise before discussing a paid package.
Specialist methods and a defined contribution.
Bring relevant analytical or experimental expertise, a comparator suggestion, and the conditions under which your method could resolve this question.
A jointly scoped proposal could connect your contribution with a dimensional conversion ledger and testable data export.
Define contributions, required access, independent preparations and permitted outputs before work or protected information is shared.
The commercial purpose of the next milestone.
Bring the application or asset thesis, the buyer you expect to value it, and the scientific or commercial uncertainty that must be resolved before another commitment.
The proposed decision record would connect the buyer question with a dimensional conversion ledger and testable data export. It would identify what a subsequent comparison needs to demonstrate.
Demand, development cost, resources, rights and a decision-changing milestone would need examination. No financing terms or investment outcome are represented here.
What a useful comparison
would record.
- Define the record needed for “A clean axis can conceal a broken comparison” and identify what is currently missing.
- Check the evidence behind “Kinetic units need their concentration basis” against the proposed buyer decision.
- Retain the applicable source links, versions, method limits and the exact evidence needed before another commitment.
What the proposed
brief could leave behind.
- A dimensional conversion ledger and testable data export
- A preparation, comparator and endpoint record tied to this question.
- A source-linked account of the evidence gaps, study assumptions and next review point.
The proposed discussion brief
A brief you
can take away.
Use non-confidential notes to connect this topic with your own decision. Entries stay in this browser tab; saving creates a text file on your device. Nothing is submitted.
A scoped evidence/data decision brief or qualified comparison programme; recurring or API access only after delivery capacity and repeat buyer value are established.
Notes are optional. The brief includes this page’s proposed question and public source links.
Proposed scope; resources, methods, rights and delivery terms would be agreed before work. Begin with non-confidential information.
Sources and reading notes.
External work is identified below. Access notes describe the material inspected for this page; company research questions and proposed work are not presented as findings from these sources.
Nemergut et al., 2023Nemergut et al. (2023) Illuminating the mechanism and allosteric behavior of NanoLuc luciferase
Source kinetic table and full method context for within-study variants and substrates.
Scope and limitations: Efficiency is not brightness or affinity. Reported CTZ triple efficiency differs from quotient of reported means; no Bio result.
Open original sourceSTRENDA Commission, 2021STRENDA Commission (2021) Guidelines Lists Level 1A and 1B, version 1.8
Catalyst identity, assay conditions, activity units, replicate definitions and model reporting.
Scope and limitations: Reporting guidance, not assay approval or a probabilistic quality score.
Open original sourceWoodbridge et al, 2025Woodbridge et al. (2025) Rheological Characterisation of a Carbopol Microgel and a Commercial Body Lotion: Steady, Oscillatory, and Parallel Superposition Measurements
Acquired six source CSVs: 392 flow, amplitude and frequency rows for two source specimens; source units and README conditions.
Scope and limitations: CC BY 4.0 version 1; two studied specimens, not independent lots or a current commercial product specification. No parallel-superposition or slip data analysed.
Open original sourceJCGM, 2008JCGM (2008) Evaluation of measurement data—Guide to the expression of uncertainty in measurement
Measurement models, uncertainty components and covariance in propagation.
Scope and limitations: Does not provide application tolerances or missing source covariance.
Open original source
