I spoke too soon.

---

I didn't get any today, maybe the ptoblem has been sorted out.

I'm sure it'll take several months to clear them all out, if nothing is done to block the resends. There will certainly be some tasks that get sent to hosts that go dormant and they'll have to wait to time out before being sent on. The good news is that these have fairly short deadlines, about 3 weeks, unlike the 2 months that "normal" MB tasks are given. However, since it generally takes 10 tasks to max out each of these WUs, I'm sure there will be some that end up with more than one "timed out" task, which will stretch out their demise.

I got 125 of these so far.
http://setiathome.berkeley.edu/results.php?userid=77852&offset=0&show_names=0&state=5&appid=

---

203 so far and another 127 sitting in the inconclusive spread out over 6 machines.

I've checked just to make sure it wasn't my machines and they almost all resends from other peoples invalids.

Just going to have to wait them out

I didn't get any today, maybe the ptoblem has been sorted out.

I'm sure it'll take several months to clear them all out, if nothing is done to block the resends. There will certainly be some tasks that get sent to hosts that go dormant and they'll have to wait to time out before being sent on. The good news is that these have fairly short deadlines, about 3 weeks, unlike the 2 months that "normal" MB tasks are given. However, since it generally takes 10 tasks to max out each of these WUs, I'm sure there will be some that end up with more than one "timed out" task, which will stretch out their demise.

So far your hypothesis seems to be correct the ones i have goten were resends with lots previous invalids

---

So far your hypothesis seems to be correct the ones i have goten were resends with lots previous invalids

I think the original distribution of _0 and _1 tasks was completed sometime Friday night (Berkeley time). I got my last one of those about 06:00 UTC Saturday. From there on it's been nothing but resends, _2 thru _9 tasks. As the days go by, we should be seeing more and more of the higher numbers, with a dwindling number of tasks overall as more WUs hit their 10 task maximums (of which I've seen a half dozen in my task list, so far).

Anyway, I keep aborting 'em when I see 'em. Even though that does knock down the "max tasks per day" figure, it doesn't do enough damage to prevent me from keeping my queues full with tasks that I can process productively.

I just aborted 10 more on my i7.

More concerning to me is http://setiathome.berkeley.edu/workunit.php?wuid=1669848312. It validated without an AC count. I just posted in the invalid host thread about one of the hosts that got credit for it.

---

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

I just aborted 10 more on my i7.

More concerning to me is http://setiathome.berkeley.edu/workunit.php?wuid=1669848312. It validated without an AC count. I just posted in the invalid host thread about one of the hosts that got credit for it.

Yes, that one should be concerning because the tasks labeled as Invalid found Zero Pulses whereas the 2 tasks that validated found 31 Pulses. Something is very wrong with that.

All of them ran as; Legacy setiathome_enhanced V6 mode.
The reason the two Overflows Validated is that Overflows are exempt from AC checking.

Oh wait, both the tasks that Validated were nVidia 9 series cards running CUDA 32...which is known to Produce Invalid results.
I suspect we are witnessing two otherwise Invalid tasks Validating against each other. I wonder how many other times that has happened when No One was watching...

Anyway, I keep aborting 'em when I see 'em. Even though that does knock down the "max tasks per day" figure, it doesn't do enough damage to prevent me from keeping my queues full with tasks that I can process productively.

Isn't getting these things up to their 10 invalids so they will be purged from the system productive?

---

Anyway, I keep aborting 'em when I see 'em. Even though that does knock down the "max tasks per day" figure, it doesn't do enough damage to prevent me from keeping my queues full with tasks that I can process productively.

Isn't getting these things up to their 10 invalids so they will be purged from the system productive?

The threshold is not 10 Invalid tasks but rather 10 total tasks, so an aborted task counts the same as an invalid, and actually helps the count get to 10 more quickly.

Anyway, I keep aborting 'em when I see 'em. Even though that does knock down the "max tasks per day" figure, it doesn't do enough damage to prevent me from keeping my queues full with tasks that I can process productively.

Isn't getting these things up to their 10 invalids so they will be purged from the system productive?

The threshold is not 10 Invalid tasks but rather 10 total tasks, so an aborted task counts the same as an invalid, and actually helps the count get to 10 more quickly.

I think Jeff was referring to his computer's (or his account's) "max tasks per day," not that of any particular WU.

---

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

I'm hit by invalids with the same strange error - falling back to legacy V6 mode... Most of them are downloaded on 10th January, 1 on 11th, 1 on 12th. Here they are:
http://setiathome.berkeley.edu/workunit.php?wuid=1671871621
http://setiathome.berkeley.edu/workunit.php?wuid=1672119102
http://setiathome.berkeley.edu/workunit.php?wuid=1671995053
http://setiathome.berkeley.edu/workunit.php?wuid=1672399479
http://setiathome.berkeley.edu/workunit.php?wuid=1672077377
http://setiathome.berkeley.edu/workunit.php?wuid=1672077264
http://setiathome.berkeley.edu/workunit.php?wuid=1669827081
http://setiathome.berkeley.edu/workunit.php?wuid=1672012258
http://setiathome.berkeley.edu/workunit.php?wuid=1672012264
http://setiathome.berkeley.edu/workunit.php?wuid=1672012270
http://setiathome.berkeley.edu/workunit.php?wuid=1672012141
http://setiathome.berkeley.edu/workunit.php?wuid=1672012131
http://setiathome.berkeley.edu/workunit.php?wuid=1669862262

---

A list which starts with

19ap11ad.18067.xxxxx.140733193388039.12.xxx

and ends with

19ap11ad.19368.xxxxx.140733193388035.12.xxx

- as previously reported.

I just dumped 2 more, for a total of 14 on my i7 (1 on my other box).

Two or three of my aborts are now out to their _9 host, so they should die soon. Several others are out to their _8.

---

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

I'm seeing the same thing and it's not just the 19ap11 work units although that does account for the majority. I've seen 21mr11, 28dc12, 28fe13 and others with the same problem. They were all downloaded between 7-Jan-15 and 14-Jan-15.

---

I'm seeing the same thing and it's not just the 19ap11 work units although that does account for the majority. I've seen 21mr11, 28dc12, 28fe13 and others with the same problem. They were all downloaded between 7-Jan-15 and 14-Jan-15.

Could you link a few examples from those other tapes, please? I've been watching pretty closely, and I haven't seen any at all with this specific problem except from the 7 channels from 19ap11ad tape.

Yeah I've seen some of those others as well.

Can't point them out to you as I'm at 250 total invalid so far with another 140 in the inconclusive pile and it's too much of a pain to go thru each and everyone to find those others.

Sorry. If one pops up closer to the most recent I'll link it.

Yeah I've seen some of those others as well.

Can't point them out to you as I'm at 250 total invalid so far with another 140 in the inconclusive pile and it's too much of a pain to go thru each and everyone to find those others.

Sorry. If one pops up closer to the most recent I'll link it.

Filter by invalid/inconclusive.

Click 'Show names' in the Task details column header (which applies an alphanumeric sort as well)

Page through until you find a batch that isn't 19ap11ad...

http://setiathome.berkeley.edu/result.php?resultid=3908579086
http://setiathome.berkeley.edu/result.php?resultid=3908764301
http://setiathome.berkeley.edu/result.php?resultid=3908620433
http://setiathome.berkeley.edu/result.php?resultid=3907680126
http://setiathome.berkeley.edu/result.php?resultid=3911303782
http://setiathome.berkeley.edu/result.php?resultid=3911303782
http://setiathome.berkeley.edu/result.php?resultid=3911416547

These are just a few. Beside the 19ap11ad.. there are several others spread out in my inconclusive. None have made it yet to the invalid pile. So of my 250 invalids 249 are all from 19ap11ad..

Those all say "Detected setiathome_enhanced_v7 task. Autocorrelations enabled"

In what way do they match the subject of this thread, which is about tasks saying "Legacy setiathome_enhanced V6 mode" instead?