Construct · 4 fields · 4 citations

Where does metric collide?

One name. Different field. Different construct. One map.

● jingle · one word, four constructs Nearest construct by meaningcontractioncompare the meanings
How to read this

Every construct on the map is compared with every other by the meaning of its definitions, and the closest one is surfaced here. The nearest construct to metric is contraction.

Hold this as a prompt, not a verdict. Two constructs sitting close in meaning is a reason to read them side by side and decide for yourself whether they are one idea under two names. It is not proof that they are. Compare the meanings in the Collider.

metric4 CONSTRUCTSMetric (distance)FRÉCHET · DISTANCEMetric tensorEINSTEIN · METRIC TENSORPerformance metricNEELY · PERFORMANCE KPISoftware metricMCCABE · CYCLOMATIC

Spokes are fields; dashed arcs are shared lineage. Tap a field for its definition, unit, and measures.

2026

Drag to watch the word get claimed. Each field appears at the publication date of the earliest source cited for it. Tap a year to see which.

Mathematics

A distance function on a set

A rule that assigns a real distance to every pair of points in a set, obeying four conditions: the distance is never negative, it is zero only when the two points are the same, it is the same in either direction, and the trip from one point to another is never longer than a detour through a third (the triangle inequality). Fréchet's 1906 thesis Sur quelques points du calcul fonctionnel introduced this abstract notion of distance and the spaces built on it, which became the foundation of analysis and topology. Here the referent is a function satisfying axioms on an arbitrary set, not a tensor field bending spacetime, a number tracked on a business dashboard, or a count taken from source code.[1]

Unit
A real-valued distance between two points, zero only when they coincide
Recovery means
Not applicable
Measured by
Established by checking the four axioms (non-negativity, identity, symmetry, triangle inequality) for the proposed distance rule

Physics and general relativity

The metric tensor of spacetime

The mathematical object that fixes distances, times, and angles at every point of curved spacetime, and that encodes the gravitational field itself. Written as a symmetric array of components, it tells how to measure the interval between nearby events, and its curvature is what we experience as gravity. Einstein's 1916 Die Grundlage der allgemeinen Relativitätstheorie made this tensor the central variable of general relativity, related to matter and energy through the field equations. Here the referent is a physical field that shapes the geometry of the universe, not an abstract distance rule on a set, a performance indicator, or a code measurement.[2]

Unit
A symmetric tensor field defined at each point of spacetime, with ten independent components in four dimensions
Recovery means
Not applicable
Measured by
Inferred from the paths of light and freely falling bodies, and determined by solving Einstein's field equations for a given distribution of matter

Business and performance management

A quantitative performance measure

A quantity chosen to track and judge how well an organization or process is doing, such as a defect rate, a delivery time, or revenue per customer, often called a key performance indicator. Each such measure is defined by a formula, a data source, and usually a target, so that results can be compared over time and used to steer decisions. Neely, Gregory, and Platts's 1995 Performance measurement system design reviewed how such measures are selected and assembled into a coherent system. Here the referent is a managed indicator of organizational performance, not a distance rule, a spacetime tensor, or a property computed from program code.[3]

Unit
A single quantified indicator on a defined scale, usually paired with a target and a reporting period
Recovery means
Not applicable
Measured by
Specified by a formula, a data source, a target value, and a reporting frequency, then read off periodically to assess performance

Software engineering

A measure of software code

A number computed from a piece of software to quantify a property of its code, such as its size or how tangled its logic is. A well known example is cyclomatic complexity, which counts the linearly independent paths through a routine and so estimates how hard it is to test and maintain. McCabe's 1976 A complexity measure defined that count from the program's control-flow graph and proposed it as a guide to code quality. Here the referent is a figure derived from a software artifact, not an abstract distance function, a field describing spacetime, or a business performance indicator, though it shares with the business measure the general habit of managing what you measure.[4]

Unit
A number derived from source code, for example the count of linearly independent paths through a routine
Recovery means
Not applicable
Measured by
Computed automatically from the source code or its control-flow graph by a static analysis tool

Next

Run it through the Collider, or take the citations with you.

See how metric sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in ColliderExport BibTeXReport this collision

Nearby collisions

topology4 fields · 6 citationsjingle · one word, four constructstensor2 fields · 3 citationsjingle · one word, two constructscompleteness3 fields · 4 citationsjingle · one word, three constructs

References

  1. Fréchet, M. (1906). Sur quelques points du calcul fonctionnel. Rendiconti del Circolo Matematico di Palermo, 22(1), 1–72. https://doi.org/10.1007/BF03018603
  2. Einstein, A. (1916). Die Grundlage der allgemeinen Relativitätstheorie. Annalen der Physik, 354(7), 769–822. https://doi.org/10.1002/andp.19163540702
  3. Neely, A., Gregory, M., & Platts, K. (1995). Performance measurement system design: A literature review and research agenda. International Journal of Operations & Production Management, 15(4), 80–116. https://doi.org/10.1108/01443579510083622
  4. McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, SE-2(4), 308–320. https://doi.org/10.1109/TSE.1976.233837

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct