[QUOTE=Bdot;290529]
I'm currently finishing
26073517 [83.45%] "Double-checking to "ANONYMOUS" on 2012-02-22"
26087389 [79.11%] "Double-checking to "Kyle Askine" on 2012-02-22"
25834519 [94.67%] "Double-checking to "Frederick Menninger" on 2012-02-22"
26078791 [90.99%] "Double-checking to "ANONYMOUS" on 2012-02-22"

[/QUOTE]


26087389 still has ~ 7hrs to go, the other 3 are successfully completed now. I wrote a PM to bcp19 who got the 2 "ANONYMOUS" ones. I hope Frederick's machine picks up that the DC is complete ...

Kyle, I'll let you know when your one is submitted so you can remove it from your machine. Thanks for your help.

[QUOTE=chalsall;289787]Just so everyone knows, Dubslow has once again beaten me (:smile:) to announcing that I've added an overall GHz Days per Day of Work Saved graph, and a Linear Regression Trend line to many of the graphs, on the [URL="http://www.gpu72.com/reports/overall/graph/month/"]Overall System Progress Graphs[/URL] page.

I've been thinking about how to do this for the TF Depth graphs. The problem I'm having is what would I regress?

The aggregate of each completion type?

Those that have been TFed to the release level?

I need to run some experiments, and see what visually communicates the information best.[/QUOTE]

Re-posting from 4 page back because, I think it went under the radar...

That graph looks highly suspicious... Just roughly adding the DC saved in the graph would give about [B]45,000[/B] GD in the [B]last 30 days[/B], but if we look at the overall report it shows we have only saved about 16,925 GD (Now 22,278) for DC [B]since the project started[/B].

[QUOTE=diamonddave;291062]Re-posting from 4 page back because, I think it went under the radar...[/QUOTE]

It didn't go under the radar -- Dubslow speculated, and I confirmed he was correct.

But to be explicit... The graph shows the amount of DC, LL and P-1 saved (although the latter is so small in comparison to the other two that it can barely be seen).

The chart is showing the total amount of DC, LL and P-1 (if it was actually needed) saved by each of the factoring work types -- DC TF, LL TF and P-1. As in, a successful DC TF will save a DC, while a successful LL TF will save a LL, a DC and possibily a P-1. A successful P-1 (currently) saves a LL and a DC; in the future it might only save a DC if we ever find a DC candidate which has not yet had P-1 work done.

I have added a note to the page to hopefully make it clearer.

[QUOTE=chalsall;291065]if we ever find a DC candidate which has not yet had P-1 work done.[/QUOTE]There's a huge pile of them. Although, if you're looking <40M you're unlikely to find any since I (and a few helpers) cleared them all out last year. There's a bunch starting at around [url=http://mersenne-aries.sili.net/p1small.php]44M[/url].

[QUOTE=chalsall;291065]It didn't go under the radar -- Dubslow speculated, and I confirmed he was correct.

But to be explicit... The graph shows the amount of DC, LL and P-1 saved (although the latter is so small in comparison to the other two that it can barely be seen).

The chart is showing the total amount of DC, LL and P-1 (if it was actually needed) saved by each of the factoring work types -- DC TF, LL TF and P-1. As in, a successful DC TF will save a DC, while a successful LL TF will save a LL, a DC and possibily a P-1. A successful P-1 (currently) saves a LL and a DC; in the future it might only save a DC if we ever find a DC candidate which has not yet had P-1 work done.

I have added a note to the page to hopefully make it clearer.[/QUOTE]

So in the last week we saved about 10,000 Ghz-Day of DC LL? Yet since the project started we saved 23,000 Ghz-Days of DC LL?

I really don't understand how those number makes any sense.

1 successful DC TF saves about 43.75 Ghz-Day (lets be very generous and give a 35M credit here)

So if I add all those little blue bars in the graph I included in attachment we should have found at LEAST 1000 DC factor in the last month to get 44k Ghz-Day of work saved.

Yet since the project started we only found 727 DC Factor...

[QUOTE=diamonddave;291068]1 successful DC TF saves about 43.75 Ghz-Day (lets be very generous and give a 35M credit here)... Yet since the project started we only found 727 DC Factor...[/QUOTE]Remember that a DC-TF factor saves a DC-LL. But a LL-TF factor also saves a DC-LL. So does a P-1 factor. DC work saved isn't based on DC-TF factors, but on [i]all[/i] factors found.

[QUOTE=diamonddave;291068]So in the last week we saved about 10,000 Ghz-Day of DC LL? Yet since the project started we saved 23,000 Ghz-Days of DC LL?

I really don't understand how those number makes any sense.[/QUOTE]

You're comparing two different things.

Since the project started DCTFing saved 22,178 GDs of DC work.

But since the project started, DCTFing, LLTFing and P-1'ing saved 161,595.11 GDs of DC work.

Let me give you an example raw query from the database:

[CODE]mysql> select date(Completed) as Date,count(*) as Facts,
sum(GHzDaysLL),sum(GHzDaysDC),sum(GHzDaysP1) from Facts
where Completed>"2012-02-21" group by date(Completed) order by Date(Completed);
+------------+-------+-----------------+-----------------+----------------+
| Date | Facts | sum(GHzDaysLL) | sum(GHzDaysDC) | sum(GHzDaysP1) |
+------------+-------+-----------------+-----------------+----------------+
| 2012-02-21 | 26 | 736.2905807495 | 1357.4044265747 | 13.1904993057 |
| 2012-02-22 | 38 | 1371.8684616089 | 2208.5607604980 | 13.2259583473 |
| 2012-02-23 | 23 | 1070.4165115356 | 1514.3111228943 | 13.2968802452 |
| 2012-02-24 | 19 | 736.9928588867 | 1122.5219669342 | 8.7936668396 |
| 2012-02-25 | 32 | 1221.2140426636 | 1898.4470863342 | 11.4979257584 |
| 2012-02-26 | 27 | 1369.0946960449 | 1822.6814956665 | 13.2426235676 |
| 2012-02-27 | 29 | 2142.2888793945 | 2448.9804286957 | 18.7429766655 |
+------------+-------+-----------------+-----------------+----------------+
7 rows in set (0.00 sec)[/CODE]

GHzDaysLL is the amount of LL saved, etc. GHzDaysLL will never be more than GHzDaysDC.

If you (or anyone) would like this data exposed as a CSV, please let me know. I'm happy to share data, and welcome sanity checking and integrity auditing.

[QUOTE=chalsall;291070]You're comparing two different things.

Since the project started DCTFing saved 22,178 GDs of DC work.

But since the project started, DCTFing, LLTFing and P-1'ing saved 161,595.11 GDs of DC work.

Let me give you an example raw query from the database:

[CODE]mysql> select date(Completed) as Date,count(*) as Facts,
sum(GHzDaysLL),sum(GHzDaysDC),sum(GHzDaysP1) from Facts
where Completed>"2012-02-21" group by date(Completed) order by Date(Completed);
+------------+-------+-----------------+-----------------+----------------+
| Date | Facts | sum(GHzDaysLL) | sum(GHzDaysDC) | sum(GHzDaysP1) |
+------------+-------+-----------------+-----------------+----------------+
| 2012-02-21 | 26 | 736.2905807495 | 1357.4044265747 | 13.1904993057 |
| 2012-02-22 | 38 | 1371.8684616089 | 2208.5607604980 | 13.2259583473 |
| 2012-02-23 | 23 | 1070.4165115356 | 1514.3111228943 | 13.2968802452 |
| 2012-02-24 | 19 | 736.9928588867 | 1122.5219669342 | 8.7936668396 |
| 2012-02-25 | 32 | 1221.2140426636 | 1898.4470863342 | 11.4979257584 |
| 2012-02-26 | 27 | 1369.0946960449 | 1822.6814956665 | 13.2426235676 |
| 2012-02-27 | 29 | 2142.2888793945 | 2448.9804286957 | 18.7429766655 |
+------------+-------+-----------------+-----------------+----------------+
7 rows in set (0.00 sec)[/CODE]

GHzDaysLL is the amount of LL saved, etc. GHzDaysLL will never be more than GHzDaysDC.

If you (or anyone) would like this data exposed as a CSV, please let me know. I'm happy to share data, and welcome sanity checking and integrity auditing.[/QUOTE]

Yeah, took me a while, but I finally figured out the graph while walking to go grab me some lunch...

I really taught it was a break down of the summary exposed at the top of the page for each work type in the last 30 days...

Sorry,

[QUOTE=diamonddave;291075]Sorry,[/QUOTE]

No problem. You've helped catch mistakes I've made in the past. :smile:

And since this GDs saved metric is new, I should probably add another table to the Overall Stats page which shows what the graph does.

[QUOTE=Bdot;291039]26087389 still has ~ 7hrs to go, the other 3 are successfully completed now. I wrote a PM to bcp19 who got the 2 "ANONYMOUS" ones. I hope Frederick's machine picks up that the DC is complete ...

Kyle, I'll let you know when your one is submitted so you can remove it from your machine. Thanks for your help.[/QUOTE]

Crap... I removed it from my worktodo.txt thinking that as long as I didn't manually remove the assignment from primenet I would keep it.

I was wrong: [URL="http://mersenne.org/report_exponent/?exp_lo=26087389&exp_hi=26087389&B1=Get+status"]http://mersenne.org/report_exponent/?exp_lo=26087389&exp_hi=26087389&B1=Get+status[/URL]

I'm really sorry to you, but more to the person who got it.

[QUOTE=KyleAskine;291081]Crap... I removed it from my worktodo.txt thinking that as long as I didn't manually remove the assignment from primenet I would keep it.[/QUOTE]

The problem was you Unreserved it on your G72 Assignments page, and Spidy then unreserved it from PrimeNet but wasn't able to recapture it in time.

So everyone knows, I finished with the manual clean-up of this, and sent PMs to those last three people affected. Most were simply given new keys, but unfortunately Bdot actually lost a few.

So this doesn't happen again, I have modified Spidy and AnonSpidy such that if it recaptures a candidate which is assigned as LL or DC work to one of our workers, it will be put into a "quarantine" state. I'll be notified, and it will not be assigned to another worker nor released back to PrimeNet.

But in addition to this, for anyone who's going to work on such assignments with either a GPU based system, or a CPU system which isn't going to talk to PrimeNet until the work is finished, could I ask that you still use Prime95/mprime to claim the assignment from PrimeNet when you get them?

In this way the assignment will be officially transfered to you and appear in your PrimeNet assignments page. Then you can extend it on PrimeNet via the Manual Testing -> Extensions function if needed.

And please note that PrimeNet appears to expire any and all candidates after appoximately 60 days of no communcations.