I am delighted to see that your work has addressed such a deep need. That is an amazing interactive graphic.

Kudos, Thanks, and Praises! :party:

[QUOTE=kladner;370000]I am delighted to see that your work has addressed such a deep need.[/QUOTE]

Thanks guys. I am quite proud of this work.

I'm working with some really great people here, and Barbados is actually leading the Caribbean in the fight against HIV/AIDs.

Particular thanks to Xyzzy who privately pointed out a subtle issue which I never would have seen because I have looked at the pages far too often, and so it was simply filtered out. Interesting how human perception works.... :smile:

Hi Chris I am back. Very nice that work. Congrats. That is something I will definitively read! (as much as I will be able too, I am kinda interesting in the subject).

mis post, heh.

I grabbed some LL TF to 73 bits (everything default, asked for 100 assignments) and the preview showed 70,002,XXX from 72 to 73, but I got 66M 71 to 73. I don't really care what kind of work I get as far as TF is concerned but because this has been brought up earlier, I thought I'd mention it now.

I also grabbed a hundred DC-TF since I haven't done any in a while. How are we doing there?

[QUOTE=TheMawn;370524]I don't really care what kind of work I get as far as TF is concerned but because this has been brought up earlier, I thought I'd mention it now.[/QUOTE]

With George's knowledge, I brought in everything in the 70M range not yet assigned and not yet TFed to at least 72 bits. This was to prevent anything below 72 bits from being assigned for P-1 work.

Not likely to occur -- we're two days away from having the Category 4 candidates start to be recycled (several hundred a day), so we should be able to start bringing back in candidates not yet TFed to 74 bits, and return to that TF level as the default release level shortly.

[QUOTE=TheMawn;370524]I also grabbed a hundred DC-TF since I haven't done any in a while. How are we doing there?[/QUOTE]

We're looking fine; LaurV, I and others (and occasionally Jerry) have build up a comfortable buffer, and again, several hundred will be recycled per day starting Thursday. But, such work is still needed; we're just not under a "crunch" situation.

[QUOTE=chalsall;370551]Not likely to occur -- we're two days away from having the Category 4 candidates start to be recycled (several hundred a day), so we should be able to start bringing back in candidates not yet TFed to 74 bits, and return to that TF level as the default release level shortly.[/QUOTE]

Where do you get that information from? The Assignmentrules on the threshold page would only say Cat4 candidates to be recycled after 180 respectively 360 days. Or did I miss something else in the forum according to that?

[QUOTE=manfred4;370561]Where do you get that information from?[/QUOTE]

I have Spiders... :wink:

[QUOTE=manfred4;370561]Or did I miss something else in the forum according to that?[/QUOTE]

You missed that the original recycling rules would still be in place. As in, a candidate claimed but not reported on for 60 days would be recycled (with the exception of Manual Assignments, which are allowed 180 days if not manually extended).

In two days at least 354 candidates will be recycled under this rule, and the number increases significantly over time.

Ah I see. The new assignment rules and recycling rules are listed on the site, but the recycling is still noch implemented as stated there.
For GPUto72 that's a good thing because the buffer at that range is not built well enough yet.

But are the Rules getting implemented anytime soon then? Because that would only lead to more candidates having to be TF'd over the triple amount of time those C4 assignments would stay stuck.

[QUOTE=manfred4;370582]Ah I see. The new assignment rules and recycling rules are listed on the site, but the recycling is still noch implemented as stated there.
For GPUto72 that's a good thing because the buffer at that range is not built well enough yet.[/QUOTE]

Take a few more sips from the flask. And then watch how it's done.

[QUOTE=chalsall;370551]With George's knowledge, I brought in everything in the 70M range not yet assigned and not yet TFed to at least 72 bits. This was to prevent anything below 72 bits from being assigned for P-1 work.[/QUOTE]
That is a very good idea. In this case, would you please extend [URL="http://www.gpu72.com/reports/current_level/"]these tables[/URL] vertically? (few rows more). And for estimated completion too. If (and only if) any space constrains, the first two rows in both tables can be dropped). I don't know others, but I am watching those tables at least 3-4 times per week, to see how we progress.