Assay Harmonization

Assay harmonization is the process of making measurement records comparable before training or evaluating a model. In chem-bio ML, labels with the same column name can come from different protocols, targets, units, and biological contexts.

A measurement should be treated as:

where is a molecule, is a target, is an assay protocol, and contains conditions such as organism, construct, endpoint, units, and environment.

Harmonization Fields

FieldExamplesWhy It Matters
target identityprotein, isoform, species, construct, mutationdifferent constructs can change activity
endpoint, , , percent inhibition, binary activeendpoints are not interchangeable labels
unit and transformnM, uM, pIC50, Delta G, normalized scoretransformations change loss scale and thresholds
censoring>, <, detection limit, inactive above cutoffcensoring is not exact measurement
replicate policymean, median, best, latest, source-prioritizedaggregation changes label noise
assay sourcelab, campaign, dataset, protocol, publicationsource can leak into train/test splits

Common Conversions

When a concentration is converted to a logarithmic activity score:

This conversion is only meaningful when is a comparable endpoint and unit. Mixing , , and can be useful for rough triage but should not be presented as a clean physical target without stating the approximation.

Label Direction Contract

Before training or evaluation, define whether larger means stronger activity:

For concentration-like endpoints, lower raw concentration means stronger binding, but higher transformed p-scale means stronger activity. Mixing raw and transformed values can invert the label.

Raw fieldLarger raw value meansCommon transformed direction
, , weaker activityp-scale larger means stronger
percent inhibitionstronger activity if same concentration and assayoften larger means stronger
binary activedepends on threshold definitionmust state active threshold
censored > concentrationweaker than bound onlynot an exact value
censored < concentrationstronger than bound onlynot an exact value

Conflict Policy

The same molecule-target pair can have multiple labels:

These labels should not be collapsed unless the endpoints, units, constructs, protocols, and censoring rules are compatible.

ConflictSafer handling
different endpointskeep endpoint-specific labels or model endpoint as context
different constructs/specieskeep target construct explicit
replicate disagreementaggregate with documented rule or mark uncertain
censored and exact valueskeep censoring direction or use interval-aware objective
different assay sourcessplit or stratify by source when source transfer is claimed

Split Implications

ClaimSplit or Control
new molecule in same assay settingscaffold split with assay held fixed
new assay or campaignsource/campaign holdout
new target familyprotein-family split plus assay-source control
cross-dataset transferexternal dataset or source holdout with harmonization audit
target-conditioned activitykeep target, assay, endpoint, unit, and threshold explicit

Checks

  • Are endpoint types mixed, such as , , , inhibition percent, or binary labels?
  • Are units and transformations recorded?
  • Are censored values such as > or < handled explicitly?
  • Are replicate measurements aggregated deliberately?
  • Are conflicting molecule-target labels resolved or kept assay-specific?
  • Does the split hold out assays or campaigns when that is the deployment claim?
  • Is the label direction consistent, so larger always means more active or less active?
  • Are source-specific missingness and measurement limits documented?
  • Is larger-is-better or smaller-is-better made consistent before metric computation?
  • Are labels collapsed only when the assay context supports it?