algorithmic modeling for Rhino

Path Mapper Component - what are "placeholders"?

checking out the new path mapper component, I think it's probably really powerful to simplify path remapping operations - could I only figure it out for the life of me!!!

i.e. What are "placeholders", as mentioned in its help file? How do I "define" them, and control them?!

What is the principle behind "lexical operations", and what the relationship between "source" and "target" masks? I cannot penetrate the jargon.. anyone care to explain it in simple terms?

thanks! hugz

Views: 13374

Replies to This Discussion

Ok, I see what you are saying. So then graft the planes and use pathmapper to flatten down one level:

yes, now it's working : 5planes/5set of section with 2 and 3 lines each, but still I'm having problems selecting the set of lines related to the planes, where is the mistake?

yes, thank you, now is very clear.


thanks for your explanation!


thanks for your further specification!

I am beginning to use the software and I have a question about the Path Mapper.

In the very first Path Mapper (image on top) of Sameer's definition he used:

{A;B} (i) > {A} (i)

Let's suppose that you have 5 curves selected in your definition. So you will have:

 - Data with 5 Branches

 - N=11 (as default value from Divide Curve)

 - data structure (0;0) (0;1).....(0;4)

Here the question: WHY?? the points coming out from this Path Mapper belong to the fifth curve (and not the fourth, the third...etc.)?

Thanks a lot!

If you import 5 curves from Rhino, you'll most likely only have a single branch with 5 items in it: {0}(N = 5)

When you then run these curves through a Divide Curve component, you'll get 5 branches, where each branch contains all the points generated by dividing each curve, so if you divide into 10 segments, you'll get:

{0;0}(N = 11)

{0;1}(N = 11)

{0;2}(N = 11)

{0;3}(N = 11)

{0;4}(N = 11)

Where the second integer in the curly brackets refers back to the index of the curve in the original list.

Another way to look at this data is to see it as a table. It's got 5 rows (one for each original curve) and 11 columns, where every column contains a specific division point.


David Rutten

Poprad, Slovakia

Thanks David for your fast and precise reply!! :)

I try to explain my question better.

1. I have my 5 curves running through a Divide Curve component. So I will have the data structure you wrote:
{0;0} (N=11)
{0;1} (N=11)
{0;2}(N = 11)
{0;3}(N = 11)
{0;4}(N = 11)

2. I run the Points that are coming out from the Divide Curve Components through the Path Mapper components with this definition:

{A;B} (i) > {A} (i)

3. I run data coming out from Path Mapper component through:

a) Parameter Viewer component and the result is:

{0} N=11 (data with 1 branches)

b) Point > Panel and the result is:

collection of 11 point (N=11) which is the exactly the same as the collection of point belonging to {0;4} (N = 11).

So, here is the question:

why the collection of points coming out from the Path Mapper {A;B} (i) > {A} (i)  component is the same as the collection of points belonging to the curve {0;4}(N = 11) ?

Anyway ... It 's the first time I ask a question here... so I would like to thank you for what you do with your work! Thank you! You are really great!

This could be a stupid question but how do you obtain a "path mapper" component or where can I download it? i want to simply swap a structure, but the .ghx on this thread is not compatible with my version of grasshopper.
First of all you'll need a fairly recent version of Grasshopper. You can download 0.6.0059 from this site.

Then you can either double click on an empty spot on the canvas and type "Path Mapper", or you can drag+drop a new path mapper from the Logic Tab, Tree panel. It looks like a Red cube on its side (couldn't think of anything better).

David Rutten
Poprad, Slovakia
Attached files are a copy and a reworked GH from Woo Jae Sung 's tutorilal "Grasshopper workshop materials". As part of an exercise, the '(OBSOLETE) Divide Surface' component is replaced by components from the current 6.0059 release.

Gut feeling tells me that 'Path Mapper' could do a much, much cleaner/neater job. Correct?
Is there consolidated material - sample exercises, e.g. - available to get grip on all(?) possibilities of this powerful component?

This thread is inspiring! Thank you all!






  • Add Photos
  • View All

© 2023   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service