[QUOTE=hansl;521669]From new participant reference:

Needs a superscript: 2[sup]p[/sup]-1
[code]2[B][[/B]sup[B]][/B]p[B][[/B]/sup[B]][/B]-1[/code][/QUOTE]
Oops. Done. Say hi to gretl.
[url]https://www.youtube.com/watch?v=9246msCh7x4[/url]

[QUOTE=nomead;517219]About the manual assignment progress reports. Different programs have wildly different progress logs. Example from Mlucas:

[C][May 20 03:38:41] M50346019 Iter# = 24280000 [48.23% complete] clocks = 00:26:42.587 [160.2587 msec/iter] Res64: 54912F2731A45A41. AvgMaxErr = 0.042192089. MaxErr = 0.062500000. Residue shift count = 12144693.
[/C]
But minimum common requirements should be current iteration count and Res64/shift so that interim residues could be stored, if needed.

I propose that instead of having the manual results submission form decipher many different log formats, there should be a simple common format, and let the client submission script do the conversion to that.[/QUOTE]
What I was looking for was manual progress reports that are submitted manually, by the user, not by some script. Motivations are to provide the server with interim residues from manual assignments, keep a manual assignment from being expired, and possibly detect error conditions earlier.

Perhaps a useful but easy form to enter would be:
<appname> <version> <console output line>
Only few <appname> <version> combinations would be supported.

Candidates are
CUDALucas v2.06
GpuOwL v6.5 and maybe v5.0 v3.8
These could be case-insensitve.

So an example would be
cudalucas 2.06 followed by an entire console output line copy/pasted. Like this:
cudalucas 2.06 | May 30 22:04:09 | M89000671 10000000 0xf2af4c9456abf0de | 5040K 0.09766 39.4100 197.05s | 36:01:03:19 11.23% |

Then the server can easily parse any such interim progress submission as
<appnamestring><spacedelimiter><appversionstring><spacedelimiter><consolelinestring>, parse the consolelinestring in that app/version's way, and get the exponent, iteration number, and interim residue, or if the appname version combination at the front is not a supported one, respond
"Application and version combination submitted is not supported by the manual results page."
If the error is because the user typed cudlucs instead of cudalucas, or 2.60 instead of 2.06, they can try again.

[QUOTE=kriesel;522098][B]Mlucas[/B]:
[Test|DoubleCheck]=[<AID>,]<exponent>,<how_far_factored>,<p-1_done>
DoubleCheck=B83D23BF447184F586470457AD1E03AF,22831811,66,1
Test=DDD21F2A0B252E499A9F9020E02FE232,48295213,69,0
Test=332220523,80,1[/QUOTE]

Mlucas can also handle just a prime exponent on a line by itself, which triggers an LL test of the corresponding Mersenne number. But if one is using the primenet.py script for assignment/results management, its "do I need to fetch new work?" calculation only uses official Primenet-server-style assignments, with the 32-digit hex code, like the first 3 lines in the above sample.

The next release, v19, will add PRP support.

From point 5 of post 18 of the Prime GPU Computing reference material thread, you mentioned that mersenne.ca has exponent status up to 10^10. This is true, and it also has a list of exponents beyond that limit which have factors [URL="https://www.mersenne.ca/export/"]available to be downloaded (see the bottom of the page).[/URL]

(grrr, man, my OCD gets ticked when I see #value and #div0 in those tables!)

Thanks for doing this!
 

Feel free to delete this post (as it isn't reference material), but I just wanted to say thanks for doing this.

The curation of this relatively complex subject domain is important and beneficial! :tu:


(Apparently referring to the Google Colab blog thread I've started in this blog; moved here from that thread; Kriesel)

How much faster is 5700 XT vs RX480? How long it takes to PRP on the 90M exponent range?

I have built mlucas on the Colab, using the reverse tunnel code. See [URL="https://mersenneforum.org/showpost.php?p=528099&postcount=40"]this[/URL] and subsequent replies for debug stuff from me and Ernst.
And for post 9 of the Colab reference, another way to work with a worktodo.txt would be to directly connect to the server via SSH using the method described [URL="https://mersenneforum.org/showthread.php?t=24840"]here[/URL] and then use your favorite text editor to modify/create the file (which may require using apt-get to get certain ones, like emacs).

A suggestion for the GIMPS progress thread: some people like to factor numbers, either partially or completely. For example, petrw1 has his [URL="https://www.mersenneforum.org/showthread.php?t=22476"]thread on his efforts to get under 20M unfactored exponents below the PrimeNet boundary of 1G[/URL] and GP2 routinely posts [URL="https://www.mersenneforum.org/showthread.php?t=19407"]exponents which are fully factored.[/URL] Perhaps these are things to track?

[QUOTE=Dylan14;530236]Perhaps these are things to track?[/QUOTE]Thanks for your input. They occur to me as having little or nothing to do with finding new mersenne primes, the goal of GIMPS.

"Top of" navigation links addition
 

To hopefully aid navigation in this large and growing collection of reference posts, I've begun adding links for
[B]Top of thread[/B] where I think it makes sense (page 2 or higher of multipage threads)
and [B]Top of reference tree[/B] to reference posts, beginning with the gpu computing reference thread, which got
[QUOTE]Top of thread: [URL]https://www.mersenneforum.org/showpost.php?p=488289&postcount=1[/URL]
Top of reference tree: [URL]https://www.mersenneforum.org/showpost.php?p=521922&postcount=1[/URL][/QUOTE] on pages 2 and 3, and
[QUOTE]Top of reference tree: [URL]https://www.mersenneforum.org/showpost.php?p=521922&postcount=1[/URL][/QUOTE] on page 1

Does this seem useful? Less clear than some other naming? Suggestions?