GPU72 has been down for the last few hours.

[QUOTE=cardogab7341;391114]GPU72 has been down for the last few hours.[/QUOTE]

Sorry about that; back now. A weird memory-starvation issue....

[QUOTE=TheMawn;391110]What will be asked of the Beta Testers?[/QUOTE]

Not much; just keep an eye on things, and yell if things aren't working as expected.

[QUOTE=TheMawn;391110]I would like to continue focusing my efforts on DCTF unless there's an emergency of some sort (i.e. IBM devote all their spare cycles). If I can continue to do this but help in any way, I'd be glad. I just don't know what you need, yet.[/QUOTE]

Continuing on DCTF is fine; everyone's free to do whatever they enjoy.

Please be aware however that we are now again so far ahead in the DC range that any work you do won't be "used" for quite a number of months; the "churning" has stabilized. But again, the choice is yours.

Oh, and so you know, the new system will honour the WorkType setting (LLTF or DCTF) so long as you don't use the "What Makes Sense" or "Let GPU72 Decide" options.

[QUOTE=kladner;391106]I sure hope it does the trick. When you say, "another four days", is that due to limitations on how much of the stuff you can take, or some other cause? Is this anti-inflammatory a steroid?

Sorry for the probing questions. However, I am very curious about the disease, and your progress of recovery. I wish you the best possible outcomes. How is your girlfriend doing?[/QUOTE]

Limitations on length of time allowed. And yes, it is a steroid, which I assume is the reason.

Thanks for your concern -- this has been quite an experience! My girlfriend is slowly getting better as well.

[QUOTE=Mark Rose;391101]Is there any way to have a setting that:

1. Only hands out DCTF
2. At a GPU72/PrimeNet chosen bit depth?[/QUOTE]

Hmmm... Good point.

Perhaps I could set things up such that What Makes Sense honours the WorkType (DCTF in your case), but sets the Pledge level. As in, only "Let GPU72 Decide" chooses which range to do as needed.

Thoughts? The only significant change is WMS currently honours the pledge level.

[QUOTE=chalsall;391126]Thanks for your concern -- this has been quite an experience! My girlfriend is slowly getting better as well.[/QUOTE]

Glad to hear it!

[QUOTE=chalsall;391128]Hmmm... Good point.

Perhaps I could set things up such that What Makes Sense honours the WorkType (DCTF in your case), but sets the Pledge level. As in, only "Let GPU72 Decide" chooses which range to do as needed.

Thoughts? The only significant change is WMS currently honours the pledge level.[/QUOTE]

I like that idea. It may surprise a few people if you change it though. But once the integration with PrimeNet is complete with the current plan, there wouldn't otherwise be any difference between WMS and LG72D, would there?

78M 73-74 bits DC-TF just assigned....
 

Is that a "BUG" or a "FEATURE" :smile:

For now I changed MisFit to give me specifically DCTF - lowest Exponent and I got 41M 70-71 Bits even though there are still 40M 71-72 Bits available....and 41M 69 - 70 Bits.

Then I unreserved the 78M from GPU72 and deleted from the MisFitWorkToDo. It that the correct procedure?

[QUOTE=petrw1;391150]Is that a "BUG" or a "FEATURE" :smile:

For now I changed MisFit to give me specifically DCTF - lowest Exponent and I got 41M 70-71 Bits even though there are still 40M 71-72 Bits available....and 41M 69 - 70 Bits.

Then I unreserved the 78M from GPU72 and deleted from the MisFitWorkToDo. It that the correct procedure?[/QUOTE]

That is a feature. Primenet decided that doing that 78M exponent would save more LL CPU time than working on any other DC TF exponent available. "What makes sense" always translates into "saves the most LL CPU time per unit of GPU work expended".

Primenet does not hand out 40M exponents for DCTF to 72. By default, Primenet uses James' crossover charts for a GTX 670 and switches from bit depth 71 to bit depth 72 when the chart crosses 71.75. See [url]http://www.mersenne.ca/cudalucas.php?model=487[/url]

[QUOTE=Prime95;391168]That is a feature. Primenet decided that doing that 78M exponent would save more LL CPU time than working on any other DC TF exponent available. "What makes sense" always translates into "saves the most LL CPU time per unit of GPU work expended".

Primenet does not hand out 40M exponents for DCTF to 72. By default, Primenet uses James' crossover charts for a GTX 670 and switches from bit depth 71 to bit depth 72 when the chart crosses 71.75. See [url]http://www.mersenne.ca/cudalucas.php?model=487[/url][/QUOTE]

Fair enough.

Would this not always hand out the largest exponents since that would result in the most LL savings?
And if so how do you get the leading edge (lowest exponents) TF'd?

[QUOTE=petrw1;391150]For now I changed MisFit to give me specifically DCTF - lowest Exponent and I got 41M 70-71 Bits even though there are still 40M 71-72 Bits available....and 41M 69 - 70 Bits.[/QUOTE]

Please remember that only LG72D (and, soon, WMS) sets the "Pledge" level. You asked for "Lowest", but still have only pledged to 71. This is why you didn't get anything to take to 72. And, also, you didn't get any assignments from 69 because, again, you asked for lowest exponent. If you had asked for lowest TF level, you would have been given the lowest available candidates at the lowest bit level.

[QUOTE=petrw1;391150]Then I unreserved the 78M from GPU72 and deleted from the MisFitWorkToDo. It that the correct procedure?[/QUOTE]

Scott (Mr. MISFIT :smile:) would have to answer as to how to handle the MisFitWorkToDo side of things. But unreseving from GPU72 is definitely the correct first step.

[QUOTE=petrw1;391170]Would this not always hand out the largest exponents since that would result in the most LL savings? And if so how do you get the leading edge (lowest exponents) TF'd?[/QUOTE]

Please be aware that the GPU72 to Primenet proxying is not yet "live". As in, the 78M assignments you were given were by GPU72.

As I understand George's plans, Primenet will give out TF assignments which are the most profitable to the project AND are likely to be assigned in the next 60 days or so.