Sorry I found a flaw in the SSE2 part of the App (only) that leads to occasional invalid results (thanks again, Bikeman).
I updated the App package, new md5sum is 93dc3c4f4980e441fe82b0acaee46b1e. Please update your einstein_S5R4_6.10..._2.exe file from the new package if your CPU uses SSE2.
Sorry I found a flaw in the SSE2 part of the App (only) that leads to occasional invalid results (thanks again, Bikeman).
I updated the App package, new md5sum is 93dc3c4f4980e441fe82b0acaee46b1e. Please update your einstein_S5R4_6.10..._2.exe file from the new package if your CPU uses SSE2.
BM
I will update in a little while, have had a few more that's marked as unvalid and I was beginning to think it had someting to do with me testing the Seti-cuda app.
Glad to help catch these problems before the app is released!
@Bikeman
Thanks for letting the staff know about this!
Sorry I found a flaw in the SSE2 part of the App (only) that leads to occasional invalid results (thanks again, Bikeman).
I updated the App package, new md5sum is 93dc3c4f4980e441fe82b0acaee46b1e. Please update your einstein_S5R4_6.10..._2.exe file from the new package if your CPU uses SSE2.
BM
After this new SSE2 executable is tested some, what are the prospects for making it the stock application for Windows? Also, what's going on with S5R5?
After this new SSE2 executable is tested some, what are the prospects for making it the stock application for Windows? Also, what's going on with S5R5?
S5R5 is still somewhat delayed until staff an scientists are back from holidays around Jan 5.
Note that testing the 6.10 S5R4 App is actually testing the code we will use for S5R5 (in fact the "flaw" I found in the SSE2 App was that it was built as an S5R5 one, i.e. it contained the leap seconds fix that we need to switch off for compatibility to existing S5R4 Apps).
My goal is to make this S5R4 App "official" before we issue more ABP1 (PALFA) work, which is bound to similar constraints as S5R5.
After this new SSE2 executable is tested some, what are the prospects for making it the stock application for Windows? Also, what's going on with S5R5?
S5R5 is still somewhat delayed until staff an scientists are back from holidays around Jan 5.
Well, they could always have an Epiphany (Jan 6)... :-)
Quote:
My goal is to make this S5R4 App "official" before we issue more ABP1 (PALFA) work, which is bound to similar constraints as S5R5.
Sorry I found a flaw in the SSE2 part of the App (only) that leads to occasional invalid results (thanks again, Bikeman).
I updated the App package, new md5sum is 93dc3c4f4980e441fe82b0acaee46b1e. Please update your einstein_S5R4_6.10..._2.exe file from the new package if your CPU uses SSE2.
BM
I have updated all my farm to the latest version of the 6.10 app. All appear to be working fine.
All machines are Win XP. One has BOINC 6.5.0 and the others are 6.2.19.
...
Note that testing the 6.10 S5R4 App is actually testing the code we will use for S5R5 (in fact the "flaw" I found in the SSE2 App was that it was built as an S5R5 one, i.e. it contained the leap seconds fix that we need to switch off for compatibility to existing S5R4 Apps)....
...
Note that testing the 6.10 S5R4 App is actually testing the code we will use for S5R5 (in fact the "flaw" I found in the SSE2 App was that it was built as an S5R5 one, i.e. it contained the leap seconds fix that we need to switch off for compatibility to existing S5R4 Apps)....
Your system has been having similar problems for several days now, before Bernd had put up the new SSE2 package, so I don't think it is the "new" SSE2 application...
Is the system overclocked? Have you tested the memory using something like Memtest86? Have you checked for stability using something like Orthos or Prime95? Do you have the most recent drivers for your video card?
Sorry I found a flaw in the
)
Sorry I found a flaw in the SSE2 part of the App (only) that leads to occasional invalid results (thanks again, Bikeman).
I updated the App package, new md5sum is 93dc3c4f4980e441fe82b0acaee46b1e. Please update your einstein_S5R4_6.10..._2.exe file from the new package if your CPU uses SSE2.
BM
BM
RE: Sorry I found a flaw in
)
I will update in a little while, have had a few more that's marked as unvalid and I was beginning to think it had someting to do with me testing the Seti-cuda app.
Glad to help catch these problems before the app is released!
@Bikeman
Thanks for letting the staff know about this!
RE: Sorry I found a flaw in
)
After this new SSE2 executable is tested some, what are the prospects for making it the stock application for Windows? Also, what's going on with S5R5?
Thanks...
RE: After this new SSE2
)
S5R5 is still somewhat delayed until staff an scientists are back from holidays around Jan 5.
Note that testing the 6.10 S5R4 App is actually testing the code we will use for S5R5 (in fact the "flaw" I found in the SSE2 App was that it was built as an S5R5 one, i.e. it contained the leap seconds fix that we need to switch off for compatibility to existing S5R4 Apps).
My goal is to make this S5R4 App "official" before we issue more ABP1 (PALFA) work, which is bound to similar constraints as S5R5.
BM
BM
I got these 'no heartbeat'
)
I got these 'no heartbeat' errors yesterday using 6.10 SSE2 version. I have not installed the revised 6.10 SSE2 version yet.
113110714
113113943
Seti Classic Final Total: 11446 WU.
RE: RE: After this new
)
Well, they could always have an Epiphany (Jan 6)... :-)
Deadline back to 14 days? ;-)
RE: Sorry I found a flaw in
)
I have updated all my farm to the latest version of the 6.10 app. All appear to be working fine.
All machines are Win XP. One has BOINC 6.5.0 and the others are 6.2.19.
Thanks for the quick fix.
BOINC blog
RE: ... Note that testing
)
Had an error with the new version here:http://einsteinathome.org/task/113509588
After over 5 hours :((
RE: RE: ... Note that
)
Your system has been having similar problems for several days now, before Bernd had put up the new SSE2 package, so I don't think it is the "new" SSE2 application...
Is the system overclocked? Have you tested the memory using something like Memtest86? Have you checked for stability using something like Orthos or Prime95? Do you have the most recent drivers for your video card?
Im crunching with an
)
Im crunching with an AMD3000+. System is using automatically the right app for SSE. The app is working fine on my system until now.
6.04 - 5 results - average CPU time 17.8 hours
6.10 - 5 results - average CPU time 14.5 hours
greetings KnB-Construction