Grasshopper, MultiPipe, SizePoints & worked examples …

IN respect of Multipipe’s SizePoints option, in Grasshopper 1.0 Docs the online example uses a grid of squares with node-sizes interpolated across the grid.

While this is clever, it may not be ideal as a first introduction.

In my view, that example would be better if, for instance, it showed how the node size for each of two or three sets of nodes could be specified.

Does there exist somewhere a minimal, worked example of the basic principles of the SizePoints option, please?

I think the key takeaway is that you need to supply an equal amount of radii values within NodeSizefor points used within SizePoints

Do you think it’d be simpler to visualise it as an open curve rather than a grid?

With this example you’d have directly on the piped geometry the node where each radius happen a bit more explicitly but you do end up with the trade-off of not showing the interpolation effect that happens when you have a bigger set of input curves in relation to your NodeSize and SizePoints inputs (which is shown in the original example of the documentation)

Alessandro,

Thanks for your thoughtful reply.

Yes!

I also think that MultiPipe is so capable and is applicable to so many different use cases, that a single example for NodeSize is IMO, not enough as an introduction.

The online example that features a two-dimensional grid may be directly helpful to many, but for a wider audience IMO it packs too much into a single example. Most of its inside nodes connect to four other nodes, but it is unclear for instance, if those nodes could join another layer and have different radii and if so, how.

If only a single example were used, then your one-dimensional pipe illustrates the increasing radii possible in NodeSize more clearly (what was the expression used in the Expression Editor please?).

Daniel Piker’s example half-way down this post suggests that NodeSizing can operate generally in three dimensions. I’d like to know if NodeSize could handle layers of struts radiating from a central core, whose overall shape were like a drum. What I envisage is specifying different Node Sizes for the (a) core (b) struts (c) circles and (d) vertical curves linking four circle curves ~

Absolutely, there’s many ways you can format the data structure of the nodes (points) and axes (curves) to meet any connection rules or relationship you’d like to stablish between them to achieve what you need, and you’re right to assume that Daniel’s example is a good one for your case.

A bit rushed (and there’s better ways you can do this) but In the example below we have a “drum like” structure (albeit, I’ve made it non-symmetric on purpose to show the flexibility of it) where its broken down in 3 horizontal sections, base (red), middle (yellow), and top (green), with their respective nodes, axis and radii (vertical struts in magenta just connect at the horizontal section’s nodes, so we just need their axes, no need to define their radii):

(For the definition, I’ve made one option without proper use of tree data structure as it helps to see what happens on each “section”)


(Below would be my preferred way)

In this example, I’ve chosen to label my structural sections to define in a small way what’s what through Layer and Name so that I can filter them through Geometry Pipeline and run the rest of the operations I need. This part you can define entirely through the definition/algorithm if you wish or you can be even more explicit by creating attributes into the model objects themselves. (if you really need to handle a complex structure/design, I’d highly recommend exploring the latter)

Hope this is helpful.

Form Finding_Drum Structure_AC_18102026.3dm (56.6 KB)

Form Finding_Drum Structure_AC_18102026.gh (57.2 KB)

Do you mean the preformatted text block and font? You can access it through the + icon: (I believe it used to be exposed by default, Discourse must have changed it recently)

Hi Alessandro,

Many thanks, most helpful.

I will study your several, excellent examples carefully.

In respect of my Expression/ Expression Editor query, I noticed your screenshot yesterday included the little Star or Asterisk in front of Count, part of the Divide Curve component.

As it was an image, I wasn’t able to tell if there were an “Expression …” inside the Expression Editor. Perhaps it was just a hangover from something else and not relevant and/or there was nothing inside it!

Oh yes, you’re correct, there is an expression in the Count parameter of “x-1”. I do this because Divide Curve will give you 4 points on a count of 3 (since the count in this case is the curve segments) and I wanted the count input value to match the others.

I should have exposed the expression :slight_smile: .