peration. In other words, it is very easy to accidentally run your computer into the ground if you are not careful.
I looked at your Rhino file an the geometry is perfectly good. The reason why your computer is crashing when you input your geometry is that your Rhino document is in millimeters and the grid size that you input to the Shade benefit component is in Rhino document units (in your case also mm). The Rhino document that I was using in the videos was in meters and, as such, I set the grid size to 0.5 meters, which is a number that gives me a reasonably-sized set of mesh cells in my case. In your case, however, you were inputting your geometry without changing the grid size, which essentially set the grid size to 0.5 millimeters. As you can imagine, this is a huge number of test points and grid cells. Accordingly, it overwhelmed your memory (as it did mine).
Attached you can find a fixed GH file where the grid size has been set to a reasonable value (500 mm instead of 0.5 mm). I also updated the components to the most recent version on the github. There is new an option for a much faster solar-adjusted temperature calculation and a number of other features. These components will be in the stable release that we are doing in the next few days.
Enjoy!
-Chris…
of the possible positions of the staircase, ie. the volume that defines the area within my building that I need to make sure is empty in order to ensure that the staircase will not hit anything as it moves.
The staircase's movement is all governed by one number slider, so my quick fix was to replace that slider with a series component, which gives a good approximation of the volume I'm looking for (screenshot attached, staircase in red volume in gray- you can see that it jagged since the series only has 50 numbers in it, rather than smooth as it would be if it were infinite). The only problem is that I can't really do anything with this volume afterwards since it is made up of hundreds of boxes. When I try to boolean union these objects in Rhino, it fails, and trying to split a plane through all of these boxes to get an outline causes my computer to freeze.
Does anyone know of a way to find the true range of motion volume that I am looking for, or a way of working with the output that I already have that won't cause my computer to freeze?
Thanks!
…
Added by Alex Fortheim at 3:18pm on November 13, 2011
the 'core' of the building
What I want the script/definition to do is this:
- Keep the given points on their place
- create ellipse form balconies
- The different points which create the balconies and plan sections are parametric
- create different plan sections at different heights and loft them
- Differ the placement and size of the balconies
I am trying to achieve something like the skyscrapers by Zaha Hadid (see attached picture).
I want to know how I can create such thing as a parametric plan section, can someone help me getting started with the principle.
I attached my files!
Thanks in advance!
Maria…
erimeter zone but I can't seem to visualize my daylight results. I'm trying to use the recolor mesh component but the number of results points is five times as long as the number of points in my mesh. I can see the source of the error using param viewer - I do have (for example) 100 points in my mesh, but 500 results points from the UDI output. I've included a screenshot of the error, plus a screenshot of the param viewer "mismatch" and my grasshopper file. My gh file is large but I've grouped the problem areas in orange.
My initial guess was that it was calculating daylight results for each zone and for each mesh (5x5)?
I'm also having trouble with my EPConstruction and RADMaterial items. They seem to work initially when I copy them from another file but they frequently "fault out" giving the error to Let Honeybee fly or Update Honeybee. I'll re-update HB, delete and re-add the components and maybe get them working again but it's happened so frequently I'm not sure if there's something else causing this error. …
lla progettazione parametrica e le tecniche di modellazione algoritmica per la generazione di forme complesse
___________________________________________________________________________________
luogo:
Sala meeting Hotel Mercure Milano Centro Piazza Oberdan 12 – 20129 MILANO
Scadenza iscrizioni: 12 Novembre 2011 – ore 15.00
___________________________________________________________________________________
info e prenotazioni:
Le Penseur (coordinamento formazione)
info@lepenseur.it
081 564 21 84
347 548 71 78
quote di partecipazione e programma (formato PDF)
ulteriori informazioni sui corsi PLUG > IT
___________________________________________________________________________________
PROGRAMMA DEL CORSO
GIORNO_01
10.00 – 10.30: presentazione workshop
10.30 – 11.30: introduzione alla progettazione parametrica: teoria, esempi, casi studio
11.30 – 13.00: Grasshopper: concetti base, logica algoritmica, interfaccia grafica
13.00 – 14.00: break | lunch
14.00 – 16.00: nozioni fondamentali: componenti, connessioni, data flow
16.00 – 18.00: esercitazione
GIORNO_02
10.00 – 12.00: funzioni matematiche e logiche, serie, gestione dei dati
12.00 – 15.00: analisi e definizione di curve e superfici
GIORNO_03
10.00 – 12.00: definizione di griglie e pattern complessi
12.00 – 13.00: trasformazioni geometriche, paneling
13.00 – 14.00: break | lunch
14.00 – 16.00: esercitazione
16.00 – 18.00: attrattori, image sampler
GIORNO_04
10.00 – 13.00: data tree: gestione di dati complessi
13.00 – 14.00: break | lunch
14.00 – 15.00: digital fabrication: teoria ed esempi
15.00 – 18.00: nesting: scomposizione di oggetti tridimensionali in sezioni e posizionamento su piani di taglio per macchine a controllo numerico CNC…
rce of power.
A fortified emplacement for heavy guns.
Synonyms
accumulator
And use component:
com·po·nent
/kəmˈpōnənt/
Noun
A part or element of a larger whole, esp. a part of a machine or vehicle.
Adjective
Constituting part of a larger whole; constituent.
Synonyms
noun.
constituent - element - ingredient - part
adjective.
constituent - constitutive
…
n to finding a concave contour polyline (which is in general what you need). In your case each contour section contains a series of points of which you do not know the order and you need to sort them so that by connecting them you find the contour. This is fairly easy to do when the contour is convex (basically you find the average point then calculate the vectors from the average to the points and sort the vectors by angle - sorting the points by the same angle gives you the right order for the contour), but generally impossible to find uniquely when the contour is concave (PS: convex means that, for ANY 2 points inside the figure, a straight line connecting them doesn't intersect with the border curve - i.e. circles, ellipses, rectangles, triangles - concave shapes are a star, a crescent moon, an arrow, a boomerang, etc.).
The problem goes like this: given a generic list of points:
Each of these configurations for a perimeter equally fits the above:
Laurent already went for another possible solution, the stochastic approach (by subdividing the connecting lines), I slightly adjusted a few things over his solution:
namely, I added a rounding option to adjust for some weird tolerance issues (some points that should be at Y=80 were at Y=79.99998 or something) and a more straightforward solution to group them by section plane using sets logic. This, coupled with alpha shape, gives a quite good approach, still very coarse in terms of results but that depends on the sampling resolution of the field (i.e. number of height sections in which you calculate the metaballs) and sampling length of the connecting lines.
Definition attached.…
Diffraction , I left it, how it is.
For the unusual issues that comes in the image source component, so, is it something strange? But, I still have the same issues when I sets any integer component (single or multiple) in the “reflection order” of the image source component, in the “image source order” in the ray tracing component, and again, when I connect the output “Direct sound data” of Direct Sound component in the Energy Time Curve.
Do I wrong something with the integer component? I used it already in the first parts, for sets “grasshopper layers”, in the “Scene” component, but here it works. Should I start with a new file?
For the multi-object optimization, thank you for all suggestions. Yes, I red PHD thesis work of Tomas Mendez and the article “ EDT, C80 and G Driven Auditorium design” and still others. Thank you to all these articles, I decided where to focus my thesis.
I understand the potential of Multi-object optimization, and problems that I can finding without using it. Actually, in the beginning of my thesis, I tried to jet in contact with the Politecnico di Torino, but was not easy because I’m not a Politecnico student.
Here, in University of Florence (Building engineering), there isn’t a department or someone that is already familiar with these field of study, so, as you can image, for design my thesis, I can confide on online resources. So far, my Professor suggest me to begin with a Nonlinear Global optimization like Galapagos, and only after see the multi-object. In this way, step by step if something doesn’t work is easier to understand way and where something is going wrong: if are problems due to the setting of the programs, because we are not practical about these, or if there is a wrong in the simulations or in the algorithm and ect.
Do you think is a good way for go on?
Thank you very much,
Kind Regards
Giulia
…
I'v try to implement your solutions. But I found some bugs (in GH or caused by my code)
So I've create globally two params:
private IGH_Param sensRadiusParam; private IGH_Param grayScaleParam;
and some static method to create new instance of this param (example) :
private static IGH_Param addSensRadiusParam() {IGH_Param param = new Param_Number() { Name = "Sensitivity Filter Radius", NickName = "Sr", Description = "", Access = GH_ParamAccess.item }; return param; }
I'm registering three static Inputs, additional two should be optional:
And in DropDown menu I'm calling this event:
private void MenuSensitivityFilter(Object Sender, EventArgs e) { oParam.UseSensitivityFiltering = !oParam.UseSensitivityFiltering; if (oParam.UseSensitivityFiltering) { sensRadiusParam = addSensRadiusParam(); Params.RegisterInputParam(sensRadiusParam,3); } else { sensRadiusParam.RemoveAllSources(); Params.UnregisterInputParameter(sensRadiusParam, true); } this.ExpireSolution(true); }
So creation of new inputs working great. Also destroying them is fine, but rest of the behaviour is corrupted...
For example, when one of the inputs is created, I cannot connect to it any already existing on canvas object (in my case slider). If I create new object or copy existing one it works. Maybe I need to redraw canvas?
Also removing and adding Inputs in any order cause some mess on canvas... Specially when I remove connected Input.
Here, for example I've created 2 output and remove one...
As you can see, removed input param still exist somewhere... ( i can add connection between inputs slots as on picture, but when I release mouse button connection disappears, slider inheriting Input name and components get orange with warning (no data on input xxxx).. strange).
Sometimes it looks like input get connected with slider, but component warns me about "no data on input xxxxx" or slider is getting wrong name (from different parameter)
Could you help me?
I'm attaching full cs file…