Enum SystemAnomaly 

pub enum SystemAnomaly {
    Dangling {
        relation: EntityId,
        missing: EntityId,
    },
    ZoneMemberNotSpatial {
        relation: EntityId,
        zone: EntityId,
        member: EntityId,
        type_name: String,
    },
    ContainedTwice {
        element: EntityId,
        first: EntityId,
        second: EntityId,
    },
    PortAttachedTwice {
        port: EntityId,
        kept: EntityId,
        rejected: EntityId,
    },
    NotAPort {
        relation: EntityId,
        entity: EntityId,
        type_name: String,
    },
    NotASystem {
        relation: EntityId,
        group: EntityId,
        type_name: String,
    },
}

A system membership the file states but cannot support.

Anomalies are collected instead of rejected: a file with one broken relationship still has a usable system graph, and refusing the whole model would make the crate useless on real exports.

Variants

Dangling

A relationship names an entity that is not in the file.

Fields

relation: EntityId

The relationship entity that made the claim.

missing: EntityId

The id it named.

ZoneMemberNotSpatial

An IfcZone member that WR1 does not permit.

WR1 restricts zone members to IfcZone, IfcSpace and IfcSpatialZone. Anything else makes the file invalid, so it is reported and excluded rather than silently listed as zone content.

Fields

relation: EntityId

The IfcRelAssignsToGroup stating it.

zone: EntityId

The zone.

member: EntityId

The member WR1 rejects.

type_name: String

Its type, for diagnosis.

ContainedTwice

An element contained by two different spatial structures.

ContainedInStructure is SET [0:1]: an element has one home. Two cannot both be true, so the first by id wins and the conflict is stated rather than silently resolved.

Fields

element: EntityId

The element with two homes.

first: EntityId

The structure kept.

second: EntityId

The structure rejected.

PortAttachedTwice

A port is attached to two different elements.

IfcPort.ContainedIn is SET [0:1] in the schema, so this cannot be expressed by a valid file. It happens when an exporter writes both an IfcRelNests and a legacy IfcRelConnectsPortToElement that disagree. The first attachment in file order is kept so the result stays deterministic, and the conflict is reported rather than hidden.

Fields

port: EntityId

The port with two owners.

kept: EntityId

The element that was kept.

rejected: EntityId

The element that was rejected.

NotAPort

A connection names a port that is not an IfcPort subtype.

IfcRelConnectsPorts is typed to IfcPort in the schema, so this is a malformed file rather than a modelling choice.

Fields

relation: EntityId

The relationship entity.

entity: EntityId

The entity it named as a port.

type_name: String

That entity’s declared type, upper-cased.

NotASystem

IfcRelAssignsToGroup whose RelatingGroup is not a system.

The relationship is shared with every other kind of group, so a membership may legitimately point at something this crate does not model. It is recorded rather than silently dropped.

Fields

relation: EntityId

The relationship entity.

group: EntityId

The group it named.

type_name: String

The group’s declared type, upper-cased.

Trait Implementations

impl Clone for SystemAnomaly

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for SystemAnomaly

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Eq for SystemAnomaly

impl PartialEq for SystemAnomaly

fn eq(&self, other: &Self) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for SystemAnomaly