I am not quite sure I have fully understood the concept of credits. At the "results"-page there are columns for claimed and granted credit. After a job is done, there are credits claimed but not granted. Until now I thought that after a while the credits are then granted until all claimed credits are granted.
However at some finished jobs I now have more granted credits than claimed ones. Why is that? What are granted and claimed credits actually?

I am not quite sure I have fully understood the concept of credits. At the "results"-page there are columns for claimed and granted credit. After a job is done, there are credits claimed but not granted. Until now I thought that after a while the credits are then granted until all claimed credits are granted.
However at some finished jobs I now have more granted credits than claimed ones. Why is that? What are granted and claimed credits actually?

Okay I will start this but I am by no means an expert...claimed credits means that is what your particular pc is asking for. This is based on Boinc itself and how it crunches the unit. Granted credits are the credits you actually receive for crunching the unit. In some cases this will be higher than the claimed and in some cases lower than the claimed. If you go to each workunit, where credit has been granted, you will see a line that says "canonical result", this is how the Project determines if your crunching was accurate and how much credit you are going to get. Some projects require 2 or more people to crunch each individual workunit, some only one. In those projects that require more than 1 person to crunch a unit, no credit is granted until they both, or another pc, returns the unit. Another pc would get the unit if one of the original pc's did not return it fully crunched for some reason.
For instance this unit of yours https://boinc.bakerlab.org/rosetta/workunit.php?wuid=196735290 the first pc did not return the unit, so you got it to crunch.
Welcome to the world of crunching!!

---

The granted credit is based on the average processing power that those before you have taken to do models in the same batch (and same protein within a batch). This way eveyone gets the same credit, regardless of what claims they may make. If they submit an inflated credit claim, it goes in to the average and actually helps the next people to report, not the one that made the claim.

Normally, Rosetta grants credit right as the task is confirmed. The past couple of days I've noticed the process that completes this task seems to be a bit behind some times. So you will see "pending" for the granted credit for a period of time until that task catches up.

So, you're not waiting for a quarum, and not waiting for an entire batch of work to report completed. Just for a task to catch up on it's queue of work.

---

Rosetta Moderator: Mod.Sense

Normally, Rosetta grants credit right as the task is confirmed. The past couple of days I've noticed the process that completes this task seems to be a bit behind some times. So you will see "pending" for the granted credit for a period of time until that task catches up.

How long is that period, usually? I've only been using the client for about 2 days, but I've got 10 crunched units in a "Pending" state.

Yes, typo, you picked the perfect time to join :) These past 2 days or so the servers have been overloaded and are behind in assimilating the recent results. This is delaying the credits being actually granted. They have now taken steps so that the tasks that are overloading the server are not issued as frequently, but it will take some time to process through the backlog. You WILL GET CREDIT!

---

Rosetta Moderator: Mod.Sense

You WILL GET CREDIT!

Heh no rush, I'm just curious, is all. :)

I have a successful work unit that received only a very small credit (1.07 compared to requested 49.08) for a standard amount of work (10,007 CPU sec)... All others credits have been for more than requested. ...any explanation for this? Thanks, John

364338580 332912772 10 Sep 2010 7:31:23 UTC 10 Sep 2010 14:28:27 UTC Over Success Done 10,007.10 49.08 1.07

---

No suggestions on why the discrepancy between requested and granted credit?? J

I have a successful work unit that received only a very small credit (1.07 compared to requested 49.08) for a standard amount of work (10,007 CPU sec)... All others credits have been for more than requested. ...any explanation for this? Thanks, John

364338580 332912772 10 Sep 2010 7:31:23 UTC 10 Sep 2010 14:28:27 UTC Over Success Done 10,007.10 49.08 1.07

---

I sent a note to the Project Team describing your situation. I call it the double header problem. Looking at the completed task, it has two sets of headers describing how many decoys were completed. This is not normal. Fortunately it occurs only very rarely. The net result seems to always be that the task is only granted credit for what is shown in the last header section.

Nothing on your end to change. It looks like some of your tasks are started and restarted several times, if you could offer any details on what was happening during that time that may prove helpful to tracking down the problem. Is this machine rebooted frequently? Is it hibernating? Are you running multiple projects on the machine? What is your settings for keep tasks in memory?

---

Rosetta Moderator: Mod.Sense

Thanks for looking into this, J

I sent a note to the Project Team describing your situation. I call it the double header problem. Looking at the completed task, it has two sets of headers describing how many decoys were completed. This is not normal. Fortunately it occurs only very rarely. The net result seems to always be that the task is only granted credit for what is shown in the last header section.

Nothing on your end to change. It looks like some of your tasks are started and restarted several times, if you could offer any details on what was happening during that time that may prove helpful to tracking down the problem. Is this machine rebooted frequently? Is it hibernating? Are you running multiple projects on the machine? What is your settings for keep tasks in memory?

---

The Boinc process is running 100% of the time on a new LINUX box that I built... It is one of the ways I test most the new system issues. I have only rebooted it twice and it is set not to hibernate... Memory (2 gig) use is 50% when 'in use' and 90% when 'idle.'

I sent a note to the Project Team describing your situation. I call it the double header problem. Looking at the completed task, it has two sets of headers describing how many decoys were completed. This is not normal. Fortunately it occurs only very rarely. The net result seems to always be that the task is only granted credit for what is shown in the last header section.

Nothing on your end to change. It looks like some of your tasks are started and restarted several times, if you could offer any details on what was happening during that time that may prove helpful to tracking down the problem. Is this machine rebooted frequently? Is it hibernating? Are you running multiple projects on the machine? What is your settings for keep tasks in memory?

---