Grasshopper

algorithmic modeling for Rhino

I have problem with data matching. I want to get a list of lines from two lists of points.
For some reason changing from Longest list algorithm to Shortest list algorithm (which is what I want) does not give any changes in which Grasshopper matches data.

Is the reason for this because I am trying to match points with different number of branches?
Take a look:

[img]http://imageshack.us/f/706/datamatching.jpg[/img]

First list of points has following branches - A:
{0;0;0;0;0;0;0}
{0;0;0;0;0;1;0}
{0;0;0;0;0;2;0}
{0;0;0;0;0;3;0}

and second list of points B:
{0;0;0;0;0;0}
{0;0;0;0;0;1}
{0;0;0;0;0;2}

What I want is to remove that last branch in list A: {0;0;0;0;0;3;0}
I though I will succeed to do that, by using the Shortest list alhorythm, but as I said, nothing changes, when I switch from Longest list algorithm to Shortest list algorithm.

Is the problem in different level of branches - A list has 6 subranches, and list B has 5?

How can I solve this?


Thank you for the help.

P.S.

I am apologizing for not being able to attach the files, and images. Something is wrong with my PC.

Views: 722

Replies to This Discussion

Maybe some of users can not see the attached image from imageshack.
I will reattach it here:

Any opinions about this problem?

Data Matching such as Shortest List, Longest List and Cross Reference only applies to the data inside branches, not to the way branches are combined themselves. In fact, Data Matching is gone come 0.9.0001, the functionality is been put into dedicated components (see this post for further details).

Different branches are always combined using Longest List logic. I'm unhappy about this as well, I need to give more control over how different branches are combined, but I haven't figured out yet how to expose such functionality without it being utterly incomprehensible to 99% of the users.

If you want to ignore the data inside the fourth branch, you'll need to remove that branch before the data goes into the Line component. It's easy to remove a specific branch, somewhat trickier to make this removal dependant on variables elsewhere in the network.

You can use the Split Tree component to achieve this either way. Using a fixed mask (like in the image below) may be sufficient.

The !3 means that any branch is allowed except when it has a 3 in that location. The [0-2] means that only branches which have a number in between and including 0 and 2 will be allowed.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Thank you David, worked perfectly.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service