Hi, Maybe this shouldn't be a bug? It's only present in your 'disp_speed' branch and is only seen with a debugging flag turned on. If you add the check I mentioned at http://www.mail-archive.com/relax-devel@xxxxxxx/msg05731.html to the first line of this function, maybe all the checks you have added compared to the trunk could be removed and this issue will just disappear. It would be worth trying. Also, what does the following line do? # Calculate lowest positive val, which raised to the power will not be represented less than 1.-e300. low_pos_rep = power(1.e-300, 1./max_t115) Why is max_t115 inverted when the original code from Nikolai and Martin is: t115 = N/2; t116 = (t69/2+t83/2+t92/2+t96/2+t112/2).^t115; t118 = 1./t112; t120 = t69+t83-t92-t96+t112; t122 = (t69/2+t83/2+t92/2+t96/2-t112/2).^t115; Here t115 is never inverted. The 1/max_t115 is causing this divide by zero error. Anyway, adding the 'No Rex' check in the above link will likely make all of this redundant. Regards, Edward On 21 May 2014 18:46, Troels E. Linnet <NO-REPLY.INVALID-ADDRESS@xxxxxxx> wrote:
Follow-up Comment #3, bug #22065 (project relax): This only fails when --numpy-raise is set on. _______________________________________________________ Reply to this item at: <http://gna.org/bugs/?22065> _______________________________________________ Message sent via/by Gna! http://gna.org/