About 3-4 months ago, my systems, all of which have 24/7 internet connectivity, stopped auto-uploading the results of finished jobs (all projects, not just SETI). I have to "UPDATE" daily to upload these results. Was a change made in Boinc about that time? I have preferences set to always have connectivity. Any suggestions?

Pete

---

Is it a problem uploading, or reporting? They are two different things.
Uploading is returning the work you have done, and if there are problems there you use the retry button.
Reporting work is where your computer tells the project about what work has done (and previously uploaded), and if there are problems there you use the update button.
Did you upgrade your BOINC client 3-4 months ago, because the way the v7 manager handles work caching & reporting is completely opposite to the way v6 handled it.

---

Grant
Darwin NT

Probably a stupid question that I have wondered about since Boinc came to be, but "Uploading is returning the work you have done, and if there are problems there you use the retry button.
Reporting work is where your computer tells the project about what work has done (and previously uploaded), and if there are problems there you use the update button.", why are they separate?
It seems to me that once the project has been told about the work that has been done, they know the results.

---

Grant,
I don't remember when I last upgraded BOINC, but probably shortly after 7.0.28 became available. I see no "RETRY" option under any menu heading or on the "Projects" tab, only update. Jobs which have been completed (100% Progress) do not disappear as they used to; I have to for each project select the project and hit the "UPDATE" button to send the results back to SETI or the other projects (I'm running Rosetta and Milky Way as well as SETI). I never had to do this before, the jobs would both come and go automatically.

I was unaware that uploading the results was considered a different action than telling SETI that the particular data set had finished.

Any further clarification on the latter point is welcome, but is secondary to getting the jobs to come and go automatically, if possible.

Thanks,
Pete

---

Where are you setting your preferences, on the web page or locally on your machine?

Reporting work is where your computer tells the project about what work has done (and previously uploaded), and if there are problems there you use the update button.", why are they separate?

To reduce the load on the servers. Reporting each result as it is uploaded would add a massive amount of load on an already struggling system.

It seems to me that once the project has been told about the work that has been done, they know the results.

They do. But uploading the result doesn't tell the project that the work as been done, all you're doing is uploading it.

---

Grant
Darwin NT

I see no "RETRY" option under any menu heading or on the "Projects" tab, only update.

It's only on the Transfers tab as it relates to uploads & downloads.

Jobs which have been completed (100% Progress) do not disappear as they used to; I have to for each project select the project and hit the "UPDATE" button to send the results back to SETI or the other projects (I'm running Rosetta and Milky Way as well as SETI). I never had to do this before, the jobs would both come and go automatically.

Reporting work done varies depending on your cache settings, work share settings, deadlines of work done, how many hours a day you allow work, how many hours a day you have interet access allowed, how many hours a day you are actually processing work & half a dozen other factors.


I only run Seti, my compuiters run 24/7, i have Seti running all the time regardless of what else the systems are doing & i run the v6 client.
I do all of my settings on the web, not on the local computer.

Your account, When and how BOINC uses your computer, Network usage,

Maintain enough work to keep busy for at least x days
...and up to an additional y days.

Running v6 the settings i have are x=0.2 & y=6 for a 6 day cache (if Seti didn't have the per machine limits). Running v7 you would have to have x=6 & y=0.2 to get the same result. The values are reversed between the 2 versions.

---

Grant
Darwin NT