Much slower. In the past week or so, the rate has slowed from around 1,000 per day to about 300 per day, and it's still declining.

I think there are many many v6 results in "database limbo", and a manual purge is needed. If one looks at the valid SETI@home Enhanced tasks on any of the top hosts' machines, you will in many cases find several dozen such tasks. Computer 6716400 is a good example.
____________

hmm. The transitioner makes another check at original deadline, but even that has passed.
There's a bunch where there was another replication even though the first was still out. Or though the first pair was valid.
Looks like most of those are from the transition - didn't go quite that flawless then.
Fair number of database oddities - yes, that will require a manual purge, but probbalt best to wait that most tasks have reported back in.

We had that when AP v5 was phased out, a couple of tasks were stuck in the DB. We know of course that sometimes tasks get stuck that way, but the occurence is too low to show up in the normal course of things. Plus that migration resulted in a higher rate.

Besides, that decline is pretty much as expected. With about a six week deadline we are now in the second round of extra replications. going to slow down to a trickle.
____________
A person who won't read has no advantage over one who can't read. (Mark Twain)

Actually out of my 26 remaining SETI Enhanced w/u's (across 3 rigs), 23 will need manual assistance to clear, which may mean there are way less than the actual number showing (maybe as few as 25% of those showing), so the end maybe closer than we can see. ;-)

You would think these have been reissued by now and maybe they have been. But there's the chance they got assigned to drive by crunchers or part time crunchers or just some old and slow cruncher.
____________
"Life is just nature's way of keeping meat fresh." - The Doctor

The last countdown we had was with Astropulse v505. At the time, I did some linear projections to predict the date when the last one would disappear, but re-sends of the last few threw that out by several weeks, despite a database purge by the project administrators when there were 39 left. (As the numbers decrease, so does the linearity.)

So, this time I will only say that the last one won't have been crunched before 9 August 2013 at 13:23 UTC, and probably quite some time after that!

That time has passed and there are still 6307. Care to make a new guess?

____________DavidSitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Have a look at your wingman's stderr_txt file. I'll bet you find it's an errored result from a rogue 560Ti or similar and the resend to the third computer has timed out.

Then to cut corners, the good result has been "validated" against the bad one and a credit of ~30 given to both.

T.A.

I just read this whole thread, from the beginning, in one shot. For the first time, I checked my current machines and noticed that I have 3 units that are all in the boat you describe above. But looking closer, I see that for one of them, BOTH of us errored out on it. I got a -9 and my original wingmate got a CUFFT. It was apparently only ever sent to one replacement host, which timed out several weeks later. The two of us who returned it got credit of 35.45, which seems odd for both of us having errors.

____________DavidSitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

The last countdown we had was with Astropulse v505. At the time, I did some linear projections to predict the date when the last one would disappear, but re-sends of the last few threw that out by several weeks, despite a database purge by the project administrators when there were 39 left. (As the numbers decrease, so does the linearity.)

So, this time I will only say that the last one won't have been crunched before 9 August 2013 at 13:23 UTC, and probably quite some time after that!

That time has passed and there are still 6307. Care to make a new guess?

My linear regression now shows 24 August 2013 at 00:26 UTC. However, as has been noted, there are probably hundreds if not thousands of tasks in the database that have been validated but not deleted. These tasks have arrived in "limbo" for a variety of reasons, and manual intervention will likely be required to clear them.
____________

However, as has been noted, there are probably hundreds if not thousands of tasks in the database that have been validated but not deleted. These tasks have arrived in "limbo" for a variety of reasons, and manual intervention will likely be required to clear them.

Those tasks, at least all that has been reported back to the servers, *should* not be shown as "in progress" (i.e. "out in the field" on the server status page), but simply as "waiting for db purging" or maybe as "returned and awaiting validation" (both not available on the project status page).

Only timed out tasks might be counted as "in progress", there it could make some sense, since they are indeed still out in the field and theoretically still can be returned. But maybe I expect too much...
____________.

Have a look at your wingman's stderr_txt file. I'll bet you find it's an errored result from a rogue 560Ti or similar and the resend to the third computer has timed out.

Then to cut corners, the good result has been "validated" against the bad one and a credit of ~30 given to both.

T.A.

I just read this whole thread, from the beginning, in one shot. For the first time, I checked my current machines and noticed that I have 3 units that are all in the boat you describe above. But looking closer, I see that for one of them, BOTH of us errored out on it. I got a -9 and my original wingmate got a CUFFT. It was apparently only ever sent to one replacement host, which timed out several weeks later. The two of us who returned it got credit of 35.45, which seems odd for both of us having errors.

I checked my other computer and it has one in similar condition: I got 4 spikes, other host got a CUFFT, third host timed out.

I guess the question being begged is, if these are showing as validated, why are they still appearing at all?

Also, just for fun, I'm showing one v6 still in progress.

____________DavidSitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.