Overall worker reports are sane again...
 

Just to let everyone know...

I finally had some cycles yesterday to figure out the SPE which was causing the [URL="https://www.gpu72.com/reports/workers/"]Worker's Overall Progress Reports[/URL] to include in the "Done" column work which was actually unreserved instead (naturally, it was all of about eight characters in a part of a very complicated SQL query's conditional).

Please let me know if anyone sees anything strange. I'm Only Human, and might have very well broken something else fixing this....

[QUOTE=chalsall;372641]Just to let everyone know...

I finally had some cycles yesterday to figure out the SPE which was causing the [URL="https://www.gpu72.com/reports/workers/"]Worker's Overall Progress Reports[/URL] to include in the "Done" column work which was actually unreserved instead (naturally, it was all of about eight characters in a part of a very complicated SQL query's conditional).

Please let me know if anyone sees anything strange. I'm Only Human, and might have very well broken something else fixing this....[/QUOTE]

Thanks for fixing this — I just noticed today that the report had been corrected.

The nine that show tf'd to 72 on this page are actually tf'd up to 73 (as of awhile ago)

[url]http://www.mersenne.info/trial_factored_tabular_data/4/336000000/[/url]

[QUOTE=pdazzl;372663]The nine that show tf'd to 72 on this page are actually tf'd up to 73 (as of awhile ago)

[URL]http://www.mersenne.info/trial_factored_tabular_data/4/336000000/[/URL][/QUOTE]

The Spider only updates once a day (assuming you believe this to be a bug).

Tf'd to 73 about eight days ago, so yes appears buggy

[QUOTE=pdazzl;372675]Tf'd to 73 about eight days ago, so yes appears buggy[/QUOTE]

Some might consider this a bug (of Mersenne.info, not GPU72.com), but it's actually by design...

To lessen the load on Primenet, the Spider only "looks" at ranges (by 1M blocks) which have had a change in state as it appears on the [URL="http://mersenne.org/primenet/"]PrimeNet Activity Summary[/URL] report, plus another 30 or so sorted by last updated date.

It would be pointless and wasteful to spider all 1,000 ranges every day, and for those ranges actually important the reports update daily (or, more specifically, when there's a "state change"). The "state change" which triggers a scan is a factor being found, a LL or a DC being completed, or a change in the number of assignments.

So, if you really want to see this specific sub-range reflect the newly TF'ed candidates from 72 to 73 "bits", either do some more TF'ing and find a factor, manually get an assignment from that range and hold it for 24 hours, or wait about a month....

[QUOTE=chalsall;372641]Please let me know if anyone sees anything strange. [/QUOTE]
Still small numbering problem (like double 14, double 25, etc, even if the credits are totally different). But generally the page looks much better now.

[QUOTE=LaurV;372705]Still small numbering problem (like double 14, double 25, etc, even if the credits are totally different). But generally the page looks much better now.[/QUOTE]

Yes, I know about that... I'm working on a better fix, but right now two users who haven't been updated recently (in addition to any which have had a "state change" (read: completed work, received work)) are updated every time the script runs (twice an hour).

As the numbering issue only occurs when someone passes another, this should largely mask the issue until I implement the better solution (I have it modeled, but it's a bit of code, and I also have "real work" to do...).

[QUOTE=petrw1;369444]Did you happen to check about another 20 spots higher....?[/QUOTE]
Which "two spots" are you talking about? :huh:
(going to be "minus one" spot soon:boxer::showoff:)

[QUOTE=LaurV;373114]Which "two spots" are you talking about? :huh:
(going to be "minus one" spot soon:boxer::showoff:)[/QUOTE]

Wow, either you have a good memory, or was reading the history, or... or....

No, I could say nothing that time, so I put it on a black list on the wall and kept it till I had something to say :razz: And why do you care? This is between me and Syd, hehe...