nologically label them (there are currently 65 points and this is labelled as in the file i've attached). However, what i'm actually after is to reformat these points into an x and y style grid.(a1, a2, a3, a4, a5)(b1, b2, b3, b4, b5)(c1, c2, c3, c4, c5)(d1, d2, d3, d4, d5) etc.Any ideas/help how this can be made possible would be great.Thanks in advance…
I have a database with about 80 tables on it, so i wanna connect to the database, make 5/6 different queries, extract the info and use it as an input to grasshopper.
on for curves, if you make an algorithm that dynamically defines the possition of the controlpoints for NURBS curves as a function of the parameteres in F(t, a1,...,b1,...,c1,...)= x(t, a1, a2...)+y(t, b1, b2...)+ z(t, c1, c2...) or F(x, a, b ,c...)?
…
e. I want to be able to give it the panels a range let say between 1-3 and then give it a specific number of variations allowed, like only 80 different heights can be generated and the rest of the panels would be rounded up or down to match with one of the 80 heights. would that be possible?
Thanks…
me in 19 different pipeline components. Marginally better, but I'll still need to do this operation approx. 80 times...gulp.
Here's a wishlist request for David: expose string inputs in the Geometry Pipeline for Layer and Name. If I had that, I could change one string to swap my whole geometry set! (My layers have names like "B1 red rail", "B1 blue rail" etc., then the next time I'll want "B2 red rail", "B2 blue rail" etc.)
BTW, I'm happy to script something in C# if it will help: maybe I could write something like the Geometry Pipeline that takes a string input for layer name? Hmmm...
…
this target list:
(a1, b1, c1, d1)
(a2, b2, c2, d2)
(a3, b3, c3, d3)
....
What I want to do is injecting one more value (arbitrary angle in my case) to each point before I cull many of them - so that each point brings its angle data along.
Any hep would be greatly appreciated. TIA
…
gone with the wind topic: since this is utterly Academic the main issue here is to oversimplify LBS (in real life: a collection of columns/beams/slabs/X members + tube frame rigid members (shafts/elevators/cats/dogs)). Reason is that if we use the real "solids" (turned into meshes) as the "node" pool for the hinges required ... only HAL 9000 could solve it in "real-time" (for instance an E5 Xeon 1630 v3 takes ... several minutes). And this is ... er ... challenging I must say. This is a typical case where "simplifying" means "stupidity" almost instantly.
Spam on:
where's my collection of "bend-a-truss-that-looks-like-a-tower" K1 demo defs? Is in this workstation or in another? (blame Alzheimer).
Spam off.
More soon.…