ven if the number of panels inside each cell varies. The current solution works when the number of panels inside each cell is always two or other same numbers, but it wouldn't work if the number of panels inside frames are different in each cell. It would be perfect, if numbering of panels are automatically added correctly next to the cell number based on the number of panel division instead of feeding the fixed number.
To take an example, let's assume that the cell #80 has three panels and the #81 has two ones. In this case, three panels within the cell #80 would be numbered like 80-1, 80-2, 80-3, while two panels within the #81 would be numbered such as 81-1 and 81-2 automatically. …
ded a circle and been able to draw the two lines and cull out the correct distances but do not know how to pull out those two original lines - the one from the starting point to the circle division + the circle division to the end point.
To recap - I'm looking for a way to have 2 lines = 80" when the direct path between two points is 60". I do not want the 2 new lines to be equal in length but variable lengths.
thanks!
_patrick
…
ragazzi ciao =) , una domanda. Ma i file che vengono nominati nel manuale, dove li posso trovare? Perchè quando ho scaricato il manuale mi è uscito solo il pdf. (es. pag 89)
Added by chiar molino at 11:10am on November 1, 2017
tries, of different types, both annotation objects and curves, won't it be slow to iterate through all these objects for each rectangle?
I use 0.6.X but i'm soon making the shift to 0.7.X…
ve is most impacted by the characteristics of the vector field...If accuracy is not so important, you can use the curve re-sampling components to create a smoothe curve.…
"surfaces" ? Our teacher said to place the truncation according to this relation : Capture%20d%E2%80%99%C3%A9cran%202016-05-01%20%C3%A0%2008.03.46.png I already make the five platonic polyhedrons in Rhino.
Best,
Nastia …
), my script is triangulating slabs by drawing line in a crossreference way. This part was "easy"
What I want to do now is to link those slabs together
ie : if a slab is a surface AxBxCxDx
I want to link A1 to A2, B1 to B2, C1 to C2 etc.
I know it's a simple question of restructuring the tree in my Pshift component, so that I can use the line component with shortest list, and link each of those points.
Any ideas on how to fix that?
Thank you
Simon…
hreads where Thread I solves object A1 and Thread II solves object A2. As soon as A1 is completed, Thread I can move on to object B1 and as soon as A2 completes, Thread II can move on to object B3 (whichever comes first). When both A1 and A2 are complete, we can spawn a new thread (III) to take care of object B2.
If B2 completes before B3, then Thread III will terminate. If B3 completes before B2, then Thread II terminates. Whichever thread is last will pick up execution of object C3. And so on and so forth.
This sort of threading is actually not guaranteed to help much though, as it is likely that the bottleneck components in the network will still need to be handled by a single thread.
A more efficient solution would be to divvy up the execution per component to multiple threads. If you're trying to compute the Curve Closest Point for 10,000 points and your machine contains 4 cores, then we can assign 2,500 points to the first core, 2,500 points to the second core etc.
This approach will actually work when there's only a few bottleneck components and it also means the order in which components are solved is no longer important.
An even more fine-grained approach to threading would be to make the Curve Closest Point function in the Rhino SDK threaded. There's a lot of looping going on in any given Curve CP computation so the curve could be broken up into loose spans where each span is solved by a different core. Then the partial results get consolidated once all threads finish.
The benefit here is that it would be multi-core for everyone, not just Grasshopper components.
The bad news: Some functions in Rhino are not thread-safe. Meaning that data structures such as NurbsCurves cannot be modified from multiple threads at once as it will compromise their validity. You might well end up with invalid curves and quite possible weird crashes. In very bad cases it might even be that a specific function in our SDK can only be running once, so even if you were to duplicate the curve it would still not work.
Until our SDK is thread-safe there can be no global threading in Grasshopper. I don't know where we're headed with this, but I do know that we've started using some threaded algorithms in the display as of Rhino5, so it seems we're at least getting our feet wet.
--
David Rutten
david@mcneel.com
Seattle, WA…
Added by David Rutten at 5:47pm on November 17, 2010