.", 1.5);
pManager.Register_DoubleParam("Maximum Force", "MAXF", "Maximum force w/h which the boid can turn.", 3);
pManager.Register_DoubleParam("Separation Factor", "SEPF", "Flock separation factor.", (double) 0);
pManager.Register_DoubleParam("Alignement Factor", "ALNF", "Flock speed alignement factor.", (double) 0);
pManager.Register_DoubleParam("Cohesion Factor", "COHF", "Flock cohesion factor.", (double) 0);
pManager.Register_IntegerParam("Number of Boids", "NBDS", "Number of boids to be spawned in the system.", 50);
pManager.Register_IntegerParam("Tail Size", "TSZ", "Size of the tail the boids leave behind.", 50);
//pManager.Register_BRepParam("Obstacles", "OBS", "Environment obstacles.", GH_ParamAccess.list);
pManager.Register_DoubleParam("Obstacles power", "OBSP", "How hard should a boid steer away from obstacles", 2);
//pManager.Register_PointParam("Start points", "SPTS", "Start points - where the boids will spawn from.", GH_ParamAccess.list);
//pManager.Register_PointParam("Attractors", "ATTS", "Attractors - boids will converge towards these targets.", GH_ParamAccess.list);
pManager.Register_DoubleParam("Attractor power", "ATTP", "How hard should a boid steer towards an attarctor.", 3);
//pManager.Register_IntervalParam("World boundaries", "BNDS", "World boundaries. If a boid gets out of the cube defined by this interval it will be killed.");
commenting out the GH_ParamAccess.list inputs takes care of everything - i mean no more errors, and no more lists as well.…
ructions etc.
I'd keep as a minimum ADF 2% or something like that, because i dont find the minimum of 1.5% for the living rooms very comfy in real life. (uk regul.)
Since I am about to desing a high rise, I have modeled just one 'unit' so i could understand easier what it is about.
I must confess i do not clearly understand how did you 'standardized' the ADF value in grasshopper file. I am subtracting the ADF that I am looking for from the ADF that I get from the calculations? But doesnt that give me the ADF that is just reduced for a fixed value that i give as a B value in the subtraction? Huh, i hope you can understand me?
The other problem I am facing with is to present graphically the ADF results. Since i'm using DIVA 2.0 it is a bit different that 1.9 version :/
I know guys i'm asking much, but I'm a bit lost with what to do, and i think that the solution is quite simple, but i'm missing something...
Could you please help! :/
…
. So there is one part of the error. This you can overcome in making the mesh denser. Or don't relay on the mesh structure and connect the nodes also diagonal and over a larger distance than just to the neighbours defined by the mesh structure. This of course comes with the error that there might be errors if the mesh is not flat.
Second: SpiderWeb uses the drawing tolerance for calculation. So if this is set to large e.g.: to 1 and you have two edges one 1.5 meters and the other 1.9999 both will be viewed as 2 for calculations.
Third: You have to use the nodes of the graph from which you search from to generate the voronoi diagram.
However if you are familier with coding then I would like to point you to this example, it might make your definition way, way way, faster and gives you more options with SpiderWeb...
Scripting with SipderWeb
Any further questions are welcomed, and please keep us posted would be very very interested...
BEst Richard
…
the shorter one) rotates in one direction about a fixed point. This rotation is generally limited to 0-180 degrees. The longer segment can rotate freely at the "elbow" (like a socket joint). All 3 arms converge at a single point (where an end effector would be). To generate this point I referenced a curve from rhino and I move the point along the curve in grasshopper.
I did it in 9 components (including the method of creating the point on the curve and piping the lines at the end).
The length/sizes of your arms can be whatever you would like. Just for reference my short segments are 1.5 inches and long segments are 3 inches.
Rules are that it must be GH native with no scripting. Deadline is monday the 26th at midnight (pacific time).
let me know if you have any questions!…
am trying to make a pattern distribution on a surface which scales objects by a certain percentage depending on the row, ie, i have a 3x4 surface division, i want the first 3 objects to be scaled by 1.0 second row by 1.5 , third row by 2, etc.
I understand the basic scaling "by object" but can't figure how I would do for row-based scaling. I have tried (and failed) to follow danny boyles' http://www.grasshopper3d.com/forum/topics/dividing-list-into-sub-lists-according-to-multiple?commentId=2985220%3AComment%3A471376 post into dividing the list into branches but don't know whether this is the correct way and also i couldn't figure out where I should insert this into my diagram.
Any tips on what i should be looking at would be very welcome.
Thanks.
Klaus
…
hen this happens a lot it means one of two things:
The entire population is highly clustered in a single spot meaning there's not enough genetic 'room' in between individuals to create unique offspring. When this is the case, it means a (local) solution has been found and there's little point in continuing the process.
The possible gene-pool is very shallow. Say you have 3 sliders, each of which can take on 4 values. That means you have a total of 43 = 64 possible combinations. The first genome picked is always unique, the second genome (when picked at random) has a ~1.5% chance of being identical. The third genomes (when picked at random) has a ~3.1% chance of colliding with the two existing genomes. And so on. Very soon you'll have exhausted all possible genomes and Grasshopper will frantically try and mutate any additional individual until it becomes unique, but of course never succeeding.
Based on your screenshots the latter is the case. You have two sliders, one with 4 and one with 3 possible states. This gives you a total of 12 possible genomes which corresponds to the 12 lines in the middle graphic and the 12 groups in the left-most graphic. You've computed each genomes more than once and there is no new information to be had.
I suppose Galapagos could be smarter about this and detect when it has exhausted all possibilities, but at the moment it has very little smarts.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 1:09am on January 23, 2013
am trying to do is using RenderAnimation component, I want to render animation with Vray Toon material, with colour.
I have Marc Syp's definition and used his C# components to do so, but since I have no knowledge in scripting, couldn't get it done.
Problem I am having is that the Vray Toon material, even though I have managed to import into grasshopper, the render result does not shows toon effect.
I am using Rhino 4 and Vray 1.5.
I have attached my GH definition and it's screenshot.
…
e no reply was given. Please if something is not clear do not hesitate to comment back, in that way some other user might see your reply and post a solution.
A more in detail continuation of the upper mentioned reply would be:
Find the Z coordinate of area centroid of your curtain wall panels.
Then by using "windProfileHeight_" and/or "distBetweenVec_" inputs from Ladybug Wind boundary profile component find the wind speed (m/s) at each of Z coordinate values from the previous sentence.
Convert those wind speed values into pressure (N/m2): p = (1.25*(windSpeed^2))/2.Derive the point load force from the pressure (Newtons):
F = p * A (A being an area of a curtain wall panel in m2)
Fnode = F/4 ("disposing" the F force to each support-node of your curtain wall panel).
Apply all these Fnode forces to your panels which are somewhat normally oriented to the wind direction. These will be your wind pressure forces. On the opposite side of the building, we can use a rule of a thumb and apply the same Fnode forces/2. These are your wind suction forces.
On lateral panels nodes (lateral in comparison to the wind direction) you can apply Fnode forces, in magnitude Fnode*(1 to 1.5). These are lateral suction forces.
Have in mind that wind load in structural engineering is a complicated subject. Most codes and equations currently used come from a very simplified 2D or 3D (cylinder, box) models. In reality one would need to use CFD software for detailed analysis (Ansys, NX, SolidWorks...), or if the project is actually going to be built then wind tunnel tests.…
consistent with the length of the curve (ie for a 3m curve evaluated at halfway (t) would be 1.5). This is also true for the one that was offset 'inwards.'
For the one that is offset outwards the (t) value is consistent with the curve length up to the first discontinuity (ie the first kink). After that the parameters do not relate to the length and only increase slightly from (t) value at the first kink.
I've attached a picture of this, and tested it in version 0.9.0014 in Rhino 5 and 4... The same applies with lines imported from Autocad and Microstation, as well as those drawn in Rhino. A solution to this would be much appreciated, as I swear it used to work - I have a script that draws seats for a stadium that worked on this principle and been using it for a while without any problems, although not for a few months, possibly before the install of grasshopper 0.9.0014.
Thanks…