Error: EDGECOIN_PROBLEM - system inconsistency processing edge coincidence

[jnoordzij]

Does anybody know or understand this error:

EDGECOIN_PROBLEM - system inconsistency processing edge coincidence.

I don’t understand it. What is going on?

[jnoordzij]

Nobody?

[jnoordzij]

Found a similar topic. Says it’s unlikely an easy fix…

Solid.ByUnion Error

[image] I would like to combine all elements’ solids into one solid. But when I used ‘Solid.ByUnion’ node, the error comes out (EDGECOIN PROBLEM). I already tried to explode all element solid into surfaces and re-joined it, but the outcome was same. Anyone who had the same problem??

[jnoordzij]

Another similar topic. Also still unsolved

Intersection Issue between a Polysurface and a Mesh: EDGECOIN_PROBLEM

I have a mesh (input “geometry”) and a surface (input “other”) going into a Geometry.IntersectAll. It is giving me the error “EDGECOIN_PROBLEM – system inconsistency processing edge coincidence.” I have run a Geometry.DoesIntersect node on the same inputs with a List.FilterByBoolMask and it gives me the right configuration without cutting the excess lines. I cannot find any information on the error to determine the issue. [image] This runs a mask to find the intersecting geometry but doesn’t t…

[lucamanzoni]

It seems that your geometry is too complex and somehow cannot be used for boolean unions.

Instead of creating families from the project environment, you can work in the family environment and then import it in the project. In this way you don’t need to merge solids.

You can use Springs.Form.ByGeometry to convert (“bake” in grasshopper) from Dynamo to Revit geometry, apply the material and then load in the project.

[jnoordzij]

Thanks for your reply, @lucamanzoni. Just 1 question, can you explain me why it is called a ‘boolean’ union, or a ‘boolean’ operation? I see this term often but do not really get why it’s called ‘boolean’.

[lucamanzoni]

Boolean operations are operations involving boolean variables, which can be only TRUE or FALSE.

Those operations are:

• AND: when A = True and B = True, give TRUE, otherwise FALSE
• OR: when at least A or B are TRUE, gives TRUE, otherwise FALSE
• NOT: gives the opposite, so when input is TRUE gives FALSE, and viceversa.

The operation of solid UNION, SUBTRACTION and INTERSECTION are the geometrical equivalent of these booleans operations:

• AND = INTERSECTION: it gives the portion of space that is shared at the same time by the 2 solids
• OR = UNION: it gives the portion of portion that belongs at least to one of 2 solids
• NOT = SUBTRACTION: it gives the portion of A that doesn’t belong to B

You can also find here more information:

Boolean algebra

[jnoordzij]

Thats very clear thank you!