[QUOTE=Dubslow;293551]What link...? :unsure:[/QUOTE]

Log in, it'll be the last link in My Account. It's also the destination of the links that are the worker names at pages like [url]http://www.gpu72.com/reports/workers/[/url]

[QUOTE=Dubslow;293551]

What link...? :unsure:
[/QUOTE]
I think he means [URL="http://www.gpu72.com/reports/worker/829a683f5d991e17d4cca0453117d491/"]this[/URL].

[QUOTE=Mini-Geek;293554]Log in, it'll be the last link in My Account. It's also the destination of the links that are the worker names at pages like [url]http://www.gpu72.com/reports/workers/[/url][/QUOTE]

[QUOTE=LaurV;293555]I think he means [URL="http://www.gpu72.com/reports/worker/829a683f5d991e17d4cca0453117d491/"]this[/URL].[/QUOTE]

You are both right, but I still don't see it, look at the HTML code I pasted. I am logged in, in fact the HTML came from the "View Completed" page, so I am totally sure I'm logged in. I see "Get Assignments", "View Assignments", "View Completed" (again, see the HTML) and their submenus (none of those are right either). In fact, I lost this post once because I just cleared my cookies etc., and tried to post this and lost it (because I was then not logged in), and I still don't see it.

And suddenly it appears! Thanks chalsall! (I wonder why I was glitching out? Or was it server side?)

[QUOTE=Dubslow;293558]And suddenly it appears! Thanks chalsall! (I wonder why I was glitching out? Or was it server side?)[/QUOTE]

Sigh... My fault (as usual). Error in my SQL table definition. Text versions of IP numbers can be up to 15 characters, not 13....

Huh... the heuristics table does not appear to update itself as often as the other tables. Presumably this is deliberate, to keep down CPU usage? (Is it updated daily or something?)

I also just noticed that Spidey is now collecting 60M-61M expos...

[QUOTE=Dubslow;293563]
I also just noticed that Spidey is now collecting 60M-61M expos...[/QUOTE]

Do we really need to go that far ahead of the LL wavefront? I would think the 34000 reserved for TF by GPU272 would be plenty? Especially when we see that only 8000 are currently assigned? Or perhaps spidy is running wild? :smile:

[QUOTE=diamonddave;293565]Do we really need to go that far ahead of the LL wavefront? I would think the 34000 reserved for TF by GPU272 would be plenty? Especially when we see that only 8000 are currently assigned?[/QUOTE]

I'm not sure 60M is much "ahead" of the LL wavefront....looks to me like it is close to 59M. Until now this sub-project has mostly been grabbing returned LL (and DC) assignments and TF'ing deeper to eliminate some before they are reassigned. By TF'ing just ahead of LL emilinates even the first LL attempt.

[QUOTE=diamonddave;293565]Do we really need to go that far ahead of the LL wavefront? I would think the 34000 reserved for TF by GPU272 would be plenty? Especially when we see that only 8000 are currently assigned? Or perhaps spidy is running wild? :smile:[/QUOTE]

If Spidy was "running wild", it would have allocated everything currently at 69 bits... :smile:

As petrw1 points out, entering the 60M range isn't that far ahead of the wave. And at our current rate, we hold less than three months of TF work. Over the next week you'll see our rate of released candidates increasing as more and more people have been "pledging" to go straight to 72 bits.

[QUOTE=Dubslow;293563]Huh... the heuristics table does not appear to update itself as often as the other tables. Presumably this is deliberate, to keep down CPU usage? (Is it updated daily or something?)[/QUOTE]

I had to upgrade the script which runs after work is "observed" to use the new subroutines. This has now been done.

[QUOTE=chalsall;293573]I had to upgrade the script which runs after work is "observed" to use the new subroutines. This has now been done.[/QUOTE]
Ah good :smile:
[QUOTE=chalsall;293571]If Spidy was "running wild", it would have allocated everything currently at 69 bits... :smile:

As petrw1 points out, entering the 60M range isn't that far ahead of the wave. And at our current rate, we hold less than three months of TF work. Over the next week you'll see our rate of released candidates increasing as more and more people have been "pledging" to go straight to 72 bits.[/QUOTE]

I would rather get the lower expos at 71 bits than the higher expos at 69 bits. Make sure everything it thoroughly done.