Examples of Grasshopper Workflows not using Node Full Names

I’ve been using Grasshopper for around 2 years, still very much a novice, love playing around and find I learn something new everytime I use it.

One hurdle I have faced is that in so many example images and videos, the Grasshopper nodes are not displayed using their Full Names.

I find with so so many node types and different plugins, as a novice, it’s quite dificult to follow the examples, as I have little to no idea what the nodes are.

I appreciate this is a total user preference/experience thing and arguably once you learn the software more you’ll start to recognised more and more nodes.

Curious if anyone else has difficulty with this?

1 Like

As an example, how many people would be able to assist with workflows using the below info/dispay?

Only one of them seems to be a native component… kangaroo remesh by color.

I translated a blueprint to grasshopper.

It was important to reference each blueprint quote to a code and in which plane. A code that is referenced in GH. A point that moves 11.5 mms left or right up to down, etc.

Now, the first thing I noticed is that you need to find a reference point where the whole plan begins in the blue print. I can’t help you with that, it’s parts of industrial engineering 101 - reading quotes but it’s from where all the changes start (this part 4mm this way or that way that is NOT referenced to another moving part). This would be a plane source point [for at least one part] of the model.

This works well if you only have one part - If you have two or more parts (Im building a guitar so my points are the bridge in the body and the nut of the neck - two parts, one distance but it could be the corner of a room for a cabinet).

So I have a source point in the body and a source point in the neck. Each have their own reference XYZ, or their relative position to the CNC’s XYZ = 0,0,0 (or whatever offset you use as G54)

Anyway to keep it simple I use NX1 for Neck X0 position and BX1 for body X0 position, NXY, or NXYZ reference points. I put these references on the blueprint plan and the related GH reference object.

Documenting each part, module group, adding a text note about it will go a long way. If you go back to an old module or file, you will see what is what and hopefully why you changed something in your change history logs.

That’s me after 5 years in GH… I have 100’s of design patterns and one serious project - with full quote references.

Here is one example of my code… Q is the guitar body, I also use N for each N eck part…

Not this this will help you but it’s my link for any measure in the blueprint in the GH model.

Which I learned is not always the right logic to program in GH…

Also wanted to add that working with planes instead of points can have serious advantages but it’s much harder. Do you own experience… It’s definitely not obvious from the start which is better - planes to points work, points to planes can be hardy. I work with points and add planes later which is now right/true to planes… But it really work with multipart blueprints I would say in general.