Betaserver: Double renders?

Just a little question. When i look in the upload/renderque and look at the rendered frames of the sheep.... why are the frames 160-319 exactly the same as the frames 0-159?
I can see it wrong, but now it seems to me that the rendering of one loop or edge takes twice as long as needed?

Gr, ReFa

Dupes are for redundancy

The frames are rendered twice to automatically check for bad renders (which happen on occasion - corruption of the genome when transferred, etc. The frames *are* different (different random seeds, I believe) so they are averaged together to get the frame that goes into the animation.

Erik Reckase
flam3 developer
AIM: flam3dev

right, each frame is rended

right, each frame is rended twice with different random seeds. the results are averaged to form the final frames, so I wouldn't call it redundancy, since if an error is detected then both frames get redone. no rendering is wasted.

the problems don't come from network transmission, since TCP has a checksum, but from bad RAM and cosmic rays which flip bits during the rendering.

Both are re-rendered?

Wouldn't it be more economical to re-render just one, and compare that to the 2 original ones?
2 out of 3 should be identical, unless you got 2 corrupted versions. In which case you continue adding one until you do get a duplicate.

--
"Mary had a little lamb"
Parse error
Terminated

that's what we call "crazy

that's what we call "crazy talk". 10 times more complicated, infinitessimally more efficient. aka: a bad plan, not happening.

Ok, thank you both for the

Ok, thank you both for the answers :)