[QUOTE=petrw1;344595]I'd hate to think that someone with such a fine first name could consider poaching?[/QUOTE]

Can you please PM me the assignments in question? I can do some "drill-down" on the historical data. (I could figure them out myself, but it would be quicker if you just tell me; I'm *really* busy at the moment.)

Hey Chris, your proxy got some dysentery too! :razz: (related to the new thread's title). Please check my assignment report, I just got a couple of LL tests which are already done by other people, and reported in the same day I got them, therefore they appear as "poached" in the report (one by Bdot, and one by George Woltman :razz: :razz: no joke, hahaha.... I am fighting giants here...)

I am not going to do DC in this range, if I do DC, i prefer to do it under 50M... So, should I reserve them by myself or you do some magic voodoo? I did not start working on them fortunately, but this would be within today or tomorrow (the previous expos in queue are like 93-98% done).

edit: grrr, 50253187 is the one I got two days ago, already done by Bdot at the time, this i will cancel. For the second, 50803043, that was reported by George on June 11, and I already did 98% of the work... I guess I have to live with a DC report this time... I will take the proxy off till this kind of problems are fixed, and go to PrimeNet directly for getting assignments...

[QUOTE=LaurV;344722]Hey Chris, your proxy got some dysentery too! :razz: (related to the new thread's title). Please check my assignment report, I just got a couple of LL tests which are already done by other people, and reported in the same day I got them, therefore they appear as "poached" in the report (one by Bdot, and one by George Woltman :razz: :razz: no joke, hahaha.... I am fighting giants here...)

I am not going to do DC in this range, if I do DC, i prefer to do it under 50M... So, should I reserve them by myself or you do some magic voodoo? I did not start working on them fortunately, but this would be within today or tomorrow (the previous expos in queue are like 93-98% done).

edit: grrr, 50253187 is the one I got two days ago, already done by Bdot at the time, this i will cancel. For the second, 50803043, that was reported by George on June 11, and I already did 98% of the work... I guess I have to live with a DC report this time... I will take the proxy off till this kind of problems are fixed, and go to PrimeNet directly for getting assignments...[/QUOTE]

This happened to me too...I have had two LL tests assigned by the GPU72 proxy which were turned in as first-time LLs by George before I started on them. I didn't worry about it and just considered them DCs.

[QUOTE=Chuck;344811]This happened to me too...I have had two LL tests assigned by the GPU72 proxy which were turned in as first-time LLs by George before I started on them. I didn't worry about it and just considered them DCs.[/QUOTE]

I have had a few DC's completed by others as well, hilariously doing a triple check... and no, they were not expired.

On 2013-10-01 between 14:55 and 15:00 I reserved 1027 LLTF-to-71 assignments on GPU72. Reporting in the first 642 results, I get the following:

[code]
Processing result: no factor for M68020567 from 2^70 to 2^71 [mfaktc 0.20 barrett76_mul32_gs]
Error code: 40, error text: TF result for M68020567 was not needed
[/code]Turns out said result was reported in by @rduerr, 3 days ago. Also turns out, a list of my assignments taken prior to reporting results lists only 1026 LLTF assignments with exactly the one in question missing.

A few questions here:

- Why is @rduerr processing an assignment that is supposedly mine?
- Is GPU72 handing out assignments to multiple participants, again?
- Why are assignments silently being removed from my account?

Just wondering. :huh:

[QUOTE=ckdo;355912]A few questions here:

- Why is @rduerr processing an assignment that is supposedly mine?
- Is GPU72 handing out assignments to multiple participants, again?
- Why are assignments silently being removed from my account?

Just wondering. :huh:[/QUOTE]

1. I don't know. According to my SQL records you were assigned these to TF from 70 to 71. And, at least for 68020567, you got the credit on GPU72.

2. No.

3. Could you provide examples of assignments silently being removed from your account (public, PM or email is fine)?

I have not done anything with the GPU72 system nor your account which would explain what you are claiming. So either I have a bug I need to deal with (documentation welcome), or something else is going on (documentation welcome).

(Hint: A likely scenario of what you are reporting is that someone's "Poached" you. GPU72, nor PrimeNet, can't stop that.)

(Hint 2: Take less work at a time, less chances of "poaching".)

Look one page back in this thread for a very similar report from yours truly in [URL="http://www.mersenneforum.org/showpost.php?p=339472&postcount=124"]Message 124.[/URL] :kladner: The response from Chris is pretty much the same, too.

As far as 3. is concerned, I cannot provide an actual example. However my assignment count certainly goes down at times without me reporting in any results whatsoever. I didn't get the idea of checking whether I was actually credited, yet.

At times my assignment count will go down less than I expected when reporting results, but in the long run I don't seem to end up with leftover assignments. I have no idea whether someone else is credited for these.

It just happened again yesterday btw:

[code]
Manual testing 40009553 NF 2013-10-19 18:14 0.0 no factor for M40009553 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4942
Manual testing 40008413 NF 2013-10-19 18:14 0.0 no factor for M40008413 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4942
Manual testing 40007659 NF 2013-10-19 18:14 0.0 no factor for M40007659 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4943
Manual testing 40007507 NF 2013-10-19 18:14 0.0 no factor for M40007507 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4943
Manual testing 40007167 NF 2013-10-19 18:14 0.0 no factor for M40007167 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4943
Manual testing 40006961 NF 2013-10-19 18:14 0.0 no factor for M40006961 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4943
Manual testing 40006739 NF 2013-10-19 18:14 0.0 no factor for M40006739 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4943
Manual testing 40006121 NF 2013-10-19 18:14 0.0 no factor for M40006121 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4943
Manual testing 40005871 NF 2013-10-19 18:14 0.0 no factor for M40005871 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4943
Manual testing 40004827 NF 2013-10-19 18:14 0.0 no factor for M40004827 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4944
Manual testing 40003913 NF 2013-10-19 18:14 0.0 no factor for M40003913 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4944
Manual testing 40003819 NF 2013-10-19 18:14 0.0 no factor for M40003819 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4944
Manual testing 40003559 NF 2013-10-19 18:14 0.0 no factor for M40003559 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4944
Manual testing 40003177 NF 2013-10-19 18:14 0.0 no factor for M40003177 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4944
Manual testing 40003027 NF 2013-10-19 18:14 0.0 no factor for M40003027 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4944
Manual testing 40002653 NF 2013-10-19 18:14 0.0 no factor for M40002653 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4944
Manual testing 40001249 NF 2013-10-19 18:14 0.0 no factor for M40001249 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4945
Manual testing 40001057 NF 2013-10-19 18:14 0.0 no factor for M40001057 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4945
Manual testing 40000853 NF 2013-10-19 18:14 0.0 no factor for M40000853 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4945
Manual testing 40000837 NF 2013-10-19 18:14 0.0 no factor for M40000837 from 2^68 to 2^69 [mfaktc 0.20 barrett76_mul32_gs] 1.4945
[/code]All still assigned to me as per GPU72. For any potential bug hunting: These are all the results from the 40M range that I reported. All results from the 47M range were accounted for, it appears.

[QUOTE=ckdo;356842]All still assigned to me as per GPU72. For any potential bug hunting: These are all the results from the 40M range that I reported. All results from the 47M range were accounted for, it appears.[/QUOTE]

Sorry... I might have too many balls up in the air...

When I brought in the 40M range I forgot to tell Spidy to watch it. I manually limit what Spidy watches to lessen the impact on PrimeNet.

My apologies everyone. I try to do my best, but when busy Stupid Humans often make stupid mistakes.

Please keep pointing out the mistakes. I'll do my best to minimize them, and will try to deal with them as they are documented.

On a similar note, I have two stuck assignments that Spidey seems to be blind for.
[URL]http://www.mersenne.org/report_exponent/?exp_lo=30970483[/URL]
[URL]http://www.mersenne.org/report_exponent/?exp_lo=30970501[/URL]

I have done them twice, first when I was assigned them and second when I thought I had missed to run them. :smile:

Three times a charm, but I think I stop after two times and ask for help.

Göran

I have an odd situation.

My worktodo, P95 Status, and PrimeNet say I have 9 DC assignments. GPU72 is holding out at 8 DCs, even after repeated Manual Communication attempts. This may, somehow, be the result of the gyrations I went through to get P95 lined up to do all DC work after having done P-1 for some time. There were many instances of making changes, running Manual Comm., and un-reserving unwanted assignments.

Fortunately, or unfortunately, the missing assignment is about 15% complete. Is there some way to get things reconciled?

EDIT: ".....or am I just j*rking off?"