http://einsteinathome.org/task/3922999
I know it's invalid. I did terminate boinc in half of work, then started it again and expected it to finish it's work.
However boinc did sent it to server and the validator made it valid.
I doubt in science value of this whole computation.
Same dobt applies to accuracy of computation.
Others threads showed that linux is more accurate than windows, however becouse of windown majority count, windows results have greater meaning.
Pity.
Copyright © 2024 Einstein@Home. All rights reserved.
validator makes invalid results valid
)
http://einsteinathome.org/task/3922999
I know it's invalid. I did terminate boinc in half of work, then started it again and expected it to finish it's work.
However boinc did sent it to server and the validator made it valid.
I doubt in science value of this whole computation.
Same dobt applies to accuracy of computation.
Others threads showed that linux is more accurate than windows, however becouse of windown majority count, windows results have greater meaning.
Pity.
I'm confused: your output file is BINARY IDENTICAL with results from another user. Compare the two checksum values given at the Fstat outputs. What's more, the output indicates that the computation ran all the way to completion. Is it possible that it was some other result which you terminated halfway through?
Director, Einstein@Home
Looking at the CPU time it's
)
Looking at the CPU time it's quite clear that something went wrong in the process ; 11,7K for this type of cpu is way to short.
However the time between reporting and time Sent is a mere 12 hrs. so wijta it could be that all calculations were finished properly.
Only your cpu time calculations were corrupted (client_state file I believe) but that I have seen more often after crashing of the wine application under windows. (you are running wine as I remember).
John,
This is really strange
)
This is really strange then.
I do remember, that I was suprised that eah was occupying 100% of CPU.
I stop it. After restart, boinc sent "finished" work.
But if result if fine, then wery well.
Looking at report times, it looks like this unit was crunched for 17hours.
Normally it takes about 8h. So John.mac, I guess You right.
Just my wine makes new and new problems.
I think I switch back to 4.19 version, which is reported run well under wine.
Sounds little like my messup
)
Sounds little like my messup here.
All XP platforms.