While seti took a free weekend I decided to crunch for einstein in the mean time.

I've got there a diffrent CPID (Cross Project ID) even I used the same e-mail adress.

How will they be synchronized?

---

> I've got there a diffrent CPID (Cross Project ID) even I used the same e-mail
> adress.
>
> How will they be synchronized?

That should happen automatically as both projects communicate with your client (read Berkeley gets their servers back online).

---

Stewie: So, is there any tread left on the tires? Or at this point would it be like throwing a hot dog down a hallway?

Fox Sunday (US) at 9PM ET/PT

" ('cross-project identifier') is a unique identifier across multiple projects. Accounts with the same email address on different projects will have the same cross-project identifier (as long as at least one computer is attached to both accounts)."

So just sit back and wait and it will be fixed :)

---

There are four things that have to be true before the CPID shows the same at the external stats sites.

1) The email addresses must be the same for all projects including case. Foo@bar.com is not the same as foo@bar.com.

2) There must be a path from server to host to server that covers all project servers. The easiest way of doing this is to have one host connected to all projects.

3) The projects where the CPID is going to change must actually update through successful communications (in 4.19 and earlier, this required the download of work if work was requested). The client picks the CPID that it will keep from the new one and the existing one (if any). In 4.19 and earlier the client picked the numerically larger of the two which means the existing projects could change CPID. In 4.20 and later the client picks the CPID of the project with the oldest join date. This means that only the new project will change.

4) The stats XML must be updated, and the stats sites must download it.

---

BOINC WIKI

>
> 1) The email addresses must be the same for all projects including case.
> Foo@bar.com is not the same as foo@bar.com.
>

Foo@bar.com is converted to foo@bar.com, so case isn't a problem. ;)

> " ('cross-project identifier') is a unique identifier across multiple
> projects. Accounts with the same email address on different projects will have
> the same cross-project identifier (as long as at least one computer is
> attached to both accounts)."
>
> So just sit back and wait and it will be fixed :)
>
I have a similar, but not quite the same problem. Just before SETI went off the net I changed my email address (in preparation for upcoming loss of the email address I've been using). When SETI was offline I joined einstein, creating an account using the new email address (thinking that SETI already had changed over). When SETI came back up it turned out that the email change had not gone through -- instead it said 'pending verification'. No email for verification was coming so I changed the 'pending verification' to the new, desired email. Got the verification email, and activated.

The new account (Einstein) probably referred to another email than SETI when Einstein was created. Now, both SETI & EINSTEIN refer to the same email account, but both accounts still refer to different CPID. I have been up/downloading (mainly) seti WU's after both accounts were pointing to the same email, but they still refer to same CPID's.

And now the question: how long to wait before I am certain that the this will not resolve itself?


Murphy strikes again -- just checking at BOINCstats and lo and behold, they are synchronised! In short, the answer to my own question is say 4 days...

---

Pindakoe: it HAS resolved itself. Look at my stats site. (sorry, primary server is offline so see here. It shows you as having both seti and einstein credit on the same CPID.

The other issue is that there are multiple versions of the server-side software out there. There is an "internal" and an "external" representation of the CPID. The stats sites get the external representation. Older versions of the server (particularly the home.php file) show the internal representation whereas the new version shows the external one which is what you will see on the stats sites. I thought einstein was up to date but maybe they didn't update that particular file. I know seti@home is up to date.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

Toby,

thanks for the answer and extra detail -- I noted it after posting 1 minute after you (see the last mod time on my original post).

I guess I should have paid more attention to a very common response in this forum ---- be patient (the website will stand up, the dataserver will have WU's, your stats will sync etc).

---

> >
> > 1) The email addresses must be the same for all projects including case.
>
> > Foo@bar.com is not the same as foo@bar.com.
> >
>
> Foo@bar.com is converted to foo@bar.com, so case isn't a problem. ;)
>
It is not converted for lower case for hashing with the internal CPID. It is a problem.

---

BOINC WIKI

> It is not converted for lower case for hashing with the internal CPID. It is
> a problem.
>

Since all email-addresses is converted to lower-case before inserted into the BOINC database, it is not a problem.

Look at checkin_notes 14.06.2004 and 18.11.2004.

> > It is not converted for lower case for hashing with the internal CPID.
> It is
> > a problem.
> >
>
> Since all email-addresses is converted to lower-case before inserted into the
> BOINC database, it is not a problem.
>
> Look at checkin_notes 14.06.2004 and 18.11.2004.
>
>
Correct, however addresses already in the database may still have uppercase characters. Also some projects are slow to implement server-side changes. So in my opinion the reminder about using all lowercase email addresses is stil a good thing to include.

---

BOINC WIKI

BOINCing since 2002/12/8