Is it too early to ask whether some of the results computed so far will have to be recomputed? Sounds like a rather serious problem affecting all platforms.
All platforms are affected, but not all workunits. People haven't reached a consensus yet how many this actually are. My current wild guess would be of an order of a few percent, but the main question is how reliable we can identify the ones affected without completely re-calculating them all.
There seems to be some thought that Homogenous Redundancy should be turned on. Is it fair to say that this would only mask "the problem" (credit not being granted) from mainly our perspective as volunteers and still leave an actual scientific problem from the science/project side
Yes.
The validation "problem" is only a symptom of an actual "scientific" problem.
The problem was technically a variable that was used uninitialized, but only in some cases. The value of such variables often ends up being zero on Unix-type systems (such as Linux an MacOS, depends also on the compiler and optimization), and some random value on Windows. Unfortunately even zero isn't a valid value from the meaning of this variable, so in these cases actually all results are scientifically invalid.
Did you see my comment about using /RTC if you are using VC++ 2005?
Yes, I did. Actually that's how I found the bug (though we are still using VS ".NET" of 2003), but it was necessary for me, too, to get the Runtime Debugger working for this (and to dig out the right workunits).
Your posts are incredibly helpful, thanks a lot! Are you doing Windows programming for living?
This bug was there and needed to be fixed, but it turned out that it is not responsible for (all of) the platform discrepancies. We're still looking into that.
Will you be releasing a new app with that bug fixed, or holding off until you can try and localize the remaining issues?
A new Beta App for MS Windows will be released in the next few days (hopefully tomorrow), it will at least reduce the client errors that arise from this bug. A release of a complete series of Apps for all platforms has be postponed until we know a bit more about the problem.
RE: Is it too early to ask
)
All platforms are affected, but not all workunits. People haven't reached a consensus yet how many this actually are. My current wild guess would be of an order of a few percent, but the main question is how reliable we can identify the ones affected without completely re-calculating them all.
BM
BM
RE: There seems to be some
)
Yes.
The validation "problem" is only a symptom of an actual "scientific" problem.
The problem was technically a variable that was used uninitialized, but only in some cases. The value of such variables often ends up being zero on Unix-type systems (such as Linux an MacOS, depends also on the compiler and optimization), and some random value on Windows. Unfortunately even zero isn't a valid value from the meaning of this variable, so in these cases actually all results are scientifically invalid.
BM
BM
RE: Did you see my comment
)
Yes, I did. Actually that's how I found the bug (though we are still using VS ".NET" of 2003), but it was necessary for me, too, to get the Runtime Debugger working for this (and to dig out the right workunits).
Your posts are incredibly helpful, thanks a lot! Are you doing Windows programming for living?
BM
BM
This bug was there and needed
)
This bug was there and needed to be fixed, but it turned out that it is not responsible for (all of) the platform discrepancies. We're still looking into that.
BM
BM
RE: Will you be releasing a
)
A new Beta App for MS Windows will be released in the next few days (hopefully tomorrow), it will at least reduce the client errors that arise from this bug. A release of a complete series of Apps for all platforms has be postponed until we know a bit more about the problem.
BM
BM
See here. BM
)
See here.
BM
BM