Available software for pursuing mersenne primes
 

There are several cells in the table with only ? in them. Please reply or PM with any software that could fill in the holes, or suggestions for making the table more useful.

Missing Mlucas, LLR, and gpuOwl.

[QUOTE=Mark Rose;463139]Missing Mlucas, LLR, and gpuOwl.[/QUOTE]

and gpu-ecm

How does GPU-ecm help do anything with mersennes? All Mersennes small enough for GPU-ecm to work are already fully factored.

[QUOTE=VBCurtis;463156]How does GPU-ecm help do anything with mersennes? All Mersennes small enough for GPU-ecm to work are already fully factored.[/QUOTE]

My answeer was related to line 5 of the picture on post #1. For completeness.

table revised, and some questions
 

Thanks everyone!

URLs, notes, MLucas and a column for non-intel CPUs have added

LLR: Lucas-Lehmer-Riesel? k 2^N+-1? Does this also do Mersennes efficiently? Is LLR different from LLRCuda? Where's it found?
gpuOwl: where would I find this and information on it?
GPU-ecm: where would I find this and information on it?
What became of GLucas?
(Yes I did some web searching for each. I don't want to waste anyone's time. That's also the motivation for making the table.)

gpuOwL : [url]https://github.com/preda/gpuowl[/url]
discussion about it on mersenneforum: [url]http://www.mersenneforum.org/showthread.php?t=22204[/url]

I googled "LLR prime" and got a bunch of links to forum threads where the software releases are announced and linked.

GMP-ECM version 7 includes a -gpu flag which uses CUDA for stage 1 of ecm. However, it's limited to 1018 bits, smaller than any unfactored mersenne number; so it's useful for other projects, but not specificially for factoring mersennes.

There are a handful more factoring programs like mmff ([url]http://www.doublemersennes.org/download.php[/url]), some home brew stuff (user TJAOI might be one, Graff [Gareth] has his own IIRC), etc.

This afternoon's update
 

Thanks to all for your input. I've added GpuOwL, versions, notes, formatting, and switched to pdf so links can be used more easily.

I'm sorry I wasn't more clear with you at the outset, and part of that is I wasn't entirely clear myself, about this:

My intention was to collect in one place a reference of software available that is usefully fast and capable for factoring or Lucas-Lehmer testing Mersenne numbers, at or somewhat above the current wavefront of GIMPS effort, and organize the software coverage by approach, and computing hardware, for the operating systems of primary interest due to popularity and throughput potential. (Proth or Riesel software, and Crays or iPhones for example I think fall outside the scope. I'm open to new information that may persuade me. I felt I needed to draw a clear boundary, because there's so much variety out there. There's a lot of great, and interesting, software and pages and forums out there, and outside my intended scope.)

My purpose in creating this table is:
It makes maximizing my contribution easier. I've been running Prime95 for decades and my own cpu code before that, but I was new to and unfamiliar with using GPUs
Sharing it may make others' contribution easier also.
It may get more participants ramped up to speed earlier, and so their hardware too.
It may get more total horsepower applied to GIMPS
It may create less distraction for the various skilled coders, site administrators, forum moderators, etc.in the long run.

Pointers to additional mersenne prime hunting software or alerts to version updates of software are welcome, here or by PM.

[QUOTE=kriesel;463270]Thanks to all for your input. I've added GpuOwL, versions, notes, formatting, and switched to pdf so links can be used more easily.

I'm sorry I wasn't more clear with you at the outset, and part of that is I wasn't entirely clear myself, about this:

My intention was to collect in one place a reference of software available that is usefully fast and capable for factoring or Lucas-Lehmer testing Mersenne numbers, at or somewhat above the current wavefront of GIMPS effort, and organize the software coverage by approach, and computing hardware, for the operating systems of primary interest due to popularity and throughput potential. (Proth or Riesel software, and Crays or iPhones for example I think fall outside the scope. I'm open to new information that may persuade me. I felt I needed to draw a clear boundary, because there's so much variety out there. There's a lot of great, and interesting, software and pages and forums out there, and outside my intended scope.)

My purpose in creating this table is:
It makes maximizing my contribution easier. I've been running Prime95 for decades and my own cpu code before that, but I was new to and unfamiliar with using GPUs
Sharing it may make others' contribution easier also.
It may get more participants ramped up to speed earlier, and so their hardware too.
It may get more total horsepower applied to GIMPS
It may create less distraction for the various skilled coders, site administrators, forum moderators, etc.in the long run.

Pointers to additional mersenne prime hunting software or alerts to version updates of software are welcome, here or by PM.[/QUOTE]

The actual Mlucas version is 17.0

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]

CUDAPm1 runtime scaling, and comparison to CUDALucas
 

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. See the attachment. This is a somewhat different way of looking at test speed than the GPU Lucas-Lehmer or trial factoring performance benchmarks at [URL]http://www.mersenne.ca/cudalucas.php[/URL] etc. There is no P-1 factoring performance benchmarking data posted at [URL]http://www.mersenne.ca[/URL] to my knowledge.

Software for managing Mersenne hunting software
 

The attachment contains a summary grid I put together for software that helps run one instance or multiple instances of factoring or LL testing software implementations. Please comment:

1- Which did I miss entirely

2- additions, corrections, suggestions

Ancestry of available software
 

Some software was derived from other earlier software (or multiple others). The attached crude diagram shows my understanding of ancestor/descendant relationships, gleaned from sources such as source code comments/credits, and web pages. It's intended to show ancestry of code, not concepts. Code shown without connecting lines is believed to have been developed independently. The thin line between lucdwt and prime95 is intended to represent prime95's adverb "loosely".

As usual, please respond with any additions, corrections, comments.

If you put submitting spiders in the graph, then a mention of Misfit won't hurt...

Ancestry graph
 

Meant to include Misfit earlier. Oh well.

Ancestry updated
 

Changes since last time:
Switched to a better draw program, reformatted somewhat in doing so;
Added glucas

Available client management software table updated
 

Added "Mersenne manager". (which is actually separate programs, for tf, and for LL/DC.)

Available mersenne prime hunting software table updated
 

Added row for PRP testing in part 1,
updated and extended various data in part 2 to reflect recent software updates, etc.

Utilities for GPU computing etc.
 

Here are some things I've run across that I found useful or interesting, or have seen recommended by others.

Versions stated for each, and links, are current as of Jan 23 2017.
Subject to change without notice, no warranty express or implied, availability versus OS etc will vary, don't look a gift horse in the mouth.


For end users
-------------[CODE]Adjustment of GPU clock rates and fan curves (Use cautiously, test thoroughly for reliability)
MSI Afterburner https://www.msi.com/page/afterburner Windows, Android V4.4.2
EVGA Precision XOC Windows Vista through 10 https://www.evga.com/precisionxoc/ V6.2.3
NVIDIA http://www.overclock.net/forum/folding-home-guides-tutorials/1506137-ubuntu-f-h-installation-ubuntu-gpu-cpu.html#user_optional Linux
overclock and fan curve etc on AMD linux https://linuxconfig.org/overclock-your-radeon-gpu-with-amdgpu

CPU-Z Detailed information on your system hardware contents (down to DIMM serial numbers)
Windows 32 and 64 bit, English, Chinese.
https://www.cpuid.com/softwares/cpu-z.html V1.82

CUDALucas -memtest option for NVIDIA GPU memory reliability testing
Source, Windows, linux
https://sourceforge.net/p/cudalucas/wiki/Home/ V2.06beta

Factoring calculators online
see https://www.calculatorsoup.com/calculators/math/prime-factors.php
or https://alpertron.com.ar/ECM.HTM

"GPU-Z is a lightweight system utility designed to provide vital information about your video card and graphics processor." Extensive

features, including advanced tab showing OpenCL, CUDA, etc parameters; overclock, default clock; GPU BIOS backup.
Supports NVIDIA, AMD, ATI and Intel graphics devices; Windows XP through 10, 32 and 64 bit. https://www.techpowerup.com/gpuz/ V2.7.0

HWMonitor
Monitor temperatures, clock rates, power, disk utilization, battery status, etc.
AMD, Intel, NVIDIA; XP through Windows 10, 32 and 64 bit; English
https://www.cpuid.com/softwares/hwmonitor.html#version-history V1.34

hwinfo List all hardware on the system
lspci list and identify PCI devices
lsusb list and identify USB devices
These can be useful when trying to identify what would be a suitable driver for a piece of hardware linux https://en.wikipedia.org/wiki/Lspci

The PCI Utilities
"The PCI Utilities are a collection of programs for inspecting and manipulating configuration of PCI devices, all based on a common portable library libpci which offers access to the PCI configuration space on a variety of operating systems." linux, *BSD, Windows, etc
http://mj.ucw.cz/sw/pciutils/ V3.5.6

Tail (show last lines of a file) linux native command; addon for Windows http://tailforwin32.sourceforge.net/

Tee (native in linux; present in Powershell in some Windows versions) Sends stdout to both console and file

TightVNC remote desktop (for remote administration of systems otherwise lacking graphical remote desktop server support, or cross-platform; versions compatible to Windows 10 and back to Windows 95 and NT4; linux) http://tightvnc.net/ V2.8.8
Additional remote desktop choices at https://lifehacker.com/5080121/five-best-remote-desktop-tools including for MacOS
[/CODE]Suggestions?



Checking OpenCL on a system
---------------------------
[CODE]
clinfo https://sourceforge.net/projects/clinfo/ indicated as pre-alpha, for linux; from 2010

OCLDeviceQuery.exe Query OpenCL properties of devices and store in text file in current directory
http://developer.download.nvidia.com/compute/DevZone/OpenCL/Projects/oclDeviceQuery.zip
https://github.com/sschaetz/nvidia-opencl-examples/blob/master/OpenCL/src/oclDeviceQuery/oclDeviceQuery.cpp
Use results with caution; understates V2.0 as 1.2. From 2012

OpenCL hardware detection listing, etc https://streamhpc.com/blog/2011-12-29/opencl-hardware-support/
[/CODE]Suggestions?



Development oriented
--------------------
[CODE]
Intel OpenCL drivers, runtimes and SDK (CPU and Intel GPU)
https://software.intel.com/en-us/articles/opencl-drivers

AMD tools and SDKs https://developer.amd.com/tools-and-sdks/

NVIDIA OpenCL https://developer.nvidia.com/opencl
NVIDIA Performance Analysis https://developer.nvidia.com/performance-analysis-tools
NVIDIA CUDA Toolkit https://developer.nvidia.com/cuda-downloads
NVIDIA drivers http://www.nvidia.com/Download/index.aspx?lang=en-us

Microsoft Visual Studio Community Edition
"A free, fully featured, and extensible solution for individual developers to create applications for Android, iOS, Windows, and the web."
Target several platforms from one development platform. Windows, Mac
https://www.visualstudio.com/downloads/ 2017

MinGW free and open source software development environment for creating Microsoft Windows applications.
"MinGW can be run either on the native Microsoft Windows platform, cross-hosted on Linux (or other Unix), or
'cross-native' on Cygwin."
https://en.wikipedia.org/wiki/MinGW
http://mingw.org/

"VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2. See "About VirtualBox" for an introduction. Presently, VirtualBox runs on Windows, Linux, Macintosh, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, Windows 7, Windows 8, Windows 10), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x
and 4.x), Solaris and OpenSolaris, OS/2, and OpenBSD." https://www.virtualbox.org/ V5.2.6
[/CODE]Suggestions?


(end)

Available software, updated
 

Numerous updates. See the change notes and bold text.

FFT lengths reference list
 

Table of 7-smooth numbers that are multiples of 2^10, from 2^10 to 2^26.

Available software, updated
 

A couple of corrections from the previous update, a couple of clarifications

Four primality test programs' performance charted together
 

Note the speed disparity of the GTX480 CUDA gpu, (at 244W), at 3.6-3.7 times the hardware performance rating of the OpenCL low power card (50W), when interpreting these values. Normalizing to equal speed hardware, gpuOwL seems to perform fastest by a comfortable margin.

Work coordination sites vs type and exponent
 

Here's another condensation of information I gathered along the way. Please reply here or by PM with any corrections or additions you may have.

Devcon 6 (Automating recovery from TDR events for old gpus)
 

Windows has provision for detecting delays in display devices responding to it. Above a certain threshold delay, it concludes the device is hung and restarts it. Even if the gpu involved is only running math code, not a display, and may not have a display connected.
(You can find such restarts in the system event log. For example, Event ID 4101; something like "Display driver nvlddmkm stopped responding and has successfully recovered." for NVIDIA. AMD gpus are also affected.) Older gpus with low compute compatibility levels have issues with these display restarts. (For example, GTX480, Quadro 4000, which are Compute Capability 2.0) As GIMPS work advances to larger exponents, computations take longer. Windows detects a long time for the gpu to respond and interprets it as a hung device, and stops and restarts it. Unfortunately, it does this in a way that does not reconnect to existing sessions of GPU-Z or other utilities, or to CUDA applications such as CUDALucas or CUDAPm1 or mfaktc, or the opencl equivalent applications.

Historically, the applications have been wrapped in batch scripts to restart them, and adding a TdrDelay value in the registry larger than the implicit default has been recommended. However, these are incomplete solutions, that often fail. A system restart clears it up. The restart is disruptive to gpu applications running on other gpus, prime95, and anything else running on the system, and requires operator intervention to stop and restart it all.

But, there is another approach. In Device Manager, disable and reenable the errant display device to avoid a system restart. I've seen this reenable access to sensor readings of a GPU in a preexisting GPU-Z session, as well as make the gpu available again for use by a newly launched CUDA application. The system restart is avoided, allowing prime95 and other GPUs' application instances to continue uninterrupted.

Can the device disable/reenable be done from the command line or a batch script, minimizing idle time and operator intervention? Yes, using the appropriate version of devcon.exe (available in Visual Studio, the Windows Driver Kit, etc) per
[URL]https://superuser.com/questions/429016/enable-disable-windows-7-device-via-command-line[/URL]
[URL]https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon[/URL]

Such a script may benefit if it includes delays between commands. Some Windows OS versions don't support the timeout command. Delays can be provided on versions where timeout generates an error, by conditional ping to a nonexistent address, padding the number of seconds wait with 3 zeros since ping timing is in milliseconds.
[CODE]set delay=3
set nonexist=192.168.2.3
timeout /t %delay%
if errorlevel 1 ping %nonexist% -n 1 -w %delay%000[/CODE]Another piece of the puzzle is the device id for devcon.exe in the correct form.

Another piece of the puzzle is getting the batch file containing the devcon command to run as administrator. Otherwise devcon will run at too low a privilege level and list devices but not control them, even when the batch file is launched by an account with administrator permissions. (Most online how-tos for it omit that crucial little detail.) For getting devcon to work, see [URL="http://classicshell.net/forum/viewtopic.php?f=5&t=423"]http://classicshell.net/forum/viewtopic.php?f=5&t=423 [/URL]particularly the requirement to create a shortcut to force the batch file to run as administrator, and [URL]https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon-examples#ddk_example_17_display_the_status_of_all_devices_on_the_local_computer[/URL] to find the names of your gpu device(s).

So, putting the pieces together:
a) make the batch file that runs the CUDA app (CUDALucas, CUDAPm1) or OpenCl app that is affected by driver timeouts. In my experience mfaktc seems unaffected.
b) make a shortcut to the batch file, and in the advanced tab of the shortcut properties, set it to run as administrator
c) modify the shortcut to cmd /k batchfile so it sticks around after it exits and the flow can be examined
d) install devcon.exe on the system, either in the working directory of the CUDA app or in \windows\system32, or somewhere else that's in your path.
e) use devcon.exe interactively to obtain the unique device ID for the gpu to be controlled
f) modify the batch file to use the unique device ID obtained, in the disable and enable lines, and adjust other settings as needed. Be sure to use enough of the id that it identifies a unique gpu device matching the CUDA device number affected.
g) test
h) make adjustments to TDR related registry settings as needed; increasing TDRDelay helps some; increasing TDRDdiDelay may also help. See [URL]https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys[/URL] for the list and defaults
i) use and enjoy

Draft batch file, to be run from the high-privilege shortcut:
[CODE]
set delay=1
set maxdelay=10
set count=0
set countmax=5
set exe=cudaPm1_win64_20130923_CUDA_55.exe
set model=GeForce GTX 480
set dev=1
set nonexist=192.168.2.3
cd "\Users\ken\My Documents\cudapm1"
echo worktodo.txt >>cudapm1.txt
goto loop
: change the above set commands etc to suit your situation and preferences
: following is what does the production work, from the worktodo file, putting results in the results file and appending history in the cudapm1.txt log file
: limited looping may be useful in some cases (such as Windows TDR events); too high a count or no limit mostly pointlessly inflates log size, especially if worktodo is emptied

:loop
echo batch wrapper reports (re)launch of %exe% on %model% at %date% %time% reset count %count% of max %countmax% >>cudapm1.txt
title %computername% model %model% %exe% dev %dev% reset count %count% (%0)
%exe% -d %dev% >>cudapm1.txt
echo batch wrapper reports exit at %date% %time% >>cudapm1.txt
echo attempting disable/enable cycle on gpu device >>cudapm1.txt
devcon disable "PCI\VEN_10DE&DEV_06C0&SUBSYS_14803842" >>cudapm1.txt
devcon enable "PCI\VEN_10DE&DEV_06C0&SUBSYS_14803842" >>cudapm1.txt
timeout /T %delay%
if errorlevel 1 ping %nonexist% -n 1 -w %delay%000
if %delay% lss %maxdelay% set /A delay=delay*2
if %delay% gtr %maxdelay% set delay=%maxdelay%
set /A count=count+1
if %count% lss %countmax% goto loop
echo at %date% %time% countmax=%countmax% reached, exiting batch file
[/CODE]

Reference material for gpu mersenne hunting
 

I was offered "a blog area to consolidate all of your pdfs and guides and stuff" and accepted.
Feel free to have a look and suggest content. (G-rated only;)
General interest gpu related reference material [URL]http://www.mersenneforum.org/showthread.php?t=23371[/URL]
That links to several application-specific reference threads.
Future updates to material previously posted in this "Available Software" thread will probably occur on the blog threads and not here. Having multiple threads and in-place update makes it more manageable.

[QUOTE=VBCurtis;463156]How does GPU-ecm help do anything with mersennes? All Mersennes small enough for GPU-ecm to work are already fully factored.[/QUOTE]


gpu-ecm can still be used for partially factored mersenne-numbers with small enough composites like M1217, for which I'm just giving a try.

[QUOTE=heliosh;488948]gpu-ecm can still be used for partially factored mersenne-numbers with small enough composites like M1217, for which I'm just giving a try.[/QUOTE]

Have fun. gpu-ecm has its uses, in the small exponents. As does ecm in mprime/prime95 (up to ~20M exponents) which I'm running now.

The discussion about what to include or not in the list of available software led me to clarify my purpose for creating the thread, in [URL]http://www.mersenneforum.org/showpost.php?p=463270&postcount=10[/URL]
(The spectrum of on-topic, tangential, and off-topic is common, so no problem there.)
The person you responded to correctly perceived early my initially unclearly stated intent; to find and tabulate software for productive use at the wavefront of efforts to find new Mersenne primes, which are now in the tens of millions of bits exponent and above.

gpu-ecm as far as I know is limited to 4K bit exponents. For that reason, I've listed gpu-ecm in the last section of the available software table. (not suitable for pursuing a big new Mersenne prime, not included)

update
 

The Available Mersenne hunting software list has been updated in post two of [URL]http://www.mersenneforum.org/showthread.php?p=488291#post488291[/URL]

Another update
 

[QUOTE=kriesel;490189]The Available Mersenne hunting software list has been updated in post two of [URL]http://www.mersenneforum.org/showthread.php?p=488291#post488291[/URL][/QUOTE]
Added gmp-ecm, updated various table entries

[QUOTE=kriesel;492128]Added gmp-ecm, updated various table entries[/QUOTE]


It would be nice if we could adapt Kunde21/MersenneManager to send/receive PRP results and to extend it to work with many instances of mersenne prime search program.

Another update today, mostly due to recent gpuOwL advances
 

[QUOTE=kriesel;490189]The Available Mersenne hunting software list has been updated in post two of [URL]http://www.mersenneforum.org/showthread.php?p=488291#post488291[/URL][/QUOTE]
While you're there, look around at some of the other reference information gathered

Available Mersenne Hunting Software reference updated
 

Updated just now, re prime95/mprime, mlucas, and gpuowl.
I don't post a notice of update here every time, but this time around seemed significant.
[url]https://www.mersenneforum.org/showpost.php?p=488291&postcount=2[/url]

I'm no longer posting notices of updates here. Just go to [URL]http://www.mersenneforum.org/showpost.php?p=488291&postcount=2[/URL] for data on the available Mersenne hunting software applications, [URL]http://www.mersenneforum.org/showpost.php?p=488292&postcount=3[/URL] for data on software for managing such applications, or [URL]https://www.mersenneforum.org/showthread.php?t=24607[/URL] for the site map for the whole reference documentation tree. If you don't find what you're looking for, check the drafts thread, then ask questions. Much of the content was created because of questions that identified gaps. And if you have answers, or leads to new software, those are much appreciated too.

Reference material expansion
 

The reference material tree begun with a focus on gpu-based GIMPS computing for finding the next Mersenne prime has been expanded to include cpu-based and cloud-based content. See [URL]https://www.mersenneforum.org/showthread.php?t=24607[/URL]
Expansion will continue as I identify additional topics and write them.
There's a wide variety of content, from introductory, to how-to, to reference data for developers.
Suggestions for new reference content and other comments are always welcome, in the relatively few discussion threads also located in that thread tree.

Suggest the OP add actual links to the various currently-relevant programs (along with brief summaries of their target platforms), and their how-to threads (if those are separate), in Post #1, and update those to reflect new software and hardware platforms having their own how-to threads. Thank you!

[QUOTE=ewmayer;535068]Suggest the OP add actual links to the various currently-relevant programs (along with brief summaries of their target platforms), and their how-to threads (if those are separate), in Post #1, and update those to reflect new software and hardware platforms having their own how-to threads. Thank you![/QUOTE]Can't; not a moderator of this thread, can't modify post one. The current and maintained version is at [url]https://www.mersenneforum.org/showpost.php?p=488291&postcount=2[/url]. The links you seek are in the attachment there. The whole reference tree's table of contents is at [url]https://www.mersenneforum.org/showthread.php?p=521922#post521922[/url]