manually editing grasshopper components in rhino

Hello guys, I have a theoretical question which might really improve work flow for me and perhaps many more. It ever so often happens that you have a bunch of geometry coming out of a grasshopper definition which you just need to manually tweak a bit before attempting the next operation in Grasshopper. For instance, a bunch of lines where you need to move a few endpoints to meet your criteria which is unique only to few of them. The problem is that when you bake it you lose all the nesting in grasshopper and end up with "dumb" lines. Is there a way to tweak grasshopper geometry in rhino ? I mean control points, end points and things that don't interfere with the grasshopper nature of the object. I know I could replace points and so forth but its much nicer to actually design with a freehand and not write extra algorithms for each case..

Thanks for the help

Replies to This Discussion

Permalink Reply by peter fotiadis on June 25, 2016 at 3:44am

You got it wrongly.

What you actual ask is an ability to modify/manage individual items in collections (whatever these may be: cats, dogs, points, breps ... etc etc). Not nuclear science ... but requires addressing it solely via code.

Spend some time with this demo (out of many) attached and try to get the gist of what I mean.

PS: Write "algorithms" for each case:

Well ... in real life any project worth using parametric stuff ... has a certain fee, he he > thus spending some time (not that much, mind) to do it - or some portions of it anyway - is just a tiny portion of the whole (especially compared with the actual effort/time/cost required in order to deliver the real-life full package [final level studies with regard all the engineering disciplines involved + specs + BOM + you name it ... under some BIM umbrella obviously]).

BTW: Time for "custom"/per case parametric(s) [C# in my case] is less than 5% of the whole Project time.

best, Lord of Darkness

Attachments:

INTERACTIVE_surf_pieces_V2.gh, 221 KB
INTERACTIVE_surf_pieces_V1.3dm, 197 KB

Permalink Reply by kipodi on June 27, 2016 at 12:06am

thanx Peter, helpful as always, I"ll look into it straight away.

Permalink Reply by peter fotiadis on June 27, 2016 at 1:05am

Plan ZZTop: Skype

Permalink Reply by Matt Gaydon on June 27, 2016 at 3:08am

You can use the Geo-Cache Components to send you GH geometry to Rhino edit it and bring it back again with all it tree structure intact. This can be found at Params > Geometry> GeoCache

You can use this both to edit GH data and to delete GH Data, See Srf example.

If you change the data you can just reload it into and out of rhino using the arrows on the components.

Note it will 'Bake' Geo Cache Bakes to Rhino onto the first index in the documents layer table (This may not be visually the Top layer in your layers palette.

Peter, Not everything needs to be done by pure code.. ;) David has written alot of hidden gems as native components over the years. Though not everything i realise, I also code things like camera's and clipping planes and exports still.

Attachments:

Geo-Cache Explained.3dm, 397 KB
Geo-Cache Explained.gh, 37 KB

Permalink Reply by taz on June 27, 2016 at 8:35am

Well I learned something today.

Thanks Matt!

Permalink Reply by Andrew Heumann on June 27, 2016 at 9:38am

Matt's explanation of Geometry Cache is very thorough and useful. I'd also like to add that the Human bake component now supports the embedding of path data in a similar manner to geometry cache - in case you need to have finer control over layers or other attributes when baking. Just right-click the bake component and choose "Preserve Data Trees." To retrieve this information, use a Dynamic Pipeline in tandem with the new "Reinstate Tree" component - this will bring back the data tree organization of the geometry.

One advantage of this workflow is that it listens "Live" so you don't need to manually refresh every time you make a change in Rhino.