Pie Chart

Hi everybody! :)

Sorry, but how it works the new "Pie Chart" function?

Replies to This Discussion

Permalink Reply by David Rutten on March 3, 2010 at 6:08am

Feed it a list of Strings, and it will group similar Strings together into single pie segments. If you feed it multiple lists of strings, it will create a multi-banded chart.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Evan C on March 3, 2010 at 7:15am

the pie chart and bar graph charts are really useful, but one thing i would love to see is some output parameters from the graphs... for instance a list of unique values in the input, and a list with the # of input items with that value.

so if i gave the pie chart a list like this:

1.0
4.5
4.5
0.0
4.5
7.0
0.0

the two output lists would be:

0.0 - 2
1.0 - 1
4.5 - 3
7.0 - 1

GH must be doing this calculation, otherwise how would it build the graph?

Permalink Reply by Benjamin Golder on October 27, 2010 at 12:14pm

yeah, a unique value histogram would be super useful in tons of situations. I completely agree.

This actually brings up something I've been thinking about a lot lately, which is how to represent key/value pair combinations in Grasshopper generally. This comes up a lot, since key/value pairs are great for storing attribute data, and so far I have always taken a two list approach to representing this kind of information, possibly keeping those two lists as branches in the same data tree. Does anyone have any recommendations of how to manage key/value information?

In the very long term, I wonder if there isn't some way that grasshopper lists could get a little bit more 2d, and incorporate such data structures. The branch and tree structure is great, but they seem bulky for key/value pairs, or lists of attributes associated with items. But maybe I'm overlooking some obvious working methods.

Permalink Reply by taz on October 27, 2010 at 2:28pm

If I follow what you're saying I think you can use braches for storing values, but you'd need a separate index that correlates to the branch names. I never thought to try it in the same tree. But yeah, a lot of (sometimes mind bending) tree work...

I noticed that the [ u t o ] mesh tools will let you tag meshes with attributes, meaning you could also (probably) use geometry to help manage key/value pairs.

$0.02

Permalink Reply by Benjamin Golder on October 27, 2010 at 4:07pm

I know that storing and retrieving key/value pairs is easy with the sdk.
But I think the real question is a GUI one: what is the most elegant and easy way to manage and view key/value attributes from a user point of view?
Would a two-column table make sense in this case? How would it interact with other tools, like the list a data tree tools? It seems problematic, but there might be some reasonable solution here that would be really helpful.

I just made this user text component, and I wonder if I should just try to make one that reads and writes user text with grasshopper geometry, rather than just rhino objects.

What if the panel objects could snap together into a table-like object?

Permalink Reply by David Stasiuk on October 27, 2010 at 2:49pm