Strategic couple and dribble checks (PRP's, P-1's, and special Certs too)

[Uncwilly]

New sticky to house the lists. Post requests for DC and TC's and claim of exponents. The mods will keep the lists maintained in the top posts. Post with requests for rechecks and exponents claimed will be removed when the lists are updated.
Always register your claims right away. Those that are claimed but not registered will remain on the lists. If they are listed as being assigned to Anonymous (or others not known to be finishers) and show no progress, they will be moved to the watch list section.

The lists are kept fairly up to date.

The easy way to get some assignments (with Prime95):

• Grab the lines of the exponents that you will do.
• Stop Prime95.
• Edit your worktodo.txt, inserting the new lines, save it, and close the editor.
• Restart Prime95
• Go to the menu Advanced-> Manual Communication
• Make sure "Contact PrimeNet server now" and "Send new expected completion dates to server" are checked. Hit OK
• After Prime95 is done communicating, look and see if any of the new exponents don't have an Assignment ID (because they were already assigned.) If they don't, stop Prime95, reopen the worktodo.txt, remove those lines, save, then restart Prime95

Instructions for mprime:

• Grab the lines of the exponents that you will do.
• Stop mprime.
• Edit your worktodo.txt, inserting the new lines, save it, and close the editor.
• Delete the line starting with `LastEndDatesSent=` in `local.txt`.
• Run `mprime -c` for force communication, and watch for errors: exponents that didn't get assignments should be removed from `worktodo.txt`.
• Restart mprime.

For gpu runs, see https://www.mersenneforum.org/showpo...4&postcount=21 and follow links it contains as needed.

[Uncwilly]

This is the location for the DC list:

Any exponent that has had a single First Time LL should no longer have an LL DC. It should get a PRP on a machine running Prime95 v30+ or GpuOWL v 6.11-318+ that produces VDF (proof files). The extra effort to run the certification from the proof files vs the need for TC tips the balance in favour of the PRP (with the better error checking code.) PrimeNet will see these as FTC PRP's and not hand out an assignment ID. A work around is to register them as a DoubleCheck (LL), then replace the entry in your WorkToDo.txt with the PRP entry with the assignment ID.

PRP=1,2,83961433,-1,76,0
PRP=1,2,84013277,-1,76,0
PRP=1,2,84023363,-1,76,0
PRP=1,2,84155879,-1,76,0
PRP=1,2,84192467,-1,76,0
PRP=1,2,84198743,-1,76,0
PRP=1,2,84224431,-1,76,0
PRP=1,2,84297923,-1,76,0
PRP=1,2,84308857,-1,76,0
PRP=1,2,84325013,-1,76,0
PRP=1,2,84781223,-1,76,0
PRP=1,2,84843697,-1,76,0
PRP=1,2,84893569,-1,76,0
PRP=1,2,84913909,-1,76,0
		
PRP=1,2,85570697,-1,76,0
PRP=1,2,85984321,-1,76,0
PRP=1,2,85991401,-1,76,0
PRP=1,2,86120491,-1,76,0
PRP=1,2,86219849,-1,76,0
PRP=1,2,86300813,-1,76,0
PRP=1,2,86410861,-1,76,0
PRP=1,2,86651011,-1,76,0
PRP=1,2,86926523,-1,76,0
PRP=1,2,87095759,-1,76,0
PRP=1,2,87199163,-1,76,0
PRP=1,2,89130749,-1,76,0
PRP=1,2,89323649,-1,76,0
PRP=1,2,89695157,-1,76,0
		
PRP=1,2,90129101,-1,76,0
PRP=1,2,90187913,-1,76,0
PRP=1,2,90553741,-1,76,0
PRP=1,2,90816041,-1,76,0
PRP=1,2,90831599,-1,76,0
PRP=1,2,91076681,-1,76,0
PRP=1,2,91355993,-1,76,0
PRP=1,2,91414471,-1,76,0
PRP=1,2,91528733,-1,76,0
PRP=1,2,91539529,-1,76,0
PRP=1,2,91762823,-1,76,0
PRP=1,2,91808117,-1,76,0
PRP=1,2,91815293,-1,76,0
PRP=1,2,91815821,-1,76,0
PRP=1,2,91858783,-1,76,0

PRP=1,2,131709491,-1,77,0
PRP=1,2,131709719,-1,77,0
PRP=1,2,131709997,-1,77,0
PRP=1,2,131710003,-1,77,0 
PRP=1,2,131719591,-1,77,0
PRP=1,2,131719619,-1,77,0
PRP=1,2,131999083,-1,77,0
PRP=1,2,150015091,-1,77,0
 .

Suggestion: Copy both entries into your Worktodo, comment out the PRP entry by preceding it with a *, then do a coms with PrimeNet to get an AssignmentID(s), copy AID to the PRP entry (between the = and the 1 {using a comma of course}), then remove or comment out the DC line and remove the comment out on the PRP line.

[Uncwilly]

This is for the list of needed triple (and higher order) checks.

Exponents with 2 Unverified results:
Cat 0

Cat 1

Cat 2

Cat 3
DoubleCheck=70629089,75,1

Higher level

Exponents with 1 Suspect result + 1 Unverified result:(use LL to clear/confirm suspect results)
Cat 1

Cat 2

Cat 3

Higher level
.

Exponents with 1 LL + 1 PRP result:

NOT gpuowl (shift 0) unless recent version with proof file generation:
.

Quad and higher

.

The "Watch list". Exponents assigned to Anon or others outside this thread that have yet to show progress. Do not poach these!

.

[GP2]

PRP checks. Note: please use V30 for these.

PRP=1,2,543656371,-1,83,0
.

Special Cert assignments Note: these will take much more time than a standard cert run.
They will show up as assigned to -Anonymous-, but will be transferred to your user id once your system reports the assignment.

.

[Uncwilly]

Potentially bad P-1 results that need to be redone.

Place holder post. There are ~50 P-1 tests that might be bad. If Madpoo provides the list it will go here:

.

[ewmayer] @Uncwilly: Are these results suspect due to a bug in one particular client? If so, would you or Aaron please provide [do|don't]-run-under guidance together with the assignments?
[uncwilly] @ewmayer: Can't find Aaron's post at the moment. The forum search does not accept P-1 as a keyword. Look at the original date on this post and check for Aaron's post 0->30 days before.

[ATH]

Originally Posted by endless mike

Claimed this one.
Is there a post that describes what all the fields are in a worktodo entry for PRP? I always guess and hope I did it right.

PRP=EDDC25414116177C4F046D79BE11A463,1,2,96365519,-1,76,0,3,1

Added the 2 extra arguments that can be in the assignment: ",3,1"

1,2,96365519,-1: Number to test: 1 * 2^96365519 - 1
76: Trial factored to 2⁷⁶
0: Not sure about this one. (Maybe if P-1 has been done or not? or how many PRP tests has already been done on the exponent?) [EWM comment: Per the assignment-format examples on my Mlucas readme page, a 1 following the TF bit depth means this expo has had some p-1 testing done but could use a deeper round of p-1; thus a 0 presumably means no deeper p-1 is warranted.]
3: PRP base 3. This is always 3 as standard for normal GIMPS candidates.
1: PRP type 1. This can vary between 1-5, but mostly 1 or 4 for older gpuowl tests. Prime95 and newer gpuowl versions and Mlucas? default to type 1 (and Prime95 uses type 5 for PRP-CF tests on exponents with known factor(s)).

Both PRP base and PRP type has to be the same for the PRPDC test as the original PRP test.


PRP type from undoc.txt, the "(default is 5)" is only for PRP-CF tests, the type number is 1 on normal PRP tests.

PRP supports 5 types of residues for compatibility with other PRP programs.  If
a is the PRP base and N is the number being tested, then the residue types are:
1 = 64-bit residue of a^(N-1), a traditional Fermat PRP test used by most other programs
2 = 64-bit residue of a^((N-1)/2)
3 = 64-bit residue of a^(N+1), only available if b=2
4 = 64-bit residue of a^((N+1)/2), only available if b=2
5 = 64-bit residue of a^(N*known_factors-1), same as type 1 if there are no known factors
To control which residue type is generated, use this setting in prime.txt:
	PRPResidueType=n		(default is 5)
The residue type can also be set for PRP tests in worktodo.txt entries making
this option somewhat obsolete.

[edit]
And also for base >3, some versions of gpuowl, PRP res type 0.
Gpuowl supported PRP res type was 1 for some versions, 4 for others, 1 currently.

Worktodo formats for all common applications are described in https://www.mersenneforum.org/showpo...8&postcount=22

[Uncwilly]

DC's on suspect single LL's should no longer be done.

Any single suspect LL should be redone with v30 as PRP-VDF. The balance between the DC and higher than usual TC rate vs running a fresh a PRP & cert lean toward the PRP path to require fewer cycles long term. The error checking is better on PRP.

TC-LLs still make sense to clean up as LL (the required quad rate is low enough).

[tdulcet]

Originally Posted by Uncwilly

The easy way to get some assignments

[...]

For gpu runs, see https://www.mersenneforum.org/showpo...4&postcount=21 and follow links it contains as needed.

As people may have seen from my big announcement yesterday, @danc2 and I's PrimeNet Python script now fully supports reserving individual assignments using the register assignment endpoint of the PrimeNet v5 API. I suspect most users using this functionality will be those following this thread, so I thought I should provide more detailed instructions here.

This works the same as with Prime95/MPrime. It also supports all worktypes supported by the Mlucas, GpuOwl and CUDALucas programs, including PRP, LL and P-1 assignments. For users of these GIMPS programs, this should be much easier and less tedious than those two existing options explained in @kriesel's post.

Instructions for the PrimeNet script:

1. Grab the lines for the exponents that you want to do.
2. Optionally stop the PrimeNet script and the GIMPS program (Mlucas, GpuOwl or CUDALucas).
3. Open the worktodo.txt (GpuOwl/CUDALucas) or worktodo.ini (Mlucas) file, insert the new lines, save it and close your editor. If you elected not to stop the script and/or the GIMPS program, create a new worktodo.add file instead.
4. Optionally restart the PrimeNet script and watch for errors. Any exponents that did not get an assignment can safely be removed from the respective worktodo file.
5. Optionally restart the GIMPS program.

As with Prime95/MPrime, the local.ini configuration file will contain a line starting with LastEndDatesSent, but users do not need to delete this line. Our PrimeNet script will always check for any assignments to register each time it is run and once per update interval based on the -t/--timeout option. Feedback is welcome!

Originally Posted by Uncwilly

PrimeNet will see these as FTC PRP's and not hand out an assignment ID. A work around is to register them as a DoubleCheck (LL), then replace the entry in your WorkToDo.txt with the PRP entry with the assignment ID.

If this would be useful for anyone, I could easily add an option to our PrimeNet script to automatically convert LL assignments to PRP after they are registered.

[JHagerson]

Thank you for your work.

If this would be useful for anyone, I could easily add an option to our PrimeNet script to automatically convert LL assignments to PRP after they are registered.

It would be helpful if the server recognized that PRP assignments in the double-checking hinterlands are not Category 0 and overdue after 7 days, but that may be someone else's bailiwick.

Thanks again.

[tdulcet]

Originally Posted by JHagerson

It would be helpful if the server recognized that PRP assignments in the double-checking hinterlands are not Category 0 and overdue after 7 days, but that may be someone else's bailiwick.

Thanks again.

No problem, I am happy to help. 😀

It is not clear from your response if you are actually requesting this proposed new functionality, but I will consider adding something like a --convert-ll-to-prp option in the next version of the script to automatically convert LL assignments to PRP. You may also be interested in the 155 worktype (double-check using PRP with proof), which is supported by our PrimeNet script for GpuOwl users.

You would of course need to talk to @Prime95 about any issues with the assignment rules and the PrimeNet server.

[JHagerson]

Originally Posted by tdulcet

No problem, I am happy to help. 😀

It is not clear from your response if you are actually requesting this proposed new functionality, but I will consider adding something like a --convert-ll-to-prp option in the next version of the script to automatically convert LL assignments to PRP. You may also be interested in the 155 worktype (double-check using PRP with proof), which is supported by our PrimeNet script for GpuOwl users.

You would of course need to talk to @Prime95 about any issues with the assignment rules and the PrimeNet server.

I used the server to request three manual assignments of Double-check using PRP with proof. The server initially gave me 7 days to complete each assignment. Then, it automatically renewed each assignment for another length of time. My home PC is only a "sedan," when many who haunt this forum drive "supercars." One of my assignments 81034027 was booted from worktodo.ini because it was estimated to require too long to run. I am currently processing that assignment "under the radar" because my PC communicates daily with the server but does not report progress. If I understand correctly, @Prime95 said that very few are working in the 80MM space, and I don't need to worry about poaching. I like to show that I'm contributing to my team. Oh, well.

To avoid future problems, I plan to take assignments from Uncwilly's list one at a time.