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.…
. The rules to dispatch the lines are the next:
I start with a list that alternate true/false; like that: true, false, true, false.
If the angles between those lines are greater than 89° I want to inverse the next part of the list:
True, False, True, False, True, False,...
become
True, False, [>89°] False, True, False, True, [>89°] True, False,...
I managed to create a true false list, to check for the greater than 89° angle, to separate the lines relatively to the angles, but I don't know how to inverse part of the list at certain index.
(In the picture, I have written 90° but it should be 89°, I check for greater than 89° and not equal to 90° because in the real rhino model, the lines won't be exactly orthogonal)
If you have another idea to to reach the same result, it's also okay, I tried to find rules to solve the problems, but I may have overlooked other solutions !
And if there is some part of the patch that are correct but there is easier solution, I would love to learn as I am still new to grasshopper.
Thanks for taking the time to read. :)
…