Thank you Willy for your reply, but surely you must consider that it is a BAM. I tell you way:
1. In four weeks after checking each projects , their CPID was the same as BAM, yet it never merged. I spoke to about this problem to all projects and all I got as a reply that yes, we do export all stats therefore it is a BAM problem, confirmed by a BOINC Committee member.
After the fourth Sunday update nothing changed so I was desperate and reversed the problem by changing my email address back to what is was in the first place, that is now redundant and low and behold the missing projects appeared in my stats.
This proves to me that it is a BAM problem supported by many users that have expressed their opinion and one should never change their email address and PW for BAM does not know how to fix the change over, for it is not in the capability to fix for it is a BAM PROBLEM AS STATED BY ALL.
Hi Cruncher Pete, I'm glad you were able to revert your email which is about your only option in your situation.
I only caught onto your plight the other day and I needed to check some facts before posting so my apologies for being late.
The following is based on my understanding of how BOINC, BOINCstats, BAM and CPID interact.
The reason you have an issue from changing your email address is that in doing so your CPID will change and this risks a split CPID situation, there is no mechanism built into BOINC to merge CPID's, only to propagate them, I guess the original developers did not foresee the need.
In defense of BAM (BOINC Account Manager), this is a service that helps to minimize the pain of managing multiple hosts and projects by allowing you to make changes to the projects and your hosts in a central location and very helpful it is too. There are of course multiple BAM applications available but the BAM built into BOINCstats is my BAM of choice and the one I am referring to here.
However just because BAM is available through the same web interface as BOINCstats you should not assume that it has any influence on the way your stats are collated, BAM and BOINCstats are basically two unconnected applications. Yours stats as reported by the projects you crunch for must remain pure and unadulterated, the only exception I know of is that when projects are retired BAM on BOINCstats will ensure that your stats, within BOINCstats only, will remain tallied even if your CPID changes, there is however a condition that the project must have been included on your BAM account before the project is retired, whilst projects are considered live its hands off as far as BAM tinkering with stats is concerned.
In your case you attempted to change your email which resulted in a split CPID, the reason being that there are a number of "live" projects you crunch for that are currently in limbo, some like GoofyxGrid are not contactable and so you would be unable to update your email address, others like Seti@Home have not exported stats since 16th June 2020 but have not yet been retired and so even if you change your email the stats will not be corrected. The fact that you can see the new CPID within a project does not guarantee the stats until the project has exported your stats with the your new CPID. In addition you have quite a number of retired projects that were not carried over by BAM, presumable because those projects were not included in your BAM account before they were retired.
To shed some light on how CPID operates in the context of the user CPID; Whenever you first sign up for a new project that project assigns you a new CPID, in fact it assigns two CPID's known as internal and external. The internal CPID is never shared publicly, you shouldn't even be able to see it within your project account, the CPID listed there is your external CPID. The difference between the internal and external CPID is that to generate the external CPID the project hashes the internal CPID with your email address and that is why when you change your email address your external CPID changes even when the internal CPID remains the same.
There are four key elements at play which you can see within the <project> section of client_state.xml, they are <email_hash>, <cross_project_id>, <external_cpid> and <cpid_time>. Here <cross_project_id> refers to the internal CPID.
When one of your hosts requests a project update, note you don't need to be actively crunching the project a manual update request will do, your host will check all the projects it knows about in client_state.xml that have the same email_hash and look for the lowest/oldest corresponding cpid_time, it will then send the corresponding cross_project_id and cpid_time to the project server. The project server then checks if the host supplied cpid_time is before its own cpid_time and if so it will update its internal CPID to match that sent by your host, the project will then rehash its external CPID, which because it is derived from your email address and the internal CPID will become the same as all your other projects. This mechanism ensures that all your live and healthy projects with the same email hash have the same internal and external CPID's. This is why Willy recommends you keep at least one host with all your projects registered as that host will be the ultimate arbitrator of the internal CPID. The external CPID should always revert to the oldest known CPID for an email hash.
In short you can change your email address but it will only work seamlessly for live projects that are online and are actively exporting stats, it will not work for projects in a state of limbo or that have been retired unless the retired sites where previously registered to your BAM account. QED register all your projects in your BAM account whilst they are live and never delete them from BAM.
CPID for hosts works in much the same way. An explanation of CPID can be found on the BOINC site
here.
BOINCstats and all other stats sites only know about the external CPID and so they can only use that to group your project stats, consequently a split CPID will result in two separate stats listings for the same person or as in your case there appears to be six such listings as pointed out by Willy
here, this is down to changes in your CPID over time and not the fault of BAM or BOINCstats.
Reverting to a previous email as you have done should give you back the previous external CPID provided that the internal CPID has not changed in the meantime.
I hope this sheds some light and may help others in a similar situation decide what is the best course of action for them.