It would be really nice if there was a way to continue to have the work unit count available so that new PC's we add could still show the contribution to the analysis for SETI on the BOINC project count. Sounds silly but SETI was the first of its kind and those first work units on those old slow PC's were a huge investment for us ..

I know the project is in hibernation mode.
I needed to rebuild a PC.
I added BOINC and tried to add in SETI@home as a project but it was gone from the "list".
I found the SETI Project link and added it to the pool of active projects on BOINC.
ON this PC now I am showing zero contribution to SETI...

That makes me sad.

I provided 17+ years of computing support, and over 5M work units.

It would be really nice if there was a way to continue to have the work unit count available so that new PC's we add could still show the contribution to the analysis for SETI on the BOINC project count. Sounds silly but SETI was the first of its kind and those first work units on those old slow PC's were a huge investment for us ..

Thanks.

Chris

---

The short answer is "NO".
The project is down to do the next stage of the analysis. This is a hard enough task with a "locked" dataset, it would be incredibly difficult (next to impossible) with a database that was forever changing.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

No, but rather that you could be crediting a couple of users instead, for that of their work being "assigned" to this project, for also reported.

Too bad they couldn't find a way to make the result set/database read-only....

It would be an idea to implement it in BOINC. Maybe even as a general rule, for projects that shut down, but for SETI@home in particular, being the one that started it and so tied with BOINC. So have a BOINC database with the final stats for SETI@home, or if possible for as many / all shut down projects, and when a user logs on, they'll be able to import and display their stats that way. Said database will just need to be written to once per project (or once, period, if just for SETI@home).

---

BOINC does already maintain a project-by-project record of tasks completed: for this project, the file is

job_log_setiathome.berkeley.edu.txt

and it's located in the top level of the BOINC data folder structure.

All you need to do is open that file in an editor with a line-count facility. This machine is showing 456,789 [what a remarkably neat number! I hadn't noticed that before]. It's a bit of a cheat, though - I copied the data folder from an older machine attached in 2007, and that's the grand total of both generations of hardware added together.

There's no central record of those logs, though. You'd have to gather the file from each separate hard disk you've used. And they'll only cover the BOINC phase of the project - I don't know whether the original Classic application kept any logs.

That's not what I was suggesting. Meant to be able to have it show up on the projects list page in BOINC, and preferably also have the final information for the user saved and accessible via the BOINC site for when the project pages will no longer be accessible.

---

I needed to rebuild a PC.

Well, this might not help you, but perhaps someone else who plans to rebuild his computer: you should have back up your data dirctory and restore it after the rebuild, than nothing would be lost.

---

I found the SETI Project link and added it to the pool of active projects on BOINC.

I added mine, but they stick on attaching. Have I got the right link?
http://setiathome.berkeley.edu/
If that's wrong, how do I detach? Boinc refuses to detach what is still attaching (which I tried as I thought maybe I should have used https).

You would need to persuade a member of the project staff to install a working scheduler program on the server designated as the scheduler.

Otherwise, you just get the message

29/12/2020 14:28:33 | SETI@home | Scheduler request failed: HTTP file not found

You would need to persuade a member of the project staff to install a working scheduler program on the server designated as the scheduler.

Otherwise, you just get the message

29/12/2020 14:28:33 | SETI@home | Scheduler request failed: HTTP file not found

All I'm interested in is running SETI if and when it restarts. I don't need anything while it's not running, I'm not concerned about credits. Will the address I attached to suddenly start working when they get going? If I need to use a different one, how do I removed the jammed attaching one?

We assume that the address will be the same, but there is no guarantee.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

We assume that the address will be the same, but there is no guarantee.

I was thinking it might be the https version, but I don't know how to stop my Boinc trying to join the http one. Until it's attached, I cannot detach.

Although since I'm getting "master file download succeeded", I assume it's still half alive and would still be there when they get going.

Is there a thread which will have a post when it starts? That way I can subscribe to it and be told when it's ready.

And will it ever restart? Or is it back end stuff forever more?

I'd expect it to be front page news, if and when it restarts.

Possibly preceded by some Beta news, because I'd expect they'd take the chance of writing a whole new application for whatever they want to do next.

Wellllllllll........

As you suggest the fact that your "new" computer doesn't exist in SETI@Home means it is not attached to SETI@Home, thus you should be safe in removing, manually, all references to SETI@Home from the control files (quite a few of them - someone else will come along and say exactly which ones to edit).

The place where the return of us to processing data for SETI@Home will be on the front page and in the "news" section of the forum.

Finally, the official line is that SETI@Home will return once the current round of analysis is completed. My guess is that this will not be using the previous set of applications for a number of reasons.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Wellllllllll........

As you suggest the fact that your "new" computer doesn't exist in SETI@Home means it is not attached to SETI@Home, thus you should be safe in removing, manually, all references to SETI@Home from the control files (quite a few of them - someone else will come along and say exactly which ones to edit).

The place where the return of us to processing data for SETI@Home will be on the front page and in the "news" section of the forum.

Finally, the official line is that SETI@Home will return once the current round of analysis is completed. My guess is that this will not be using the previous set of applications for a number of reasons.

I have 7 computers and 2 smartphones. I can't remember if any were attached to it years ago. But I guess it does no harm to delete everything, it's no worse than formatting a computer. My credits are on the server, not the computer.

I can't see a way to subscribe to an entire section of the forum, and that would probably result in a barrage of emails, so I'll just pop back and check whenever I remember, if I remember! No doubt SETI will be mentioned in another project forum by someone when the excitement starts.

Actually only 4 of your devices have contacted the servers this year (2020), two Android, and two Intel based Windows 10 PCs, so not a big task and fairly for you easy to work out which one is which. The next oldest contact was made in Jun 2018.

Just be careful when deleting everything as you may find you remove files that are needed for other projects to run under BOINC, and that would be "very undesirable" to say the least.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Actually only 4 of your devices have contacted the servers this year (2020), two Android, and two Intel based Windows 10 PCs, so not a big task and fairly for you easy to work out which one is which. The next oldest contact was made in Jun 2018.

Just be careful when deleting everything as you may find you remove files that are needed for other projects to run under BOINC, and that would be "very undesirable" to say the least.

That's very odd, I actually have 7 Windows 10 PCs all trying to attach, they retry every few hours as far as I can see, I assume the server isn't keeping a record of these failed attempts. I attached them all within the last month. The 2 you've seen were detached months ago, then those 2 and 5 more (re)attached recently.

Should I just delete the SETI folder under Program Data/Boinc/Projects? Or is there something else to be done?

I'll just leave them trying to attach just now anyway, I only need to intervene if the project address is different to http://setiathome.berkeley.edu (they're trying to attach with http, not https) when SETI restarts.

Well, that means none of your current group of 7 PCs have managed to attach - the last one of your devices to succeed was back in June (an Android device), your last Windows device was back in January 2020.
The best thing to do is to set them to "no new tasks" and "suspend" for SETI@Home.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Well, that means none of your current group of 7 PCs have managed to attach - the last one of your devices to succeed was back in June (an Android device), your last Windows device was back in January 2020.
The best thing to do is to set them to "no new tasks" and "suspend" for SETI@Home.

I'm confused, I thought they were not attaching because currently the server is not allowing it, since SETI is on hold. Are you saying they should have succeeded? What is the correct address to attach them to? Should I use https?

Ah.... Boinctasks doesn't let you detach from a still attaching project, but the Boinc manager does. I'll go through them all and remove it, then add properly when I know SETI is running. No sense having them wasting time pestering the server just now.

Except one of the Androids, which doesn't have a Boinc manager, it's only controlled by Boinctasks. Oh well.