Help using Brep plane to find normal to surface

Precursor, I am still learning grasshopper …

My overall goal is to create a horizonal lattice that is driven by section curves below them. My approach was to create the section lines in rhino, then in grasshopper divide those curves, take those points and draw new lines from those points. Then I want to loft a profile along those lines that stays normal relative to the surface these section lines create.

I am trying to find the normal vector to this surface at given points. My goal is to rotate the planes so they are normal to the surface at that point. Any suggestions on how to achieve that would be much appreciated.

I used the Brep Plane component to slice the surface at those locations. However the component does not seem to like it. Is there a better way to approach this?

Any input is much appreciated



MNO_1.3dm (138.1 KB)
MNO_1.gh (24.6 KB)


MNO_1_revA.gh (29.5 KB)

If by that you mean a W Truss (truss with “thickness” as opposed, say, to some Geodesic truss) see attached - but only as an indicative guide line (unless you are familiar with C# or you have plans to be).

Mesh_ToTruss_For_Amateurs_Intro_V1A.gh (138.8 KB)

Tips:

  1. Use a Mesh out of BrepFace.
  2. Avoid that type of thing if you are not prepared to fully solve it. And this means full connectivity between truss vertices and axis. Connectivity is your weapon for resolving - via trigonometry - clash issues (rather the norm for the general case).
1 Like

Thanks Rajeev2 for the help, this is exactly what I was attempting to solve.

That is definitely too complicated for me.

this is amazing solution
well if i have some column at specified locations how to modify it based on it
Regards
rajeev

@mohammed_dahodwala

You mean that you want an attractor pull result (i.e. “big local gradual W amplitude” ) in order to continue with some sort of column? (usually a truss as well).

Like:


1 Like

Mesh_ToTruss_For_Amateurs_Intro_V1A_with columns.gh (143.9 KB)

Nice !!

A few notes:

  1. The very simple C# posted is not written having WOW columns in mind. It’s just an intro after all (and an Interview case as well). I have other far more complex things for similar - real life - solutions (using a vast variety of attractor related params/options/checks).
  2. AVOID at any cost combining a double curvature “airy” truss with plain columns (i.e. straight pipes and the likes > an aesthetic disaster is a given). This means: never mix 2 totally different topologies
  3. ALWAYS use a truss as intented: big overhangs and the likes. Otherwise why bother?

1 Like