Grasshopper

algorithmic modeling for Rhino

Well...

...after searching here I've sampled all the available (legacy and new) ways to split a surface (i.e. brep) with curve(s) via some sort of script. 

However in cases 2,4,5 things are not working as expected (especially as regards "copying and pasting" Giulio's Python code - 4,5).

Any ideas?

BTW: Although I have a great respect for all GH developers ... I would strongly suggest to look at Generative Components (8.11.09.459 and on) as regards the whole script approach, related GUI, accessing methods/classes, samples, testing/debugging etc etc etc. Of course the process of learning scripting on a per CAD app basis is akin to learning any new CAD app ...  but compared GH scripting VS GC scripting ... appears to be harder.

BTW: In some smoke (i.e. pre Beta) future fully parametric/feature MCAD app there's a rather working effort to optionally expose the "code behind the tool" - even with drag and drop in some sort of "canvas". They predict that extensive scripting would become a trivial "must" within the future CADD workflow ... and they prepare accordingly. See Modo 8.xx as well.

best, Peter

Views: 1040

Attachments:

Replies to This Discussion

Hi Peter,

Apart from few typos (solution4: missed "b" in line 10 ("face" instead of "bface"); solution5: missed "t" in line 4 ("SpliSurfaceWithCurves" instead of "SplitSurfaceWithCurves")) I think the reason why solution 3 is working, and the other ones are not is because solution 3 component uses an older version of ghpython.

Not sure if support for surfaces should be added to the rs.coercebrep() function too:i

if isinstance(geom, Rhino.Geometry.Surface): return geom.ToBrep()

Giulio am I missing something?

When you do not define your input as ghdoc, but rather to their respective types, you do not need to use the rs.coerce functions. Check example 5b.

Haven't been using Generative Components, so can't comment on that.


By the way, love your replies related to structural issues Peter!!

Attachments:

Hi djordje,

Mille grazie for locating the typos (blame 12.34 am) . Indeed 5b appears to me the way to go. I'll be back with a similar case soon (hopefully without typos).

take care, Peter

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service