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 itemRelatingControl 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§
- Cost
Anomaly - A nesting the file states but the schema forbids, and how it was resolved.
- Cost
Relation Error - 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.