Unable to get manual TF assignments for GPU

[Rodrigo]

Not sure if this or the PrimeNet subforum is the right place for this topic, but here goes...

Over the past several days, more than once I have been unable to obtain most types of manual GPU assignments. Of the preferred work range categories available in the drop-down menu, only "TF for 100M digit Mersenne numbers" works. The rest meet with a result like this one:

aError code: 40 
Error text: No assignment available for GPU trial factoring, cpu_id:

Is this a glitch, or an intended result?

Thanks for any info on this!

[axn]

I got some work in the 100m bits (not digits) range by giving:

Preferred work range: TF for first time LL
Exponent rage: 95m to 105m
Work preference: Lowest exponent
Bit Level: 76

[Prime95]

A little history. This page was originally written to replace the heuristics GPU72 uses. GPU72 would still exist, but would basically relay requests to this page and return the assignments. GPU72 would no longer reserve huge blocks of TF assignments.

Given that goal, the server tracks what range of exponents it expects to be handing out for LL in the next 90(?) days. The GPUs would then TF those ranges as deep as possible - with assignments always given out to maximize the LL-time-saved vs. chance-of-finding-a-factor.

Fast forward to today. GPU72 never changed over to this system. That is fine, Chris does a great job monitoring the various wavefronts, probably better than an algorithm I came up with 5 years ago. This page is now used only by a few non-GPU72 users. What has happened is GPU72 has reserved pretty much all of the next-90-day ranges (displayed on the bottom the web page).

What you need to do is manually extend the top end of the LL range.

[kriesel]

Originally Posted by Prime95

A little history. This page was originally written to replace the heuristics GPU72 uses. GPU72 would still exist, but would basically relay requests to this page and return the assignments. GPU72 would no longer reserve huge blocks of TF assignments.

Given that goal, the server tracks what range of exponents it expects to be handing out for LL in the next 90(?) days. The GPUs would then TF those ranges as deep as possible - with assignments always given out to maximize the LL-time-saved vs. chance-of-finding-a-factor.

Fast forward to today. GPU72 never changed over to this system. That is fine, Chris does a great job monitoring the various wavefronts, probably better than an algorithm I came up with 5 years ago. This page is now used only by a few non-GPU72 users. What has happened is GPU72 has reserved pretty much all of the next-90-day ranges (displayed on the bottom the web page).

What you need to do is manually extend the top end of the LL range.

Thanks for the info.
And please consider moving the upper limit of the gpu manual assignments page, to a level that will reduce or eliminate error 40. It used to be a rare occurrence, but lately it seems to be the default response. Currently the upper limit is 96M but needs to be manually increased to 101M every time to obtain any new manual TF assignments. Also lowest available exponent choice (instead of highest bits) I'd like saved from one assignment fetch to the next.

[Rodrigo]

Thanks everyone for the interesting background and the helpful tips.

[leonardyan96]

Originally Posted by Prime95

A little history. This page was originally written to replace the heuristics GPU72 uses. GPU72 would still exist, but would basically relay requests to this page and return the assignments. GPU72 would no longer reserve huge blocks of TF assignments.

Given that goal, the server tracks what range of exponents it expects to be handing out for LL in the next 90(?) days. The GPUs would then TF those ranges as deep as possible - with assignments always given out to maximize the LL-time-saved vs. chance-of-finding-a-factor.

Fast forward to today. GPU72 never changed over to this system. That is fine, Chris does a great job monitoring the various wavefronts, probably better than an algorithm I came up with 5 years ago. This page is now used only by a few non-GPU72 users. What has happened is GPU72 has reserved pretty much all of the next-90-day ranges (displayed on the bottom the web page).

What you need to do is manually extend the top end of the LL range.

So, does this mean, if an exponent is reported to be assigned to someone named "GPU Factoring", it has actually gone to GPU72? This is a long-time question of me because I have never seen this user to publish any result.

[kladner]

Originally Posted by leonardyan96

So, does this mean, if an exponent is reported to be assigned to someone named "GPU Factoring", it has actually gone to GPU72? This is a long-time question of me because I have never seen this user to publish any result.

The results show up for the individual users who got assignments from GPU72.

[leonardyan96]

Originally Posted by kladner

The results show up for the individual users who got assignments from GPU72.

I have always been thinking "GPU Factoring" is just a troll that reserves large amount of tasks without actually running the computation.

[chalsall]

Originally Posted by leonardyan96

I have always been thinking "GPU Factoring" is just a troll that reserves large amount of tasks without actually running the computation.

Nope. The account "GPU Factoring" was created before GPU72 was even named thusly.

And, so you know, while no assignments are actually completed by this account, what happens is GPU72 "lends" out assignments to TF'ers, who submit the results back to Primenet (and so get the credits).

This repeats (to ever higher bit-levels) until the candidate has either been factored, or it's been TF'ed as high as makes sense. They're then released back to Primenet to assign for either P-1'ing or FC'ing.

[leonardyan96]

Originally Posted by chalsall

Nope. The account "GPU Factoring" was created before GPU72 was even named thusly.

And, so you know, while no assignments are actually completed by this account, what happens is GPU72 "lends" out assignments to TF'ers, who submit the results back to Primenet (and so get the credits).

This repeats (to ever higher bit-levels) until the candidate has either been factored, or it's been TF'ed as high as makes sense. They're then released back to Primenet to assign for either P-1'ing or FC'ing.

Thanks for your answer. That makes me relieved because now I'm sure all these exponents are taken care of.