Since the ONLY "feedback" from a client's machine is the run time for each task, and NO credit information is fed back (either the user, task or client) the only place for such a thing to happen is on the server.
Juan's case is most definitely a strange one, and appears to be an isolated one.

[Edit] - What is very strange is that Juan's computer history only goes back to January this year, and yet his account goes back to 2007. For most users one can see a user's entire computer history by clicking on the "show all" computers option - and that does nothing when looking at Juan's account....

when submitting a WU, that might be the only data exchanged, but that's certainly not the only data exchanged between the host and server. when you make a connection to the server it sends a bunch of info about the host. how else would the server know things about the host like what CPU it has, what it's computational preferences are, what and how many GPUs are there, what GPU drivers it's using, etc.

you can only see juans history from this year because he got a new host ID. you are seing stats from that new host ID only. it looks like his old host got deleted somehow because it doesnt show up.

IIRC, TBar had a similar problem with incorrect host stats. but in his case he saw a random reduction of points from his host, which also did not affect his user stats.

see here: Anyone Else Lose Close To 1000000 SETI Points on Monday Nov 5th?

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

I remember that thread of TBar's. Something quirky happened to him also. You can see something happened to Juan's original host also when its credit per day went negative 271 million on 30 January from the BoincStats History graph for that host.
https://boincstats.com/en/stats/-1/host/detail/331253682/lastDays

[Edit] So kids, the lesson to be learned here is don't install the repository version of BOINC on top of TBar's version of BOINC or strange and wonderful things can happen.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I have just a simple explanation: The servers like me.

---

FACT - there is NO transfer of credit data from the client "sitting on your desk" back to the servers, as doing so would expose the whole credit system to the sort of abuse that brought the old credit system into serious discredit. This is part of the "security" that was put in when BOINC was implemented all those years back.
In Juan's case, and probably a few more, something went astray in the server that looks after user accounts.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Does inflating your GPU count get you more work for your GPU'S ?

---

Does inflating your GPU count get you more work for your GPU'S ?

Yes.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Does inflating your GPU count get you more work for your GPU'S ?

It also provides a way to "automate" bunkering up (storing more gpu tasks) for the Tuesday maintenance outage.
When the Seti servers are working right, you can get all the gpu tasks you want for processing. All you have to do is set the "extra" days processing to something like 0.1 and the client will keep connecting with the server often enough that you won't run out of tasks. If everything is "normal".

Mostly the issue of running out of gpu tasks is an issue for machines with the faster gpu cards. For slower cards, they don't run out of gpu tasks during the Tuesday outage. The same is true of higher than 4 core count cpu's. They run out of cpu tasks during the Tuesday outage but the slower/smaller machines don't.

Tom

---

A proud member of the OFA (Old Farts Association).

Yah, iam out in no time.

Could someone pm me on how to do this.

---

Thanks Keith

---

Perhaps one way out of this would be to find out why Seti insists upon having a 1/2 day outage once a week, when other Boinc projects don't need to?

Because other BOINC projects don't have the same number of active users & systems, nor the same requirements for validation of work, amongst other things- meaning the Database loads of other projects and their hardware requirements are significantly less than those of Seti.

---

Grant
Darwin NT