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.…
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…
more complex geometries, nothing works anymore and the output is weird: every test point has the same value (97% DA) and it's impossible to visualize these values even if a text tag 3D is assigned to points (check Result.jpg)
The output that we get is a uniform mesh.
To check this output we also run an illuminance analysis using the same test surface, giving 300lux as high and low bound and some areas didn't reach the target value - which means that there must be some areas below that threshold.
Another thing: as you can see from Screenshot.jpg at one point we get the string saying *.dgp not found. Is that a problem?
Attached you can find the Grasshopper file.
Thank you all!
Simone
…
untime error:
Runtime error (PythonException): unable to add point to document Traceback: line 97, in AddPoint, "C:\Users\AKIDRIBM\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rhinoscript\geometry.py" line 136, in Point, "" line 47, in toGH, "" line 187, in RunScript, ""
Could anyone help me figure out what's causing it? The code for adding the point is below:
# Plots points/text dots def Point(self, pointSource): print pointSource, type(pointSource) pt = rs.AddPoint(float(pointSource.value.x.value), float(pointSource.value.y.value), float(pointSource.value.z.value)) return pt
pointSource is a custom object that stores information about the point. Its only relevance here is to obtain the point coordinates. I do not get this error all the time, so I'm having trouble figuring out what is exactly causing it.…