Exponent expired?

[Chuck]

I'm not sure why this one was expired 7 days after it was assigned to me. I was working on it and someone else just finished it.

http://www.mersenne.org/report_expon...1623929&full=1

[chalsall]

Originally Posted by Chuck

I'm not sure why this one was expired 7 days after it was assigned to me. I was working on it and someone else just finished it.

http://www.mersenne.org/report_expon...1623929&full=1

All I can tell you is you were assigned this on 2014-02-04 00:28:50 by GPU72 (when it legitimately owned it), but then someone else completed it today, and so Primenet told your machine to stop work on it, and it did so 2014-02-10 22:31:49. (All times UTC.)

Please let us know if you see further problems; this will likely be an unfortunate situation of a recycled candidate being completed by the former assignee.

On the other hand, we are in a stage of transition, so all "hmmm... that's strange" observations should be reported. Humans are well documented to being profoundly error prone.

[Prime95]

Originally Posted by Chuck

I'm not sure why this one was expired 7 days after it was assigned to me. I was working on it and someone else just finished it.

When a result is reported that makes your assignment unnecessary then the assignment is marked "expired". The assignment is kept in the database so that you can get CPU credit should you subsequently report a result. The expired setting also makes it easy to keep the "work distribution map" web page accurate.

The database actually records a reason why the assignment was expired. Reasons include poached, expired due to 60-days of no contact with the client, and violation of the new assignment rules.

[Chuck]

Originally Posted by Chuck

I'm not sure why this one was expired 7 days after it was assigned to me. I was working on it and someone else just finished it.

http://www.mersenne.org/report_expon...1623929&full=1

It is possible PrimeNet is using the date that GPUto72 captured the exponent, not the date that I reserved it from GPUto72?

[LaurV]

Originally Posted by Chuck

It is possible PrimeNet is using the date that GPUto72 captured the exponent, not the date that I reserved it from GPUto72?

That is for sure. There is no way for PrimeNet to know when the exponent was transferred to you. Gpu72 reserves exponents as "anonymous", transfers them to you. If you don't report any progress during the work, they are still reserved as anon. First time when you report any progress (or no progress just queuing them up, and P95 contacts the server, or when P95 directly reports the result), PrimeNet knows who the "anonymous" is, i.e. you, from the assignment key. There was no other way, as long as you put a "name" to the reservation (i.e. "gpu72"), then the exponent can not be "transferred" to someone else (i.e. you), even if gpu72 gives the key to that user. Therefore, Gpu72 had to reserve the expos as "anonymous" to be able to transfer them to you. PrimeNet assumes that you were the "anonymous" who reserved the work, once you do your first "named" contact to the server. So, if nobody take the Gpu72 assignment for a month, you get a "brand new" assignment which is one month old already.

Fortunately, this will be obsolete, with the new assignments rules you will take the exponents directly from PrimeNet in the future. Right now, Gpu72 is clearing its queue (~30-40 exponents left), there will be no further additions to this queue.