Compose a wet zone's plumbing into an independent fluid domain.
This is the seam that keeps one model of moving water. The service graph
states where water is delivered and where it is taken away; the shallow-water
domain states how it then moves. Rather than inventing a second, weaker
account of flow inside the building record, the zone's supply ports become
the domain's declared sources and its drains become the domain's declared
drains, at the lattice cells they actually stand over. A basin that fills,
overflows and empties is then the fluid solver's ordinary business, and its
mass ledger is the same one every other domain is checked with.
The sill of a derived drain is the bed elevation of its own cell, which is
what a plain floor gully is: it opens the moment water stands on the floor
above it. A weir with a raised sill is a different fixture and is authored on
the domain directly.
Every supply inlet in the room becomes a source, including the inlet of a
fitting that merely passes the medium on. That is not a double count: such a
fitting declares 0, so it lowers to a source that delivers nothing, and the
water is counted once where it is actually drawn. Dropping those inlets by
node kind would instead make kind decide a hydraulic quantity the port's
own demand already states.
The network is expected to have been validated already; this lowering answers
only for the placement it performs, not for the graph it reads. Selected
plumbing inlet system and port units must both be cubic-meter-per-second;
other units throw because network admission permits nonvolumetric "other"
media, while this seam performs no physical unit conversion.
Refuses rather than repairs. An unknown zone, an unknown drain node, a node
standing off the lattice and a derived id that collides with an authored one
each raise, because every one of them would otherwise produce a domain that
silently conserves the wrong amount of water.
The returned domain shares unchanged grid, bed and authored entry records;
only source/drain arrays and derived entries are new. There is currently no
production caller for this composition, only service drainage tests.
Compose a wet zone's plumbing into an independent fluid domain.
This is the seam that keeps one model of moving water. The service graph states where water is delivered and where it is taken away; the shallow-water domain states how it then moves. Rather than inventing a second, weaker account of flow inside the building record, the zone's supply ports become the domain's declared sources and its drains become the domain's declared drains, at the lattice cells they actually stand over. A basin that fills, overflows and empties is then the fluid solver's ordinary business, and its mass ledger is the same one every other domain is checked with.
The sill of a derived drain is the bed elevation of its own cell, which is what a plain floor gully is: it opens the moment water stands on the floor above it. A weir with a raised sill is a different fixture and is authored on the domain directly.
Every supply inlet in the room becomes a source, including the inlet of a fitting that merely passes the medium on. That is not a double count: such a fitting declares
0, so it lowers to a source that delivers nothing, and the water is counted once where it is actually drawn. Dropping those inlets by node kind would instead makekinddecide a hydraulic quantity the port's owndemandalready states.The network is expected to have been validated already; this lowering answers only for the placement it performs, not for the graph it reads. Selected plumbing inlet system and port units must both be cubic-meter-per-second; other units throw because network admission permits nonvolumetric "other" media, while this seam performs no physical unit conversion.
Refuses rather than repairs. An unknown zone, an unknown drain node, a node standing off the lattice and a derived id that collides with an authored one each raise, because every one of them would otherwise produce a domain that silently conserves the wrong amount of water. The returned domain shares unchanged grid, bed and authored entry records; only source/drain arrays and derived entries are new. There is currently no production caller for this composition, only service drainage tests.