grid size 3 = 2.7 mins
grid size 2 = ??? memory peaks and rhino freezes.
However now that I have switch the unit of the rhino file to feet,
now grid size 3 = 18 mins.
which makes i suppose since the analysis will have to work with smaller tolerance.
The below img is what i got after 18 mins. I think also the fact that I have joined the individual units with solid union also make it longer maybe? you can see the mesh triangulation not only around the corners of masses but also inbetween different units (if you look at the top level you will see)
oh, and I also have very little disk space left.
I would like to share the file but right its a big mess and has a lot of stuff that is unrelated to this particular memory issue, like revit interoperability and urban modelling. and the definition is set up so that it needs to have an excel file that feeds what you see on the lower left corner, wing mass scales. In order to compare design studies I am animating the index of list component that feeds the different scale of the wings and the width of the floor plates you see. you can see it in my video here. I will try to clean it up a bit when I get a chance, but it seems like grid size 3 might work as a starting point.
when I get around to extract values from the mesh vertices and actually apply different facade designs driven from the parameters, I would know better what grid size might be necessary.
…
the one-but-last list [4]. After running out of the n- items avalaible it should continue with the second item of list 0 and so on for all items on all the lists.
Intput, six lists of 30 items each
[0] (n=30)
[1] (n=30)
[2] (n=30)
[3] (n=30)
[4] (n=30)
[5] (n=30)
Output, 18 lists of 10 items each
[0],i=0;[5],i=4; [4],i=7;...
[0],i=1;[5],i=5; [4],i=8;...
...
[5],i=1;[4],i=5; [3],i=0;...
I thought perhaps the weave component or the relative tree item component but didn't manage to figure out how to compose the mask. I couldn't find much on how to use these. I guess it should wrap the lists, but not the items.
Any help would be greatly appreciated.…
Added by Thorsten Lang at 2:27am on January 24, 2011
n. We encourage the generation of cutting edge design proposals for a structure of your design with the only caveats being it be generated and conceived digitally, incorporate repetitive elements, be optimized for relocation and transportation and be produced through fabrication technologies available within Houston, Texas.
The winning entry will be built , exhibited and subsequently given to the winner. The design and fabrication of the piece will be commissioned by TEX-FAB and installed to coincide with the TEX-FAB exhibition REPEAT, in February.
Jury: Patrik Schumacher, Marc Fornes, Lisa Iwamoto, Chris Lasch and Blaire Satterfield…
ith is attached. I have a number of curves (this number should be dynamic...i.e. in this case 5, but it could be 18) and two point lists of the same number. What I want is to split each curve (say, curve 0) with the two corresponding points (i.e. 1stPoint 0 and 2ndPoint0), producing 3 resulting curves. Currently, as you can see, that's not quite happening.
This strikes me as a data structure, but I can't quite seem to conceptualize how to solve the issue while still allowing the number of curves/points to be variable. Any help is greatly appreciated!
Austin…
18+17+16+...+2+1 intersections which amounts to 190).
The most obvious performance improvement is to build a 3D tree of all the objects so you can ignore a lot of intersection tests from the get-go (won't help if the objects are wound around each other though). Then there's sometimes tricks you can use to simplify the geometry. Intersecting two Pipes as Breps is FAR more expensive than finding the the closest points between two center curves.
The main problem with these optimizations is that it's very hard to generalise them so that they can be implemented as a Grasshopper component.
However I suspect that even a slow algorithm would be a welcome addition, I'll mull it over and see if I can find some time to add some collision test components.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
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.
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 de 3 jours est de 1050 € HT 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…
para poder parametrizarla - Entender cómo se gestionan los datos con Grasshopper - Asociar formulaciones matemáticas a modelos paramétricos - Panelizar y triangular superficies - Parametrizar estructuras sencillas - Saber deformar modelos tridimensionales paramétricamente - Elaboración de algoritmos simples y aplicarlos a modelos tridimensionales - Exportar e importar tablas de datos
El curso será impartido por dos Authorized Rhino Trainers.
También te informamos de que hemos renovado el temario del curso, preparado específica y exclusivamente por nosotros, y que es revisado y ampliado continuamente, gracias a la experiencia de cursos anteriores. El curso tiene un formato intensivo de 18 horas, cuyo horario es: - viernes, de 16 a 20; - sábado, de 10 a 14 y de 16 a 20; - domingo, de 11 a 14 y de 16 a 19.
Si estás interesado en apuntarte, contáctanos en: cursos@frikearq.com…
points within the bounds of the site boundary and use each location as an attractor point controlling a variable at each point in the grid (radius of a circle/height of a cube/colour based on a gradient etc.).This would be based on proximity to the attractor points with the effect of each attractor point essentially scaled by the percentage associated with it. For example a location with 88% visitor rates would have a more dramatic effect than a location with 26% visitor rates.
I've had a bit of a play around but can't seem to get beyond the point of what is shown in basic point attractor tutorials online. I'm definitely a novice.
Here's how I figured it would be done:
1) Create a grid of source points within a boundary curve.
2) Select 18 pre-defined attractor points.
2) Measure the distance between the source points and the attractor points.
3) Invert this data so that variables increase with proximity rather than decrease.
4) Give each of the attractor points a strength value from 1-100% based on the visitor rates.
5) Use the scaled data to control a variable at each of the source points.
6) Create some way to control the drop-off rate of the effect from each point.
It is at step 3 that I get completely lost.
I hope my description is clear. Any help would be greatly appreciated,
Adam
…
com/Master-2020/
05 October 2021 - 04 October 2022 at Faculty of Engineering - Sapienza University of Rome Registration deadline is 26th of May 2020
Number of students: 20 – 30 students Official language: English Credit hours: 60 CR. Duration: One year of 1180 total hours; 600 for courses and laboratories + 480 for internship + 100 for Final project Place: 9 months in Sapienza University of Rome - Faculty of Engineering and 3 months Internship outside the university
…
ecember 2017 from 18:30 until 20:30. We will have presentations from Heatherwick Studio and AKT II.
Please visit the following page for more details and registration: http://simplyrhino.co.uk/events/upcoming-events/grasshopper-uk-ugm-2017
Heatherwick studio will present two projects covering the topic of designing, making and collaborating through computational tools. Heatherwick’s Geometry and Computational Design team will go through the computational processes behind design and making in the studio concentrating on two projects, Vessel in New York with a focus on driving the geometry and Al Fayah Park in Abu Dhabi with a focus on Form Finding and working with collaborative tools.
AKT II's presentation will explore a series of examples where this new approach was experimented, tested and improved, the Al Fayah Park in collaboration with Heatherwick studio and the 2016 Serpentine Pavilion with BIG, and more.
We're looking forward to seeing you all again!
Many thanks,
Paul and Arthur
…