Hello,
I\'m the founder of BroadbandReports.com Team Starfire CPDN.
On 01/30/09 our total team credit was at 4,336,520.
On 02/02/2009 it dropped to 3,802,140.
Today it\'s at 3,802,140.
I\'d like to know why it dropped from the 4mils down to the 3mils.
Any help would be appreciated.
Thanks,
Dan

Unlike other projects, which use the BOINC generated credits, this project uses trickle x model value *, and the totals are all recalculated daily.
Because of this, team totals aren\'t permanent, as they\'re calculated for the members at the time the credits program is run.
So, if a person leaves a team, within 24 hours their credits will leave with them.

So your team has just lost a member who had 534,380 credits.


* This value varies with the model, from 72 for a hadam3, to 311 for a hadcm3.

---

Backups: Here

Unlike other projects, which use the BOINC generated credits, this project uses trickle x model value *, and the totals are all recalculated daily.
Because of this, team totals aren\'t permanent, as they\'re calculated for the members at the time the credits program is run.
So, if a person leaves a team, within 24 hours their credits will leave with them.

So your team has just lost a member who had 534,380 credits.


* This value varies with the model, from 72 for a hadam3, to 311 for a hadcm3.

Les,
Thanks for your explanation.
Your help is appreciated.
Dan

I am trying to understand what you are saying but still don\'t understand why all the credit earned with a team can not stay with the team it was earned for. If a work unit model was not finished the future earning of that model should go to the members new team.

Years go with the Classic SETI project one big problem for a number of teams who had good completion going on between them was the ability to go out side the team and bring in friends from other project to help them out as they has a great RAC and credit and use it for their freinds team unitl they caught up again with the other team.Then the nemmber would just sign-out taking his credit\'s and go back to his original team until needed again. So in a few days time a team leadership in Government Agencies listing of teams could change just by new recruited temporary members just so a team can be listed as being #1.

In our case the US Navy vs the U.S.Air force team. The months of March and April were selected by the US Navy as the POTM (Project of the Month) for the CPDN project. It took us 23 days of extra crunching to finally overcome about 1.1 million cobblestones. We were leading over 50,000 cobblestone when a new member joined the air Force team carrying about 1.5 million cobblestones which passed on to the Air Force teams credit. That is not fair competition allowing new members to a team to bring earned credits on one team and bringing them to there new team.

Should be that all projects in the BOINC projects have the same rules for active members changing teams.

---

This project started in a similar way to SETI; on it\'s own. The credit here was, (and still is), based on a certain amount for each trickle returned from a model.

When BOINC started up a year or so after this project went public, it was decided to change things to use the BOINC framework.
But BOINC grants credit based on a completed workunit. And it soon became apparent (back in the second half of 2004), that some models were being granted credit by BOINC on completion, in addition to that which had already been granted by the trickles. And people soon started complaining about this extra credit that others got when they didn\'t. It was nicknamed the random credit lottery.

So, to get around this, Carl, the project\'s chief software architect at the time, came up with the idea of running a script to re-calculate everyone\'s credit each time a trickle was returned. Over the years, the amount of data has grown to terabytes, and this re-calc was first reduced to once every 4 hours, and then to once daily.

One of the two anomalies is that Pending credit, (created by the BOINC part of the server), sometimes doesn\'t agree with Granted credit in various places.

And the 2nd is that the historical record of members of a team isn\'t stored; only the current members are known at the time the re-calc program is run each day. So only credit for current members is posted for team totals.

The core product of this project is climate models, not credit. So people just have to get used to the idea

Thanks for the update...much clearer now.

---