[Thanar]

Finally, the WU exited again, twice, so I reset the project. I got the exact WU back from the server. If it does it again, I will switch back to the stock client which works fine under 50% CPU (I just can't listen to the fans revving at maximum in my work place) and wait for Alex to compile a new optimized one from a more recent CVS.

[Odysseus]

Originally Posted by kennet 

Index of /~alexkan/seti

Here are the new Alex Kan Seti Enhanced nographics versions 7.2. I take it that the mb in the version name means multibeam?

I do not know if they process multibeam or not but these were made available the 21 and 22 of August 2007, as indicated at Alex's download site.

Any S@h Enhanced version can process Multibeam data; note that there’s been no jump in version numbers since last summer. AFAICT most of the development effort for Multibeam was server-side, especially in retooling the splitters to accommodate the new data format, but I guess also in handling & interpreting the results. The only obvious differences in the recent science apps, aside from the continuing, non-CPU-specific performance tweaks, are a new reporting item or two, in the text output and the screensaver display, not affecting crunching per se, and an adjusted credit claim. (In the bizarre case of v5.23, one might better say “maladjusted”. )

[Gecko_r7]

Alex,
Seeing a strange error in stderr report.

CPU time 4501.188005
stderr out
<core_client_version>5.10.7</core_client_version>
<![CDATA[
<stderr_txt>
MacOS Error -5000 occured in /Users/alexkan/seti/boinc/mac_build/../api/mac_icon.C line 107
MacOS Error -5000 occured in /Users/alexkan/seti/boinc/mac_build/../api/mac_icon.C line 107
OS X optimized S@H Enhanced application by Alex Kan
Version info: OS X SSSE3 (Intel, Core 2-optimized v7.2mb-nographics) V5.13 by Alex Kan

Work Unit Info:
...............
Credit multiplier is : 2.85
WU true angle range is : 0.601678

Flopcounter: 12938162691841.638672

Spike count: 0
Pulse count: 1
Triplet count: 0
Gaussian count: 0
</stderr_txt>
]]>
Validate state Initial
Claimed credit 42.6944023978573
Granted credit 42.6942978617936
application version 5.27

Doesn't appear to affect processing or validation.

lib issue?

[Knightrider]

Seeing a strange error in stderr report.

I am getting this as well, but I also had it with the V7.1 as well. Alex is aware of it, but I don't know what causes it. It seems to have no adverse effect.

K.

[Odysseus]

Originally Posted by Gecko_r7 

Seeing a strange error in stderr report.

See upthread. I just installed the new “mb” app—thanks, Alex!—on my G5 running BOINC v5.4.9, but it hasn’t got any work yet; I’m expecting not to see the message because the icon problem doesn’t seem to affect clients of this vintage. (It may even have been fixed in an alpha version by now.)

[Gecko_r7]

Originally Posted by Odysseus 

See upthread. I just installed the new “mb” app—thanks, Alex!—on my G5 running BOINC v5.4.9, but it hasn’t got any work yet; I’m expecting not to see the message because the icon problem doesn’t seem to affect clients of this vintage. (It may even have been fixed in an alpha version by now.)

Thanks. One of the disadvantages to this long thread. Little gems like this get lost.
I ran 5.4.9 until a few weeks ago. Never happened w/ it.
Interesting also that the V8 pre-releases didn't show this w/ 5.10.7, but the revised 7.2 displays the error.
Thanks for the heads-up Odysseus.

[Todd Madson]

With Boinc Manager 5.50 and the new Alex Kan optimized G5 bits I'm getting
computation errors with every downloaded work unit. Ideas?

Interestingly, it's working fine on my G4.

[Thanar]

An update:

I think I am giving up on Alex' builds, since on my Mac Mini I had another failed task:
Sat Aug 25 23:50:37 2007|SETI@home|[file_xfer] Started download of file 11fe07ad.17065.3748.10.5.142
Sat Aug 25 23:52:16 2007|SETI@home|[file_xfer] Finished download of file 11fe07ad.17065.3748.10.5.142
Sat Aug 25 23:52:16 2007|SETI@home|[file_xfer] Throughput 3828 bytes/sec
Sat Aug 25 23:52:17 2007|SETI@home|Starting 11fe07ad.17065.3748.10.5.142_1
Sat Aug 25 23:52:17 2007|SETI@home|Starting task 11fe07ad.17065.3748.10.5.142_1 using setiathome_enhanced version 527
Sun Aug 26 02:34:39 2007|SETI@home|Restarting task 11fe07ad.17065.3748.10.5.142_1 using setiathome_enhanced version 527
Sun Aug 26 03:21:52 2007|SETI@home|Restarting task 11fe07ad.17065.3748.10.5.142_1 using setiathome_enhanced version 527
Sun Aug 26 04:30:30 2007|SETI@home|Restarting task 11fe07ad.17065.3748.10.5.142_1 using setiathome_enhanced version 527
Sun Aug 26 06:20:18 2007|SETI@home|Restarting task 11fe07ad.17065.3748.10.5.142_1 using setiathome_enhanced version 527
Sun Aug 26 09:19:35 2007|SETI@home|Task 11fe07ad.17065.3748.10.5.142_1 exited with zero status but no 'finished' file
Sun Aug 26 09:19:35 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Sun Aug 26 12:25:54 2007|SETI@home|Task 11fe07ad.17065.3748.10.5.142_1 exited with zero status but no 'finished' file
Sun Aug 26 12:25:54 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Sun Aug 26 15:14:45 2007|SETI@home|Restarting task 11fe07ad.17065.3748.10.5.142_1 using setiathome_enhanced version 527
Sun Aug 26 16:19:12 2007|SETI@home|Restarting task 11fe07ad.17065.3748.10.5.142_1 using setiathome_enhanced version 527
As you can see, lots of restarts and exits.

However, on my iBook G4, a WU completed successfully, although the one currently under process is 14 hours in computation which -according to BOINC manager- means 0.01% complete! Huh?

Switching mack to the stock worker for moth G4s, waiting for a new optimized client based on earlier CVS source version. Mind you, the above issues occur ONLY when CPU usage percentage is set to any lower than 100% value, through BOINC manager's preferences.

[Gulliver64]

Originally Posted by Odysseus 

See upthread. I just installed the new “mb” app—thanks, Alex!—on my G5 running BOINC v5.4.9, but it hasn’t got any work yet; I’m expecting not to see the message because the icon problem doesn’t seem to affect clients of this vintage. (It may even have been fixed in an alpha version by now.)

Odysseus,

as far as I understood alex this new version for G4/G5 is NOT multi-beam. It only corrects the multiplier. Version 8 will be MB.

[Todd Madson]

I don't get it. It didn't work at all yesterday (see errors) but it appears to be working today.

Sun Aug 26 09:48:07 2007||Rescheduling CPU: files downloaded
Sun Aug 26 09:48:07 2007||Rescheduling CPU: files downloaded
Sun Aug 26 09:48:07 2007|SETI@home|Starting task 11fe07ae.27849.20522.14.5.185_0 using setiathome_enhanced version 527
Sun Aug 26 09:48:07 2007|SETI@home|Starting task 11fe07ae.27639.21749.12.5.161_0 using setiathome_enhanced version 527
Sun Aug 26 09:48:08 2007|SETI@home|Unrecoverable error for result 11fe07ae.27639.21749.12.5.161_0 (process exited with code 2 (0x2))
Sun Aug 26 09:48:08 2007|SETI@home|Deferring scheduler requests for 24 minutes and 54 seconds
Sun Aug 26 09:48:08 2007||Rescheduling CPU: application exited
Sun Aug 26 09:48:08 2007|SETI@home|Computation for task 11fe07ae.27639.21749.12.5.161_0 finished
Sun Aug 26 09:48:09 2007|SETI@home|Unrecoverable error for result 11fe07ae.27849.20522.14.5.185_0 (process exited with code 2 (0x2))
Sun Aug 26 09:48:09 2007|SETI@home|Deferring scheduler requests for 1 hours, 9 minutes and 5 seconds

Any ideas on what's happening here and how to fix?

[kennet]

When I switched from 523 Boinc Client to Alex's optimizer and 527 the client forced the resending of the previously downloaded workunits (had to reload the Boinc Client so that Alex's optimizer would work). Those previously downloaded workunits in 523 were multibeam and they were restarted with the optimizer.

[Odysseus]

Originally Posted by Gulliver64 

as far as I understood alex this new version for G4/G5 is NOT multi-beam. It only corrects the multiplier. Version 8 will be MB.

That’s my understanding as well; AFAICT v7.2 is still based on the stock v5.13 codebase. My point was that it can still process tasks from Multibeam WUs, and its results should still validate against those of the stock app.

[Todd Madson]

Machines with the MB version:

Macs:
G5 2.5 dual
G4 400

PCs:
Linux Box with Athlon 2400 with Chicken Good 2.2 (checking, it's 2.4 actually)
Pentium M 1.7 Windows XP Box

Observations:
So far it looks like my RAC is dropping like a rock. Not sure if this
is a seti thing or just the effect of the corrected credit system with
the new clients or not.

I've got at least one Mac that needs to be updated to the MB
version that I haven't had the time to get to and theres' another
x86 system that needs to get updated but so far the results
have been curious.

Seems like the time for work units to crunch is longer but
looking at the records for the machines doesn't bear that out - it
seems slightly sooner but I have a lot of pending credit.

[arkayn]

Alex has just released a new version of his app...

i386-v7.2mb1-coreduo-nographics
i386-v7.2mb1-core2-nographics


* pulse-finding fixes to address weakly similar WUs


source code

[kennet]

Thanks muchly

Kenn

[BTBlomberg]

It appears that SETI stats are just dropping with the new WUs. You can have a good WU that takes several hours get 60+ Credits and then have one that runs 5 times as long to error out and get 0.XX credits. Looks like there are a lot of noisy WUs out there and the effect is you can work a long time on junk and get no credit for it. This is not just Mac and not just optimized Clients. I have seen it with 2.4 and 2.2 clients as well as stock all failing with excessive time on a WU.

I also am seeing the Pending credits rising. I went from just a couple hundred a couple weeks ago to nearly 4000. So my machines are cranking them out, they are just sitting there waiting to be confirmed.

On the other hand I am also seeing 100+ Credit WUs from time to time.

My feeling is that the MB WUs are a little junky right now and I think the tech bulitin at Seti confirmed this at one point. SO I am hoping they work throught them adn get things teeked so that we can get back up there.

Going from nearly 4000 credits a day to 2000 credits a day sucks.

[halimedia]

Originally Posted by arkayn 

Alex has just released a new version of his app...
i386-v7.2mb1-coreduo-nographics
i386-v7.2mb1-core2-nographics
* pulse-finding fixes to address weakly similar WUs
source code

Kudos to Alex for releasing this fix so quickly!

Since installing these new builds, my pending credit is decreasig instead of increasing. I'd highly recommend anyone install these new builds. While it's rare that WUs fail or receive no credit with Alex' first Intel MB-builds, the weak similarty of many results provoke SETI to send out a third WU per quorum. This results in the increasing pending credit situation many have experienced, puts unnecessary load on the SETI servers, and reduces project efficiency over-all.

Thanks again, Alex - and thanks to arkayn for posting this here!

Cheers, Ron

[gorbag]

I certainly hope pending credit starts to decrease (I just updated all my x86 workers). I've got over 31K pending!

[halimedia]

Originally Posted by gorbag 

I certainly hope pending credit starts to decrease (I just updated all my x86 workers).

No worries, it will

I've got over 31K pending!

My max was 60k, and I'm down to 49k as of this writing. I installed the updated workers a little less than two days ago.

Cheers, Ron