ara aplicarlo a la manufactura digital en láser y/o CNC. El taller se desarrolla a lo largo de 5 clases y una presentación donde los talleristas presentarán una pieza cortada con láser o CNC.
LOS PRECIOS SON EN DOLARES. OFRECEMOS PAQUETES CON EL TALLER Y LA LICENCIA DE RHINO COMERCIAL Y EDUCACIONAL…
ld be by no means a general benchmark of all arrays and lists, but it would give an idea of where List<T> and where T[] might be more appropriate.
Here is how you could set this up: on my PC, with 1'000'000 arrays/lists constructions and 50 inner loops on each, "arrays vs. list" has about 1:2 speed relationship, and "array vs. unknown length list" 1:9. You can test on your system and change the tests, too. If you do, remember to build in release mode and "Run without debugging".
- Giulio
____________________
giulio@mcneel.com
McNeel Europe, Barcelona…
asshopper file seem to work but the results are not sensible at all to changes in loads and materials (i tried to put a 1m-thick concrete wall or 50 people instead of 2 and nothing changes inside!). On the contrary if I change the maximum indoor or outdoor temperature for natural ventilation, it ends up changing a lot.
Can anyone take a look and help me? :)
Thank you,
Irene…
ding on the topography of your location you will probably end up with a 10 000 meters mask radius.2) Again you would plug in all the geometry (those blocks) into the context_ input. Depending on the topography of the location, you will probably end up with a mask radius higher than 10 000 meters.But in this case the default value of 0 of the minVisibilityRadius_ input needs to be increased, so that the topography near the location gets excluded. Which is exactly what the minVisibilityRadius_ serves for.To my knowledge there is no paper which describes the exact amount of the minVisibilityRadius_ which needs to be used.ShadeUp plugin for example uses 50 meters of minVisibilityRadius_ by default and 50 000 meters of maxVisibilityRadius_ by default, for objects of a tens of meters in diameter.Something similar can be applied to our minVisibilityRadius_ input. For example: for relatively flat location surroundings one can use minVisibilityRadius_ to be at least 3 times larger than the contextRadius output. For more hilly locations surroundings this value can be increased (6, 7 times of the contextRadius).For example if the contextRadius is 600 meters, minVisibilityRadius_ can be 3.6 kilometers, and so on.Let me know if this answers your questions.…
list of points (only if you have too many points, so that you don't have a big delay)
2. Use a data recorder with a record limit (right click on the recorder to set this) at least twice the number of points and as large as possible to still run smoothly. (I am testing 50 points and have set the record limit to 1000 and it works ok)
3. Use [CullPt] set to "Cull All" (right click again).
4. And test when this list of points will be empty (list length equal to 0).
The accuracy of this depends on the number of points tested(larger=better), the record limit of Data recorder(larger=better) and the T input of CullPt(smaller=better).
If you want to be absolutely sure the simulation has finished completely, you could add another data recorder at the output of [Equality] and use [Mass Addition] to count the number of True's, so you could bake only after you have, let's say, 1000 true's.…
e and i get it. If you have time check the attached papers we published a while ago in relation to the contribution of thermal mass in the reduction of temperature in residential buildings. See the nice contribution of the heavy TM or the lower one for light TM.
As for the solarHeatCapacity, your description (of the 50W) is derived on a 1 Facade/Floor ratio and fully glazed. The only way to reduce it is to increase the ratio (bigger facade area). Which is not recommended (energy losses), but this is a different issue. So, roughly, we can say that 50 is the lower value. If i have less glazing area this number will be higher (right?)
I want to define a value list of "architectural situations", so it is easy to explain and understand. One situation can be:
"Ratio facade/floor 1 & Fully glazed" = 50
"Ratio facade/floor 1 & Half glazed" = 75
"Ratio facade/floor 1.5 & Fully glazed" = 30
"Ratio facade/floor 1.5 & Half glazed" = 50
"Ratio facade/floor 0.75 & Fully glazed" = 70
"Ratio facade/floor 0.75 & Half glazed" = 90
Makes sense for you something like this?
I also defined a value list for the timeConstant like this:
Light Building (Mobile home) = 1Medium-light building (Cement tiles on floor) = 4Semi Heavy Building (Concrete floor + Tiles) = 8Heavy Building (Concrete floors/ceilings + Heavy external and internal walls) = 12
As for the first 5-10 cm effective TM in general my assumption is that you take half of the mass to your space and half to the space above/below you. Will be interesting to do a parametric study on just the thermal mass, uninsulated and insulated to see what the depth limits effectivity will be. Interested in doing such a study together? Can be a nice work even for publishing.
Thanks a lot ... again,
-A.…
within tolerance. If it is than it can be considered as being "On the surface", although if you look closely enough (I'm talking VERY close), then there will always be a gap between a curve that lies on a surface and the surface itself.
Anyway, the Fin command doesn't use a standard surfacing command such as Loft or Sweep 2 rails or something. It constructs the nurbs surface directly, so it can take care of its own sampling. This is something that's likely to be overkill or extremely involved to try and replicate in GH. So if you're going to be using loft to recreate a fin, then throwing a bunch of points at it is pretty much all you can really do. If you throw enough at it (and by enough, I'd say from a couple dozen to about 50, depending on the complexity of the surface), then the resulting surface will be close enough to lying on the original surface.…
(7/32") Diameter.
I want to "Randomly" select 50% of the high lighted points and assign it a new 3/16" Diameter Circle.
I basically want to add a new variable to the field of points I have "baked" out in Rhino.
For some reason the definition that I have isn't working. When I hover over the outputs I have a list of values but when I turn on the circles and center points I only have 2 visible.
What is going on? Any input would be great - thanks. …
possible to send a number back and have the slider reflect that number?
For example:
1. If a number slider is connected to a component that ranges from 0 to 100 would it be possible to set that slider to a point between those two numbers - for example the number 50?
2. If a number slider is connect to a component that knows it's range - can it send that range to the slider to automatically configure it?
Thanks in advance.
NOTE: this discussion is being continued at this link [ here ].
…
n due at the end of march. i am hoping to see if i can do this as a sort of "HIVE MIND" experiment with one or two or more posters to the forum. i have uploaded two files to http://www.formpig.com/nine_bar-FAR and I have the following goals:
1. To "kinematically iterate" various formal building envelopes based upon a 50' x 100' lot that "conform" to the nine bar linkage geometry.
2. This lot would have "setbacks" consisting of two 5' side setbacks, a 10' rear yard setback and a 25' front yard setback. max height on the structure is 32' and the allowable overhangs into the setbacks are 2'. I would like to find a way to use the "nine bar geometry" to construct a series of iterations for "floors", "walls" and "ceilings", which would then be tied to a volumetric (cubic volume), or a total square footage (perhaps based upon two horizontal section cuts) which was based upon a given number that I will provide per local building code.
3. Laid on top of this we would also have "mcmansion ordinance" requirements based upon the pdf enclosed. i expect to have this "tent restriction" data in digital form to upload to ftp shortly.
It would be up to you individually or collectively to determine how best to position this "in the real world" based upon the lot, setbacks, zoning requirements etc. For instance, perhaps the nine bar configuration has its vertices coplanar with the 50' x 100' x 32' envelope restrictions and then the chosen volume is "trimmed' by the setback requirements. Or perhaps the nine-bar configuration is generated completely within the setbacks, or perhaps it is generated 2' outside of the setbacks so as to take advantage of the 2' overhang allowance on the setbacks, etc.
*
Given an opportunity to develop the work in a second phase we would have an opportunity to tie this into various efficiencies such as Bill of Materials (wall floor and ceiling square foot calculations), envelope to volume calculations, solar panel efficiencies (solar orientation and envelope geometry) etc, etc (love to get suggestions for this).
*
I've become /really/ convinced that this would be a /really/ interesting entry based upon my just finishing up Kas Oosterhuis' Towards a New Kind of Building: A Designer's Guide for Non-Standard Architecture". In an ideal world I was hoping that it would be possible to hash this out discussion-wise and then literally passing it around on the list after someone eventually made the first move by tossing out a rough ghx script. My expectation would be to finalize it rapidly in the next two weeks. Something of a contemporary version of a design charette.
However, I realize this may not be workable so if you have experience in this arena and particularly if you think this is a brief that is straighforward enough to be almost literally implemented in Grasshopper, please contact me for any wage and/or contract fee requirements.
I'm getting a bit of a late jump on this but my hope is that with the right participant(s) that I can thrash it together quick enough for the first round.
info@formpig.com…