se the cull pattern, so I wanted to make the pattern using a function component. x=y. x= the original list and y= the interval i wanted to remove. So the pattern should be:
0: false
1:false
2:false
3:false
4:true
5:true
6:true
7:true
8:false
9:false
10:false
etc...…
Added by Rasmus Holst at 3:32am on November 17, 2009
he first problem:
1. Define 7 as the start point.
2. Iterate through the remaining list of points, find the closest point
3. Now, what do you do: find the next closest point from the previous one? Or stick testing from point 7? Note that if you stick with 7, how do you then deal with NOT creating a line between 6? (Or put another way, what will tell the computer its found all the shortest paths and to begin testing from the next set?) If you test each path as the alternative, you will end up with a diagram completely different to what you have drawn in numerous solutions, in fact, they would just be incorrect, not without an exhaustive and overly complex set of conditionals.
You could define zones - circular extents - but that again will produce results differently to what you have drawn, namely connections such as 2 & 3, 2 & 8, 3 & 4, and of course 1 & 2 would be problematic with this approach. Do you see why this isn't as simple to solve using a computer?
Mario, here's your moment....(i hope youre still young, it might take some time, and it needs to work for any possible combination, not just the one above! I'll pass)…
6;i
0;7;i
Level 3 (shown sparse)
0;0;0;i
0;0;1;i
...
0;3;0;i
0;3;1;i
...
0;7;6;i
0;7;7;i
etc...
This will encode the parent-child relationship right into the tree.
Also, if i switch to using individual mesh faces for mesh clash detection then i'll be sorting them as i go (classic space partitioning sort) so i can add an output with a sorted tree for those too.
Also, I would be interesting to output them in Arend's voxel tool data format.
Also, I will add the voxels status to another output - outside is never incuded in the tree (nulls will be placed) but "on boundary" and "inside" will be represented.
Also, the bigger projects requires that the voxels know about their topology - I'll probably include that in this little test but i have to think about the best way to represent it.
Also, I was just looking at David's oct-tree component and hoping that i haven't replicated that function. It will have to wait for tomorrow since the machine i'm writing this on doesn't have rhino on it. The project is still useful for me as it is the data structure that i'm after but as a general component it might be a tad redundant.
Also, right now it accepts a list of meshes but the only uses the first one. I need to fix this.…
fset the original curve in Z axis.
4) Offset my 3rd curve in the Y axis.
5) Divide al the curves into equal segments.
6) Use a cull pattern with "Tue False-False True" Booleans.
7) Connect the culled points.
8) Pipe around the curves.
I dont´s know why my conections go from point 1 to point 2, and instead of keep going from point 2 to point 3, it starts back on point 3 to point 4.
I´m sending the image of what I´m getting, the image of what I want to get, and the definition in case anyone can help me modifying some parameters or components. Thanks!…
ow do you sort data trees with distinctive number of list items in each branch?
In this example, there are 161 branches with three distinctive number of list items, 3, 4, and 5. I want to know if there is another way to sort out this data tree into this way: 3 vertices {0;0}, {0;1}, {0;2],...4 vertices {1;0}, {1;1}, {1;2},... 5 vertices {2;0}, {2;1}, {2;2},...
2. Is there a way to sort our surfaces based on number of distinctive list items automatically? For example, if there are surfaces with 3, 4, 5, 6, and 7 vertices, I want to make five branches with the same number of vertices automatically.
I hope my questions make sense...
Thank you!
Dongyeop …
Added by Dongyeop Lee at 12:14pm on October 3, 2016
ceros.
Public concerné /
Architectes et designers, utilisateurs de Rhino souhaitant paramétrer Rhinocéros à l’aide de Grasshopper, programme
associant des composants et une structure de graphe interagissants avec le modèle Rhino.
Une bonne connaissance de Rhinocéros est nécessaire. La langue de la formation est le français.
Structure et Objectif de la formation /
La formation se déroule sur 3 jours : les 2 premières journées sont consacrées aux « fondamentaux » de Grasshopper
avec en préambule une introduction au design et à l’architecture paramétrique et leurs impacts dans la conception, la
création et la construction.
La troisième journée sous forme d’atelier est dédiée à l’étude de cas concrets proposés par les stagiaires, qui, quelques
jours avant la formation, pourront envoyer leurs projets par mail à info AT rhinoforyou DOT com
Les stagiaires, après la formation, pourront rester en contact avec les formateurs de HDA par le biais du blog
complexitys.com et le twitter @HDA_Paris. La durée de cette formation permettra d’atteindre une autonomie et une
bonne compréhension basée sur des exemples concrets.
3 Formules possibles /
3 jours ( Initiation+Atelier ) : du lundi 20 septembre au mercredi 22 septembre
2 jours ( Initiation ) : lundi 20 et mardi 21 septembre
1 jour ( Atelier ) : mercredi 22 septembre
Programme ind icatif des notions traitéES pendan t la formation /
Introduction à la conception Paramétrique . Rhinoscript, Grasshopper: différences et similarités . Interface
graphique de Grasshopper . Objets, Données, Listes . Opérateurs scalaires : La mathématique de
Grasshopper . Gestions des données : la logique de Grasshopper . Vecteurs, Points, Lignes, Surfaces : La
géométrie de Grasshopper . Listes, Arbres, Branches . Le dessin paramétrique: exercices divers et exemples
. Références, Bibliographie, Support de cours . Ateliers d’architecture et design paramétrique (3ème jour) .
Moda lité de la formation /
Venir avec un PC portable équipé de Rhinocéros version 4.0 SR 7 et de la dernière version du plug-in
Grasshopper (téléchargeable sur www.grasshopper3d.com).
Le coût du stage est de 350 € HT/jour par personne.
Réserver votre place dès que possible car les places sont limitées à 10 participants maximum.
Inscriptions et renseignements: Jacques Hababou, info AT rhinoforyou DOT com
Pour en savoir plus sur l’architecture paramétrique: www.complexitys.com…