This may not be anything serious but I was just looking at my tasks summary page and noticed I have 2 tasks marked as invalid compared to 67 tasks marked valid. When I looked more closely at the 2 invalids I noticed that both of them were similar in that my result used the Milkyway@home N-Body Simulation with Orbit Fitting v1.93 (mt) windows_x86_64 application and the original wingman used the Milkyway@home N-Body Simulation with Orbit Fitting v1.93 (mt) x86_64-pc-linux-gnu application. Both tasks were originally marked as Inconclusive and both were eventually decided by a third wingman which also used the Milkyway@home N-Body Simulation with Orbit Fitting v1.93 (mt) x86_64-pc-linux-gnu application.

See Workunit 1006405351 and Workunit 1006502579.

To be clear I am not complaining about missing credit on my account. I am only raising this issue as a potential problem which may impact the validity of the science. That is, if the scientists are convinced that the windows_x86_64 application and the pc-linux-gnu application both produce results whose simulations are adequate for their purpose, then I am satisfied

This is a well-known issue and commented on a lot. The devs have not considered the issue to be critical and aren't willing to expend the resources for a fix. It only amounts to about 1-2% invalid rate among hosts.

You will run into this when your returned result is matched with a different client platform than yours. It's just because of the difference in math calculation between gpus, cpus and OS'. The devs would have to set a lot more permissive result variance allowance which they decided would impact the science negatively.

This is just the cost of doing business with this project. Either accept it and move on or look for a different project that doesn't have this kind of issue.

---

Last update on it was a week ago. The issue seems to have appeared in 1.92 and seems to be caused by the Windows and Linux versions being compiled differently, which tends to result in slight differences, so if a work unit is processed by a computer on one and one on the other they'll tend to disagree, and assuming that there are no other issues then whichever OS the third computer it's sent to uses will validate the one on the same OS and invalidate the other. According to that last update they currently believe that the Linux results are the correct ones, but the differences are usually tiny and at this time they don't consider them a problem in terms of science, though it may add up to one if this lasts long. Does make for a fair bit of wasted computing time though. And, if the Linux results are the correct ones, then all of the Windows results that validate each other are slightly off as well, which is what may cause the science issue if this keeps up.