Since NOBODY announced it. Pirates@Home looks like it has finished since the pages no longer work from the site and the announcement showing retired projects contains the name of the PIRATES project.

So IF you are wondering, PIRATES@HOME is RETIRED.....

@Willy:

You will still make the last DAILY update on pirates, right? :wink:

Yep!

Great

Sorry to be a bother, willy, but what was the last totals for users, hosts, teams, countries and especially credit for pirates?

I'll include these numbers in the Project Stats.

They're there.

Thanks

Have the Pirates stats been subtracted now? They don't seem to show up in the user stats anymore. It seems odd to remove credit for a project just because it's retired... people earned the credit even if the project is no longer active.

Pirates has Re-opened!!!

New URL: http://pirates.spy-hill.net/

Sending and receiving WUs successfully.

Please reactivate statscollection

Already did.

How slow am I..

I think this may have happened cause the users got a new cpid an were not able to adjust it with the one at pirates.

We had the same probs in our stats.

@BOINCstats crew: What do you think? This will happen with XtremLab, too?
We will surely have this problem in our stats, but there it's only for one team so I can adjust it manually.
Do you have planned any way to remain the connection between the different projects for one account even if the users get a new cpid?

When a project retires, and a users' CPID changed, the connection with the retired project account will be lost, and the credits will not be included in the combined account.

I think there are ways to prevent this, but it will be difficult. It may be possible to match a CPID from the XML file (of a living project) against the existing CPID in the stats DB. If they differ, update the 'old' CPID in all retired projects. While this is doable, it may put too much strain on the server (you must have read about the struggles I have to keep up with the growing userbase).

Another option is using an AMS (link). Once a project is included in the AMS-account, the AMS user could update a retired project him/her self when the CPID changes. But this will only work if the AMS works together with BOINCstats (some people will know why that smiley is here).

BUT: with the way CPID's are handled now (oldest CPID always wins instead of highest CPID) this shouldn't be a problem at all. Once established, the CPID will remain the same forever. A new project could have a different CPID, but will line up with the older one. The catch: you need to use a v5 client or higher.

Well, I was wondering, if now that you've released BAM, if BAM detected a second CPID, if it could not either link them (for stats purposes), or effect the necessary changes (well in the future, not so much retro-active) that would prevent this sorta thing from happening... But then if BOINC itself has provided the solution, it wouldn't really matter either way I s'pose...