Table update this evening
 

[QUOTE=ET_;463310]The actual Mlucas version is 17.0[/QUOTE]

Thanks!

Changed since last posting:
added freebsd mprime, date column, gpuowl iGP footnote,
corrected Mlucas version,
removed ecm work type.

Table update this morning
 

changes since last update:
discussion forum links, Mfakto note, gpuLucas, Glucas data, CEMPLLA data, formatting added

Thanks, Ken - please remove any mention of Mlucas being TF-capable - while there is TF code it's not part of the current build, it needs a custom standalone build at present. I shall also have to clarify that on my readme page, as well.

This morning's update
 

changes since last update:
added exponent limits to some notes,
added runtime caution footnote;
removed other-cpus TF software reference per request of its author.

[QUOTE=kriesel;463531]changes since last update:
added exponent limits to some notes,
added runtime caution footnote;
removed other-cpus TF software reference per request of its author.[/QUOTE]

I don't know if it's worth mentioning it... but I wrote a trial-factoring software for Mersenne and double Mersenne numbers (Factor5). It can run on 1, 2, 4, 8 or 16 threads, compiles under any OS recognizing the pthreads library, being full C-compliant works fine on ARMs and has no upper limit (apart from physical memory) for the exponent.

Being written in C and using the GMP library, it may result painfully slow, but, it's there, and it's the only software that can trial-factor Mersenne numbers with exponents higher than 2[sup]32[/sup], at least as long as Ernst re-releases his (faster) Mfactor... :smile:

[QUOTE=kriesel;463531]changes since last update:
added exponent limits to some notes,
added runtime caution footnote;
removed other-cpus TF software reference per request of its author.[/QUOTE]

1. I still see Mlucas in the TF-for-x86 list at top left;

2. CEMPLLA should not be listed until at least one person we know [a] successfully installs it, and [b] verifies that it does what it purports to do. Our own David Stanfill failed to even install it despite several attempts on different kinds of GPU hardware, and its author has ducked all questions re. [b].

Or perhaps better, do include a link but in a separate "Unproven; Not Recommended" category, together with the above caveats. 100% open-sourcedness is not required, but complete-black-box is not something you want to be appearing to recommend in any way.

Today's update
 

[QUOTE=ewmayer;463560]1. I still see Mlucas in the TF-for-x86 list at top left;

2. CEMPLLA should not be listed until at least one person we know [a] successfully installs it, and [b] verifies that it does what it purports to do. Our own David Stanfill failed to even install it despite several attempts on different kinds of GPU hardware, and its author has ducked all questions re. [b].

Or perhaps better, do include a link but in a separate "Unproven; Not Recommended" category, together with the above caveats. 100% open-sourcedness is not required, but complete-black-box is not something you want to be appearing to recommend in any way.[/QUOTE]

1: D'oh!
2: See revised table.

Disclaimer and draft criteria for available software table
 

Disclaimer

The table I've been putting together is not a personal endorsement of everything or anything in it. Don't sue or curse me or GIMPS or its officers if something undesired occurs after loading any of the mentioned software on a system. I'm just sharing information I've managed to gather after spending numerous hours reading through forum threads and by other means. Make your own informed decision what to use or not use. As with all downloaded software, the end user assumes any risk. There are no warranties express or implied that I'm aware of.

Draft criteria for inclusion in Mersenne prime hunting software package table:

Benign function: It actually does what the author claims it does and accomplishes the factoring or testing approach, and it does not do things that are objectionable (such as interfere with other programs, destabilize or damage system, make console unresponsive or hang the system, crack passwords, transmit user files, mine bitcoin, send spam, install or contain data extortion virus or other malware, search for data useful for blackmail, join a botnet, participate in DDOS, LAN-scan, etc). It can handle the ranges of exponents of interest currently (GIMPS wavefront). It's preferred it also currently supports ranges of exponents extending at least a year into the future at current rates of progress. That allows time for testing for correct function in advance before the wavefront arrives there.

Speed: fast enough relative to any available alternatives that could consume the same computing resources, that running the program does not constitute a large waste of resources. Faster than existing alternatives on similar hardware at high accuracy and reliability is desired.

Accuracy: nothing's perfect, and lengthy LL test or factoring operations are exceptionally unforgiving of error, so high effort to ensure accuracy matters greatly. Software should implement self test to verify itself and the hardware it's running on, and implement various on-the-fly error checking and verification such as roundoff error checking, detection of illegal output values, status output including interim 64-bit residues, etc.

Stable: Can run for weeks or longer without attention. Stability issues have known effective workarounds. (An example is the Nvidia driver restart issue and the combination of checkpointing and batch file wrappers.)

Robust: Saves interim results periodically and can resume from saved interim results in case of later nonrecoverable error. Includes input parameter checking, error handling.

Validation: Outputs should be available in plain text to make easy validation of correct operation. Documentation of data formats of interim save files for comparison of full length interim residues or other computations in progress to results of other programs and to theoretically correct values is a plus.

Trusted: Open Source is the best bet here and highly recommended. Authors willing to put their own full names on it help create confidence. Aliases or closed source or concealed documentation or encryption of code or communication can have the opposite effect.

Availability: It is available on a known server for free download. License restrictions minimal and publicly available before download and installation are completed, for an informed decision at the outset or very early. Ideally the documentation can be downloaded separately from the program or installer.

Work management: Optionally provides for connection with work assignmentservers. Optional scripting to distribute work or report results automatically. Provision for queuing up work locally is required, enabling manual operation and operation throughout network access interruptions. Provides for resuming or launching subsequent exponent tasks upon completion of one in progress.

Logging: logging to file of results is required. logging of program console activity is desired but not a requirement. For software lacking builtin screen output logging, end user use of tee or redirection from a terminal window or command processor window are suggested.

Platform requirements: runs on hardware and operating system(s) which are numerous, and resource requirements are not exceptionally demanding or exotic.

Support: there's a user community, a forum, source code available online, executables easily available, patches easily available, currently maintained software and documentation, clear accurate and ample documentation, online documentation, a wiki, or a responsive capable involved friendly developer. More is better. All the preceding is best.

Tuning: program should implement sensible defaults, and provide for user modification of tune. Some people enjoy tuning, some want set and forget. New hardware not designed when the software was written may benefit from retuning.

User interface: command line options and ini file are the minimum. An interactive keyboard mode is helpful for tuning and debugging. A GUI is a plus.

Other: what am I omitting that is of importance to the current or potential users?

Your list of criteria looks good to me, Ken, and supplies one further accompanying enhancement request - add a set of checkbox-columns to your tables, one for each of the various categories in your criteria list. Column labels contain condensed category description, final page of the document has the detailed criteria list.

For the checkboxes you will likely want a third option beyond the binary checked-or-not ... e.g for George's code, it's mostly open-source except for the primenet-comms security module, so perhaps an asterisk in the checkbox with a corresponding footnote beneath the table.

Trial factoring run times for Mfaktc on NVIDIA GTX480
 

Timings for an assortment of exponents and bit depths are tabulated and charted for reference. Note, only one trial per combination was tabulated, so no measure made or indication given of reproducibility run to run for same inputs. See the attachment. This is a somewhat different way of looking at it than the factoring benchmarks at [URL]http://www.mersenne.ca[/URL]

Lucas-Lehmer run times for CUDALucas on NVIDIA GTX480
 

Timings for an assortment of exponents are tabulated and charted for reference. Note, only one trial per combination was tabulated, so no measure made or indication given of reproducibility run to run for same inputs. (One exponent's run time was estimated from a fit made on results from several other exponents, with unexpectedly good results. Likely fit error appears to be 1-5% typically, subject to revision later.) See the attachment. This is a somewhat different way of looking at test speed than the GPU Lucas-Lehmer performance benchmarks at [URL]http://www.mersenne.ca/cudalucas.php[/URL]