[Developers] AHFinderDirect accuracy for test suite

[Erik Schnetter]

I see some AHFinderDirect test cases fail because the absolute or  
relative difference of the results is about 1.0e-6 for some results.   
The test cases currently allow only an error of 1.0e-8.  Given that  
the test cases pass on some problems and fail on others, do we think  
that this is a real problem that could be solved e.g. by changing  
solver parameters, or should we just accept these errors?

AHFinderDirect's accuracy is set to 1.0e-12.  We could change  
compiler optimisation switches, which may (or may not) make a  
difference.

-erik

-- 
Erik Schnetter <schnetter at cct.lsu.edu>

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.cactuscode.org/pipermail/developers/attachments/20070306/4ecd2dca/attachment-0001.bin