LHC@home

Noticed this, when checking my own results... Anyhow, thus far he returned a credit claim that wildly conflicted the other cruncher who returned it so far

http://lhcathome.cern.ch/workunit.php?wuid=1348242

He claimed .02 credits, the other person claimed 30.75... So I clicked on his client, and saw this:

http://lhcathome.cern.ch/show_host_detail.php?hostid=61123

Average turnaround time 124227.13 days
Results 1096

How many years would that represent? Definitely more then 10 years... Umm, the project wasn't in place for 10+ years, a definite hack job...

Now for the juicy part in his results page:

http://lhcathome.cern.ch/results.php?hostid=61123

All of his credit claims are low, as in < 1 claimed credit as far back as I cared to look...

Edit: Looking further at this user's computer list

http://lhcathome.cern.ch/hosts_user.php?userid=751

he's got 24 computers, and a hell of a lot with a 0/day WU quota...

---

I have another one similiar to this.

http://lhcathome.cern.ch/workunit.php?wuid=1348168

One user successfully completed the workunit in 2 seconds where the other user completed the workunit in 14,000 seconds. Hmmmmmmmm

**Edit**

Check it out here. All of the workunits he has gotten thus far he has completed in under 3 seconds. Something is fishy here!

http://lhcathome.cern.ch/results.php?hostid=84721

---

*cough* overclocking junkie *cough*

---

Want to search the BOINC Wiki, BOINCstats, or various BOINC forums from within firefox? Try the BOINC related Firefox Search Plugins

or it could be the pc having a hardware issue (overheating), or the boinc client getting frazzled.

---

I'm not the LHC Alex. Just a number cruncher like everyone else here.

What I was thinking, is a possible editing of .xml files/cheating... Don't know for certain however what the actual cause is; but it's a bad host regardless

---