[QUOTE=chalsall;294411]Yes, unreserve it through GPU72 to clear the record.

So you know, the sequence of events for this was:

2012-03-22 03:45:02 -- GPU72 issued this to Jerry to DC.
2012-03-23 23:35:48 -- Jerry submitted a bad DC to PrimeNet.
2012-03-24 00:12:11 -- PrimeNet reissued 26229943 to Triple Check to Spidy.
2012-03-24 01:20:21 -- GPU72 issued this to you to DC.
2012-03-27 ??:??:?? -- Jerry submitted a good DC to PrimeNet.

Bad Jerry!!! Bad! :wink:

Good to know the sanity check works. :smile:[/QUOTE]
Thanks, chalsall. Will do. As I said, it was just in queue, not started. ;)

What a remarkable residue, there is only one hexit that is not a letter :smile:

[QUOTE=Dubslow;294425]What a remarkable residue, there is only one hexit that is[COLOR=Red] [strike][COLOR=Black]not[/COLOR][/strike] [/COLOR]a letter :smile:[/QUOTE]

Fixed. Chances are 1 in 1153, roughly. "Remarkable" is something different.

[QUOTE=chalsall;293948]It was assigned to you by the system. Somehow it was "lost" back to PrimeNet and reassigned to another PrimeNet worker. I have updated your records to give you the credit for the P-1 work, as you obviously did the work.



There is. The system had detected that the candidate was no longer owned by us (one of only two), and had marked it for no further assignments after you had completed the P-1. For reasons I won't bore you with, it was watching for you to complete a TF rather than a P-1; that's why it didn't detect that you'd finished the work.[/QUOTE]
Your powers of organization never cease to amaze me!

x

[QUOTE=kladner;294409]Just now I checked my assignments and found the notice that an assigned LLDC had been completed by another user. No harm done as I had not started it.

Should I unreserve it through GPU272? Exponent is 26229943.[/QUOTE]

I'm sorry...:blush:
[QUOTE=chalsall;294411]Yes, unreserve it through GPU72 to clear the record.

So you know, the sequence of events for this was:

2012-03-22 03:45:02 -- GPU72 issued this to Jerry to DC.
2012-03-23 23:35:48 -- Jerry submitted a bad DC to PrimeNet.
2012-03-24 00:12:11 -- PrimeNet reissued 26229943 to Triple Check to Spidy.
2012-03-24 01:20:21 -- GPU72 issued this to you to DC.
2012-03-27 ??:??:?? -- Jerry submitted a good DC to PrimeNet.

Good to know the sanity check works. :smile:[/QUOTE]

Whoops. Reference this (and the surrounding posts):
[QUOTE=flashjh;294043]The original P95 DC is correct based on my second run, so the P95 DC will be correct.

M( 26229943 )C, 0x76916187254012__, n = 1474560, CUDALucas v1.69[/QUOTE]

We had to leave town for a family emergency. I logged in remote this morning to upload a DC and inadvertently submitted the whole results file instead of just the most recent results. Hence the 'bad' and the 'good' DC results on the exponent [URL="http://www.mersenne.org/report_exponent/?exp_lo=26229943&exp_hi=10000&B1=Get+status"]status page[/URL].

[QUOTE]Bad Jerry!!! Bad! :wink:[/QUOTE]
Chastisement accepted ;)

No harm. I had not remembered the previous discussion, anyway.

This is odd. Looking at the PrimeNet communications thread in P95 this morning I saw the following:

[CODE]Sending expected completion date for M45188xxx: Jun 29 2012
Sending expected completion date for M45483xxx: [B][COLOR=Red]Oct 16 2014[/COLOR][/B]
PrimeNet success code with additional info:
WARNING: Estimated completion date is more than one year away. The assignment may be reassigned to another user after one year.
Unreserving M26161xxx[/CODE]

The DC assignment which was unreserved does not show any assignment on PrimeNet, but the system does not allow me to re-reserve it. GPU to 72 still thinks I own it.

Forcing communication with PrimeNet yielded this:

[CODE]Updating computer information on the server
Sending expected completion date for M45188xxx: May 05 2012
Sending expected completion date for M45483xxx: Jun 05 2012[/CODE]

which is approximately what was being reported before today.

There was no work done on the DCLL assignment, so I am not particularly attached to it. Should I unreserve it on GPU to 72?

[QUOTE=kladner;298442]There was no work done on the DCLL assignment, so I am not particularly attached to it. Should I unreserve it on GPU to 72?[/QUOTE]

Yes, this appeared in my Admin "Warnings" page this morning as "Rereserved".

As luck would have it, Spidy managed to grab the candidate back after your system released it. I'll transfer it over to AnonSpidy, and send you the new AID so you can claim it again.

[QUOTE=chalsall;298446]Yes, this appeared in my Admin "Warnings" page this morning as "Rereserved".

As luck would have it, Spidy managed to grab the candidate back after your system released it. I'll transfer it over to AnonSpidy, and send you the new AID so you can claim it again.[/QUOTE]

Many thanks! I'll unreserve the old version. I have to suppose that something (local) was making my system look much slower than usual to PrimeNet.

[QUOTE=kladner;298451]Many thanks! I'll unreserve the old version. I have to suppose that something (local) was making my system look much slower than usual to PrimeNet.[/QUOTE]

No, don't unreserve it on GPU72. The assignment on the system will remain the same; just the AID in the Candidate table will need to be updated (nothing to do with you).

Edit: Whoops. Too late. You just unreserved it.

No problem, I've un-unreserved it for you.

[QUOTE=chalsall;298454]No, don't unreserve it on GPU72. The assignment on the system will remain the same; just the AID in the Candidate table will need to be updated (nothing to do with you).[/QUOTE]

Ah Sh!t! I misunderstood your response, and ditched the assignment. My bad.