Research portal

Mathematical note

Notation and units

math/notation.md

Edition
Site v0.3.0 · continuous main snapshot
Source revision
ec2865b0eac15148675c629981a545632b3571c5
Extent
375 words
Public route
https://www.cordana.dev/math/notation/

System variables

SymbolMeaningUnit
xxone input event or task instancedeclared by task
QQtask-quality measuretask-specific
RRrisk, error, or miscalibration measuretask-specific
Lp95L_{p95}95th-percentile end-to-end latencyseconds
EEenergy over a declared intervaljoules
PPaverage power over a declared intervalwatts = joules/second
TTmeasurement durationseconds
NNqualified events completedcount
BBbytes transferred across a named boundarybytes
CCcounted arithmetic or module workdeclared operation
gi(x)g_i(x)gate for module ii on event xxdimensionless
ci(x)c_i(x)cost proxy for module iioperations, bytes, or joules
ztz_tlatent state at time ttdimensionless vector
σt\sigma_tpredicted uncertainty for ztz_tsame scale as distance
sts_tnormalized surprisedimensionless

Symbol scope

The table above reserves unqualified project-wide symbols. A chapter may add subscripts or superscripts, but it must not reuse a reserved symbol for a different physical quantity. In particular, PP remains power and sts_t remains normalized surprise. Predictors use symbols such as fθf_\theta, and an environment state uses a locally declared symbol such as utu_t.

Time durations use seconds. Discrete sequence horizons use an explicit count such as TτT_\tau or TBT_B rather than the unqualified duration TT. Every local objective must state the unit of its value and of every coefficient that makes unlike terms commensurable.

Required qualifiers

FLOP, operation, token, event, and sample are not interchangeable. Every use must define:

  • arithmetic precision;
  • dense, effective-sparse, or executed count;
  • training or inference;
  • batch and sequence shape; and
  • whether memory and communication are included.

Boundary labels

  • EdeviceE_{\text{device}}: accelerator package only.
  • EnodeE_{\text{node}}: accelerator, CPU, memory, local storage, and node cooling.
  • EclusterE_{\text{cluster}}: nodes plus network and shared infrastructure.
  • EfacilityE_{\text{facility}}: cluster energy multiplied by a contemporaneous, attributable facility overhead.

Results must not move between boundaries by implication.