Does anyone know why AP tasks only stick around for about 2 days before they are purged, while MB tasks about 7 days?
Or is it - Just because, LOL.

Good question.

short answer: because APs are bigger and contain more data. Therefore, you only get something like ~1/7 as many of them from a single tape as you get with MB. (I do not have the specific numbers on-hand.. Josef and Richard have answered this one tons of times though, I'm sure they still have it memorized without looking through their notes.)

So because of that, when a new pile of tapes shows up, AP can run through and split at ~7x the speed of MB. That's why AP feeding frenzies never last long. On top of that, multiple AP splitters can work on one tape simultaneously, and MB really doesn't like doing it and tends to "hang" and need a kick from the admins.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

...
At this point, not knowing how long this has been occurring, I'm going to say the AP database is hopelessly Polluted.

If that's the case, then some logic updates need to be made in the server-side code...which hopefully means we have to run through all those tapes again. That would be good news for us crunchers, right? Would mean a lot more work to become available once again. Sucks that it comes at the expense of potentially invalid science though.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I see I have one CPU task marked as invalid

single pulses: 1062368079
repetitive pulses: 1481755986
percent blanked: 328.60

WTF?

I've collected another 31 of them so far this morning.

Cheers.

Up to 53 now and it looks like I should be able to collect a few according to the SSP.

Cheers.

I've collected 16 of them so far. Just one computer running nowadays, and here on main, only running AP.
Now, they're also from November 2016.

Keep them coming.

I pursued them for years and they fed me well, now I've given up and just gladly accept what the server sends me. In order to help celebrate your sucess I might have some pickled herring, that's far better than lutefisk.

---

SETI@home	Requesting new tasks for CPU
SETI@home	Scheduler request completed: got 0 new tasks
SETI@home	No tasks sent
SETI@home	No tasks are available for AstroPulse v7
SETI@home	This computer has reached a limit on tasks in progress

Well it's been a while since I've seen that.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

88 of them now out of this run.

Cheers.

Got 83 this time.

WoW

---

With each crime and every kindness we birth our future.

got 172 since midnight UT. 17.5 hrs ago ... about 10/hr on my 9 computers ( about 1/hr each).

The computers are set to accept only AP's starting with a full cache of MB's

EdF

EDIT: oops That's my 5 computers ( about 2/hr each).

164 randomly collected out of this run now.

[edit] 169 now.

Cheers.

My i5 has enough to make it though maintenance - and more!
51 CPU, 4 cores ~2.6 days
75 ATI ~ 5.7 days

I wound up with 182 in that last batch and now more are being split.

[edit] I just got 3 off them.

Cheers.

Amazing AP supply, I crunched more than 100. It also interesting to see that my RAC hasn't increased significantly. I guess the MB opencl app has become very powerful.

I got 35 so far out of this latest batch today.

Cheers.

I've gotten 118 WUs in last 12 hrs across my 5 computers ... so the rate remains about the same here ... ~2/hr/computer

Ed F

I lost count after 170 in that last batch.

Cheers.

My best single result was 741.09 on the last batch.

---

Spoke too soon, best task is now at 823.19 credits.

I see some strange things going on. These two WUs validated on the first try even though the results are different. This is Not supposed to happen;
https://setiathome.berkeley.edu/workunit.php?wuid=2576361008
https://setiathome.berkeley.edu/workunit.php?wuid=2576360582
The NV card found 2 & 0, the AMD found 0 & 0 and it was validated without being sent to a third Host?
WTH?

Please catch stderr in message next time you see smth like this.
Links live too short so this particular alreat gone in vain.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.