Also to note.. not that it really matters at all, but if you take a look at your application details page for any machine... the old, discontinued apps have been purged (APv505/6, MB6).

---

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

TL

Abort any MB tasks that were split on Nov 4 with a tag of _4 or over. They will be invalid anyways, might as well take and error for it now than waste the time on it.

The faster we can get these out of the system, the better.

---

TL

Abort any MB tasks that were split on Nov 4 with a tag of _4 or over. They will be invalid anyways, might as well take and error for it now than waste the time on it.

The faster we can get these out of the system, the better.

Well, it seems that both my systems are clear of any Nov 4 WUs... So, I hope that means that after the 23 Inconclusives are marked Invalid that I will be clear of this mess.


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

TL

Abort any MB tasks that were split on Nov 4 with a tag of _4 or over. They will be invalid anyways, might as well take and error for it now than waste the time on it.

The faster we can get these out of the system, the better.

Well, it seems that both my systems are clear of any Nov 4 WUs... So, I hope that means that after the 23 Inconclusives are marked Invalid that I will be clear of this mess.


TL

Actually I will continue to work them, they all have to be worked until there have been enough Invalids to make them go away. Until then they will continue to circle around.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

I see two _7 and one _4 on your AMD.

And one _9 on your Intel.

They are all Nov 4 original splits.

---

Abort any MB tasks that were split on Nov 4 with a tag of _4 or over. They will be invalid anyways, might as well take and error for it now than waste the time on it.

The faster we can get these out of the system, the better.

Thanks. Should have thought of this myself, sure crunched a ton of VLARs I didn't need to ...

---

I see two _7 and one _4 on your AMD.

And one _9 on your Intel.

They are all Nov 4 original splits.

Unfortunately; you are mistaken. I just rechecked my Tasks in queue on both machines; and NO Nov 4 units are present. You must be seeing completed units that are in the Inconclusive category, and waiting for validation to be marked Invalid... As stated, I have 23 of those waiting for validation.

I have plenty of 08ap11... 11no11... 08ja11...

The ONLY 04... Unit I have in queue is on Exeter, (GTX-760), AMD machine, and is 04ap11...

Unless, they are GHOST units; all I need on top of faulty Invalids, so, don't know what to say - but NO Nov 4 Units on my two systems.


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

Side note, which I noticed the last time this broken-WU debacle happened.. if you happen to be lucky enough to get the _9 task... that one will not reset your consecutive valid count. My single-core machine (side-note: since it was made in 2007, it finally just reached 1M credits) got a _9 the last time around and I contemplated aborting it, but I had looked at some other WUs that were affected and noticed that the machine that got _9's consecutive, didn't have their consecutive valid counter reset since the _9 task doesn't get marked as an error/invalid.

Of course, it doesn't really matter if your consecutive streak has already been obliterated. I was fortunate enough in that previous event to have only gotten one single bad WU out of that, and even luckier to get a _9.

---

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

you have to look on the web page and see when the WU was initially processed, not when it was resent to you ( for the 7th time).

---

you have to look on the web page and see when the WU was initially processed, not when it was resent to you ( for the 7th time).

Looking at the web page; NO UNITS of Nov 4th or 5th can be aborted; as requested by your original post to me... ALL of these Units have been completed and marked Invalid, now up to 60; or are in the Inconclusive pile; now down to 22.

So, AS I STATED, my queue is CLEAR of these units... I have NO MORE to be processed.


TL

[EDIT:]

Also, it seems that the units marked as Invalid or Inconclusive start from Nov 4 and go through Nov 8 issuance; AGAIN, ALL completed, and marked, or waiting to be marked; so UNABLE to be aborted.

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

WU's from 23oc11ah.17390 keeps arriving in my cache, and every one is reported as invalid. Theses are split on 8th and 9th of Nov.

Just pruned my caches of 11 WU's receoved today with _5, _7 and _9.

ChrisD

WU's from 23oc11ah.17390 keeps arriving in my cache, and every one is reported as invalid. Theses are split on 8th and 9th of Nov.

I have plenty of 08ap11... 11no11... 08ja11...

The ONLY 04... Unit I have in queue is... is 04ap11...

We still seem to have some severe temporal dislocation in this thread.

The problem is neither when the original data was recorded at Arecibo, nor when the individual task was replicated to send out to the latest user:



but only when the original workunit was carved out of the recording tape:

Also to note.. not that it really matters at all, but if you take a look at your application details page for any machine... the old, discontinued apps have been purged (APv505/6, MB6).

I asked for an option to hide them (#1433), David chose to remove them. Is probably easier.

---

Also to note.. not that it really matters at all, but if you take a look at your application details page for any machine... the old, discontinued apps have been purged (APv505/6, MB6).

I asked for an option to hide them (#1433), David chose to remove them. Is probably easier.

But, sadly, it removes the opportunity to verify that a new application or application version is performing as intended by comparison with previous versions. We can, for example, no longer look at the relative APR values for setiathome_enhanced and SETI@home v7 (the previous and current MB apps). Those should indicate whether <rsc_fpops_est> has been calibrated properly, and hence (IMH - but lone - O) whether CreditNew is likely to score jobs realistically.

WU's from 23oc11ah.17390 keeps arriving in my cache, and every one is reported as invalid. Theses are split on 8th and 9th of Nov.

I have plenty of 08ap11... 11no11... 08ja11...

The ONLY 04... Unit I have in queue is... is 04ap11...

We still seem to have some severe temporal dislocation in this thread.

The problem is neither when the original data was recorded at Arecibo, nor when the individual task was replicated to send out to the latest user:



but only when the original workunit was carved out of the recording tape:

That being the case, Richard, (now I give up, because I don't understand how, or where to find that date), I have looked in my BOINC queues on both machines for ANY units with "_7", "_4", or "_9" in each and EVERY WU in queue... NOTHING exists in either machine.

Therefore, I conclude, once again, that I am clear of these WUs... They have run their course on my machines...

Thank you - sincerely,


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

WU's from 23oc11ah.17390 keeps arriving in my cache, and every one is reported as invalid. Theses are split on 8th and 9th of Nov.

I have plenty of 08ap11... 11no11... 08ja11...

The ONLY 04... Unit I have in queue is... is 04ap11...

We still seem to have some severe temporal dislocation in this thread.

The problem is neither when the original data was recorded at Arecibo, nor when the individual task was replicated to send out to the latest user:



but only when the original workunit was carved out of the recording tape:

That being the case, Richard, (now I give up, because I don't understand how, or where to find that date), I have looked in my BOINC queues on both machines for ANY units with "_7", "_4", or "_9" in each and EVERY WU in queue... NOTHING exists in either machine.

Therefore, I conclude, once again, that I am clear of these WUs... They have run their course on my machines...

Thank you - sincerely,


TL

Some people seem to confuse task & workunit or use the terms interchangeably. You need to use the site to see the workunit information.
On your task list click on the ID number under the Work unit click for details column instead of the ID under the Task
click for details column.

I like to think of it as:
A task contains the record of the host & it's result data.
A workunit contains the records of all the tasks for that workunit.

---

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

Yes, finally some Mac nVidia GPUs. Thank you very much.
Now to see how long it lasts.
;-)

Appears to have been broken again for about a day or so...
NVIDIA
Mac
No GPU tasks reported

So we're back from maintenance, but unless I'm mistaken the splitters have not yet been turned up??

---

So we're back from maintenance, but unless I'm mistaken the splitters have not yet been turned up??

Read Technical News.

Splits (Nov 10 2015)

BUT ALSO we needed to update some fields in the current science database schema to also make the database itself telescope agnostic. Just a few "alter table" commands to lengthen the tape name fields beyond 20 characters. We thought these alters would take a few hours (and completed before the end of today's Tuesday outage). Now it looks like it might take a day. We can't split/assimilate any new work until the alters are finished. Oh well. We're going to run out of work tonight, but should have fresh work sometime tomorrow morning. It is a holiday tomorrow, so cut us some slack, if it's later than tomorrow morning :).

Claggy

it is a holiday tomorrow, so cut us some slack, if it's later than tomorrow morning :)

Veteran's day is not a Federal Holiday........although it should be!

---

"Sour Grapes make a bitter Whine." <(0)>