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.…
ts will basically be a set of different ellipses:{a1, a2, b1, b2} (with different properties) From that i want to create random Lists of let’s say 15 items (ellipses) Something like that {a1, b2, b1, a1, a2, b1, b1, a2, a1, b1, b2, a1, b2, a1, a1}. But I want to be able to create some constrains. So for example if I have a1 I will be able to have next a2 or b1 but not to b2. I am not sure if this is possible in grasshopper and i was messing around with some logic components but without any luck.
Any help will be greatly appreciated.
…
dro). The quality of the driver is also critical: hard to imagine NVidia working overnight to fix "some" driver bugs due to requests from gamers. Game cards are notoriously bad in dual monitor configurations.
3. A zillion of cores (triumph of marketing VS common sense) divided by the given clock rate ... gives you just ONE poor old core (Rhino/gh are single-threaded apps) that tries to do the job.
4. Single Xeon E5 2xxx V3 (the higher the clock the LESS the cores = better) would be my recommendation. ECC fast memory is also a must.
PS: Find a friend who operates a "loaded" H/P Z840 and test your defs.
…
of lines, etc) but I can't see a way to add the text I need where I need it. If I could get each line for the print run to generate automatically, I can put the rest in manually, so just need something like:
... ; I would do the previous to this manuallyG1 X10 Y5 Z3
G1 X5 Y5 E5
G1 X5 Y15 E10
... ; I would do the rest manually
for a 5 mm line from [10, 5, 3] to [5, 5, 3], followed by a 10mm line from there to [5, 15, 3]. Any pointers greatly appreciated.
Ewan…
ng long in the x axis and three in the y and they don't all intersect each other... I wrote a script to Boolean difference them but its not working like i want it to . I included a rhino result that id like to achieve in the file. THX -ethan
heres the script:
import rhinoscriptsyntax as rs
b1 = []for i in range(b1L): b1.append (x)print b1bb= len(b1)print bbb2 = []for j in range(b2L): b2.append (y)print b2bc = len(b2)print bc
def bool ():....for i in range (bb):........for j in range(bc):............a = rs.BooleanDifference( b1,b2, False).....return (a) a = bool ()…
est of the best)
Crucial DDR4 2133 ECC (what else?)
4* WD RE 500 in Raid combo (not shown)
Some stupid 2.5'' HD thingy (avoid 2.5'' disks)
No SSD thingy
Corsair CPU cooler (Tequila replaced the OEM liquid: it works)
…