Nope. No dual or quad-cpu action, from either Intel or AMD, without paying for a "2" or "4" capable cpus (Xeon or Opteron)CoolColJ wrote:can't the regular AMD/Phenom desktop chips run in dual CPU?
That's the way I would go myself - save some bucks
Cut Crystal Tests
I just compared my Cauchy curve for BK7 against the graph on wikipedia. My curve behaves the same vs the measured data as the one on wikipedia. I am now 100% sure I have the A and B calcs perfect now. I've only changed one thing since last post of the spreadsheet and that was switching the 'n' in the A calcs from the median of nD and nd to the mean of nD and nd (which is what I originally intended but had a brain fart
).
EDIT: Decided to go back to meassured nd for the A calcs, made more sense. Updated link to version 13.
Link removed, new link further down.
EDIT: Decided to go back to meassured nd for the A calcs, made more sense. Updated link to version 13.
Link removed, new link further down.
Last edited by WytRaven on Wed Oct 17, 2007 1:32 am, edited 3 times in total.
Render update:
bidirectional: 1
width: 1920
height: 1200
super_sample_factor: 2
hybrid: 0
metropolis: 1
num_threads: 2
large_mutation_prob: 0.40000
max_change: 0.01000
max_num_consec_rejections: 1500
maxdepth: 15000
ray_origin_nudge_distance: 0.00001
num_samples: 25915570000.00000
render time elapsed: 601386.28205
samples_per_pixel: 11248.07726
samples_per_sec: 43093.05146
It's actually getting pretty close to convergence now
bidirectional: 1
width: 1920
height: 1200
super_sample_factor: 2
hybrid: 0
metropolis: 1
num_threads: 2
large_mutation_prob: 0.40000
max_change: 0.01000
max_num_consec_rejections: 1500
maxdepth: 15000
ray_origin_nudge_distance: 0.00001
num_samples: 25915570000.00000
render time elapsed: 601386.28205
samples_per_pixel: 11248.07726
samples_per_sec: 43093.05146
It's actually getting pretty close to convergence now
It's really facinating watching this scene evolve. Every time I think it's moving toward convergence indigo finds some new detail to start working on. Its over 175hours now and all of a sudden some brand new caustics just started showing up 
I'm actually really peeved that I din't put more effort into the scene setup now. What was supposed to be a simple test has grown into aa render marathon and unfortunately the end result whilst being technically cool will make for a flawed render due to the crapy scene.
I promise my next 200 odd hour render will be a good picture as well as being technically cool
I promise my next 200 odd hour render will be a good picture as well as being technically cool
Here's a pretty comparison of my calced values for BK-7. The comparison from wikipedia shown first:
Wikipedia values:
A: 1.5046
B: 0.00420
My Values:
A: 1.50457412559239
B: 0.00422072479206567


Considering that wikipedia doesn't show the values they calculated their A and B from it's no surprise that the numbers aren't eactly the same but you can see from the graph that the curves are behaving the same. I think it's safe to say from this that the method I am using is correct.
Wikipedia values:
A: 1.5046
B: 0.00420
My Values:
A: 1.50457412559239
B: 0.00422072479206567


Considering that wikipedia doesn't show the values they calculated their A and B from it's no surprise that the numbers aren't eactly the same but you can see from the graph that the curves are behaving the same. I think it's safe to say from this that the method I am using is correct.
WytRaven wrote:It's really facinating watching this scene evolve. Every time I think it's moving toward convergence indigo finds some new detail to start working on. Its over 175hours now and all of a sudden some brand new caustics just started showing up
All of a sudden you're going to have an electricity cut while Indigo is saving and your .igi will be fucked up
You should backup your .igi sometimes if you don't already do


