poka.sh

 Docs

BND

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 Node/Branch Report (BND).

At a glance
Original creator EnergyPlus (U.S. Department of Energy)
Purpose The EnergyPlus branch and node details: the HVAC topology a run built, with every node, branch, connector, air loop and plant loop.
Extensions .bnd
Poka parser poka-bnd
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-bnd/src/lib.rs, tests/samples.rs and unit tests; corpus oracle_1zone.bnd (EnergyPlus 26.2) only, and that file has every count at 0 (a model with no HVAC), so no populated BND has ever been run through the tests. The parser is generic over the self-describing record grammar, so every record type and field is read whatever the version.

What Poka does not read

  • Nodes, branches, loops and connectors are listed as flat record rows; the topology is not assembled into a loop diagram or linked between records
  • Only validated on an empty (no-HVAC) BND: populated records are untested against real output; the header-to-row matching is asserted on the corpus, whose counts are all 0

Background

The EnergyPlus documentation says the branch node details file is meant to help diagram the nodes and components of the HVAC system. It uses the same self-describing grammar as the EIO. Poka lifts the counting records (#Nodes, #Branch Lists and so on) into a summary that shows at a glance whether the run built an HVAC system at all, and shows the other record types as branches of rows, not as the branch and loop topology. A header may space its bracketed name where the data lines do not (<# Plant Loops> over #Plant Loops,0); the two are read as one record type, whose name is then the data line's. Section rules made of = signs are skipped.

Versions

Version Identifier Poka Note
EnergyPlus BND Read

Sources