polyhedra cells,more specific the Weaire and Phelan structure.https://en.wikipedia.org/wiki/Weaire%E2%80%93Phelan_structure
The size of each cell is 10mm * 7mm.The whole size of the model that I want to create is a box of 160mm * 160mm * 100mm that is consisted by 900-1000 polyhedra. Moreover this model is going to be 3d printed and imported in a software fro thermal simulations in order to test its performance.First I tried to create a model that it is possible to be 3d printed and has some transformations in order to distinguish for the printer the solid and void part.Although I started with creating blocks and groups and using the array and copy command there are a few problems that I am facing.First the file is "heavy" and not easy to manipulate.Secondly as a next step for my model I want to manipulate the size of the polyhedra in order to create a variety of sizes.For example create smaller sizes of polyhedra at the edges of the model or at the planes of the box and larger polyhedra in the middle of the box.Do you have any suggestions on how to proceed?Is modeling in rhino a good option because until now I have spent hours to built this model and it takes hours also to manipulate.I was thinking to try to use grasshoper 3d as a second option however I am not familiar with the software and think that it might take longer to achieve my goal.Do you have any suggestions for a direction to follow in grasshopper in order to develop my model?I am looking forward for your suggestions.I have also attached some images of the model in this mail.Thank you in advance
Kind regards
Valentini…
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…
. etc. So it's 80020 which is ~1058. Assuming you're allowed to use the same component more than once.
1058 × 1049 = 10107 total possible algorithms. When talking about big numbers I only have three frames of reference. The distance from us to the edge of the observable universe is roughly 1029 millimeters, the observable universe contains 1080 protons and the volume of the observable universe is roughly 5×10105 cubic nanometers. So you could more or less put a different valid Grasshopper algorithm into every cubic nanometer of this universe.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
in the .gh-file below. However, it takes a very long time to generate this calculation, even four about five panels or so, while I have about 1600 on the hyperbolic paraboloid. You once told me in another discussion that the TOF component did less calculations than the PV Surface component and would therefore be faster. However, it seems to go even slower when you have multiple surfaces.
So what I would like to know is how to have an idea of which PV panels would be worth of keeping on the hyperbolic paraboloid. For instance, to visually represent the panels with a TOF of >90%, >80%, >70% and so on, without too long calculation time.
(You will have to zoom out quite a bit to see the surfaces. The TOF component is in the red group and there is some part of the code that is irrelevant for this question, but it's quite clear.)…
gn-by-many-designbymany/
The first sponsored challenge is to create a parametric version of Buckminster Fuller’s Dymaxion House.
It would be AWESOME to see it done in Grasshopper! And.. You can win a pretty sweep HP desktop plotter. The deadline is this Friday.
Hope to see you on the site and look for some new GH and RhinoScript videos coming soon.
Thanks,
Dave…
Added by David Fano at 12:28am on December 15, 2010
Data matching is a problem without a clean solution. It occurs when a component has access to differently sized inputs. Imagine a component which creates line segments between points. It will have…
orm of the model but when I try to add the piping to it, I get the message saying Windows has ran out of memory.
I am using Windows 7 and have tried going into the BCD as recommended here: http://wiki.mcneel.com/rhino/memoryincrease but I was not able to run this command.
I have then tried to increase my virtual memory within Windows, even up to 30GB with no luck.
I'm pretty sure I'm doing something really wrong here but I really need to get this modelled ASAP for a portfolio submission.
Any help would be very much appreciated!
Regards
James
…
it we thought our stands will be made with a fixed depth (80 or 90 cm) and incremental heights like 30-32-34-36...cm, and that is the list you have to supply.
The script will iterate over the different possible measures until it finds the smallest one that complies with your desired C value, but it wont be the exact, just the best approximation within your list.
2. Changing this also depends on the combinations of riser height and depth you provide, if you enter 1m and 1m in both lists you will get an 45º slope.
Anyway, getting a fixed-c value script would be easier (much easier than what is already there) but IMO it wouldn't have a direct application in real stadiums unless you are ready to make each stand different from the rest, discarding any pre-cast solution.
Hope this helps.
Roberto…
raries folder, seems that you need plankton.gha.
Unlock, place in folder, restart rhino+gh...
That's all.
To use it... in a basic way:
Input 0. Plug geometry.
Input 1. Set target resolution, actually it refers to the mesh edge length.
Optional input 2 and 3. Sets anchors (as points or curves) for the remeshing not escape of these parts.
Input penultimate. Number of iterations. Here are two ways, the living form, you set a low value (as 5 or 10) of iterations and plug in a timer component (that allows you to see the remesh process); or just add the total number of iterations (I generally use 80, but its relative).
The last input, set false to turn it on, true to turn it off.
For advanced configuration, trial and error, or see the code on Pikers's github.…