mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Software

Reply
 
Thread Tools
Old 2021-03-24, 13:40   #1
sp00n
 
Dec 2020

710 Posts
Default Failed FFT size in results.txt

Would it be possible to include the failed FFT size in the results.txt file for a torture test?

Currently it only displays the passed FFT sizes and the error message, but not the FFT size where the error actually happened in the log file. In the worker thread window you can at least also see which FFT size was started and then deduce from that where the error happened, but for the log file there's not even such an indication.

I've even tried to make an educated guess by looking at the order of FFT sizes, but unfortunately this only works for smaller FFT sizes, for larger ones there seems to be a random order in which the FFT sizes are tested, and therefore any prediction seems to be impossible (I also tried to find and understand the C code that defines the order of FFT sizes, but to my embarrassment failed to do so 🙈).
sp00n is offline   Reply With Quote
Old 2021-03-24, 15:47   #2
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

7×1,069 Posts
Default

I will add that information in the next release.
Prime95 is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
GMP-ECM 7.0-dev assertion failed! Antonio GMP-ECM 9 2015-03-10 08:21
Assertion failed Andi47 GMP-ECM 2 2009-08-04 14:11
integrator failed MatWur-S530113 Msieve 5 2009-01-28 03:54
connection failed musos Information & Answers 1 2008-12-12 14:29
Test 1: failed? No0dles Hardware 12 2005-11-05 09:23

All times are UTC. The time now is 08:19.

Sat May 8 08:19:58 UTC 2021 up 30 days, 3 hrs, 0 users, load averages: 3.23, 3.49, 4.04

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.