Storing and recalling configurations

Hi all,

Is there a way to store a bunch of values from driving parameters of your GH definition and recall them as needed?

Is there a way to associate automatically with a baked object the parametrical configuration that originated it?

Would be most helpful.

Thanks.

Replies to This Discussion

Permalink Reply by Daniel González Abalde on August 17, 2016 at 7:39pm

0) Go to: Solution > Save State, Restore State, Delete State.

1) I think not yet (I was planning to do something similar, it would not be difficult, also about Save State but with components for future versions of Peacock).

Permalink Reply by peter fotiadis on August 18, 2016 at 12:03am

If I got it correctly(?) you want to conditionally store (as persistent data) slider values ("driving parameters" ?? what this means?) in a "history" Tree and then recall them (i.e. getting corresponding values from a given "history" branch) at will. This ability could expand a bit: if a given slider changes then ... desired values are assigned to other selected sliders as well (LOL option: slider changes color to indicate something: say: some visual warning for some critical/incompatible/potentially problematic value etc).

That way you can manage some kind of scenarios for a given solution. I use this approach in the majority of internal defs that supposedly(?) do(??) something "meaningful"(???).

If so it's easily doable via code. Notify if you want a "simple" (kinda) example out of many.

NOTE: since that type of stuff is obviously custom (per case) I would advise to provide a "typical"/indicative case of yours in order to streamline the code accordingly.

Permalink Reply by Aristo Compasso on August 21, 2016 at 5:42pm

Peter, spot on, but also I can imagine the possibility for a component with a number of different configurations / presets added to Grasshopper panel in Rhino. This way we could have just the Rhino window and offer an easy / direct / guided interface for a co-worker / client to evaluate and return feedback.

Permalink Reply by peter fotiadis on August 22, 2016 at 12:45am

Imagine doing some real life load bearing structure using steel members (or some truss or whatever). Imagine having some IPN "generator": i.e. some C# that makes a profile (I could provide a simple example on that matter).

In real life when designing some AEC BIM thingy (using AECOSim + Generative Components + vertical aps) we use RDBMS to choose a profile (same with any "standard" object in use like doors, hinges, facade tiles, cabinets, dry wall systems, aluminum extrusions, equipment, finishing materials, cats, dogs and/or dinosaurs). That said in real life "live" cost estimations are an obvious must.

Now ... forget AECOSim, RDBMS, a variety of vertical aps used in parallel (FEA for instance), dollars and real-life ... and go to GH: imagine values stored in Trees. Say commercial available dimension combos for some steel members (IPE/HEA/IPN/C and the likes). This means that the profile desired can't be anything other than some "standard" one. This means the aforementioned C# gets the values required from a branch instead via equivalent sliders.

On the other hand in some occasions (EVEN in steel members: custom bespoke solutions for "cheapo" big projects) we need the ability to enter "new records" to that Tree (i.e. store them permanently as persistent data and/or export them to some more meaningful storage schema). Therefor we should use sliders in order to control a (valid) new dimension combo. BTW: valid because ... rules must exist since ... well ... its rather obvious, I guess.

On the other hand it's more than possible that other combinations of steel members could be used depending on some parametric solution. This yields families of "possible"/valid solutions and requires some kind of decisions "history" tracking.

On the other hand all that stuff is carried over by teams or groups of teams ... meaning modification permissions and other constrains.

Is this kind of stuff (metaphorically or literally) the thing that you are after?

NOTE: If AEC stuff is your domain (in general) you are dating the wrong girl.

Permalink Reply by Daniel González Abalde on August 22, 2016 at 1:29am

You can do that using "Remote Control Panel" (from View> RCP) and adjusting the definition with the idea of selecting presets using a number.
http://www.grasshopper3d.com/video/remote-control-panel

RSS