+- +-
Say hello if visiting :) by Gecko
11 Jan 2023, 07:43:05 pm

Seti is down again by Mike
09 Aug 2017, 10:02:44 am

Some considerations regarding OpenCL MultiBeam app tuning from algorithm view by Raistmer
11 Dec 2016, 06:30:56 am

Loading APU to the limit: performance considerations by Mike
05 Nov 2016, 06:49:26 am

Better sleep on Windows - new round by Raistmer
26 Aug 2016, 02:02:31 pm

Author Topic: AK app for SSE3 and SSE4.1 returned different spike count  (Read 13639 times)

Mongo

  • Guest
While browsing my completed SETI@Home tasks, I found a fellow SAH user's Q6600 Quad machine, using Alex's SSE3 v8.0 app returned 2 spikes for the same WU that my E8400 machine, using the SSE4.1 v8.0 app, reported 0 spikes.    Both machines are running Windows XP Pro, his on SP3, mine still on SP2.

Q6600 result is here:
http://setiathome.berkeley.edu/result.php?resultid=969767281

E8400 result is here:
http://setiathome.berkeley.edu/result.php?resultid=969767282

Shouldn't the counts be the same?

Mongo
« Last Edit: 31 Aug 2008, 09:36:23 pm by Mongo »

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: AK app for SSE3 and SSE4.1 returned different spike count
« Reply #1 on: 31 Aug 2008, 09:48:15 pm »
Hi there,

 The key here is in the "Restarted at 89.15 percent.".  This means the very much cosmetic signal counts (they do not constitute any part of the result stored at the science database) reset after the resume, and continue counting.  We may may an adjustment in a future build to include that in checkpointing but have not considered it a priority.

Jason

Mongo

  • Guest
Re: AK app for SSE3 and SSE4.1 returned different spike count
« Reply #2 on: 31 Aug 2008, 09:52:39 pm »
Hi there,

 The key here is in the "Restarted at 89.15 percent.".  This means the very much cosmetic signal counts (they do not constitute any part of the result stored at the science database) reset after the resume, and continue counting.  We may may an adjustment in a future build to include that in checkpointing but have not considered it a priority.

Jason



Thanks!  Appreciate the clarification.

[/worries]

Mongo

 

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?
Members
Total Members: 97
Latest: ToeBee
New This Month: 0
New This Week: 0
New Today: 0
Stats
Total Posts: 59559
Total Topics: 1672
Most Online Today: 50
Most Online Ever: 983
(20 Jan 2020, 03:17:55 pm)
Users Online
Members: 0
Guests: 17
Total: 17
Powered by EzPortal