A new Windows App is available from our Beta Test Page.
Compared to the 4.23 Beta App this one fixes a bug in memory access that might be responsible for some client errors. Also the "symbol store" debugging feature should work now.
For the curious: You can provoke a "client error" (Breakpoint) by putting a file named "EAH_MSC_BREAKPOINT" into the BOINC directory (remember to remove it after testing!).
BM
BM
Copyright © 2024 Einstein@Home. All rights reserved.
Windows Beta Test App 4.24 available
)
Oh, just what we need... provoking... ;-) I don't think we should provoke Einstein. He may roll over and declare E=MC3 :-O
I'll try it later... Doing some SETI stuff right now...
Loaded and crunching ... 34
)
Loaded and crunching ... 34 hours of work estimated on the Athlon 3200+. Wait and see :)
Installed on two
)
Installed on two hosts.
I'm getting lots of x-platform-validation problems now, e.g. here http://einsteinathome.org/host/962477/tasks, the series of workunits on that host seems to be a good testcase for the validation problem :-(.
Not sure whether it makes sense to continue crunching under Linux with the known issue of uninitialized variables at the moment.
CU
BRM
RE: Installed on two
)
Are you saying that if a Linux host are paired up with any Windows OS that the Linux result is guaranteed to be declared "invalid"? I could've swore that I had one result validate against Linux some time ago, but I've been paired with nothing but other Windows versions lately.
Edit: It must be something specific with either the Linux or the Windows installation that is causing the issue, because not everything fails. I guess it could also be the frequency range of the result. Don't know. I'm currently watching FalconFly's results for comparisons against my processor. Though he said that he wouldn't be really processing a lot of stuff until this week, this WU of his validated against a Windows XP Pro host...
RE: Are you saying that if
)
My Linux box just got 304.31 credits against a Windows box. Never had a validation error on my PII Deschutes running SuSE Linux 10.1, BOINC 5.8.17. Same in SETI and QMC.
Tullio
RE: RE: Are you saying
)
Hmmm... Yep, I knew there were hosts out there going along fine. Obviously something triggers the problem...but what? Is it perhaps a problem with the WU generator? Pure speculation...and I'm probably talking out of ignorance at this point... LOL
P.S. - I HATE REGULAR EXPRESSIONS!!!!! Been up all night working on something for school. I realize they are "powerful and all", but they are way too nerdy, IMO...
I'm pretty sure that the
)
I'm pretty sure that the cross-platform validation problem neither has to do with the memory access bug we fixed, nor with a particular machine.
IMHO it is rather a problem of numerical differences between libraries or compilers that is triggered only by certain Workunits. It may be the actual frequency value or the data (files), e.g. a certain type of noise in particular frequency bands.
We're working on it.
BM
BM
I remember that, at Area
)
I remember that, at Area Science Park in Trieste, my MIPS 6000 minicomputer, running UNIX System V, gave results that were different from those obtained on a SUN workstation running SUNOS. But I still don't know why.
Tullio
RE: I'm pretty sure that
)
That reminds me...: Bernd, is it true that the math library for the Linux app is linked dynamically? Wouldn't it be better to have it statically linked to have a guarantee that every Linux app uses the same?
Some frequencies really seem to be more affected than others, I had a series of WUs lately where I had a 50 % failure rate (!), and a single result I investigated contained as many as 100 mismatches between Windows & Linux in the final "toplist" containing the 10000 most promising items.
CU
BRM
RE: Some frequencies
)
A) Where do you go to see that kind of stuff?
B) Where do you come up with the time to do that analysis? ;-)