is you are not searching for a value in a list you are searching for that specific item. i.e. "3" written in the panel is not the same "3" that exists in computer memory at index 3 of the list.
Try using [Find Similar Item] instead…
ese are some examples.
https://n-e-r-v-o-u-s.com/blog/?p=3983
https://mathematics.culturalspot.org/asset-viewer/10-000-circles-1/YgHExQHhZyL5_Q?exhibitId=QAJCFieRlsF8Lw
Thanks for the insight.
Shynn…
yes choosing the right frame, according to body size, can make a big difference, especially in cases like this 100km route with 500m ascent.
btw this website is pretty nice for bike trails etc.
tead of hexagons, that is.
Q: Should I add the include the "portions" of hexagons option as well ? (It's just 3 lines of code more + a bool control).
BTW: for the present time use the V3 not the V2…
ere:
http://www.grasshopper3d.com/forum/topics/finding-the-neighboring-cell?id=2985220%3ATopic%3A135232&page=3#comments
Your posts helped me a lot to get to the point where I'm now. But still I'm trying to fix the problem posted above. I need to know for every surface in a brep the angles to the adjecent surfaces. This works almost fine and the third vector w helped alot to decide which direction to measure. But due to the strange geometry of srf 1 the centerpoint lies very high and once the angle between uw and vw is >90° and on the other srf <90°. Therefore I got at this points both angles.
I thought about to filter this points by measuring also the angles between u and v to a reverse vetor of w (lets call the reverse w'). If I got then two different values for uw and uw' I found the positions where the angles measuring is not correct.
Or is there a smarter way to do it?
Could I ask, if you could share your old grasshopper file you created here:
http://www.grasshopper3d.com/forum/topics/q-specific-pairings-from
Thanks!…
2006 and only supports Windows 2000 Service Pack 3, Windows 98, Windows 98 Second Edition, Windows ME, Windows Server 2003, Windows XP Service Pack 2.…
image with shows some simple usage of the path mapper.
The points worth noting are the following:
1. The "Source" is comrised of a single line notation which EXACTLY matches the existing path structure. This means that if your parameter viewer shows you a path strcutrure which looks like {0;0;0;1;0} (N=4), your source input should look like {A;B;C;D;E}(i). Here, all the letters A-E and i are placeholders meaning that they can be any letters and are standing by for each digit in your path structure. This also means that they could be any letters: {Q;R;S;T;U}(V) would work as well as {A;X;T;B;S}(J). The important thing is that you are identifying each digit (including the value of 'N', the total items in each path).
2. The "Target" is (obviously) your desired path structure. If you want to simply get rid of the zeros while maintaining essentially the same path structure, it is as simple as dropping out those placeholders while writing the target notation. In the above example, if your source is {Q;R;S;T;U}(V), you can use a targe like {S;T}(V) to return a structure which will be {0;1}(N=4) or {T}(V) for {1}(N=4) and so on.
3. if you want to swap the path structure, i.e. if you have 5 paths with 10 items each and you want 10 paths with 5 items each, you switch the placeholders in the source and target notations. for example, {X;Y}(n) -> {n}(Y)... and so on.
I hope that the above is of some help. Please feel free to keep asking.…
Added by Sameer Kumar at 10:29am on December 7, 2009