P-1 from GPU-72 not showing up on PrimeNet Assigments Page.
 

2 PC just started getting P-1 from GPU72 a few weeks ago.
Both PCs show the P-1 assignments being worked on.
All their P-1 assignments are on the GPU72 Assignments page
However ...
None of these assignments show up on the PrimeNet Assignments page.

Correction...there is 1 P-1 assignment for 1 PC on PrimeNet but NOT on GPU72.
[url]http://www.mersenne.org/report_exponent/?exp_lo=80243351&full=1[/url]

[QUOTE=petrw1;449493]Correction...there is 1 P-1 assignment for 1 PC on PrimeNet but NOT on GPU72.
[url]http://www.mersenne.org/report_exponent/?exp_lo=80243351&full=1[/url][/QUOTE]

Hmmm... Interesting...

I have no idea why that happened, but it _did_ go through the proxy. I see that assignment transaction in the "Traffic" logs, being assigned by Primenet rather than GPU72.

What this means is that GPU72 couldn't satisfy the assignment, and so it passed the request back to Primenet for fulfilment.

I only see only this one such case in the logs. Has this machine received other work since from GPU72?

Edit: OK, I just drilled down a bit further... It appears you switched this machine from DC to P-1 on 2016.12.12 or so. This might have resulted in a "Temporal Window" where your machine was asking for work which wasn't available from GPU72, and so the request was handed back to Primenet.

[QUOTE=chalsall;449554]Hmmm... Interesting...

I have no idea why that happened, but it _did_ go through the proxy. I see that assignment transaction in the "Traffic" logs, being assigned by Primenet rather than GPU72.

What this means is that GPU72 couldn't satisfy the assignment, and so it passed the request back to Primenet for fulfilment.

I only see only this one such case in the logs. Has this machine received other work since from GPU72?

Edit: OK, I just drilled down a bit further... It appears you switched this machine from DC to P-1 on 2016.12.12 or so. This might have resulted in a "Window" where your machine was asking for work which wasn't available from GPU72, and so the request was handed back to Primenet.[/QUOTE]

Yes I switched from DC to P-1. I see one P-1 assignment on PrimeNet though I can't tell who it came from; I assume PrimeNet because it is NOT on the GPU72 page (the 80,xxx,xxx noted above). The machine itself has lots of 82,xxx,xxx P-1 in worktodo.txt (as also listed in the GPU72 Assignments page) but NOT on the PrimeNet page.

[QUOTE=petrw1;449555]The machine itself has lots of 82,xxx,xxx P-1 in worktodo.txt (as also listed in the GPU72 Assignments page) but NOT on the PrimeNet page.[/QUOTE]

Yes, this all makes sense... P-1 assignments from GPU72 show up on the GPU72 Worker's assignment page but not the Primenet assignment page (as they are being "lent" to you to work by GPU72).

Conversely, Primenet P-1 assignments show up on the Primenet assignments page but not the GPU72 assignments page (even if they pass through the proxy) as this almost never happened.

The exact reason for the brief window of the client asking for work which can't be satisfied after a work-type change has never been fully debugged. There's a bit of "black magic" going on in the Primenet Server <=> Prime95/mprime Client protocol which I never fully reverse engineered.

It's probably time I passed control of all P-1'ing back to Primenet. I'm going to have some quiet time over the holidays -- I'll look at implementing that then.

[QUOTE=chalsall;449557]Yes, this all makes sense... P-1 assignments from GPU72 show up on the GPU72 Worker's assignment page but not the Primenet assignment page (as they are being "lent" to you to work by GPU72).[/QUOTE]

OK....so this is different than DC/LL work which showed up in both places.....or is that only since GPU72 stopped handing these out?

[QUOTE]
Conversely, Primenet P-1 assignments show up on the Primenet assignments page but not the GPU72 assignments page (even if they pass through the proxy) as this almost never happened.

The exact reason for the brief window of the client asking for work which can't be satisfied after a work-type change has never been fully debugged. There's a bit of "black magic" going on in the Primenet Server <=> Prime95/mprime Client protocol which I never fully reverse engineered.

It's probably time I passed control of all P-1'ing back to Primenet. I'm going to have some quiet time over the holidays -- I'll look at implementing that then.[/QUOTE]

OK
Thanks

[QUOTE=petrw1;449560]OK....so this is different than DC/LL work which showed up in both places.....or is that only since GPU72 stopped handing these out?[/QUOTE]

It's a little complicated...

Short form: GPU72 used to hold a couple of hundred low DC/LL candidates using spiders reserving as "Anonymous", and using a trick (bug?) hand them out to workers and Primenet would then assign that candidate to the worker and GPU72 would keep track of it.

Do you not remember the wonderful rants from a certain music lover (and others) about this?

Once the new DC/LL assignment rules were implemented this transfer trick no longer worked, so it became a simple pass-through. I welcomed this transfer of authority.

Time to now do this for P-1. But hast makes waste.

[QUOTE=chalsall;449565]But hast makes waste.[/QUOTE]And causes typos. :wink:

Hmmm I missed the memo...76 Bits
 

Seems above 83M GPU72 is now going to 76 Bits?

[QUOTE=petrw1;449652]Seems above 83M GPU72 is now going to 76 Bits?[/QUOTE]

Yeah. That's what James' analysis recommends for most cards.

I was going to announce this after 82M was completed to at least 75 bits.

As always, people are welcome to do less deep work. Only by selecting "Let GPU72 Decide", or selecting "What Makes Sense" with a pledge level of 76, will you be given this kind of work.

Here's something odd. This morning, GPU72 Assignments page tells me that someone else has completed one of my DCs. However, Exponent Status disagrees. :huh:
EDIT: However, I have not started it, so it would be painless to throw it back. In fact, until I resolve the memory problem that has me running crippled in single channel, I'll probably return more than one.....two not started returned, in fact. :smile:

EDIT2: This is drifting a bit OT, but I just turned in 4 TF results. One of them came up "not needed". When I checked the Status page, it still shows as not done, and still assigned to me. Then I checked the other 3 assignments, and none of them have shown up as done on Status. More weirdness.

EDIT3: I just realized that I have a duplicate line, which explains the Error 40. However, none show as done.

[QUOTE]EDIT3: I just realized that I have a duplicate line, which explains the Error 40. However, none show as done. [/QUOTE]
I have to retract part of the above. My work for 75-76 is showing. GPU Factoring just hasn't released it.