Clustering a [Python] Component: Input Access Does Not Change

Replies to This Discussion

Permalink Reply by Giulio Piacentino on August 3, 2015 at 11:33am

Hi Stephen,

you just encountered a problem with the automatic creation of clusters.

This user interface (UI) is shown, but it clearly does not make any difference. The 'Access' choice is shown because it is automatically created by the cluster selector algorithm. It re-uses parameter types from the script, so the parameter UI with 'List Access', etc is visualized. If you create the cluster by using cluster input and cluster output, and appropriate parameters, then the buggy interface is not shown.

Were you trying to solve some particular issu, or just reporting a bug?

Thanks,

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Attachments:

• pythonClusterInputAccess-explain.gh, 15 KB

Permalink Reply by Stephen Maher on August 3, 2015 at 1:58pm

Thanks for the reply and explanation, Giulio.

I understand that the cluster inherits the UI via the automatic creation; I was hoping this feature was a functional one!

I'm happy to report a bug, but am specifically looking for the ability to change the 'Access' Param for any given variable input without diving into the cluster. See below for what I mean.

I'm going to take a stab at a script that tries to do this.

Permalink Reply by Giulio Piacentino on August 3, 2015 at 2:05pm

I would really strongly suggest not to do this.
What problem are you trying to solve with this?

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Permalink Reply by Stephen Maher on August 3, 2015 at 2:59pm

Ha. I suppose "curiosity" won't fly in this case, will it?
To explain said curiosity: I have a cluster component that uses a mix of inputs (some are native GH component inputs, others are Python inputs). The Python script formats its own variable inputs and the 'Access' Param is crucial to the output. I'd like to be able to switch between the three options seamlessly. I hope this makes sense.

Permalink Reply by Giulio Piacentino on August 3, 2015 at 3:38pm

Curiosity is fine. :)

I see two issues though:

• you are leveraging the Python UI outside, on the cluster, which really is just a bug which has real reasons to exist, but is really still just a bug. If you use other means, like that switch, then, maybe...
• changing anything that affects solution solving is non-acceptable behavior during a solution. It is possible to do it, though. Only in UI that is outside the solution chain (basically, stuff like Galapagos or custom forms flying on top of everything).

So, if your goal is to explain students/an audience the difference between Item Access, List Access, and Tree Access, I would suggest to just include three components. If you really need the cluster thing, then, in the cluster, add three scripts and switch them on/off in scripting depending on what you are trying to do. You can then have a fourth script that selects the proper output, or use some normal Grasshopper components.

Would that work?

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Permalink Reply by Stephen Maher on August 4, 2015 at 8:38am

Curiosity did kill the cat, however. Haha.

What you wrote above all makes sense. I heeded your words of wisdom and found a work-around for what I'm trying to achieve. See below for the personal User Object I'm working on; hopefully it illustrates why I was hell-bent on having direct and easy access to the 'Access' param.

I can imagine I'll start to run into issues once the initial tree is a messy one (i.e. has branches with different path lengths, etc.). I'll cross that bridge when I get there, I suppose.

I did try to change the 'Access' param via Python scripting but couldn't really get it to work. I'll keep at it.

Thanks for the help,

/SPM

Permalink Reply by Giulio Piacentino on August 4, 2015 at 9:18am

Hi again Stephen,

this is how I would approach the never-met-before case of needing to deal with datatrees, lists and items at the same time.

I hope this helps,

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Attachments:

• three-modes.gh, 8 KB

Permalink Reply by Stephen Maher on August 4, 2015 at 9:28am

Oh, man. I wish dealing with all three was never needed, aha.

Thanks for the script, Giulio. I ended up doing something similar in one code by making the 'Access' switch a boolean toggle (I was only using 'List Access' and 'Item Access', so it suited my needs).

Your method is very slick; thanks!