Hi, didn't see this addressed anywhere else. I have 858 WUs pending validation. Seems like a lot. Am I being too impatient?

---

They don't compare work units from different users on CPDN, so they never get "validated".

They don't compare work units from different users on CPDN, so they never get "validated".

Or in other words, completed tasks are always labelled, "pending" with CPDN because the BOINC server software doesn't have an option to say that they don't need validating.There are two or three other projects like this but I can't remember which they are off the top of my head.

Collatz
GPUGRID
Moo! Wrapper
World Community Grid (compares if you return errors)
Rosetta

None of the above compare work units from different users and yet none of the tasks are listed as 'pending validation'

So I think the BOINC software does have such an option.

CPDN must be doing something wrong.

There's several BOINC options that cpdn just ignores.

Validation and Pending credit are two of them.

... however, there is quality control -- it is done mathematically.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Primaboinca has a quorum of 1, hence no comparison, but doesn't show pending tasks. I'm not sure how their project admins do it differently from the project admins here. Perhaps they could chat, if they are uncertain, or if we got credits it wouldn't really be that big a deal...

---

or if we got credits it wouldn't really be that big a deal...

Once things are fully sorted, credit will be granted again. There was an attempt to run the credit script last week but it didn't complete. Andy has started to go through the logs looking for the problem. I think he said it got to about the 7 hour point before it failed.

Primaboinca has a quorum of 1, hence no comparison, but doesn't show pending tasks. I'm not sure how their project admins do it differently from the project admins here. Perhaps they could chat,

Based on what others have said, it may be that CPDN are just leaving everything they don't have to fiddle with on the default settings if they don't interfere with the business. Changing this would produce a significant decrease in traffic on the forums. :)

From what I'm seeing, CPDN is not waiting for the same result from multiple machines to compare the results before issuing the boinc credit.

I have 3 jobs that are listed as successfully completed on Apr 22, 2018 and another 16 jobs that have successfully completed since Jul 20, 2018 that are still showing 0 credit.

I did see a reference before on the message boards that someone at cpdn runs a script that calculates the credit - I don't know what the process is.

Given the current state of the CPDN credit issuing, I lowered my boinc project priority setting. I hope that CPDN does NOT go the way of QMC or some of the other projects that went extinct.

William

---

or if we got credits it wouldn't really be that big a deal...

Once things are fully sorted, credit will be granted again. There was an attempt to run the credit script last week but it didn't complete. Andy has started to go through the logs looking for the problem. I think he said it got to about the 7 hour point before it failed.

Maybe it should be run more often so it doesn't take so long. *GASP*

Maybe it should be run more often so it doesn't take so long. *GASP*

Don't know if this was the old script which took over 24 hours to run or the new one which is much quicker.Before the database corruption problem scuppered everything, Andy was working on a script that would work on changes since last run rather than adding everything up since the year dot. If the new script, the plan is it should run daily once fully debugged.

There are so many people posting about this that haven't a clue, that it must be time to explain yet again.


cpdn DOES NOT USE the standard BOINC credit system.

Credit here is based on the trickle_up files that get returned several times during the creation of a climate model.

Each different program that is used, uses different amounts of computer resources/time.
Models also take different amounts of time because they cover different amounts of planet area, with different resolutions for the high-res part.

A value for each of these variables is stored in a table.

ALL of the trickle_up files are stored in a data base.

******************

Each time the credits are calculated, it is done from the beginning, for each person, each person's models, each person's computers, each person's team.

So the time taken to do this gets longer each time.
And longer ...
And longer ...
And longer ...
And longer ...

And probably a lot longer than that by now.

And for those that haven't been paying attention, the script has run each day for the past week, and each time it has, BOINCstats has imported it.

Unfortunately, the SQL script isn't working correctly for some reason, which is what Andy is currently trying to work out.

If the script is running, why have I received no credit for the trickles my host uploaded on the 15th and 28th August? And if the script always starts from the beginning, why hasn't the credit I lost after the crash been restored? This flat-line is shown both on the CPDN website and on BOINCstats. Are you saying the script is running, but not doing anything useful?

Are you saying the script is running, but not doing anything useful?

Yes.

Thanks for the responses to Les and Dave.
Also, thanks to Andy working behind the scene.

---

Zooniverse Old Weather transcriber
and
Old Weather BOINC team member.