omponent that increases in the x-axis (example below).
A1 A2 A3 A4 A5 etc...B1 B2 B3 B4 B5 etc...C1 C2 C3 C4 C5 etc...D1 D2 D3 D4 D5 etc...
This is as far as I've gotten:
I have collected my points on the grid into a "List Length" component and input that into a "Series" which input into a "Function" with the expression Format("A{0}",x). The result labeling resembles the example below.
A1 A2 A3 A4 A5
A6 A7 A8 A9 A10
A11 A12 A13 A14 A15 etc...
Any help is appreciated.
Thank you in advance.…
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...)?
…
behave like this:{a1;b2;c3;d1;e2;f3;g1;h2}
The ping pong matching would behave like this:
{a1;b2;c3;d2;e1;f2;g3;h2}
with a boolean option it could repeat the first and last like this:
{a1;b2;c3;d3;e2;f1;g1;h2}
If this already exist please let me know
Thanks
bye…
Added by Frane Zilic at 10:15pm on August 19, 2012
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.…