That's the answer to your question. Your result didn't match the other result. A third one was sent out. That one did match with the result from the other user. But not with yours again. So yours became an invalid result. Is your machine overclocked? This can produce calculation errors.
That's the answer to your question. Your result didn't match the other result. A third one was sent out. That one did match with the result from the other user. But not with yours again. So yours became an invalid result. Is your machine overclocked? This can produce calculation errors.
Christoph
No overclocking. Mine is a Mac. They are PC's. That's the difference. Clearly discrimination. The validator is unable to operate correctly.
It means the result was downloaded, crunched and returned to the project correctly. It does not have anything to do with Validation.
Validation is a very specific. It needs to match at a very precise calculation. So if you are off, you are invalid.
I see around the same time you got that task, you aborted a bunch. So something went on during that time. Were you doing something with you machine at that time that might have been the cause of the issue?
It means the result was downloaded, crunched and returned to the project correctly. It does not have anything to do with Validation.
Validation is a very specific. It needs to match at a very precise calculation. So if you are off, you are invalid.
I see around the same time you got that task, you aborted a bunch. So something went on during that time. Were you doing something with you machine at that time that might have been the cause of the issue?
The validation was incorrect as the Mac and the PC's are different and the validator wasn't able to do the comparison correctly. That has happened on other projects.
I was using the Beta application for Macs at around that time. I also am a tester for the Boinc Manager and that can cause some misadventures, but has nothing to do with validation on Einstein.
Is there no moderator who can do a manual correction of credit for a mistake with the validator?
I have one of these in my task list as well: 58824487
There was nothing going on at my end to suggest an explanation though I realize that doesn't mean that something unusual didn't (quietly)happen. I also realize that there may be rare occasions running a Mac leaves me on the losing end of a three way race(I believe this is the first time since I attached this machine in January)(on another note I crunched this task much faster than my wingmen, speed obviously isn't everything:).
All that said, I see we are crunching with a new Mac app and am posting in the off chance that this might be relevant and thus a closer look may in fact warranted.
I have one of these in my task list as well: 58824487
There was nothing going on at my end to suggest an explanation though I realize that doesn't mean that something unusual didn't (quietly)happen. I also realize that there may be rare occasions running a Mac leaves me on the losing end of a three way race(I believe this is the first time since I attached this machine in January)(on another note I crunched this task much faster than my wingmen, speed obviously isn't everything:).
All that said, I see we are crunching with a new Mac app and am posting in the off chance that this might be relevant and thus a closer look may in fact warranted.
Snags
I also have one, also crunched on a Mac: 60366678... A trend?
No Credit for successful task?
)
Validate State: Invalid
That's the answer to your question. Your result didn't match the other result. A third one was sent out. That one did match with the result from the other user. But not with yours again. So yours became an invalid result. Is your machine overclocked? This can produce calculation errors.
Christoph
Greetings, Christoph
RE: RE: This task
)
No overclocking. Mine is a Mac. They are PC's. That's the difference. Clearly discrimination. The validator is unable to operate correctly.
I guess "Success" needs to be
)
I guess "Success" needs to be defined again.
It means the result was downloaded, crunched and returned to the project correctly. It does not have anything to do with Validation.
Validation is a very specific. It needs to match at a very precise calculation. So if you are off, you are invalid.
I see around the same time you got that task, you aborted a bunch. So something went on during that time. Were you doing something with you machine at that time that might have been the cause of the issue?
RE: I guess "Success" needs
)
The validation was incorrect as the Mac and the PC's are different and the validator wasn't able to do the comparison correctly. That has happened on other projects.
I was using the Beta application for Macs at around that time. I also am a tester for the Boinc Manager and that can cause some misadventures, but has nothing to do with validation on Einstein.
Is there no moderator who can do a manual correction of credit for a mistake with the validator?
I have one of these in my
)
I have one of these in my task list as well: 58824487
There was nothing going on at my end to suggest an explanation though I realize that doesn't mean that something unusual didn't (quietly)happen. I also realize that there may be rare occasions running a Mac leaves me on the losing end of a three way race(I believe this is the first time since I attached this machine in January)(on another note I crunched this task much faster than my wingmen, speed obviously isn't everything:).
All that said, I see we are crunching with a new Mac app and am posting in the off chance that this might be relevant and thus a closer look may in fact warranted.
Snags
Keep crunching, this is just
)
Keep crunching, this is just a routine problem.
Overclock with the MSI G31M3-L and Intel E8600 3.33Ghz
Intel D865GLC Socket 478 Motherboard Review
Overclock your ASUS 1005HA netbook and crunch more
RE: I have one of these in
)
I also have one, also crunched on a Mac: 60366678... A trend?