got a in process task on my account that is running on I computer I do not have
10 May 2010 16:56:03 UTC
Topic 194929
(moderation:
I checked Einstein's tasks - validated and pending.
I have an "in process" task on my account that is running on I computer I do not have.
I do not have a Xeon computer, or 8 CPUs on any of my machines. Someone has problems with IDs and such if "their" task is showing up on my account. Any idea on what has happened, or how to correct it? I would be very upset if my crunching would be credited to someone else's account. I do have some of my own work done around the same time, but I do not have such a computer as shown in the info below.
Owner _ _ _ _ _ _Anonymous
Created _ _ _ _ _4 May 2010 17:50:36 UTC
Total Credit _ _ 0
Avg. credit _ _ _0.00
CPU type _ _ _ _ GenuineIntel Intel(R) Xeon(R) CPU E5410 @ 2.33GHz [Family 6 Model 23 Stepping 6]
Number of CPUs_ _8
GPU details _ _ _BOINC 5.9.11
Operating System_Linux 2.6.18-164.6.1.el5
Memory _ _ _ _ _ 16046.91 MB
Cache _ _ _ _ _ _6144 KB
Measured floating point speed _1990.87 million ops/sec
Measured integer speed _ _ _ _ 4379.24 million ops/sec
Average upload rate _ _ _ _ _ _Unknown
Average download rate _ _ _ _ _3925.33 KB/sec
Average turnaround time _ _ _ _0 days
Maximum daily WU quota per CPU _ 32/day
Tasks _ _ 2
got a in process task on my account that is running on I compute
)
You're talking about WUID 73734319. This shows the task IDs and computer IDs for this work unit. One is your computer, the other is some one else's computer.
On most projects, at least two tasks are sent out to different hosts. Those hosts will usually have different CPU makes (in some cases even GPUs) and different cache lengths (the amount of work one wants to have in store to cover for project outages).
The project doesn't take all data back and puts it in a database, it'll want to verify that the data you sent back isn't just a chapter of your favorite sci-fi book. And thus, they validate it against another computer.
Only when both results from both computers match each-other, is a copy put in the science database, credits granted etc. If they do not match, a third copy of this task is sent out and done by another computer. When that one sends its result back, that gets checked against the two that were available before. The result matching the third one gets credit, the one not matching does not get credit.
Since deadlines differ per project, it can take quite a while for tasks to get credit, especially if it has to wait for someone else's deadline to pass before it's sent out again and then returned. We're talking months here, in some cases even half a year.
RE: RE: I checked
)
I never seen this other computer idea on my account.
No other project shows the information of the "other guy" doing the task.
I never have seen any other person's task info listed on my account.
I never had any info on who is running the tasks to make sure my work was valid, or info about me validating someone else's work.
RE: I never seen this
)
You are wrong. I have about ten WUs in the "pending" state in SETI@home and I know who my wingmen are and which are their CPUs and OS. I even know their user names, except when "anonymous".
Tullio
It's been this way since the
)
It's been this way since the conception of BOINC. It isn't something newfangled that was secretly introduced here at Einstein overnight.
RE: It's been this way
)
Well it it the first time I have seen this. Maybe it is the fact that I never have looked at the work unit stuff in the pending section closely. When I was doing SETI solo, I never saw this information. When I was waiting months for the Astropulse to validate, I was told that I could not find out who was doing the work so I would know if it was even being none, or assigned to be done.
So when I find that I can see other users via my account, that was something I never heard of before.
RE: When I was waiting
)
Not sure who told you that, but the information has always been freely available. OK, personal information cannot be found if a person has their computer(s) hidden, as then they're "Anonymous", but you can still see (then and now) whether the task is sent to their computer.
Always fun to learn something new about this program, isn't it? ;-)