ed four workshops, each featuring a partnership of a creator of hardware technology and a software developer. The outcomes of the four workshops will form a single structure.
Workshops:
1. Facade panels with RoboFold & Kangaroo/Lobster
2. Cantilever CNC wooden lattice with Archiwaste & SMART Form by BuroHappold
3. Corian freeform surfaces by Cutting Edge & Evolute Tools
4. Milled foam and cast concrete with Cordek & Galapagos/David Rutten
Book on the Shape To Fabrication website or via SimplyRhino on 0208 498 9900. Tickets are limited to 10 per workshop at £500+VAT (professional) and £400+VAT (student).…
Added by Gregory Epps at 5:15am on September 29, 2011
eds 14 sec to calculate, wich is really long.
Here is my script, where ddf is the list of list, and elts a list of Point3d.
For i = 0 To elts.Count - 1 For j = 0 To ddf.Count - 1 If elts(i).From = ddf(j)(0) And elts(i).To = ddf(j)(1) Then tabElts(i, 2) = ddf(j)(2) ddf.RemoveAt(j) Exit For End If Next Next
If I decompose my list of list into a list of point3d and a list of integers, the calculation time drastically decrease (0.27 sec), even if the number of loops is 2.5 times higher (724 500).
I would prefer to use the first script, as it uses less loops, but it is too slow (my test concerns a mesh with 441 points, but I am going to use this for much bigger meshes). I don't understand why. Is it to be known that the use of list of list of different types of objects is very time consumer ? Did I make a mistake in my script ?
Thanks for your help…
ated in all editions of Architektura Parametryczna Workshops!Architektura Parametryczna Workshops Optimization Warsaw 2016 FAQWHEN?21-22nd May 2016 (Saturday-Sunday)HOW LONG DO THE WORKHSOPS LAST?The workshops last in total 16 hours.Saturday 10AM -7PM (with lunch break), Sunday 10AM -7PM (with lunch break)WHAT WILL I LEARN?On Saturday the optimization processes with solar, views and structural analysis will be explored. We will be discovering optimal solutions with the help of plug-ins such as Galapagos, Silvereye, Octopus, Karamba and Ladybug. In the Sunday morning we will learn how to present the results of the optimization: creating catalogues of solutions and printing the optimization graphs. In the afternoon participants will have time for the development of the personal project. HOW MUCH DOES IT COST?The workshops cost 600 PLN (or 160€) for Early Bird payments and 700 PLN (or 190€) for the regular payments. The 3-person group - 1500 PLN (or 440€ )EARLY BIRD?For those who are certain that they will attend the workshops, we have a special Early Bird offer till 30th of April 2016.HOW CAN I SIGN UP?Send an email to info@architekturaparametryczna.pl with the title: “OPTI WAW 16”.HOW MANY PLACES ARE AVAILABLE?We have only 11 places!WORKSHOPS: Level: intermediate – advancePerquisites: the basic knowledge of Rhino and Grasshopper3D. Plug-ins: Silvereye, Octopus, Ladybug, Karamba. Weaverbird. Python GHThe main aim of the 16-hour workshops is to give the participants the understanding of how the optimization process can be used in practice and how it can help in solving everyday design problems. The practical exercise will be supported with the short lectures explaining the theoretical background of the optimization algorithms. The general program of the Optimization Warsaw 2016 Workshops*:1. Optimization of the facade geometry with solar analysis.2. Optimization of the roof structures with Karamba.3. Finding the optimal configuration of the space frame structures with Karamba.4. Discovering the best location or/and geometry of the building in accordance to the best views from the plot.5. Presentation of the discovered solutions. *Some of the exercises might be changed.…
mbols without any inputs already there, which is currently not possible in the ZUI framework.
Thirdly it prevents people from using the same component with streams of data, some of which may be nulls. Perhaps you want to use the object to solve 1000 triangles, 400 of which have only 2 known edges, and 600 of which have 2 known angles. If the component can only handle either of these cases at the same time, you'd have to split up 500 lists of data into two separate streams, use two trig components and then fold it all back together again. This is probably a very rare case, but it sounds like an unnecessary limitation.
The angles are defined as standard angle parameters, so rounding to 0.1 degrees isn't any good if you're using Radians. Plus 0.1 degrees is pretty coarse, one can do a lot better with 64-bit floating point numbers.
I think my initial solution will be to simply add a warning to the component if you supply more values than needed.…
Added by David Rutten at 4:54pm on August 23, 2014
en breps and this formula says that all 5 is self intersecting despite if you check the visually, anyone can see that only 2 of 5 is self intersecting.
I tried to upload the files, but I cant do it, because I "500: Unexpected Error", and my message appears without the attached files.
Is there any formula available which is an exact solution? At least for my flat breps. I have searched on the net for self intersection surfaces problem, but I have found only very very long and complicated mathematical formulas which I could not translate to grasshopper.... …
...when I use the merge component - tell me if this is the wrong one to use - with the intent to join the curves between the three lists only at their corresponding indices, curves that are coming in are leaving as null entries...
that may sound convoluted - here's what I have - three lists of curves each with 500 or so branches at {0:1}, {0:2... etc etc I want the curve in one list at {0:1} to join the curve in the next list at {0:1} and so on. For some reason the merge is turning curves that were fine into nulls - has anyone experience this before? is there another way to do what I want?
thanks for the help in advance…
radiance parameters to get rid of blotching. To add another level of complexity to my problem, I am running simulations with a translucent material with the following properties: void trans testTrans
0
0
7 0.478 0.478 0.478 0.000 0.010 0.178 0.635
I have had no issues with the renderings when I use clear glazing, as seen on this image:
However the blotching-issue becomes very noticeable when I introduce translucent glazing into the scene:
For the two above cases I used the following parameters:
_av_ is set to 0
xScale is set to 2
_ab_ is set to 6
_dc_ is set to 0.5
_aa_ is set to 0.2
_ad_ is set to 2048
_st_ is set to 0.5
yScale is set to 2
_ps_ is set to 4
_ar_ is set to 64
_as_ is set to 2048
_ds_ is set to 0.25
_pt_ is set to 0.1
_dr_ is set to 1
_pj_ is set to 0.9
_dp_ is set to 256
_dt_ is set to 0.25
_lr_ is set to 6
_dj_ is set to 0.5
_lw_ is set to 0.01
I ran another test with increased Radiance parameters and got the following output:
with the following parameters:
_av_ is set to 0
xScale is set to 6
_ab_ is set to 6
_dc_ is set to 0.75
_aa_ is set to 0.1
_ad_ is set to 4096
_st_ is set to 0.15
yScale is set to 6
_ps_ is set to 2
_ar_ is set to 128
_as_ is set to 4096
_ds_ is set to 0.05
_pt_ is set to 0.05
_dr_ is set to 3
_pj_ is set to 0.9
_dp_ is set to 512
_dt_ is set to 0.15
_lr_ is set to 8
_dj_ is set to 0.7
_lw_ is set to 0.005
Although the second blotching case is much better than the first, it is still very bad for hours when the sun is lower in the sky. The above images are rendered for a clear sky at 18:00 in Germany in a West-facing room.
Sorry for the long post! Can someone help? Kind regards, Örn
…
you see (an accurate representation of real things commercially available) is an instance definition - that way you can have a Rhino file with 10K of these that requires less than 1M (the other option is ... er ... 500 MB).
…
est of the best)
Crucial DDR4 2133 ECC (what else?)
4* WD RE 500 in Raid combo (not shown)
Some stupid 2.5'' HD thingy (avoid 2.5'' disks)
No SSD thingy
Corsair CPU cooler (Tequila replaced the OEM liquid: it works)
…