When I check clients, they often have completed workunits sitting there that have not been uploaded. This is during periods when the servers are all showing OK status. They seem to upload eventually, just not necessarily when they are first completed. Is there a setting I'm missing, or anyone else seeing this?

---

The server status page hasn't been updating frequently, Matt has turned off the updates because it slows down the DB work he's been doing. Some items are updated some aren't.

You think thats fun, check this out HUH

6 wu's and 5 in, no credits issued, and wha? :)

---

The state of the workunits to which you refer are in the validate state of 'Checked, but no consensus yet' I don't know why they've not been validated yet but once validated the state will change to valid and credit will be granted..as far as I know (if I'm wrong someone will correct me I'm sure)

---

Validate state Checked, but no consensus yet

means the validator hasn't found any group of answers that matches strongly enough to have a "Canonical result", so the transitioners have resent it to more computers

The report of work completed will be made at the earliest of:
A new work fetch.
24 hours before the deadline of a result (or immediately if the result finishes after 24 hours before the deadline).
Manual update by the user.
Contact for a trickle. (CPDN only so far).
Connect every X days after a result is completed.
This is done because remote procedure calls are moderately expensive for the server, and it is good to reduce the server load by doing several things at once.

---

And the beat goes on
Sonny and Cher

BOINC Wiki

mmciastro,

Thanks for that, it did explain the issue very well and understandably. Could you answer what would happen if the maximum success results(5) or maximum total(10)were returned and still no group of answers matched strongly enough to have a "Canonical result"?

And what is considered 'close enough'?

Not trying to be difficult here I'm just curious!

[edited to correct typo's]

---

Thanks for that, it did explain the issue very well and understandably. Could you answer what would happen if the maximum success results(5) were returned and still no group of answers matched strongly enough to have a "Canonical result"?

If with 6 "success"-result Validator still fails validation with "no consensus yet", the Validator will mark wu as errored-out and give up, this also means no-one will get any credit.

If 6 results is reported as errors or 11 total results, the Transitioner will error-out the wu.

mmciastro,

Thanks for that, it did explain the issue very well and understandably. Could you answer what would happen if the maximum success results(5) or maximum total(10)were returned and still no group of answers matched strongly enough to have a "Canonical result"?

And what is considered 'close enough'?

Not trying to be difficult here I'm just curious!

[edited to correct typo's]

See Inglesides answer, he's smarter than I. I don't know how they determine "strongly" versus "weakly similar" versus NO match.

Andy, many of us are here just for the purpose of helping others.

Ask away

tony

---

When I check clients, they often have completed workunits sitting there that have not been uploaded. This is during periods when the servers are all showing OK status. They seem to upload eventually, just not necessarily when they are first completed. Is there a setting I'm missing, or anyone else seeing this?

This thread got sidetracked onto something completely different from what was being asked.

K&L, my guess is you aren't really talking about "uploading" but are talking about "reporting". Unless you are on dialup, as soon as your host completes a result, it should upload. But it will then go into "ready to report" state, and will only be _reported_ "eventually" (or when you manually hit "update" on the project).

If this is what you're asking, then yes, this is normal behavior. If you really have an upload problem, we'll need a lot more info.

mmciastro & ingleside,

Thanks for your answers guys. I've only been cruching BOINC since the news that classic was being shut down so I still have a lot to learn. Although I was crunching classic for a while !!!

With the rapid and helpful answers that you're giving it won't be toooooo long (I hope) before I to will be able to help other 'newbies'


Cheers guys,

May all your cruching days be good ones!!

---

The report of work completed will be made at the earliest of:
A new work fetch.
24 hours before the deadline of a result (or immediately if the result finishes after 24 hours before the deadline).
Manual update by the user.
Contact for a trickle. (CPDN only so far).
Connect every X days after a result is completed.
This is done because remote procedure calls are moderately expensive for the server, and it is good to reduce the server load by doing several things at once.

If you are using the trux Optimized BOINC client, you can configure it to report results immediately after the upload, instead of having to wait for the scheduler to decide to report.

---

Thanks all for the interesting and informative reponses! I didn't realize that delayed reporting of completed units was normal behavior. Have started using the trux BOINC clients.....nice! Appreciate all the help.

---