RIP DCTF.
 

Disclaimers: GhzDays ToGo for now is a rough estimate ... ideas of how to make it somewhat accurate?

[CODE]GhzDays Member
550 TheMawn
500 petrw1
300 manfred4
460 kladner
1800 LaurV
1200 Mark Rose
4810 Total
33,670 Per Week
3,000,000 ToGo

89.10 Est Weeks
1.71 Est Years
26-Aug-2016 Est Done

[/CODE]

[QUOTE=chalsall;389878]Take a look at [URL="https://www.gpu72.com/reports/estimated_completion/primenet/"]the second table on this report[/URL]. ~240 days to complete as the TF goal is currently configured (based on our thirty day rolling average of DCTF'ing).

However, as LaurV (correctly) pointed out, the "optimal TF level" for these ranges are actually higher for the higher ranges than shown, so we have some more work to do. I will adjust the report to be "correct" over this next weekend.

Also, keep in mind that you guys only seriously "surged" two weeks ago. The estimates given on the above report is based on the middle of the linear regression line on [URL="https://www.gpu72.com/graphs/dctf/month/"]this graph[/URL]. Read: If you guys keep this up, the estimate will continue to drop. :smile:[/QUOTE]

Fair enough....but we are trying to estimate the remaining time for only those who commit to stay on this "Project"...
That will change quite a bit shortly as many are moved back to LLTF with LetGPU72Decide.

Granted once this settles the number will gradually "auto correct" itself again.

Any chance we could get one more column which is the actual GhzDays to complete all the work in that row of the chart? :smile:

I calculated my Estimate by calculating the Credit for each Million range (e.g. 38,500,000 for averaging) and added them together, so it should be pretty accurate ;)
If you say, from where to go to 72 bits or even 73 bits (I think there are some, that need to go there) I can add it up to give a new and better number.

[QUOTE=manfred4;389884]
If you say, from where to go to 72 bits or even 73 bits (I think there are some, that need to go there) I can add it up to give a new and better number.[/QUOTE]
Those are different for the different GPU architectures and whether you prefer TF or CudaLucas.

To 72bit
GTX980 @38M 71.92bits [URL]http://www.mersenne.ca/cudalucas.php?model=566[/URL]
GTX580 @40M 71.96bits [URL]http://www.mersenne.ca/cudalucas.php?model=12[/URL]
GTX680 @43M 72.04bits [URL]http://www.mersenne.ca/cudalucas.php?model=467[/URL]
GTX780 @49M 71.93bits [URL]http://www.mersenne.ca/cudalucas.php?model=492[/URL]

To 73bit
GTX980 @48M 73.15bits
GTX580 @50M 72.99bits
GTX680 @54M 72.95bits
GTX780 @65M 73.04bits

So I would personally say from 40M on to 72bits and @50M to73bit, as the GTX580 is still a very popular card for TF. People with a GTX780 and who do mind their efficiency could return to LLTF or run CudaLucas instead.

Okay, but I think that the value in that graph is the maximum bit depth you should go, so if it says 72.9 bits, then 73 bits is just too much and you waste your effort. For my GPU that would be at 43M/55M for the next bit.
For an average 42M/53M looks reasonable.

Given that all the DCTF have already had at least one LL check, we're only saving one LL check not two. Should this be factored into the bit level, too?

That and the fact, that P-1 is done already is factored in, as you can see there are two lines in those charts, one for DCTF and one for LLTF

[QUOTE=manfred4;389893]That and the fact, that P-1 is done already is factored in, as you can see there are two lines in those charts, one for DCTF and one for LLTF[/QUOTE]
But isn't the number listed (for instance 71.95) at the start of the range? In that case we should increase the bitlevel halfway, for instance between 40,000,000 and 41,000,000 ?

[QUOTE=manfred4;389893]That and the fact, that P-1 is done already is factored in, as you can see there are two lines in those charts, one for DCTF and one for LLTF[/QUOTE]

Brainfart on my part :smile:

Sunday Night Wrapup
 

From here [url]http://www.gpu72.com/reports/workers/dctf/week/[/url]
115,508 GhzDays DCTF in the last week.
59 different contributors
238 Factors found
13,123 P1/LL/DC work saved.

From here: [url]http://www.gpu72.com/reports/workers/dctf/[/url]
31 contributors currently have assignments
8,856 Assignments out.

From here: [url]http://www.gpu72.com/reports/estimated_completion/primenet/[/url]
238.1908 estimated days to completion
August 6, 2015

LG72D has been switched from DCTF to LLTF. That's probably what dropped the participants.

It also looks like the throughput has dropped from 18 THz-d/d to 13 THz-d/d. The time to estimated completion is now 240 days and still dropping several days a day, so we should be done in less than 8 months from now.