Greetings,

I installed SETI yesterday, have completed a few dozen Tasks, but have a long list of Ready to Report tasks that haven't reported.
Going to the Tasks panel, I have 25 tasks ready to report.
Under the Advanced Tab, I hit the Do Network Communication, to try and send the completed tasks - but nothing happens.
Under the Transfers Tab there is nothing pending, and no options to select.
I checked all settings, have been running with Network Activity Always Available on for over an hour, but nothing has gone through that I can see.
Checking my SETI profile, no work / credit is shown as done at this time.
It's been close to 24 hours since my first task was completed.

What am I missing? Should completed tasks report right away? I recall under the old SETI they would submit completed tasks before new ones where received.

Can we force send our completed tasks to ensure they get submitted?
What is the expected wait time for tasks to be submitted and updated from the Ready to Report Status to Reported?

Thanks in advance.

---

Tasks are reported in the following conditions:

1) 24 hours before deadline
2) Connect Every X before deadline.
3) 24 hours after task completion.
4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task.
5) On a trickle up message (CPDN only, I believe).
6) On a trickle down request.
7) On a server scheduled connection. Used, but I am not certain by which project.
8) On a request for new work.
9) When the user pushes the update button.
10) On a request from an account manager.
11) Report immediately every task, if "No new Task" is set. (6.12.33+)

Thank you so much!
The Update button seemed to do the trick.
I didn't see it do anything at first, but after I went back to look at the BOINC manager later, all the Ready to Report Tasks were gone.
Would be nice to see something like Tasks Reported, similar to uTorrent when you see downloads completed.

Regards,

Robert

---

And now the explanation as to why it's done like this, copied from where I wrote this yesterday at Einstein:

BOINC uses two methods to get the information back from your computer.

One is an upload, which is done at the end of the task and is merely moving data from your computer's hard drive to a hard drive on a server at the project.

The other is to report the finished work. This uses the database which causes overhead, where the server uses CPU and memory in order to will your request. Now the overhead is about the same when BOINC reports one task or ten tasks. So projects prefer that clients report multiple tasks at the same time.

That's what is happening here. Your task has uploaded, but it's waiting to be reported. In the mean time another task has started, perhaps it gets finished in time before the previous task is reported and then it can be reported at the same time.

P.S: TUG (The Unnamed Guy) missed the last two conditions:
12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0)
13) When minimum work buffer is reached. (BOINC 7.0)

---

Thank you so much!
The Update button seemed to do the trick.
I didn't see it do anything at first, but after I went back to look at the BOINC manager later, all the Ready to Report Tasks were gone.
Would be nice to see something like Tasks Reported, similar to uTorrent when you see downloads completed.

Regards,

Robert

The point was supposed to be that you let BOINC do it automatically. There's no need to force it on your own. Doing this during times of high network traffic can cause additional stress on the servers and essentially DDoS other users from being able to contact the servers.

And now the explanation as to why it's done like this, copied from where I wrote this yesterday at Einstein:

BOINC uses two methods to get the information back from your computer.

One is an upload, which is done at the end of the task and is merely moving data from your computer's hard drive to a hard drive on a server at the project.

The other is to report the finished work. This uses the database which causes overhead, where the server uses CPU and memory in order to will your request. Now the overhead is about the same when BOINC reports one task or ten tasks. So projects prefer that clients report multiple tasks at the same time.

That's what is happening here. Your task has uploaded, but it's waiting to be reported. In the mean time another task has started, perhaps it gets finished in time before the previous task is reported and then it can be reported at the same time.

P.S: TUG (The Unnamed Guy) missed the last two conditions:
12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0)
13) When minimum work buffer is reached. (BOINC 7.0)

Your #13 possibly triggers a work fetch, but not always from the project that has work to report.

---

BOINC WIKI

Your #13 possibly triggers a work fetch, but not always from the project that has work to report.

Seeing how the OP runs only Seti, I don't think it matters much. In this case, at least. ;-)

---