poka.sh

 Docs

MTD

Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.

EnergyPlus Meter Details (MTD).

At a glance
Original creator EnergyPlus (U.S. Department of Energy)
Purpose The EnergyPlus meter details: which output variables feed which meters in a run, and what each meter contains.
Extensions .mtd
Poka parser poka-mtd
Viewer poka-tree-viewer
Depth tier Parser with a shared viewer (see Depth tiers)
Breadth tier B1 Complete (see Breadth tiers)

How much Poka reads

B1 Complete. Everything the format defines that a reader would see is decoded, in every version Poka claims. Anything not decoded is immaterial and listed.

Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-16: parsers/poka-mtd/src/lib.rs and unit tests, tests/samples.rs; corpus oracle_1zone.mtd (EnergyPlus 26.2) and modeltok-pthp-eplusout.mtd (25.1). Both directions (Variables to meters, Meters to variables) are read, including the ResourceType, EndUse, Group and EndUseSubcategory attributes. Meter details from other engine versions were not available to compare.

What Poka does not read

  • The two directions are separate sections and are not cross-linked
  • Custom-meter reference lines (OnCustomMeter=, if a run writes them) would be dropped; this could not be confirmed from the corpus or the EnergyPlus docs page, so it is unverified

Background

The EnergyPlus documentation says the MTD shows which report variables are on which meters and the reverse. The file states the mapping in both directions: for each metered variable the meters it feeds, and for each meter its resource type, group and contents. Poka reads both directions as two separate lists with no links between them, so the tree does not trace a meter to the variables summed into it; the 6,000-node cap can drop the second list entirely.

Versions

Version Identifier Poka Note
EnergyPlus MTD Read

Sources