Got up to ten GPU tasks at a time and my credits have risen. I have small cache, 0.25 days in all projects.
Tullio

---

I've received about 850 per day since the stress test stopped

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

I've received about 300 per day since the stress test stopped

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

What happened with Milkyway ? are they down ?

The Boinc Forums are a good place to look for these sort of answers.

https://boinc.berkeley.edu/forum_thread.php?id=10279

Yes the network had an "intruder" so was shut down

One OpenPandemics GPU task completed in less than ten minutes on my GTX 1060. They used to take about 20 minutes in the stress test phase.
Tullio

---

E-mail received mid-March.

The cost of supplying energy has changed, so we’re changing our energy prices. Your energy will cost about £124.15 more each year from 19 April.
The price of wholesale energy has increased, and is now 31% higher than in September due to the extra cold weather we've experienced.

Due to covid, a bit flush with funds so doubled up before it went up. That took me to the end of May.
To see what effect the increase will have on the budget, started logging usage.
Based on the usage for the 9 days so far, pro ratia, it looks like a 50% increase not 31% as stated.
Been averaging £50 a month from Sept (up from £45) but the new average looks to be around £75.
So that begs a question as that will impact the budget big time.
Which is the better option?
Shut down the dual core or run both only for 12/7?

There is extra consumption of non-CPU part
So IMHO better computations per J will provide running 12/7
If host completely unattended consider to run 24/3.5 instead to decrease booting/shutdown losses and hardware wear out overall.

BTW, don't you have discounts in night hours?... Maybe better to run @night only....

---

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

I am trying a new HP laptop with a Ryzen 5 4000 CPU and Radeon Graphics incorporated. The Einstein@home gamma ray GPU tasks take about 1095 s on my GTX 1650 board, of which 1076 are CPU.. The same tasks take about 3385 s on the Radeon chip of which only 107 are CPU. I was going to test the new laptop on the OpenPandemics-Covid-19 GPU tasks but I am not getting any of them.
Tullio

---

I am trying a new HP laptop with a Ryzen 5 4000 CPU and Radeon Graphics incorporated. The Einstein@home gamma ray GPU tasks take about 1095 s on my GTX 1650 board, of which 1076 are CPU.. The same tasks take about 3385 s on the Radeon chip of which only 107 are CPU. I was going to test the new laptop on the OpenPandemics-Covid-19 GPU tasks but I am not getting any of them.
Tullio

You could check what Radeon part time will be if CPU part fully loaded (no CPU cores reserved).

---

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

Any insider knows if Seti@home will ever come back after the Nebula pipeline is sorted out?

Maybe with data from FAST and GBT?

---

Extremely doubtful. This project went on much longer than originally planned. For all purposes, I do believe this part of SETI is done.

---

David's last Nebula post did say:

Other news: we're talking with astronomers at FAST about using Nebula as part of SETI sky survey there. Needless to say, that would be very exciting!

That's typically nebulous, but I read it more as 'We [i.e. David and Eric] might help FAST', rather than 'FAST might capture data for us [the SETI orphans]'.

If they did get a new tranche of raw data from FAST, quite a lot of hardware (and possibly a few humans) would need to be resurrected and fettled back up into working order.

I agree with the sentiments expressed here. Seti@Home achieved what it set out to do, and was a landmark project in the history of distributed computing. But there was no point in continuing to add more results to the database, just for the sake of it, without a new backend to do something meaningful with 20 years of results.

Nitpicker was the intended next step forward, but they changed their minds and wanted to do the second sift in real time. Even back then, a suitable machine was about $40,000, the money wasn't there, so it was shelved.

Nebula, if it actually ever happens, will do this second sift, but David and Eric have found it more difficult to finalise the algorithms needed, than they initially thought. Do we even know that the original agreeement 4 years ago to use Einstein's Atlas computer cluster at Hanover is still on offer? Many of the Seti big hitters have switched off or transferred to other Boinc projects, I doubt we could get back to where we were, even if there was a new source of data. I think Richard's interpretation and projection is probably correct.

But no regrets, it was fun to be part of it all while it was going. We made history!

---

Just remember that if Nebula turns out to be a success then a new version of SETI@home app that does all the necessary corrections and filtering could be possible as was hinted at quite some time ago.

Success of Nebula could lead to more funding so hold onto the faith people for that success. ;-)

Cheers.

Nitpicker was the intended next step forward, but they changed their minds and wanted to do the second sift in real time. Even back then, a suitable machine was about $40,000, the money wasn't there, so it was shelved.

Mainly because they didn't even try.

In December 2019 / January 2020, users raised nearly $60,000, primarily for a new storage array. Those figures can still be seen on the donations page.

Two years earlier (December 2017), there was another special fundraiser to extend the processing range to include data from the Parkes telescope in Australia. That's fallen off the official record, but my note from the time says that nearly $25,000 was received from users in a matter of days. In addition, the fundraiser was backed by matched funding, so the final total will have been well over $100,000. In the end, the Parkes processing channel was never implemented, but the goodwill was there.

But having said that, I think the main reason Nitpicker was abandoned was because the whole darn concept was too slow. It could never have kept up with the ideal of 'near real time' (the original Nitpicker concept), even with oodles more money: hence the switch to a batched snapshot schema with 'Nebula'.

I think the goodwill was always there. I personally am quite proud to have donated $17,000 to buy the Centurion Server, in honour of my dad that died aged 101.

The First Nitpicker idea was to take a chunk of the database, second sift them and feed the best candidates out for further processing, and then another chunk. But as Richard confirmed, the later idea was "near real time", which just wasn't practical. So life contunued as usual. It was DA's report that made people think again about the whole concept.


I would love to see S&H return in some format, I think we all would, even if it might be a bit of a shadow of it's former self. And as Wiggo said, it might attract some more funding. The dedication and the bonhomie is still there amongst us oldies.

And yes, I would come back with S@H Mk 2, but not with the current Mod team. They are the real reason that I deliberately deleted my account with over 20 years worth of memories and a billion Boinc credits.

I deliberately deleted my account with over 20 years worth of memories and a billion Boinc credits.

Some "actual" facts.
The only credits lost was 42.5+M from the Seti data.
The implication that you deleted all your boinc credits does you no justice...
...as usual with your "past" posts.

For people who may need a refresher on what we're talking about, try Near Time Persistency Checker (NTPCKR). There are links to the original proposals in technical news.

Note the date. This was first dreamed up in 2007. That's before GPUs were a twinkle in a cruncher's eye, and the database of processed results is already described as about 1TB in size. Just imagine what it became after 12 years of intensive GPU crunching.

I won't post here again for obvious reasons. Richard, I'll contact you privately.