1001 TF Factors
 

+221 P-1

[QUOTE=chalsall;286553]I have done some extensive analysis, and I am also at a loss as to how you got these assignments.

According to every database record and log I have, these were never assigned to you by the G72 system. I'm not saying you're wrong. I'm just telling you what I see from what I can audit. (And I'm probably at fault, although I can't figure out how.)

Please keep bringing to my attention any "result not needed" reports you encounter.

Is anyone else seeing such results? I want to get to the bottom of this.

(Was it Asimov who said something like "Most scientific discovery is based not on the Eureka moment, but instead on someone saying to themselves 'that's odd'."?)[/QUOTE]

My last LL was not needed. Got assignment [B]45199013 [/B]from GPUto72 on 12/26 and it was completed on 1/12, results not needed.

Doug

[QUOTE=drh;286602]My last LL was not needed. Got assignment [B]45199013 [/B]from GPUto72 on 12/26 and it was completed on 1/12, results not needed.[/QUOTE]

What appears to have happened in this situation is Jerry was assigned this, but it was removed from his worktodo.txt file and returned to PrimeNet. It was then captured again by Spidy and assigned to you. Jerry appears to have then finished it anyway, and submitted his result.

PrimeNet is showing the result, and you should have received credit for it on there (although possibly as a DC rather than a LL). The G72 system also gave you credit for the work.

Jerry, there are two other cases where it appears you "lost" the assignment back to PrimeNet. Can you confirm that you've been sometimes having G72 LL assignments be unreserved by PrimeNet?

[QUOTE=chalsall;286603]What appears to have happened in this situation is Jerry was assigned this, but it was removed from his worktodo.txt file and returned to PrimeNet. It was then captured again by Spidy and assigned to you. Jerry appears to have then finished it anyway, and submitted his result.

PrimeNet is showing the result, and you should have received credit for it on there (although possibly as a DC rather than a LL). The G72 system also gave you credit for the work.

Jerry, there are two other cases where it appears you "lost" the assignment back to PrimeNet. Can you confirm that you've been sometimes having G72 LL assignments be unreserved by PrimeNet?[/QUOTE]

It's been two weeks or so since I went through my list -- I did have some that were no longer assigned to me. I don't remember who they were assigned to but I removed them from my LL workstations and unreserved them in GPU to 72. I'll check everything again tonight. Sorry Doug :blush:

EDIT: Ok, I checked everything again. Two exponents were unassigned. I removed them from GPU-to-72 and my systems. Thanks. (I'll have to check assignments once in a while)

[QUOTE=flashjh;286604]It's been two weeks or so since I went through my list -- I did have some that were no longer assigned to me. I don't remember who they were assigned to but I removed them from my LL workstations and unreserved them in GPU to 72. I'll check everything again tonight. Sorry Doug :blush:

EDIT: Ok, I checked everything again. Two exponents were unassigned. I removed them from GPU-to-72 and my systems. Thanks. (I'll have to check assignments once in a while)[/QUOTE]

Not a problem, I did get LL-D credit, but our residues didn't match, probably because when you reported, some how my worker stopped, and it was removed from my todo file. I didn't know what happened or why at the time, so I got it started again not to waste the 80% I had done, but most likely messed up the residue. Not sure, just guessing.

Doug

Averaging over 8,000 GHz Days per Day!!!
 

Just so everyone knows, I've added a new graph on the [URL="http://www.gpu72.com/reports/overall/graph/month/"]Overall System Progress Graphs[/URL] page: GHz Days per Day.

Over the last month we're averaging 8,170 GHz Days per day (22 GHz Years per day :showoff:), and the trend is upwards!!!

In related news, Team GPU to 72 is now ranked #4 for Trial Factoring, and #5 for P-1 Factoring (over the last year).

Thanks for all the cycles everyone! :smile:

DC factor
 

mfaktc just found the first DC factor, at least on my watch.

www.GPU72.com...
 

Just so everyone knows...

When I first proposed this system, and then started developing it, I had no idea how much it would be used (nor how much of my time it would consume).

Since it appears it will be around for a while, I've registered a dedicated domain for it and moved the system over to that domain: [URL="http://www.gpu72.com/"]http://www.gpu72.com/[/URL]. I have added a "301; Redirect" from the old site, so all of the original URLs will still work.

This will give me additional flexibility to implement some things I've been thinking about... :wink:

This should have no impact on users, other than having to log in again if your browser thinks you are already logged in. If you see the "Sign Up" page when you try to access one of your account pages, please just try the link again from the Sign Up page.

The new site is on the same server, using the same SQL database. No assignments (nor work) will be lost.

But, as always, if anyone sees something they think is wrong, please let me know.

[QUOTE=chalsall;286880]moved the system over to that domain: [URL="http://www.gpu72.com/"]http://www.gpu72.com/[/URL].[/QUOTE]I've changed my links to point to the new domain.
I also notice that the not-able-to-log-in-with-Opera bug is now fixed (whether by the new domain, or you already fixed it a while ago I'm not sure).

[QUOTE=chalsall;286880](nor how much of my time it would consume)

This will give me additional flexibility to implement some things I've been thinking about... :wink:[/QUOTE]

Thanks for the hard work! Can't wait to see the new ideas.

[QUOTE=James Heinrich;286886]I've changed my links to point to the new domain.[/QUOTE]

Thanks James.

[QUOTE=James Heinrich;286886]I also notice that the not-able-to-log-in-with-Opera bug is now fixed (whether by the new domain, or you already fixed it a while ago I'm not sure).[/QUOTE]

Hmmmm... That's interesting...

No, I have not done anything to try to fix that bug (since only you encountered it), and the code base remains *exactly* the same.

This suggests a possible bug in Opera... Maybe it doesn't handle 401 error messages correctly for sub-domains (just guessing, but it's my best guess for what we've seen).