[QUOTE=GP2;517494]the worktodo file and the All CPUs section of [URL]https://www.mersenne.org/workload/[/URL] had conflicting information for the residue type for the [B][I]same[/I][/B] assignment. So the All CPUs section should instead accurately reflect the actual residue type for the assignment.[/QUOTE]Exactly!
For the same single assignment, I looked 3 places.
The assignments page was internally consistent, but did not match what the prime95 instance had in its worktodo file and so is presumably doing. The two PRP= lines given below are the same aid/assignment, and should match exactly, but differ in residue type.

[CODE]This is a PRP DC delivered by the Primenet API;
PRP=(aid),1,2,79335979,-1,75,0,3,[B]1[/B] in the worktodo file,
PRP=(aid),1,2,79335979,-1,75,0,3,[B]4[/B] in the All cpus and system-specific listings on my assignments page[/CODE]
Checking again today:[CODE]
PRP=EE...A0,1,2,79335979,-1,75,0,3,[COLOR=DarkOrange][B]4[/B][/COLOR] in All CPUs section of assignments page
PRP=EE...A0,1,2,79335979,-1,75,0,3,[COLOR=DarkOrange][B]4[/B][/COLOR] in cpu-specific (Parrot) section of assignments page
PRP=EE...A0,1,2,79335979,-1,75,0,3,[COLOR=SeaGreen][B]1[/B][/COLOR] in worktodo.txt on Parrot prime95 instance[/CODE]
Same everything, for same assignment, except residue type 1 in the worktodo is not a match to 4 in the assignment page.
It would be useful if prime95 indicated in its worker window title bar whether it thinks it's doing a first test or doublecheck, or what residue type, and indicated in its log files what residue type etc it got assigned. It only indicates when assigned, exponent, AID, and PRP, in prime.log.

[QUOTE=kriesel;517485]Why not have the page provide defaults, that correspond to the category selected[/QUOTE]It does now do that.

Not counting the "what makes sense" choices, there are 12 permutations of choices on the Manual GPU Assignments page (3 for preferred work range * 4 for work preference). I just tried all of them; the only combinations of choices that yielded anything other than an Error code 40, are TF for 100M with any of the four work preference choices -- and those all gave assignments in the 332M range.


The default ranges did show up in the "Optional exponent range field," but the 8 permutations involving TF for DCs and LLs all returned that Error code 40 for me.

[QUOTE=GP2;517494]The [c],75,0,3,[/c] has a zero in the middle, which is the number of tests saved. This parameter only makes sense for P−1 assignments, and is just a placeholder here, so it can always be set to zero.

Also, I'm not sure if I'm correctly interpreting what kriesel wrote, but it seems like the worktodo file and the All CPUs section of [url]https://www.mersenne.org/workload/[/url] had conflicting information for the residue type for the [I]same[/I] assignment. So the All CPUs section should instead accurately reflect the actual residue type for the assignment.[/QUOTE]

Whoops, I forgot about that 0 in there showing how many tests would be saved.

For what it's worth, the /workload page will *always* show 0 there. :smile: On the other hand, when the client gets the assignment from the server that first time, it should be correct.

What Kriesel said was interesting, because if I look at that example correctly, the one that the "/workload" page shows should be the correct one since it matches the most recent previous test.

Maybe the auto-assignment got confused in that case because there was the earlier test with different base/type values. If so, that seems like a bug in the assignment generator where it didn't pick the most recent PRP test to match? Not sure.

Sometimes it's hard for me to know what is by design and what's by accident. :smile:

[QUOTE=James Heinrich;517514]It does now do that.[/QUOTE]
Tried it out this morning, got for first time LL TF, defaults, lowest exponents preference, lower limit surprisingly low at 83+M (well below 91+million where P-1 is now being assigned, or even 85M where primality tests are being assigned), and an upper limit of 93 million, which resulted in error 40 no assignments available. Bumped the upper limit to 95 million, got assignments 9305xxxx. Maybe the ranges selected are off by one in some table?

It would be nice if clicking "get more assignments" displayed a page with the previous choices made in that browser /page session, rather than resetting to default load on everything.

If I want ALL the same choices, including number of assignments, just reload page works to get another batch of assignments,
but if I want to change just one field, it's "get more assignments" and then set everything again.

[QUOTE=kriesel;517565]... upper limit of 93 million, which resulted in error 40 no assignments available. Bumped the upper limit to 95 million, got assignments 9305xxxx. Maybe the ranges selected are off by one in some table?[/QUOTE]Not really, but the upper limit is dynamically chosen based on the "active range" plus a little bit. I've bumped the upper limit by +1M so it should have a better chance of finding available work now.

[QUOTE=kriesel;517565]It would be nice if clicking "get more assignments" displayed a page with the previous choices made in that browser /page session, rather than resetting to default load on everything.[/QUOTE]Done.

[QUOTE=Madpoo;517531]
Sometimes it's hard for me to know what is by design and what's by accident. :smile:[/QUOTE]There's another use for design and documentation.

I just went back into the Manual GPU Assignments page to try things out. This time, none of the 12 combinations of choices yields anything. Unlike last night, there are no Error 40's; instead, however, the favicon in the browser tab turns into a circle, spinning endlessly with no result.

Logged in on different browsers on different computers, same outcome. Internet connectivity is otherwise fine.

Just prior to posting this, the circle stopped spinning, the favicon returned to the Mersenne.org standard, and the results pane went blank. (See attachment.)

[QUOTE=Rodrigo;517575]spinning endlessly with no result[/QUOTE]I couldn't replicate that, but I did fix a small error that might have caused it for you. Please try again?

The change worked nicely!

Now all the LL and 100M combinations work. Only the DCs continue to lead to an Error code 40 here.

Thank you!

[QUOTE=Rodrigo;517578]Now all the LL and 100M combinations work.
Only the DCs continue to lead to an Error code 40 here.[/QUOTE]According to the data I'm seeing, DC's should be around ~55M right now, but the function that fetches available assignments isn't finding anything below 94M, which isn't right. I'll need George or Aaron to look into that.