Skip to main content

Module relation

Module relation 

Source
Expand description

Cost item nesting and control assignment.

§Two different relationships, two different meanings

IfcRelNests             cost item -> sub-items      (the breakdown tree)
  4 RelatingObject      the parent
  5 RelatedObjects      LIST of children, order significant

IfcRelAssignsToControl  cost item -> products       (what it prices)
  4 RelatedObjects      SET of assigned objects
  5 RelatedObjectsType
  6 RelatingControl     the cost item

RelatingControl is slot 6, not 5: IfcRelAssigns contributes both RelatedObjects and RelatedObjectsType before the subtype’s own field.

§Why nesting needs a cycle budget

IfcRelNests has a NoSelfReference WHERE rule, so a file cannot state that an item nests itself directly. It says nothing about longer cycles: A nests B nests A satisfies every stated rule and is what a naive recursive total does not survive. Depth is therefore bounded and a cycle is reported as data, not discovered as a stack overflow.

Enums§

CostAnomaly
A nesting the file states but the schema forbids, and how it was resolved.
CostRelationError
A refusal to resolve a cost relationship.

Constants§

MAX_NESTING_DEPTH
The maximum nesting depth walked before reporting a runaway tree.

Functions§

children_of
Direct children of a cost item, in authored order.
controlled_by
Objects a cost item is assigned to price, via IfcRelAssignsToControl.
controls_of
The controls assigned to an object: the inverse of controlled_by.
descendants_of
Every descendant of a cost item, depth-first in authored order.
nesting_anomalies
Second parents the file states for nested items, in file order.
parent_of
The parent of a cost item, if it is nested.
parents_of
Every parent claiming this item, for detecting malformed multi-parenting.