Validation

The additive default-off registered-floor exact identity screen is documented in ADR-031 and research usage. It reports Preserved/Failed/Unavailable separately from production validation and does not alter the production checks below. Geometry/program preservation is not full exact-composition eligibility: missing ownership/construction stays unavailable.

The additive reference research contract describes FloorResearchEligibilityValidator and the opt-in IdfOptions.RequireFloorResearchEligibility writer gate. Its spatial conditioning/control checks supplement the production rules below without changing them or certifying whole-building thermal equivalence.

Applies from v0.3.0 (S3). Code: src/Lod.Core/Validation/Totals.cs and src/Lod.Core/Validation/Validators.cs. Rules: GLOBAL.md scientific rules 1, 2, and 6; research brief §17; D-038 (conditioning), D-041 (façade coverage), D-045 (building height), D-046 (ground, roof, and exposed floor area); D-124 (infiltration is not a program load, ADR-017); D-126 (load components by end use, per-dwelling loads, the calendar; ADR-018); roadmap S3 slice feature/validation-invariants.

Purpose

Simplification deliberately changes zoning, heat transfer between zones, and controls where the LoD says so; those differences are what the study measures. It must not change the prescribed conservation invariants: floor area, volume, exterior wall area, glazed area in total and per orientation, and the installed and hourly scheduled magnitude of every program load type and, since D-126, of every load component (type, end use, and basis) together with the number of dwellings (since D-124 not infiltration, see below; the program properties of D-126 are below); for a building also ground, roof, and exposed floor area and the building height (D-045, D-046); and the target façades must cover the source façades. Validation checks these numerically, together with tiling and traceability, before a model is converted.

Validation applies to objects that exist. A simplifier that cannot produce a valid floor fails earlier, with its own diagnostics (PlanTooNarrow, DisconnectedGroup, TouchingPieces and DuplicateZoneId (D-123), FacadeNotCovered, the centred-window guards WindowNotHosted and GlazingExceedsWall (D-079), gaps and overlaps from the surface builder, aggregation errors), and returns no floor.

References

Validator	Validates	Compared with
FloorValidator	an IFloor from any plan simplifier	its source plan, IFloor.Source (the detailed Z0 plan)
BuildingValidator	an IGeneratedBuilding from any floor aggregator	1. every distinct source floor against its plan, as FloorValidator does; check names prefixed Floor0., Floor1., … in floor order. 2. the fully stacked reference Stack.Aggregate(building.Sources): the same floor entries with every storey explicit; check names prefixed Building.

If the stacked reference cannot be built, BuildingValidator adds the failed check Building.Reference with the stacking diagnostics and stops.

Totals

Totals.Of(zones, surfaces, orientationDegrees) computes the extensive quantities of a set of zones, counting zone multipliers.

Total	Definition
Floor area	Σ multiplier × zone floor area, m²
Volume	Σ multiplier × zone volume, m³
Conditioned floor area	Σ multiplier × floor area of zones whose program has a thermostat, m² (D-038)
Exterior wall area	Σ multiplier × gross area of walls with boundary Outdoors, windows included, m²
Glazing	Σ multiplier × glazed area of those walls (all their windows), m²
Glazing per orientation	the same per bin North [315°, 45°), East [45°, 135°), South [135°, 225°), West [225°, 315°) of the wall's true azimuth (plan azimuth + orientation)
Skylights	Σ multiplier × glazed area of the skylights of every ceiling, m² (DOE geometry note S5): of a plan's and a floor's ceilings, of a building's roofs
Ground area	Σ multiplier × area of horizontal surfaces with boundary Ground, m²
Roof area	Σ multiplier × area of ceilings with boundary Outdoors, m²
Exposed floor area	Σ multiplier × area of floors with boundary Outdoors (overhangs, floors not covered by the storey below), m²
Height	elevation of the highest zone top (part elevation + part height), m; 0 without zones. This is the building height when the lowest storey starts at 0
Installed magnitude	per load type, summed over all bases and end uses of the type (D-047), Σ multiplier × design magnitude (ADR-007): people for occupancy; W for lighting, electric and gas equipment; m³/h for hot water and ventilation (infiltration is not a program load since D-124)
Scheduled magnitude	per load type and hour (8760 values), Σ multiplier × design magnitude × schedule fraction
Component magnitudes (D-126)	the same two totals per load component, a load type with an end use in a basis (LoadComponent, written Type.EndUse.Basis, such as Lighting.lighting.PerFloorArea), per-dwelling components included
Dwelling count (D-126)	Σ multiplier × the dwelling count of each zone (Zone.DwellingUnits)

A court (a hole of the footprint, S8.3) is outside the building: its façades are outdoor walls and count in the exterior wall area and in the glazing of the orientation they face (into the court: the south wing's court façade faces north), and the court adds no floor, ground, or roof area. No check changes.

Checks

Relative comparisons are |a − b| ≤ tol × max(1, |a|, |b|) (ADR-004).

Check	Compares	Tolerance	Enforced
FloorArea	floor area	RelativeArea	yes
Volume	volume	RelativeArea	yes
ConditionedFloorArea	conditioned floor area	RelativeArea	no: reported only (D-038); for Conditioned Merge it never differs, in either mode (D-123)
ExteriorWallArea	exterior wall area	RelativeArea	yes
Glazing	total glazed area	RelativeArea	yes
Glazing.<Bin>	glazed area per orientation bin; one check per bin present in either total	RelativeArea	yes
Skylights (DOE geometry note S5)	skylight area; only when either total has skylights, so a report without them is unchanged	RelativeArea	yes
Installed.<LoadType>	installed magnitude; one check per load type present in either total, all bases of the type together (D-047)	RelativeLoad	yes
Scheduled.<LoadType>	scheduled magnitude at each of the 8760 hours; the detail names the worst hour	RelativeLoad at every hour	yes
Installed.<Component> (D-126)	installed magnitude of one load component, Type.EndUse.Basis, such as Installed.Lighting.lighting.PerFloorArea or Installed.ElectricEquipment.electric_equipment.PerDwellingUnit; one check per component present in either total	RelativeLoad	yes
Scheduled.<Component> (D-126)	scheduled magnitude of that component at each of the 8760 hours	RelativeLoad at every hour	yes
DwellingUnits (D-126)	the building's dwelling count, multipliers included	RelativeLoad	yes
PerDwellingLoads (D-126)	no zone, source or target, has a per-dwelling load and no dwellings (PerDwellingWithoutDwellings); the detail names the zones	exact	yes
Calendar (D-126)	every zone's program shares one schedule calendar (CalendarMismatch); the detail gives the calendar, or none for BEMGen's own presets	exact	yes
FacadeCoverage (floor)	every source outdoor wall is covered over its full length by target outdoor walls on the same façade line, before any normalisation. Two walls are on the same façade line when they face the same way (Angle), share elevation and height (Distance), overlap, and are within Distance of each other over their overlap (ADR-013)	RelativeArea, applied to lengths	yes (D-041)
NoTargetOverlap (floor)	Σ pairwise intersection area of the parts of the target zones, so the pieces of one zone are compared with each other and with every other zone (D-123)	at most RelativeArea × footprint area	yes
SourceCoverage (floor)	each source zone's floor area vs the sum of its mapping overlaps	RelativeArea	yes
Traceability (floor)	every target zone has a mapping row; an identity zone (no source zones, NoSimplification) has an identity row with source fraction 1; a derived zone has aggregation records on every load value and every load schedule, on its heat fractions and water temperatures where it has them, on its people properties and activity schedule, and, if it is conditioned, on each setpoint schedule it has	exact	yes
Building.Reference	the stacked reference could not be built	—	yes
Building.GroundArea	ground area vs the stacked reference	RelativeArea	yes (D-046)
Building.RoofArea	roof area vs the stacked reference	RelativeArea	yes (D-046)
Building.ExposedFloorArea	exposed floor area vs the stacked reference: a floor aggregator must not multiply overhanging floors	RelativeArea	yes (D-046)
Building.Height	building height vs the stacked reference: representative storeys must sit at their true elevations	Distance, absolute	yes (D-045)
Building.SkylightsOnRoofs (DOE geometry note S5)	every skylight lies on a ceiling facing outdoors; only when the building or its reference has skylights	exact	yes
Building.PerDwellingLoads, Building.Calendar (D-126)	the same two checks on the building's own zones	exact	yes
MultiplierPairing (floor), Building.MultiplierPairing (DOE geometry stage P5a, S8, ADR-026)	every interzone surface lies between zones of one multiplier; only when a source plan has multiplied rooms (a zone with a multiplier above 1), so the reports of every other plan are unchanged	exact	yes

The floor and building checks Installed.<Component>, Scheduled.<Component>, and DwellingUnits compare the zones with the source, the building with the stacked reference. Occupancy and air volume flow are not separate checks: occupancy is the load type Occupancy (people), and air-change loads are compared as m³/h magnitudes (ADR-007, D-019).

A zone of several pieces (D-123) is measured over all its parts: its floor area, volume, and exterior wall area are sums over the parts, so every total and check above counts all its pieces, and so does the exterior area its infiltration is applied to at conversion (D-124). Two pieces of one zone that share an edge are not validated but rejected when surfaces are built (TouchingPieces), because they would be one piece; two target zones with one ID are rejected before that (DuplicateZoneId).

A multiplied room (S8) counts its multiplier in every total, as Zone.Multiplier always did: its floor area, volume, outdoor walls, glazing, skylights, ground, roof, and loads count once per room it stands for, and a room multiplier times a floor entry's multiplier on a Stacked Floor Zone Multiplier storey. Its self-adjacent surfaces are neither exterior walls nor ground, roof, or exposed area. A plan with multiplied rooms is the DOE drawing, not the building, so its drawn zone area is below its multiplied area: the footprint holds the copy space as well, and the checks that compare areas compare zone area times multiplier with the same on the reference; no tolerance changes.

Not compared:

• Setpoints. Floor-area weighting over the sources that have the side is a prescribed control rule, not a conservation invariant (D-038, D-126); only that the merged heating setpoint does not exceed the merged cooling setpoint is required, and a merge that breaks it fails earlier (SetpointsCross).
• The installed power of each heat path of a load, the heat the occupants give off, and the water heat of hot water. The aggregation conserves them (the rules are in domain-model.md and the research brief, §7), and the invariant tests of the aggregator prove it for random sources, hour by hour (InstalledHeatPowerIsConservedPerComponent, PeopleHeatIsConservedEveryHour, WaterHeatIsConservedEveryHour); a floor or building has no source values of these to compare, so they are not validation checks.
• Window positions and sizes. Where walls are rebuilt, each outdoor wall gets one window centred on it with the glazed area of the source windows it covers (D-079, ADR-012), so individual windows are not conserved by design; the rule is covered by the unit tests of CentredWindows and the integration tests CentredWindowTests. Validation compares the glazed areas in total and per orientation, which the rule conserves per wall. The reference glazing is the plan's: a generator's wall or window below the ADR-011 minimum has no window (WindowOmitted), and validation compares with the glazing the generator placed, not with WWR × wall area. Every window is checked per wall when it is built, not by validation: a source window must lie on one target wall (WindowNotHosted) and a wall's glazed area must be smaller than its area (GlazingExceedsWall); both hold by construction once the façades are covered (D-041) and are kept as guards.
• Skylight positions and sizes. Each rebuilt ceiling or roof piece carries one skylight centred in its largest grid rectangle with the skylight area of the detailed zones under it (ADR-012), so individual skylights are not conserved; the areas are. A piece that is a detailed ceiling unchanged keeps its skylights, such as a source layout's (D-252). A skylight that does not fit its piece fails the step that places it (SkylightDoesNotFit), and the area handed on is guarded when it is placed (SkylightNotHosted). A floor's skylight area is compared with its plan's; a building's with Stack of the same entries, whose roofs take the skylight ratio of each detailed zone under them × their area, so a covered ceiling has none and a terrace has its share.
• Floor and ceiling boundaries of a floor. They stay Unresolved until a floor aggregator stacks the floors.

The conditioned floor area is reported because merging conditioned and unconditioned sources makes the merged zone conditioned ("any conditioned wins", D-038). With the example presets, Z2 and Z3 turn the 72 m² stair into conditioned area: note ConditionedFloorArea: reference 360.000000, actual 432.000000.

Conditioned Merge (Z1c, D-123) is the simplifier for which this check must pass: every target covers source zones of one class only, so the conditioned floor area of its floor equals the source's within RelativeArea, with separate and with joined pieces. The check stays reported only; the tests assert that it passes for Conditioned Merge and that every source of a target has the target's conditioning. Semantic Merge groups by space type, so it keeps the conditioned floor area only when the zones of each space type share their conditioning.

A program changed by mistake is caught through the totals: ValidationCatchesAChangedProgram replaces a Z3 program with a preset and fails both Installed.Lighting and Traceability.

Infiltration and program mixes (D-124)

The infiltration invariants are removed. Infiltration left the zone programs in D-124 (ADR-017), so no zone has an infiltration load, and the checks Installed.Infiltration and Scheduled.Infiltration, which compared its installed and hourly scheduled magnitude of a floor or building with its source, no longer exist: Totals.Of sums the program load types only, and a floor or building has one check per load type present, none of them infiltration. The reason is not that infiltration went unchecked. A target zone's infiltration is not transferred from source zones. It is the building's rate (an input of the envelope preset) times the zone's own exterior surface area, outdoor wall area, or volume, applied at conversion, so there is no source magnitude to conserve. It is conserved by construction wherever the quantities it multiplies are, and validation already enforces those:

Basis of the infiltration	Quantity it multiplies (per zone, with zone multipliers)	Conserved by
PerExteriorSurfaceArea	gross area of outdoor walls, roofs, and exposed floors, not ground floors	ExteriorWallArea (floor and building), Building.RoofArea, Building.ExposedFloorArea
PerExteriorWallArea	gross area of outdoor walls	ExteriorWallArea
AirChangesPerHour	volume	Volume

Convert2IDF's tests compare each zone's infiltration, read from the IDF as EnergyPlus reads it, with the design flow Convert2BEM outputs for the same zone (ZoneInfiltration), and the installed total with the building's (IdfChecks, convert2idf.md). InfiltrationOutOfProgramsTests runs every family through every plan simplifier and every floor aggregator and finds that each combination validates, that no zone program has an infiltration load, and that every installed and scheduled check is of a program load type.

New diagnostics. These come from building the objects, not from the validators: an error stops the object and gives no output; the info is a remark.

Code	Severity	Raised by	When
UndefinedLoadKind	Error	LoadDefinition.Create	The load type or basis is not defined, such as a value cast from the removed infiltration type or exterior-wall basis; the message says to set infiltration on the envelope preset
InfiltrationValue	Error	EnvelopePreset.Create, through Infiltration.Check	The design rate is negative or not finite, or the basis is not defined (a schedule that is not a fraction schedule is ScheduleKindMismatch)
MixWeight	Error	ProgramMix.Mix	The weights are not one per preset, a weight is not finite and greater than 0, or their sum is not finite
PerPersonWithAbsoluteOccupancy	Error	ProgramMix.Mix	A per-person load and absolute occupancy are in any inputs, the same or different; the message names both
MixedConditioning	Info	ProgramMix.Mix	Conditioned and unconditioned inputs are mixed; the unconditioned share becomes conditioned

Other changes to the checks. None. The load checks keep their names, tolerance, and enforcement, ExteriorWallArea still compares the walls with an outdoor boundary, and the façade-coverage check is unchanged; only the exterior-wall fraction that the plan simplifiers took from the façade attribution to transfer loads per exterior wall area is gone, so FacadeCoverage is unchanged and still required: the rebuilt walls must cover every source wall for the window rehosting (D-041, D-079). A program mix is not validated further: its aggregation record is the same as a zone merge's, and its equivalence with a zone merge on matching area shares is a unit test (ProgramMixEquivalenceTests), not a runtime check, because a mix has no source plan to compare with.

Program properties (D-126)

The program JSON stage (ADR-018) gave programs end uses, per-dwelling loads, heat fractions, people properties, thermostat sides, hot-water temperatures, and a calendar. What validation checks of them is the rows Installed.<Component>, Scheduled.<Component>, DwellingUnits, PerDwellingLoads, and Calendar above, and the larger Traceability check. Most rules that name a program property are enforced earlier, when the object is built, so an invalid program never reaches a validator:

Code	Severity	Raised by	When
PerDwellingWithoutDwellings	Error	plan generation and the PerDwellingLoads check	A zone with a per-dwelling load has no dwellings (a dwelling is a zone of space type DwellingUnit); the message says to give a per-dwelling preset to dwelling-unit zones only
CalendarMismatch	Error	plan generation, the aggregator, ProgramMix.Mix, the Calendar check, Convert2IDF	Programs expanded on different calendars meet; a program without a calendar agrees only with a calendar whose 1 January is a Monday. Convert2IDF cannot write such a building even with the validation override
SetpointsCross	Error	Thermostat.Create, the aggregator, ProgramMix.Mix	A heating setpoint exceeds its cooling setpoint in some hour by more than AbsoluteSchedule
NoSetpoint	Error (Info)	Thermostat.Create, Thermostat.ForSides	A thermostat has neither side (the info: a switched-on side has no setpoint schedule)
HeatFractionValue, HeatFractionsExceedOne, HeatFractionNotSupported	Error	HeatFractions.Create, LoadDefinition.Create	A fraction is outside [0, 1] or not finite; the fractions sum to more than 1 (ToleranceSettings.AbsoluteFraction); a load has a non-zero fraction its EnergyPlus object lacks, or fractions on a type that has none
WaterTargetBelowInlet, WaterTemperaturesNotAllowed	Error	WaterTemperatures.Create, LoadDefinition.Create	A hot-water target is below its inlet in some hour by more than AbsoluteSchedule; water temperatures on another load type
PeopleFraction	Error	SensibleHeatFraction, PeopleProperties.Create	A radiant or sensible fraction of people is outside [0, 1], not finite, or text that is neither a number nor autocalculate
CalendarYear, CalendarHoliday	Error	ScheduleCalendar.Create	A year that is a leap year or outside 1 to 9999; a holiday that is not a date of the year or is repeated
MixedOccupancyBases	Error	ProgramMix.Mix	A mix has occupancy in more than one basis and a per-person load or different people properties among the inputs with occupants: the virtual zone of a mix would weight them by a wrong split
ZeroAggregationWeight	Error	the aggregator	The weights of a derived heat fraction, water temperature, or people property sum to zero
MixedSensibleFraction	Warning	the aggregator, ProgramMix.Mix	Merged sources mix a numeric and an autocalculated sensible fraction; the result is autocalculated

The Source of a preset made by Program JSON and the diagnostics of the importer have their own codes, prefixed ProgramJson, each with the JSON Pointer of the node: they are listed in program-json.md.

Tolerances

All tolerances come from ToleranceSettings.Default (ADR-004); validation defines none of its own.

Setting	Value	Used for
RelativeArea	1e-6	floor area, conditioned floor area, volume, wall area, glazing, façade coverage (lengths), source coverage, overlap, ground, roof, exposed floor
Distance	1e-6 m	building height
RelativeLoad	1e-9	installed and hourly scheduled magnitudes, the dwelling count
AbsoluteSchedule	1e-9	also the slack of the heating-against-cooling and water-target-against-inlet checks (D-126)
AbsoluteFraction	1e-9	the sum of a load's heat fractions against 1 (D-126; checked when the fractions are built, not by a validator)

Loads can be held to 1e-9 while areas need 1e-6 because transfer fractions are normalised per source (TransferMatrix) and per source wall (FacadeAttribution): extensive quantities are conserved to floating-point precision whatever the polygon rounding, whereas areas pass through Clipper2 on a 1e-6 m grid. Normalisation is safe only because coverage is checked separately and before it (SourceCoverage, FacadeCoverage). Tolerances are never widened to make a check pass (AGENTS.md rule 12).

Report

ValidationReport.Passed is true when every enforced check passed. ValidationReport.Describe() writes PASSED or FAILED on the first line, then one line per check: ok for a passed check, FAIL for a failed enforced check, note for a failed reported-only check, followed by the check name and the reference and actual values with six decimals.

Where validation runs

• Validate component (6 Inspect): takes a floor or a building and outputs Passed and the report; a failed validation adds a warning.
• Convert2BEM (5 Convert): validates the building with BuildingValidator before converting it; the heat-transfer options (D-069) change only the written boundaries, never the building or its validation. Passed: the conversion runs and Provenance (output 15) holds the provenance tree followed by the report, the options line, the envelope line, and since D-124 the line INFILTRATION: <rate> <basis> (EnergyPlus <method>), schedule <name>. Failed with Override false (the default): error ValidationFailed, no conversion (outputs 0–14 and 16–31 stay empty), and only Provenance is set so the failing checks can be read. Failed with Override true: warning ValidationOverridden, the conversion runs, and Provenance ends with the line OVERRIDE: converted despite failed validation. The override is recorded only in that text, so keep Provenance with any result produced from an overridden model.

Tests

• EverySimplifierSatisfiesTheInvariantsForRandomPlans: each simplifier on linear plans drawn from explicit seeds (9 cases, including rotated plans and source zones split across several targets).
• MergingTheUnconditionedStairEnlargesConditionedAreaAndIsReported: the conditioned-area change is reported, not enforced.
• ValidationCatchesAnUncoveredFacade: a missing target wall fails FacadeCoverage.
• NoSimplificationPassesValidation: the identity floor passes.
• ConditionedMergeConservesConditionedFloorAreaExactly (core), ConditionedMergeConservesConditionedFloorAreaOnRandomPlans (integration, three random linear plans), and ConditionedMergeConservesConditionedFloorArea (integration, every one of the 18 plan families at the default placement and rotated and moved, with separate and with joined pieces): the conditioned floor area of the floor equals the source's and ConditionedFloorArea passes (D-123).
• AFloorWithATwoPieceZoneValidates and TheOverlapCheckReadsEveryPart (core): a floor with a two-piece zone passes every check, and a zone lying on the second piece of another zone fails NoTargetOverlap with its overlap; EveryAggregatorValidatesABuildingOfTwoPieceZones stacks such floors with every aggregator (D-123).
• ValidationCatchesAChangedProgram: a tampered program fails.
• EveryCombinationValidatesOnARotatedAndTranslatedPlan (S4.2): every plan simplifier with every floor aggregator on plans rotated and moved by Transform Plan (four placements, 64 cases) validates without warnings; AStoreyMovedOffTheStoreyBelowIsUnsupported checks the exposed floor and roof areas of storeys from differently moved plans, and ARotatedSetbackStoreyHasNoUncoveredFloor a rotated setback, whose floor is fully covered. ZeroWidthArtefactTests builds every family canonical and at the two placements of the typology tests through every simplifier and aggregator and finds no spike, repeated vertex, excursion, or sliver in any zone part or surface (ADR-002).
• DwellingCountTests (core, D-126): a generated dwelling-unit zone counts 1 dwelling and others 0 (AGeneratedZoneCountsOneDwellingWhenItIsADwellingUnit), a split gives fractional counts whose total is conserved (ASplitGivesFractionalDwellingCountsAndConservesTheTotal), validation catches a lost dwelling (ValidationCatchesALostDwelling), a per-dwelling load in a zone without dwellings (APerDwellingLoadInAZoneWithoutDwellingsFailsValidation), and zones on different calendars (ZonesOnDifferentCalendarsFailValidation).
• ProgramConsistencyTests (integration, D-126): a plan generator rejects a per-dwelling preset on a corridor (APerDwellingPresetOnACorridorIsAnError), accepts one on dwellings, and rejects presets on different calendars.
• ProgramPropertyAggregationTests (core, D-126): the aggregation rules and the conservation of installed heat power, people heat, and water heat per hour on random sources (domain-model.md). IdfExtendedProgramMatrixTests (export) runs presets with every program extension through every plan simplifier and floor aggregator to the validated building and the IDF, and IdfProgramJsonTests does the same for the Medium Office program JSON on the office plate.
• InfiltrationOutOfProgramsTests (D-124): every family through every plan simplifier and floor aggregator validates, no zone program has an infiltration load, and no installed or scheduled check is of a type other than a program load type.