A valid option. They already had a postponed Tuesday maintenance to Wednesday once. No reason why it is set in stone for Tuesday and especially pertinent with all the recent projects upsets.

---

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

A proud member of the OFA (Old Farts Association)

And the data base is smaller now to backup :D

Wonder what "They" think about such "Disconnection Technology" ! And "We" have the Gall to talk about "Self driving Cars" ! We seem to "Self Drive" ourselves to our Doom, physically as well as politically !

---

Moving along...

Moving along...

. . :)

Stephen

:)

And the data base is smaller now to backup :D

PM Eric with the idea. Maybe he could spend few minutes to read and think about. Fingers crossed.

---

An interesting idea. Just the reverse idea of splitting work in distributed computing. I have a 1 TB monthly activity limit on my ISP account. I rarely use more than 250GB any month, so I have spare capacity. But with only a 16/1 MB download/upload DSL connection, getting a data tape sent back to Berkeley will take some time.

Sounds like a job for torrents.
Can the public access Seti at Berkeley and the GBT data through Internet2? If the problem is in between the 2, get a bunch of trusted people with reasonable data allowances and set up a Torrent for each file from GBT. The trusted users download the files from GBT, Seti then downloads those files from those users. Of course this only works if there are plenty of users, and GBT can support their connections, and that Seti's Internet2 connection to those users isn't affected by the data chokepoint.

Not believe they will open to run a torrent program on the GBT server, if they do that is almost impossible to control who DL the data.
But instead open access to few users only do read & DL the tapes is not hard to to (they could easily create a user with privileges only to do that) . Each "retransmiters volunteers" could DL one tape (50gb) and transmit to the lab using the slow commercial internet speeds in a day or 2. Did anyone knows how many tapes are really used daily? Not believe is a lot greater than 10.
Another point, was posted here slow access speed from the lab to GBT what is this slow speed?
Could be slow to retrieve all the data but maybe enough to some work to be retrieved directly and some via the "retransmiters volunteers".
To help the process, instead of 50 GB tapes they could record in 25 Gb file size. More manageable with the common comercial internet connections.
Sure this not fix the problem but could bypass the problem and keep the data flowing slowly but flowing.
Can't believe will take long time to find the bottleneck in the internet2.

---

Bummer. SETI is a fantastic stability testing tool as well as getting some good work done :p I'll have to start reconnecting to my long forgotten milkyway@home project again. This was all some sort of master plan to trigger people in to remembering forgotten projects they were connected to isn't it? :D

---

Can't nothing about boinc and this system but i have 100/100 Mb line (test to 98/97- 105/110Mb) and don't use more then 20 of it and a 1TB disk that i can give 800Gb to boinc activity.. Not a heavy gamer pc but it working good for what i need .It have be nice if i can use it as a reserv link or reserv bank with work if i can get a program to work.
Hope all problems run away now soon.. or i soon need try to get bigger amount of work .. befor i run on 0,1/0,1 Now i have 0,4/0,5 and stil have no work at the end of the day
Greetings from sweden

Interesting thought, but I think your physical location may be an issue since you are no where near the USA. Maybe try https://www.speakeasy.net/speedtest/ and see if it tests speeds to a US server and see what happens.

Eric mentioned to me that they average about 1.1TB per day, which is about 120Mbps continuous 24/7. But they don't have 24/7 access to the Greenbank pipe. But it would certainly help.

You should install and test a FTP server and drop him a PM.

Test to Washington and get 47/82 d/u Mbps. And to NY 40/60 .. i don't know if it's good enuf..

Do we have any idea how long it will be down for? Must admit, I miss not being able to continue our search. . Hope one day success is achieved before I "kick the bucket" !!!

---

We have repeatedly suggested that in addition to SETI@home (with priority 100) people connect to multiple projects with priority 0 or 1, so you'll always have something useful to do.

We have very little control over what happens at the observatories, or on the networks between us.

Yes, Jeff ran into some snags with the data. Matt's unavailable to transfer more data from GBT until tomorrow.

Splitter seem to be down to me....

I dunno, seriously considering moving most of my hardware to F@H. I just get back into DC with new equipment.. ThreadRipper is idle yet again. I don't remember that SETI has been down for so long or had so many problems... Been doing S@H for over 15 years with various accounts and hardware.

Perhaps you guys have enough volunteers to do the WU's you need and my resources could be used elsewhere.

Thanks.

---

@SETIEric@qoto.org (Mastodon)

Well, LHC@home is in a crisis for unknown reasons. CPDN is unreachable, Sourcefinder an astronomy project also using VirtualBox like LHC@home has no work. Only Einstein@home is feeding my computers.
Tullio

---

POGS, Milyway and Rosetta seem to have work.

---

@SETIEric@qoto.org (Mastodon)

Well, LHC@home is in a crisis for unknown reasons. CPDN is unreachable, Sourcefinder an astronomy project also using VirtualBox like LHC@home has no work. Only Einstein@home is feeding my computers.

Thanks tullio... this is actually helpful as it shows that SETI@Home is not the only BOINC project that has its share of issues.

I would suggest a zero resource share (Edit: in project preferences in your account page on the project's site not in your BOINC client) on one's backup project as then BOINC only downloads a bare minimum of work, ie if there is a core or GPU free it will download one work unit for it, and not keep a cache. Then when SETI@Home has work it will fill the cache as much as it can and suspend the backup's work until the timeout is near.

One caveat is that BOINC will sometimes stop asking for work for the primary project... you can see that this has happened when there is no countdown timer to next contact. Clicking "Update" when it is like this will resolve it.

---

I would suggest a zero resource share (in project preferences) on one's backup project as then BOINC only downloads a bare minimum of work, ie if there is a core or GPU free it will download one work unit for it, and not keep a cache. Then when SETI@Home has work it will fill the cache as much as it can and suspend the backup's work until the timeout is near.

That's how I handle Einstein. Works just fine.

---

Hello,

may I'm blind, but where can I do, what You suggest?
"We have repeatedly suggested that in addition to SETI@home (with priority 100) people connect to multiple projects with priority 0 or 1, so you'll always have something useful to do. "

I just can't find a Option for that in the Boinc Manager.
cu
Matthias

---

Tools

---

A couple TB or early observations will be coming online soon.

One small file copied over from last nights AO observation and is in the radar blanker queue.

---

@SETIEric@qoto.org (Mastodon)