, this (or that). That's the difference between 10 minutes of coding VS 100++.
Anyway ... provide the dataset that caused the issue.
In the mean time get the trad update that proves that the pink color is good for the Pink Planet (after Utopia turn left Math.PI/666.0).
Other type of (rather expected) oops moments:
1. Dupes, 2.Closable (but not closed) "final" (see code) profiles, 3. Shortage of cigars (critical), 4."Unexpected" polylines, 5. Loft failure(s), 6. Not "matching" final profiles (N of nodes) ... 666. ...
…
my next step. i want to bake 100 solutions to make an array of 10 by 10 solutions (to render). is there a way to bake several solutions? (like 100 best? 100 random ones? 100 from different branches? ...) would be very helpful. ps. while working on Rhino4 i cannot use octopus at the moment…
with 10 ordered curves. These in turn are to be interated in a move slider( 10 vectors).
As I plug these 3 new grafts in the move slider though, these curves all iterated 10 times (100 curves total) instead of being lifted one at a time.
…
the points with panels.
I am wondering if there is a simpler way to do this so that I don't have to make 100 sections for 100 points?
I attached a small chunk of the file so far to get an idea of what I am doing currently.
Any advice would be greatly appreciated thanks!…
e whole "surface" 10 times along y axis.
I expected that the numbering of the cubes would follow the creation, but no. So, I want element number 1 to be the initial cube, number 10 the last element of the column, 11 the 1st element of the second column, 100 the last element of the last front column etc....
Any ideas??
Thanks in advance …
ndex of the list you want to draw from for that index number.
4. graft the new list of integers
5. use the list item component, with the merged grafted lists into L, and the new list of integers into i.
6. flatten the resulting list.
Example:
list A: list B: list C:
100 200 300
101 201 301
102 202 302
103 203 303
104 204 304
Integer List:
0
0
2
1
2
list item component returns:
100
101
302
203
304
I hope this is clear enough - and close enough to what you were trying to do.
Andrew…
and B inputs. This gives the odd results. I replaced the B Panel with an integer slider and the Pow component works properly.
When I use a Panel for B I get the following results (A panel is 10):
B=0 R=10
B=1 R=100
B=2 R=10,000
B=3 R=100,000,000…
Added by Steven Hall at 7:38pm on September 7, 2010
the join component and then iterates these curves through a move component(10 vectors) all is in order. Yet when I connect more than a single path the order of the generated curves as they are iterated through the move componenet seems to become arbitrary. All the curves connect, meaning Im pretty sure the first curve in path a is connected to the first curve in path b and c, yet this new curve is now curve 5 for instance.
As suggested I have attached a graf tree component which now seperates these curves in different paths before attaching them to the join slider. The result though, as I connect the latter to the move component, is that the ten resultant curves are iteraed 10 times. So 100 curves altogether instead of 10...
Any help would be awesome... Why does the join command destroy the order of the curves even when it seems to be fulfilling its (joning) function properly?
…