For Reasearch [I]is[/I] chalsall. Please complete them and submit them.

Hi Walt, and welcome!

For Research is one of the names chalsall uses as part of the GPU72 setup. That is, FR obtains assignments from PrimeNet, and then GPU72 distributes them, first, for any needed TF and P-1, before sending them out for LL. In many cases, these assignments have gone out before for LL, but have expired according to the "new" expiry rules. (They've been around for a while, now, though they are tweaked occasionally for optimum results.)

It does not sound like you have actual conflicting assignments, but the way GPU72 works might make it seem that way. Carry on, and thanks for joining our merry band! :smile:

[QUOTE=Walt;399110]I'm new GPUto72 trial factoring with GPU's. I mostly Fold@Home but send some of my GPU cycles to help out here.[/QUOTE]

Thank you very much for joining and helping out -- it's badly needed at the moment!!! :smile:

[QUOTE=Walt;399110]Last night I got 6 74 to 75 assignments. When I had done the first one, I looked at the history and saw that it had been assigned to "For_Research" to do LL testing by Primenet before I had gotten the assignment for TF'ing from GPUto72.[/QUOTE]

As axn and kladner said, this is fine. Most assignments will appear on Primenet as being "owned" by "GPU Factoring", but a few will appear as being owned by "For Research". The latter are candidates that my "Observing Spider" fetched from Primenet which aren't yet TF'ed to at least 75 bits -- this is because they've been recycled by Primenet, unreserved by the original owner, or just completed a P-1 run by someone through Primenet at 74 bits. GPU72 will never intentionally hand out an assignment owned by someone else.

Thanks again for joining our little side project of GIMPS. Please let us know if you have any additional questions or comments.

[QUOTE=flashjh;399102]For some reason every once in a while I end up with some assignments that are expiring. Is there a way to have GPU72 just put them back into my work queue at the 10 day mark so they get done? A lot of work for little gain, but I hate them sitting for 30+ days when I hardly ever check the assignments page anymore. :smile:[/QUOTE]

Thanks for the additional fire power!

WRT automatically adding them back (basically re-issuing), it would be quite a bit of work. Partially because GPU72 has no way of knowing if they've actually "gone missing", or just on a machine which doesn't regularly check in.

One possible thing I could do is have an option for an email notice when an assignment is beyond a certain limit (opt-in, of course -- I hate automatic spam).

Email would be great also, thanks!

[QUOTE=chalsall;399127] As axn and kladner said, this is fine. Most assignments will appear on Primenet as being "owned" by "GPU Factoring", but a few will appear as being owned by "For Research". The latter are candidates that my "Observing Spider" fetched from Primenet which aren't yet TF'ed to at least 75 bits -- this is because they've been recycled by Primenet, unreserved by the original owner, or just completed a P-1 run by someone through Primenet at 74 bits. GPU72 will never intentionally hand out an assignment owned by someone else.[/QUOTE]

Hilarious. I completely misunderstood. I had seen the check outs to GPU_factoring and that made sense. But I had not connected the dots that For Research was you checking them out for factoring. Oops. The five remaining ones are back running now.

-Walt

[QUOTE=Walt;399140]Hilarious. I completely misunderstood. I had seen the check outs to GPU_factoring and that made sense. But I had not connected the dots that For Research was you checking them out for factoring. Oops. The five remaining ones are back running now.

-Walt[/QUOTE]

It confused me and many others at first, too. It makes sense once you understand how the system works though.

[QUOTE=chalsall;399128]Thanks for the additional fire power!

WRT automatically adding them back (basically re-issuing), it would be quite a bit of work. Partially because GPU72 has no way of knowing if they've actually "gone missing", or just on a machine which doesn't regularly check in.

One possible thing I could do is have an option for an email notice when an assignment is beyond a certain limit (opt-in, of course -- I hate automatic spam).[/QUOTE]
Ok, something else is going on with the current batch of exponents that were set to expire. I put them back into the queue without checking to see if they were reported already (my lazy fault) to run and all of them reported as not needed.

So it looks like spidey just hasn't seen that they're done already.

[QUOTE=flashjh;399202]Ok, something else is going on with the current batch of exponents that were set to expire. ... So it looks like spidey just hasn't seen that they're done already.[/QUOTE]

Hmmm... Could you please PM me a few examples? Spidey should observe completion within (at worst) two hours.

These are the current ones:

66987227
66987269
66987493
66987533
66987631

[QUOTE=flashjh;399232]These are the current ones:

66987227
66987269
66987493
66987533
66987631[/QUOTE]

Hmmm... Interesting.

One thing I notice querying the MySQL database on GPU72 is each of these have been "extended". Most probably a very SPE on my part.

Tomorrow I'll drill down further. Thanks for bring this to my attention (sincerely).