Hi,
I am probably the one jerryyyyy referred to
![tongueout :P](http://pixinsight.com/forum/Smileys/default/tongueout.gif)
I had limited experience using PI to process D800 raw images, and I don't
remember seeing this.
What I do know is that in D800's bias files, there are many zeros, because of
the notorious black-clipping of Nikon cameras. (There is a Nikon firmware
hack that can solve this. You may want to check the nikon hacker forum.)
This definitely makes statistical analyses on D800's files give unreliable
results, but it kind of surprises me that it leads to a failure.
In your original post, you said that this problem goes away if you uncheck noise
evaluation. I would say if the results of the final image looks OK, then
it is not too big a problem to uncheck this. (In another recent thread, I asked
how to disable any statistical analyses during the integration. I am not a big
fan of such analyses, although I do believe it could be useful for other people.)
An alternative is to not provide bias files at all. (I am not sure if this is
allowed by PI.) As mentioned, because of the black-clipping of Nikon DSLRs,
D800's bias file mostly contains zeros. Not using bias files will only have minor
impact to the final results, especially when you have good dark files.
These are what I might do to bypass the problem. Really solving the problem
may require more investigation on your bias file and on PI. Unfortunately I am
traveling, otherwise I can simply take some bias images with my D800 and see
if I can reproduce the failure you saw. Sorry for being not too helpful.
Cheers,
Wei-Hao