Possible extention to the "GPU to 72 Tool" project?

[NBtarheel_33]

Is 25M the lower bound for the DC project, or will you be rounding up 24Ms as well?

[Dubslow]

While we're there, what about those <40M expos? Will those get picked up by the spider if they go up for reassignment? Certainly those should be assigned to a very reliable worker.

Edit: Just looked at the overall status page, and suddenly I haz a happy :):)
But a suggestion: "Note that for DC and LL TF work, divide the GHz Days by 100 to get the approximate time spent when comparing with other work types" or something to that effect. Otherwise, awesome! :)
Edit 2: If we divide GPU work by 100, then we should divide CPU work by 3 to get a roughly equal comparison. Maybe instead of a footnote a whole extra column?

[markr]

Originally Posted by NBtarheel_33

Is 25M the lower bound for the DC project, or will you be rounding up 24Ms as well?

Originally Posted by Dubslow

While we're there, what about those <40M expos? Will those get picked up by the spider if they go up for reassignment? Certainly those should be assigned to a very reliable worker.

Unfortunately those don't look possible. Primenet calls DCs below 25,000,000 and first-time LLs below 45,000,000 "preferred exponents" which chalsall's anonymous spider can't get.

[LaurV]

Originally Posted by chalsall

delta_t wins!

Congratulations! You were lucky I had to bring my daughter from piano lessons. When I was back the DC was finished for about 15 minutes and patiently waiting for me to report it. This was about 1:15 my time (GMT+7) so I almost could beat you (remember "need for speed" movies, with Vin Diesel and the other guy, forgot his name: "I almost had you, dude!", hehe).

[NBtarheel_33]

Originally Posted by markr

Unfortunately those don't look possible. Primenet calls DCs below 25,000,000 and first-time LLs below 45,000,000 "preferred exponents" which chalsall's anonymous spider can't get.

Perhaps George can somehow tweak that part of the assignment system.

[LaurV]

@chalsall: I believe I lost 25162937. P95 unreserved it in a very strange way, I had 4 workers, each of them with 2 (two) DC assignments, and P95 unreserved BOTH assignments of worker 2 (no joke, I am still crossed about it!) and he got a new assignment from primenet ONLY for this worker (29006071, which I am NOT going to finish, I stopped the worker and I will return the exponent back). He did not touch the work queued for workers 1, 3, and 4. What do you make of it? Were the keys for the two exponents wrong? I doubt, because in spite of the fact 25162937 was assigned from GPU-2-72, the second one (26xxxxxx) was assigned by P95/primenet (auto, I like to have more days queued just in case I run dry). That is very strange.

So I tried to recover it by using the key. Not valid anymore. It appears assigned to some anonymous user. If your spider is the one, I want it back. If not (or you already assigned it to someone else), then say so, and I have to unreserve it from GPU-2-72 page.

edit: and 25052227 which I cleared by completing DC (residue match) did not disappear from my gpu272 DC-assignment list. Are we supposed to unreserve them when we finish DC, or how it is working? (I did not get this part).

[James Heinrich]

Originally Posted by chalsall

Congratulations delta_t.

I tried, but apparently not fast enough.

[Nov 27 01:53] M25132963 is not prime. Res64: 95A0D39CF17E690B.

(time is GMT-4)

[LaurV]

@chalsal again: Now your spider completely disrespected my 8th factor!

M52431343 has a factor: 2313673646385899219839
found 1 factor(s) for M52431343 from 2^70 to 2^71 [mfaktc 0.17-Win barrett79_mul32]
M52431343 has a factor: 3771030653667250842383
found 1 factor(s) for M52431343 from 2^71 to 2^72 [mfaktc 0.17-Win barrett79_mul32]

I can't be blamed because I took the exponent to the promised bitlevel and completed all the range without stopping, can I?

[chalsall]

Originally Posted by LaurV

@chalsal again: Now your spider completely disrespected my 8th factor!

M52431343 has a factor: 2313673646385899219839
found 1 factor(s) for M52431343 from 2^70 to 2^71 [mfaktc 0.17-Win barrett79_mul32]
M52431343 has a factor: 3771030653667250842383
found 1 factor(s) for M52431343 from 2^71 to 2^72 [mfaktc 0.17-Win barrett79_mul32]

I can't be blamed because I took the exponent to the promised bitlevel and completed all the range without stopping, can I?

Hummm... Now that's something I had forgotten about and didn't design for... mfaktc will continue searching the entire "bit" range, even after a factor is found.

I'm afraid I'm going to have to let this (very rare) situation pass through undetected; as in, you won't get credit for the second factor on G72. You will, however, get the credit on PrimeNet.

To detect this unusual case would involve quite a bit of code, and a lot of additional spidering.

[chalsall]

Originally Posted by LaurV

What do you make of it? Were the keys for the two exponents wrong? I doubt, because in spite of the fact 25162937 was assigned from GPU-2-72, the second one (26xxxxxx) was assigned by P95/primenet (auto, I like to have more days queued just in case I run dry). That is very strange.

It is indeed very strange. Did you have your settings appropriate for the number of days of work you were asking Prime95 to hold? Obviously this is entirely within the domain of Prime95 / PrimeNet -- I have no control. But I assure you, the AIDs were valid.

Out of interest, how did you add the candidates to your worktodo.txt? By direct editing, or by using worktodo.add? And when did the candidates get unreserved? Lastly, you mentioned that a candidate which you had received directly from PrimeNet was also unreserved. This seems very strange as any candidate which has had work done on it should not be unreserved even if the AID is invalid.

Originally Posted by LaurV

So I tried to recover it by using the key. Not valid anymore. It appears assigned to some anonymous user. If your spider is the one, I want it back. If not (or you already assigned it to someone else), then say so, and I have to unreserve it from GPU-2-72 page.

Nope -- which ever Anonymous account grabbed that exponent was not my spider's.

Originally Posted by LaurV

edit: and 25052227 which I cleared by completing DC (residue match) did not disappear from my gpu272 DC-assignment list. Are we supposed to unreserve them when we finish DC, or how it is working? (I did not get this part).

Nope, don't unreserve completed DCs / LLs from your account. I still have a bit of spidering / parcing / database update work to do for this to be automated. Hopefully today.

[chalsall]

Originally Posted by NBtarheel_33

Perhaps George can somehow tweak that part of the assignment system.

Yes. If George set my registered spider "gpufactor" / "GPU Factoring" to be a "trusted" account, Spidy could get the lowest candidates to be TFed (and P-1'd if needed) up. The system would then release them back to PrimeNet, and my anonymous spider would not get them -- they would go to "trusted" workers via the usual route.