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…
blinds be (B1,B2..B5). Then the geometry for the five iterations will be ((A+B1), (A+B2)...(A+B5)).
And assume that you are measuring illuminance at four points inside the room (x1,x2,x3,x4) and one point outside the room(y1).
The way Daysim works ( and should work as per the best of my understanding) is that for each setting of the blind (ie. B1,B2,..B5), a separate value of (x1,x2,x3,x4) gets calculated through the Daylight Coefficient Method. So let's say you have illuminance thresholds of (p,q,r,s,t) corresponding to (B1,B2,..B5). What the shade-control algorithm does is that it compares the illuminance at y1 with your threshold of (p,q,..t) and then chooses a value of (x1,x,2,x3,x4) on basis of that. So, when we repeat this process for (365x24=)8760 hours , we end up with a value of a shade setting for each hour which was set on basis of your threshold illuminance values.
I would have gladly answered your question on HB itself, however, I usually work with Daysim directly through commandline.
(BTW, if you are interested in reading more about Daysim google Christoph Reinhart's dissertation on the subject, along with some papers by Zack Rogers).…
I'm trying to extrude a large number of them to the next surface below, they're not all at the same distance from one another so it'd have to be 84 Z components for the 84 surfaces there
t it is rounded to 25, 100, 75. I've figured out the rounding portion, but when I plug the resulting list back into the custom preview, it doesn't recognize the data. I'm guessing it is because my rounded list is in curly brackets, whereas the unrounded data straight from the image sampler is not. How can I process this to remove the curly brackets?
Thanks,
Ryan
…
Added by Ryan Dirks at 5:20pm on September 18, 2014
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)
…