If the RTS cache isn't fixed soon tomorrow's 12 hr outrage will be overly exciting.

Guess everyone came back from the weekend hungry for work, eh?

---

Looks like some new datasets have made their way in for splitting.

Just in time too I only have 599/600 MB tasks!

Braggart! LOL

Stephen

:-P

Looks like some new datasets have made their way in for splitting.

Just in time too I only have 599/600 MB tasks!

Braggart! LOL

Stephen

:-P

It looks like my statement was actually not true. I was only looking at my In progress MB tasks. As I wasn't expecting to have any AP tasks in progress, but I seem to have snagged one. I had nearly forgotten what they look like.

---

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

i just have some AP¨this night

http://setiathome.berkeley.edu/results.php?userid=92221&offset=0&show_names=0&state=0&appid=20

---

Seemed like a long outage ? or ?

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Seemed like a long outage ? or ?

13+hours

It started at noon UT is this our new normal??

BTW:

Current result creation rate **	0/sec	0.0052/sec	3.0660/sec 

...Wow

Ed F

Edit: 10 Min's later

Current result creation rate **	0/sec	0.0272/sec	44.1171/sec

Hmm, now you mention it my one running machine at the moment will run dry soon. It's only a 1050ti running stock SoG on Linux. Fingers crossed the pipes unclog.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Methinks the database may be too big. I hypothesize that some of the last 18 yrs data has been analyzed by various apps and the older ones are redundant and have no need to be carried in the data base. If true the Tuesday outrage would be shorter.
This probably not a priority for the project because it does not effect throughput very much.

---

Methinks the database may be too big. I hypothesize that some of the last 18 yrs data has been analyzed by various apps and the older ones are redundant and have no need to be carried in the data base.

No that's not how it works. We don't know how many seconds or years there might be between two signals from ET. Because we don't all the data points [canonical results] are needed just to see if something repeats. Frankly if the database were to be combined with other radio searches and optical searches we might catch an ET we might otherwise overlook.

---

Seemed like a long outage ? or ?

13+hours

It started at noon UT is this our new normal??

BTW:

Current result creation rate **	0/sec	0.0052/sec	3.0660/sec 

...Wow

Ed F

Edit: 10 Min's later

Current result creation rate **	0/sec	0.0272/sec	44.1171/sec

Even bigger wow.
Current splitting rate 66/s, sustained over 60/s for a couple of hours now.
Would have to be a new record.

---

Grant
Darwin NT

Ahh I see we have some pretty BLC data again, nice!
Will see how they will last.

---

"SETI is probably the most important quest of our time,
and it amazes me that governments and corporations
are not supporting it sufficiently."- Arthur C. Clarke 2006

Seemed like a long outage ? or ?

. . Not so long, it started early 11:00 pm NSW Daylight saving time yesterday and was over at about 10:30 am this morning (same time zone). 11.5 hours seems quite normal these days. In Berkeley time that would be from 5 am to 4:30pm tomorrow (joking .. all yesterday.

Stephen

:)

Methinks the database may be too big. I hypothesize that some of the last 18 yrs data has been analyzed by various apps and the older ones are redundant and have no need to be carried in the data base.

No that's not how it works. We don't know how many seconds or years there might be between two signals from ET. Because we don't all the data points [canonical results] are needed just to see if something repeats. Frankly if the database were to be combined with other radio searches and optical searches we might catch an ET we might otherwise overlook.

. . Perhaps they meant that much of the older data has been Re-crunched by later apps and the earlier results are perhaps redundant.

. . Stephen

??

Seemed like a long outage ? or ?

13+hours

It started at noon UT is this our new normal??

BTW:

Current result creation rate **	0/sec	0.0052/sec	3.0660/sec 

...Wow

Ed F

Edit: 10 Min's later

Current result creation rate **	0/sec	0.0272/sec	44.1171/sec

Even bigger wow.
Current splitting rate 66/s, sustained over 60/s for a couple of hours now.
Would have to be a new record.

. . And hopefully no more issues getting new work ?

Stephen

:)

Methinks the database may be too big. I hypothesize that some of the last 18 yrs data has been analyzed by various apps and the older ones are redundant and have no need to be carried in the data base.

No that's not how it works. We don't know how many seconds or years there might be between two signals from ET. Because we don't all the data points [canonical results] are needed just to see if something repeats. Frankly if the database were to be combined with other radio searches and optical searches we might catch an ET we might otherwise overlook.

. . Perhaps they meant that much of the older data has been Re-crunched by later apps and the earlier results are perhaps redundant.

. . Stephen

??

That is exactly what I meant.

---

looking good!! 50+ guppi "tapes" mounted and read to go!!

Ed F

looking good!! 50+ guppi "tapes" mounted and read to go!!

Ed F

. . So a Guppi flood is coming ?

LOl

Stephen

.

Yay, talk about fresh...Green Bank guppies recorded 3 days ago :-)

...Grete...

---

Humans may rule the world...but bacteria run it...

Some things not looking too good right now:
1) Replica DB offline,
2) AP work present but splitters not running,
3) Assimilators are down (due to 1 above, perhaps?)

Hopefully it's someone doing late work rather than a growing failure ...

---

Some things not looking too good right now:
1) Replica DB offline,
2) AP work present but splitters not running,
3) Assimilators are down (due to 1 above, perhaps?)

Hopefully it's someone doing late work rather than a growing failure ...

Well the replica shows as disabled. Which is a better sign than not running.
There is a good chance that the loaded datasets have already been split for AP work. So i wouldn't get to excited about that.

---

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