CADFEKO Geometry Faults

A list of possible geometry faults reported by CADFEKO is listed in the section that follows. A short description with a possible solution is also given for each fault.

Corrupt data structures:
The solid modeller is in an inconsistent state. If this model was imported, either the translation failed or the original model contained errors. Please send the original model file (in the original format) to the Feko support team.
Invalid or duplicate identifiers:
This situation usually arises when old Parasolid models are imported.
Missing geometry:
This situation only arises with imported models. The best solution is to select the faulty entity in the details tree and remove it. Note that this entity will not be visible in the 3D view. The geometry has to be recreated.
Invalid geometry:
The fault is usually caused by scaled importing. The best solution is to select the faulty entity in the details tree and remove it. Note that this entity will not be visible in the 3D view.
Self-intersecting geometry or degenerate geometry:
The fault is usually caused by importing and more specifically scaled importing. The best solution is to select the faulty entity in the details tree and remove it. The entity can then be recreated.
Geometry not G1-continuous:
The fault is usually caused by importing and more specifically scaled importing. The best solution is to select the faulty entity in the details tree and remove it. The entity can then be recreated.
Open or non-periodic curve attached to ring edge:
This fault can occur when a model is imported or the stitching tool has been used on the model. Please send the original model file to the Feko support team.
Open or non-periodic nominal geometry attached to ring edge:
This fault can occur when a model is imported or the stitching tool has been used on the model. Please send the original model file to the Feko support team.
Vertex not on curve of edge:
The fault is usually caused by importing and more specifically scaled importing. The best solution is to select the faulty entity and remove it. The entity can then be recreated.
Vertex not on nominal geometry:
The fault is usually caused by importing and more specifically scaled importing. The best solution is to select the faulty entity and remove it. The entity can then be recreated.
Edge reversed:
This fault only arises with imported models.
Nominal geometry in wrong direction:
This situation arises with imported models.
SP-curves of edge not within tolerance:
This fault should not arise. Please contact your Feko support team.
SP-curves not within edge's tolerance of nominal geometry:
This fault should not arise. Please contact your Feko support team.
Vertices of edge touch:
The fault is usually caused by importing and more specifically scaled importing. The best solution is to select the faulty entity and remove it. The entity can then be recreated. Note that it could be that the face has to be deleted to remove the faulty edge.
Faces incorrectly ordered at edge:
The fault is usually caused by importing. It may be possible to explode the part and try to combine the entities again.
Vertex not on surface of face:
The fault is usually caused by importing and more specifically scaled importing. The best solution is to select the faulty entity and remove it. The entity can then be recreated.
Edge not on surface of face:
The fault is usually caused by importing. It may be possible to explode the part and try to combine the entities again.
Self-intersecting face (i.e. edge/edge inconsistency):
The fault is usually caused by importing. It may be possible to explode the part and try to combine the entities again. See self intersecting geometry.
Edges incorrectly ordered at vertex:
The fault is usually caused by importing. It may be possible to explode the part and try to combine the entities again.
Loops inconsistent:
The fault is usually caused by importing and more specifically scaled importing. The best solution is to select the faulty entity and remove it. The entity can then be recreated.
Missing vertex at surface singularity:
The fault is usually caused by importing and more specifically scaled importing. The best solution is to select the faulty entity and remove it. The entity can then be recreated.
Wire-frame edge/face inconsistency:
This could be caused by unions involving wires and faced bodies. Please send the original model file to the Feko support team.
Wire-frame edge/wire-frame edge inconsistency:
This could be caused by unions involving wires and faced bodies. Please send the original model file to the Feko support team.
Size-box violation:
This fault should not arise. Please contact your Feko support team. Please send the original model file to the Feko support team.
Face-face inconsistency:
The fault is usually caused by importing and more specifically scaled importing. The best solution is to select the faulty entity and remove it. The entity can then be recreated.
Body is inside out:
This situation only arises with imported models.
Shells of region are inconsistent:
This fault should not arise. Please contact your Feko support team. Please send the original model file to the Feko support team.
Regions of body are inconsistent:
This fault should not arise. Please contact your Feko support team. Please send the original model file to the Feko support team.
Geometry/topology inconsistency in shell:
This fault should not arise. Please contact your Feko support team. Please send the original model file to the Feko support team.
Acorn shell/shell inconsistency:
his fault should not arise. Please contact your Feko support team. Please send the original model file to the Feko support team.
Unspecified checker failure or checker failure during face-face check:
It should be possible to continue working, but the part may contain faults that cannot be detected. Please contact your Feko support team. Please send the original model file to the Feko support team.
Non-printing character used in name of attribute definition:
This situation only arises with imported models and it should be possible to continue working.
B-geometry has knots closer than the allowed precision:
The fault is most probably caused by importing and more specifically scaled importing. The best solution is to select the faulty entity and remove it. The entity can then be recreated.