near logic you were asking:
This is simply using a line as a reference, and finds the projection of the mesh points on it. Then, the values along the line can be used to create a linear growth. A second example is then here a simple attractor logic. The closer to the point, the larger the thickening.
A last example is using the linear increase example as a start point, but then applies the sin function to it. This creates a moving wave. Note also how this trigonometric function returns on top of itself.
I hope this helps,
Giulio
--
Giulio Piacentino Weaverbird development…
once all neighbors overlap, its fine. otherwise just think, they can not be too big, as they will be trimmed, so maybe say: quad size is given by the host surface BBX diagonal length. for the trimming: as long as u have no concave parts on the surface, u can trim each cell with all others. try to work with planes instead of the planar cells. that saves performance. use plane-plane intersection, then u get edge lines, which then u just need to chamfer together. u can find neighbors for each cell by i.e. (the cheapest option) neighbors are the 10 closest cells to a test cell. remember: u just need to limit the number of intersecting planes. this works for rather evenly distributed cells with little concave curvatures. i found useful a kind of searchlight strategy. think of a rotating cone. from all points currently in the cone, the closest is designated as neighbor. i know this is totally unscientific, but i hope i could help!ps. lets see this http://www.grasshopper3d.com/photo/faceted-shell…
can try playing around with that.
The other reasons were pretty much covered by Mostapha and Chris. Usually you want AB (the ambient bounces) to be greater or equal to 5 no matter the quality, as it is one of the most important variables for a dependable simulation. Of course it depends on the nature of your geometry but 5 min. is a safe bet.
Btw, I couldn't see which geometry you are plugging where as one pipeline was empty in the file you posted when I opened it. Could it be that you forgot a surface?
Another point is the unit range you are using. Is that really 10 lux as maximum in your picture? Because in that case it makes sense for everything to be yellow (inside and outside) as you most likely will have more than 10 lux everywhere.
P.S.: Selecting medium/high quality sets all the variables for you, no need for additional sliders. In your case you are actually overwriting the quality settings.
Kind regards,
Theodore.…
X, Y & Z parameters. At the moment 'Z' parameter is set to 0.
Now when i use a planar surface components it works well. But because i have Z parameter i need Edge surface component to work well. Edge surface gives me a funny shape, not like planar surface.
Essentially with Z parameter as 0, edge surface should look like planar surface, or not?
When i try edge surface with simple 4 points it works. The moment it gets relatively complex i do not get desired result.
All the points 1-26 in the curve were formed progressively in order i.e. 1, 2, 2...26 in GH not in Rhino.
What m'i doing wrong?
cheers
aB
…
e.
i have come as far as creating a mesh entirely in GH to my desired form. Could any-1 please help me with creating fenestrations / holes into this mesh in GH?...
I have been stuck with this since a week now...not able to find any solution to move ahead!
i have Tried Voronoi by converting this mesh in to surface...it doesn't really work on the mesh that i have created...
any-1 with some suggestions?
cheers
aB
…
in 10 minutes or so!
If you are interested to know about the process of putting the Ladybug together, what's going on right now and what's coming next, just check the workshop website for webcast information! Here: http://www.nrel.gov/buildings/2013_radiance_workshop.html
Cheers,
Mostapha…
below:
The comand prompt window (see attached image) seems to put -ad 1000 as default even if it seems to be set to 512 in grasshopper. In contrast to -ad, the modification of -ab to 3 has been taken into account. Have you set minimum values for RADparameters? If yes, would it be possible to force them to custom values?
Thanks in advance for your help
Best regards,
Aymeric…
13;2} ... 20.{13;12}
21. {21;0}22. {21;1}23. {21;2} ... 41. {21;20}
42. {34;0}43. {34;1}44. {34;2} ... 75. {34;33}
76. {55;0}77. {55;1} ... ....
I want to grab the first 8 [0-7], the next 13[8-20], the next 21[21-42] etc
so i have the (known fibonacci seq) list of numbers on the left here:
C S
8 0
13 8
21 21
34 42
55 76
89 131
144 220
233 364
and i need the list on the right, so that i can select items using a Series (N=1 and S and C from the list above) and a List Item component.
the simple question is:
is there a component that can take a list and accumulate it in this way that I need?
if not, is there anyone that can point me to a simple relevant VB example so i could easily adapt it?
many thanks,
gotjosh…
adrid/
http://www.24studiolab.com/#/
or write to:
24studiolab@gmail.com
Course will be variable (during the weekend or during the week) depending on the convenience of the assistants.
COURSE PROGRAMME (spanish)*
Rendimiento formal / Estructural
Galápagos, algoritmos genéticos
Kangaroo physics
Optimización mediante fuerzas fisicas
Form Finding
Surface Relaxation
Edición avanzada de malla
Isosurface and fractals surface
Karamba
Rendimiento energetico
Heliotrope / Ghowl
Geolocalización
Geco
Kangaroo shape optimization
* COURSE PROGRAMME may vary depending on the demand of the assistant
…
Added by 24StudioLab at 2:10am on December 26, 2013
the optimizing process I am using Karamba+Galapagos.
Unfortunately I am getting some errors when calculating the maximum displacement of the bridge, using the Karamba “analyze” component.
95% of the times (when moving a slider), it goes well. I am getting deformations of 100-200mm as expected, and the deformed shape in the Rhino view looks good.But in the last 5%, I get unreliable deformations of 50000mm or more. What I dont understand about this is that the deformed shape in the Rhino view still looks normal. Another weird thing is if I move the slider away from the position and then back to the same position again, I suddenly get the result of 100-200mm. It seems more or less randomly when it gives the strange results.
The model has over time become pretty big. When moving a slider, calculation time is about 5 to 10 sec.Could this be the reason for the errors? Any other ideas about what goes wrong?
Thank you in advance for your answer.Attached please find the GH file.
Best regards Soeren…