1. Face[0] in the brep cannot be represented by a triangle or a quad

Hi all,

I am working on creating this mesh pattern (for later finite elements analysis) which creates the points, makes surfaces between the points, then turns all the surfaces into single-face meshes before joining everything together.

Except at the last step, the grasshopper component gives Face[0] in the brep cannot be represented by a triangle or a quad. as an error message.

The weird part is that it doesn’t seem to impact the output, the final joined mesh is created perfectly and does not seem to have any issues.

So I was wondering on what was the issue, how to fix it and does it need fixing (still, having an error code in my file is annoying, even if it works in the end)

please find the grasshopper file below (no rhino file is provided as this script does not need inputs from the rhino file to work)

thank you all in advance for your help

0227_IBO_mesh-log-grasshopper.gh (22.6 KB)

I think with Triremesh you could achieve something similar with a much less complex process.

What are your requirements for the mesh?

0227_IBO_mesh-log-grasshopper_triremesh.gh (28.4 KB)

1 Like


:cry:

Useless component.

It must do something important?
:roll_eyes:

yes of course but it could be done with a native component.

The first list of surfaces has invalid surface segments along the perimeter of the circle.

sorry, I wasn’t aware it was a plug-in component, Martin’s replacement works fine in this case (personally I used to make a quick python script)

come on, it is quality of life. Its not a huge deal to connect two wires instead of one, but when you need it all the time it becomes really annoying. Generating list of indices using series component is even worse.

2 Likes

As usual - but without posted code, I’m helpless. Not that I have anything to add.

all the relevant code is included in the .gh file

It’s just a list item component. I have not contributed anything else.

The error in the script is because of invalid surfaces caused by duplication of the outermost set of points. This here works:

0227_IBO_mesh-log-grasshopper.gh (36.7 KB)

1 Like

I don’t get it, but again, I don’t need to.

Sorry @Joseph_Oster, ‘Item Index’… The loading error showed a Pufferfish component name ‘List indices’.

Oh, thanks. But I won’t bother to follow the code.

I’m OK with ignoring code that uses missing plugins

If I can add something, you can use the same circles for the feature instead of deconstruct and reconstruct them

1 Like

I thought by using polylines instead of circles I get the vertices along the circles exactly where they should be

1 Like

Thanks to @martinsiegrist for the hint on the solution:
the issue was indeed that, among the two lists of circles between which we were creating the meshes, one of the list had one index too much

there’s a corrected version:
(although in this one there is some curious bug making the mesh messed up at 6 and 11 rings specifically, gotta look into that later)

0227_IBO_mesh-log-grasshopper.gh (22.6 KB)

After all of that, you still use Pufferfish :interrobang:

And the filename hasn’t changed for this version.
:frowning: :-1:

I believe I have replaced the pufferfish part with Martin’s method