Team stats
 

If a user joins team T1, his CPU credit is transferred to T1.
If the user later decides to join team T2, should

a) Should the users past credit be subtracted from T1 and added to T2?
b) Should the users past credit be added to both T1 and T2?
c) Should no past credit be given to T2 - only future credit?

Does it matter how long he has been a part of the team?

I think SETI uses option c, and I guess Primenet does too since your individual userid disappears when you join T1. However, computer names can still identify the user's work.

If we do new server stats, should we choose a different option?

The best would be that any work done while not part of a team would follow the user and all work done on a team would stay with that team. But I think this would be very complicated.

SETI only claims to do c) but it actually does a).

outlnder solution is perhaps the most elegant but possibly hard to implement. Essentially all the work you did on T1 stays with T1 whereas all the work you did before joining T1 travels with you.

But this may create a problem with the way primenet is set up right now as the userID disappears. Worse, the same userID can be used again and new work be done with that userID again and later merged into T1 or some other team.

b) is the worst in my opinion and should not be implemented. a) is probably better than c) but that's arguable.

If we make a new server I think the first step would be to have proper usernames and teams. The current faux teams could probably remain the way they are as just usernames but people could have a choice to create extra usernames and pool the existing team name like TPR and the new individual usernames into a team.

But right now the merge is broken and no cleared or assigned exponents are being transferred.
:shock: :sad:
George :help:

[QUOTE]If we do new server stats, should we choose a different option?[/QUOTE]

:w00t: :w00t: :w00t:

There is something moving!

[QUOTE]If the user later decides to join team T2, should

a) Should the users past credit be subtracted from T1 and added to T2?
b) Should the users past credit be added to both T1 and T2?
c) Should no past credit be given to T2 - only future credit?
[/QUOTE]

If the user has his own username and password, couldn't be up to him to decide whether giving credit to T1 or T2?

Should it be too hard to implement, I vote for c), having the chance to query user's own complete statistics.

This could be implemented if a "user" box joins "team name" and "computer name" boxes.

Luigi :whistle:

I vote letter a). If we are going to change the way we do stats, we should rebuild it from the ground up. Preferably for teams this would involve a team name with usernames inside tracked individually. Then if a user decides to go to another team or separate their PCs and create their own independent account, their past credit travels with them. Of course this will require a server rebuild also...

What happens if a team disbands, what happens to the credit ?
Back to the individual, to the team the person is currently with ?

Or is it just lost ?

If reassigning credit is too complicated how about the team credit and name is frozen ( so no new team takes the name and gets the credit ).

More questions:

1) What was the great FaH stats debacle that I read about in forums?

2) If seti currently does (c) don't teams get upset when their cpu totals decrease?

3) Is it fair that a users past cpu years are added to the team when he joins? This encourages advancing by recruiting new members rather than producing results.

4) I can see why seti didn't do (a) as it treats users past results differently: a never-teamed new member gets his past added, but a previously teamed member does not.

I'm getting a headache......

P.S. Don't read into this thread that a new server is on its way. I've gotten some emails asking to switch teams and want to know the best way to handle it.

[QUOTE][i]Originally posted by Prime95 [/i]
[B]Don't read into this thread that a new server is on its way.[/B][/QUOTE]

Darn. Had my hopes up there for a second... :sad:

And here I read that a new server was in the works under wraps as a big x-mas gift to the GIMPS community ...

I guess there could be another option, the work goes to where ever it was produced.

A non-teamed person would have their individual stats.

When he joined a team, the individual years would remain under that user name in the stats.

Any work produced as a member of a team would stay with that team.

If the person moved to a second team, only the work produced for that team would be credited.

Potentionally, a person could have several places in the stats, one for each team and one for his individual production.

This would tend to stop or slow team hopping and the individual could always go back to not being on a team and still have that production he did as an individual.

Make any sense??

It does, outInder :)

+1

Luigi