Well I have reset the project and got 5.22 to run.

I have the following observations (I have a dual processor G5):

1) The screensaver still doesn't start. It says the client is in 'test mode'.
2) Each of my machines I have 5.22 running on are now nearly five degrees F hotter than before (163 degrees now)
3) There is some memory issue. At one point one task took 900MB and caused the other task to suspend itself waiting for memory resources. After a while the memory use returned to a normal amount (66 MB), but the suspended task remains suspended with a status of 'waiting for memory'.
With this second task suspended, the machine temperature has returned to a 'normal' 157 degrees, obviously because the other task is not running.

I think 5.22 needs some additional tweaking.

---

Also work units seem to be taking about 3 times longer to run. I don't know if we are being issued bigger work units or if the program is slow.

---

I managed to get the project restarted and updated to 5.22 FINALLY.
Then it worked for 12 seconds and stopped message "paused other work in progress".
All my setting are set to allow work while computer is in use. does 5.22 have a issue working while computer is in use?

I also have a dual G5 processor machine and as far as I can tell, every time I start a new SaH task I get a crash reported from it. I also seem to get one when it completes and tries to report. No luck starting the screensaver. I did notice that all running applications kinda got pokey for several seconds.

---

My Mac's symptoms are here in this thread (don't want to double post):
http://setiathome.berkeley.edu/forum_thread.php?id=40952&nowrap=true#606539

We were just a few minutes apart from each other on posting, Bob :p (sorry ^_~ ).....

Well things were running (and crashing), but now the screensaver no longer works and none of the 3
tasks are running (2 waiting to upload and the other 'waiting for memory').

---

I am running BOINC Manager 5.10.10 on OSX 5.4.10 with what would appear to be S@H 5.13, and using Alex Kan's optimized version added in. Should I upgrade to 5.22? (Maybe, after reading this thread, waiting for 5.23 might be advisable anyway?) And, if so, how do I obtain and install same? Is it a matter of detaching SETI and then re-attaching?

Keith

SETI 5.22 does have many problems. Running OSX 10.4.10 on iMAC G5 2 GHz Power PC.
Runs hit or miss and takes up huge amounts of resources an d does not do much processing of work. Had no previoous problems with older SETI versions and Einstein works just fine. What's going on? Have reset SETI numerous times and still have been unable to finish any work units sint 18 July 2997. HELP!!!!!!!!!


Fri Jul 20 17:21:49 2007||Starting BOINC client version 5.10.7 for powerpc-apple-darwin
Fri Jul 20 17:21:49 2007||log flags: task, file_xfer, sched_ops
Fri Jul 20 17:21:49 2007||Libraries: libcurl/7.16.1 OpenSSL/0.9.7l zlib/1.2.3
Fri Jul 20 17:21:49 2007||Data directory: /Library/Application Support/BOINC Data
Fri Jul 20 17:21:49 2007||Processor: 1 Power Macintosh Power Macintosh [Power Macintosh Model PowerMac8,2] [AltiVec]
Fri Jul 20 17:21:49 2007||Processor features:
Fri Jul 20 17:21:49 2007||Memory: 1.00 GB physical, 211.60 GB virtual
Fri Jul 20 17:21:49 2007||Disk: 233.64 GB total, 211.35 GB free
Fri Jul 20 17:21:49 2007|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 572056; location: home; project prefs: default
Fri Jul 20 17:21:49 2007|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 2176191; location: home; project prefs: default
Fri Jul 20 17:21:49 2007||General prefs: from Einstein@Home (last modified 2007-07-11 22:25:37)
Fri Jul 20 17:21:49 2007||Host location: home
Fri Jul 20 17:21:49 2007||General prefs: using separate prefs for home
Fri Jul 20 17:21:49 2007||Preferences limit memory usage when active to 512.00MB
Fri Jul 20 17:21:49 2007||Preferences limit memory usage when idle to 921.60MB
Fri Jul 20 17:21:49 2007||Preferences limit disk usage to 9.31GB
Fri Jul 20 17:21:50 2007|Einstein@Home|Restarting task h1_0491.80_S5R2__159_S5R2c_0 using einstein_S5R2 version 420
Fri Jul 20 17:23:32 2007|SETI@home|Restarting task 03jn00aa.22690.18914.67340.3.17_2 using setiathome_enhanced version 522
Fri Jul 20 18:23:56 2007|Einstein@Home|Resuming task h1_0491.80_S5R2__159_S5R2c_0 using einstein_S5R2 version 420
Fri Jul 20 20:05:05 2007|SETI@home|Resuming task 03jn00aa.22690.18914.67340.3.17_2 using setiathome_enhanced version 522
Fri Jul 20 20:07:25 2007|SETI@home|Resetting project
Fri Jul 20 20:07:30 2007|Einstein@Home|Resuming task h1_0491.80_S5R2__159_S5R2c_0 using einstein_S5R2 version 420
Fri Jul 20 20:07:30 2007|SETI@home|Sending scheduler request: To fetch work
Fri Jul 20 20:07:30 2007|SETI@home|Requesting 17826 seconds of new work
Fri Jul 20 20:07:35 2007|SETI@home|Scheduler RPC succeeded [server version 511]
Fri Jul 20 20:07:35 2007|SETI@home|Message from server: Didn't resend lost result 03jn00aa.22690.18914.67340.3.17_2 (expired)
Fri Jul 20 20:07:35 2007|SETI@home|Deferring communication for 11 sec
Fri Jul 20 20:07:35 2007|SETI@home|Reason: requested by project
Fri Jul 20 20:07:37 2007|SETI@home|[file_xfer] Started download of file setiathome-5.22.powerpc-apple-darwin
Fri Jul 20 20:07:37 2007|SETI@home|[file_xfer] Started download of file setiathome-5.22_COPYING
Fri Jul 20 20:07:38 2007|SETI@home|[file_xfer] Finished download of file setiathome-5.22_COPYING
Fri Jul 20 20:07:38 2007|SETI@home|[file_xfer] Throughput 48653 bytes/sec
Fri Jul 20 20:07:38 2007|SETI@home|[file_xfer] Started download of file setiathome-5.22_COPYRIGHT
Fri Jul 20 20:07:39 2007|SETI@home|[file_xfer] Finished download of file setiathome-5.22_COPYRIGHT
Fri Jul 20 20:07:39 2007|SETI@home|[file_xfer] Throughput 6865 bytes/sec
Fri Jul 20 20:07:39 2007|SETI@home|[file_xfer] Started download of file setiathome-5.22_README
Fri Jul 20 20:07:40 2007|SETI@home|[file_xfer] Finished download of file setiathome-5.22_README
Fri Jul 20 20:07:40 2007|SETI@home|[file_xfer] Throughput 7717 bytes/sec
Fri Jul 20 20:07:40 2007|SETI@home|[file_xfer] Started download of file seti_522.jpg
Fri Jul 20 20:07:42 2007|SETI@home|[file_xfer] Finished download of file seti_522.jpg
Fri Jul 20 20:07:42 2007|SETI@home|[file_xfer] Throughput 21361 bytes/sec
Fri Jul 20 20:07:42 2007|SETI@home|[file_xfer] Started download of file setiathome-5.22_AUTHORS
Fri Jul 20 20:07:43 2007|SETI@home|[file_xfer] Finished download of file setiathome-5.22_AUTHORS
Fri Jul 20 20:07:43 2007|SETI@home|[file_xfer] Throughput 3014 bytes/sec
Fri Jul 20 20:07:43 2007|SETI@home|[file_xfer] Started download of file 04jn00ab.1874.21345.972158.3.3
Fri Jul 20 20:07:49 2007|SETI@home|[file_xfer] Finished download of file 04jn00ab.1874.21345.972158.3.3
Fri Jul 20 20:07:49 2007|SETI@home|[file_xfer] Throughput 74147 bytes/sec
Fri Jul 20 20:07:49 2007|SETI@home|[file_xfer] Started download of file arecibo_181.png
Fri Jul 20 20:07:50 2007|SETI@home|[file_xfer] Finished download of file arecibo_181.png
Fri Jul 20 20:07:50 2007|SETI@home|[file_xfer] Throughput 59142 bytes/sec
Fri Jul 20 20:07:50 2007|SETI@home|[file_xfer] Started download of file sah_40.png
Fri Jul 20 20:07:51 2007|SETI@home|[file_xfer] Finished download of file sah_40.png
Fri Jul 20 20:07:51 2007|SETI@home|[file_xfer] Throughput 18624 bytes/sec
Fri Jul 20 20:07:51 2007|SETI@home|[file_xfer] Started download of file sah_banner_290.png
Fri Jul 20 20:07:52 2007|SETI@home|[file_xfer] Finished download of file sah_banner_290.png
Fri Jul 20 20:07:52 2007|SETI@home|[file_xfer] Throughput 35389 bytes/sec
Fri Jul 20 20:07:52 2007|SETI@home|[file_xfer] Started download of file sah_ss_290.png
Fri Jul 20 20:07:53 2007|SETI@home|[file_xfer] Finished download of file sah_ss_290.png
Fri Jul 20 20:07:53 2007|SETI@home|[file_xfer] Throughput 59956 bytes/sec
Fri Jul 20 20:08:03 2007|SETI@home|[file_xfer] Finished download of file setiathome-5.22.powerpc-apple-darwin
Fri Jul 20 20:08:03 2007|SETI@home|[file_xfer] Throughput 108948 bytes/sec
Sat Jul 21 09:35:06 2007||Running CPU benchmarks
Sat Jul 21 09:35:06 2007||Suspending computation - running CPU benchmarks
Sat Jul 21 09:35:37 2007||Benchmark results:
Sat Jul 21 09:35:37 2007|| Number of CPUs: 1
Sat Jul 21 09:35:37 2007|| 537 floating point MIPS (Whetstone) per CPU
Sat Jul 21 09:35:37 2007|| 1822 integer MIPS (Dhrystone) per CPU
Sat Jul 21 09:35:38 2007||Resuming computation
Sat Jul 21 13:35:34 2007|Einstein@Home|Sending scheduler request: To fetch work
Sat Jul 21 13:35:34 2007|Einstein@Home|Requesting 42 seconds of new work
Sat Jul 21 13:35:39 2007|Einstein@Home|Scheduler RPC succeeded [server version 509]
Sat Jul 21 13:35:39 2007|Einstein@Home|Deferring communication for 1 min 0 sec
Sat Jul 21 13:35:39 2007|Einstein@Home|Reason: requested by project
Sat Jul 21 13:56:46 2007|SETI@home|Starting 04jn00ab.1874.21345.972158.3.3_0
Sat Jul 21 13:56:46 2007|SETI@home|Starting task 04jn00ab.1874.21345.972158.3.3_0 using setiathome_enhanced version 522
Sat Jul 21 14:12:42 2007|SETI@home|Sending scheduler request: To fetch work
Sat Jul 21 14:12:42 2007|SETI@home|Requesting 169 seconds of new work
Sat Jul 21 14:12:47 2007|SETI@home|Scheduler RPC succeeded [server version 511]
Sat Jul 21 14:12:47 2007|SETI@home|Deferring communication for 11 sec
Sat Jul 21 14:12:47 2007|SETI@home|Reason: requested by project
Sat Jul 21 14:12:49 2007|SETI@home|[file_xfer] Started download of file 14ap00aa.8423.27728.597160.3.42
Sat Jul 21 14:12:53 2007|SETI@home|[file_xfer] Finished download of file 14ap00aa.8423.27728.597160.3.42
Sat Jul 21 14:12:53 2007|SETI@home|[file_xfer] Throughput 148744 bytes/sec
Sat Jul 21 14:56:53 2007|Einstein@Home|Resuming task h1_0491.80_S5R2__159_S5R2c_0 using einstein_S5R2 version 420
Sat Jul 21 15:59:45 2007|SETI@home|Resuming task 04jn00ab.1874.21345.972158.3.3_0 using setiathome_enhanced version 522
Sat Jul 21 16:05:20 2007|Einstein@Home|Resuming task h1_0491.80_S5R2__159_S5R2c_0 using einstein_S5R2 version 420
Sat Jul 21 16:08:22 2007|SETI@home|Task 04jn00ab.1874.21345.972158.3.3_0 exited with zero status but no 'finished' file
Sat Jul 21 16:08:22 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Sat Jul 21 21:57:47 2007|SETI@home|Restarting task 04jn00ab.1874.21345.972158.3.3_0 using setiathome_enhanced version 522
Sat Jul 21 22:57:55 2007|Einstein@Home|Resuming task h1_0491.80_S5R2__159_S5R2c_0 using einstein_S5R2 version 420
Sun Jul 22 00:55:40 2007|SETI@home|Resuming task 04jn00ab.1874.21345.972158.3.3_0 using setiathome_enhanced version 522
Sun Jul 22 06:32:57 2007|Einstein@Home|Resuming task h1_0491.80_S5R2__159_S5R2c_0 using einstein_S5R2 version 420
Sun Jul 22 06:33:56 2007|SETI@home|Resuming task 04jn00ab.1874.21345.972158.3.3_0 using setiathome_enhanced version 522
Sun Jul 22 06:33:57 2007|SETI@home|Sending scheduler request: To fetch work
Sun Jul 22 06:33:57 2007|SETI@home|Requesting 6316 seconds of new work
Sun Jul 22 06:35:43 2007|Einstein@Home|Resuming task h1_0491.80_S5R2__159_S5R2c_0 using einstein_S5R2 version 420
Sun Jul 22 06:35:58 2007|SETI@home|Task 04jn00ab.1874.21345.972158.3.3_0 exited with zero status but no 'finished' file
Sun Jul 22 06:35:58 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Sun Jul 22 06:35:58 2007||Project communication failed: attempting access to reference site
Sun Jul 22 06:35:58 2007|SETI@home|Scheduler request failed: a timeout was reached
Sun Jul 22 06:35:58 2007|SETI@home|Deferring communication for 1 min 0 sec
Sun Jul 22 06:35:58 2007|SETI@home|Reason: scheduler request failed
Sun Jul 22 06:35:59 2007||Access to reference site succeeded - project servers may be temporarily down.
Sun Jul 22 08:42:43 2007|Einstein@Home|Computation for task h1_0491.80_S5R2__159_S5R2c_0 finished
Sun Jul 22 08:42:43 2007|Einstein@Home|Starting h1_0491.80_S5R2__144_S5R2c_0
Sun Jul 22 08:42:45 2007|Einstein@Home|Starting task h1_0491.80_S5R2__144_S5R2c_0 using einstein_S5R2 version 420
Sun Jul 22 08:42:46 2007|Einstein@Home|[file_xfer] Started upload of file h1_0491.80_S5R2__159_S5R2c_0_0
Sun Jul 22 08:42:51 2007|Einstein@Home|[file_xfer] Finished upload of file h1_0491.80_S5R2__159_S5R2c_0_0
Sun Jul 22 08:42:51 2007|Einstein@Home|[file_xfer] Throughput 33463 bytes/sec
Sun Jul 22 11:46:27 2007|Einstein@Home|Sending scheduler request: Requested by user
Sun Jul 22 11:46:27 2007|Einstein@Home|Reporting 1 tasks
Sun Jul 22 11:46:32 2007|Einstein@Home|Scheduler RPC succeeded [server version 509]
Sun Jul 22 11:46:32 2007|Einstein@Home|Deferring communication for 1 min 0 sec
Sun Jul 22 11:46:32 2007|Einstein@Home|Reason: requested by project

---

You can ignore the message "task .... exited with zero status but no 'finished' file" if the WU will not reset to 0%. This could happen when the BOINC client can not proper communicate with the SETI application. At MacOS this happens oftener compared with other platforms.

---

Here is a screen shot of the messed up graphics in SAH 5.22
http://members.buckeye-express.com/pixzy/picture%201.jpg

---

So scratching my head over all of these posts above & around and the possible solutions, what's the consensus on 5.22? Is it safe to use now without any worries of oddness & no work being done when not looking, or is it still funky and odd??? Wondering if I should risk going back and run it again or not (doin' the Einstein thing right now). It seems to do whatever it wants whenever it wants for everyone here, so any advice would be appreciated. Thanks ^^ !

So scratching my head over all of these posts above & around and the possible solutions, what's the consensus on 5.22? Is it safe to use now without any worries of oddness & no work being done when not looking, or is it still funky and odd??? Wondering if I should risk going back and run it again or not (doin' the Einstein thing right now). It seems to do whatever it wants whenever it wants for everyone here, so any advice would be appreciated. Thanks ^^ !

I see no reason, why not to crunch SETI with the new application. The compuation errors are fixed. But it looks like the screensaver has some problems and the memory util sometimes going higher than on the older app.
The screensaver is only additional an has no benefit for the science, you can disable it if you get errors. Also it crunchs faster if the screensaver is disabled.
If you set the memory prefs higher (via the website or directly with the BOINC prefs) the BOINC client would not go into the wait for memory.

---

The screensaver is only additional an has no benefit for the science, you can disable it if you get errors. Also it crunchs faster if the screensaver is disabled.

Where is the "disable screensaver" control? I can't find it.

In Mac OSX, I have screensaver activation set to "never", but I don't think this is to what you are referring.

The only relevant control is the button command "show graphics", which is only active when a running task is selected on the Tasks page. (This button was permanently "greyed out" when using the Alex Kan optimized version v5.13.) I have found no way of switching this button permanently off. And a search of all the Preference options was not productive. Maybe, you are referring to an edit a file in one of the BOINC data subfolders? If so, details would be appreciated.

The proliferation of pending tasks awaiting validation (with 2 successes flagged), that were obtained before I changed from the Alex Kan v5.13, seem to have dried up completely now with Version 5.22. Maybe this is due to the "weeding out" of the redundant tasks rather than a problem in the workings of Alex Kan's version?

Keith

While 5.22 seems to be running, it is not generating as much credit per hour of run time as 5.18 did. On my G5, World Community Grid has and average of 187 and SETI is at 108. In the past, SETI tended to give a little more credit that World Community Grid when running side by side on my system. I have both projects set to run 100% on my system so they should be producting numbers that are close to each other. It appears the problem is because the software is running slow and not a problem in the work granted for a work unit. When I compare my run times with other processors that should be about the same speed, my run times are far larger. Nothing has changed on my system other that going to 5.22.

---

When I compare my run times with other processors that should be about the same speed, my run times are far larger. Nothing has changed on my system other that going to 5.22.

Have you comapred WUs with the same granted credits ? - The WUs differs heavly in the crunching time, so only WUs with the same credits are compareable.

---

Have you comapred WUs with the same granted credits ? - The WUs differs heavly in the crunching time, so only WUs with the same credits are compareable.

My per day output when compaired to World Community grid running side by side is down. That says my system is running longer to provide the same number of credits. Not to mention the fact that work units are taking 12 hours or more to complete when they were taking less than 6 hour before 5.22. Granted the work unit could have changed but I should still be able to turn out 170 to 180 credits a day instead of 100.

---

Have you comapred WUs with the same granted credits ? - The WUs differs heavly in the crunching time, so only WUs with the same credits are compareable.

My per day output when compaired to World Community grid running side by side is down. That says my system is running longer to provide the same number of credits. Not to mention the fact that work units are taking 12 hours or more to complete when they were taking less than 6 hour before 5.22. Granted the work unit could have changed but I should still be able to turn out 170 to 180 credits a day instead of 100.

Yes. This normal. The credits per runtime differs by the projects. The different BOINC projects working together on this issue and make the runtime/credits more comparable between different project.
Also the new SETI app 5.18 and 5.2x are the new mulitbeam applications which clames more credits compared to the older 5.12...5.15. But sometimes, if your WU would be been validated with non multibeam results, the cranted credits are lower.

---

Yes. This normal. The credits per runtime differs by the projects. The different BOINC projects working together on this issue and make the runtime/credits more comparable between different project.
Also the new SETI app 5.18 and 5.2x are the new mulitbeam applications which clames more credits compared to the older 5.12...5.15. But sometimes, if your WU would be been validated with non multibeam results, the cranted credits are lower.

Understand, I spotted this problem the first day the code was loaded into my systems. I have been watching it for several days now and I have been able to refine the numbers. In my years of programming, I know when a program is not working the way it did before and I see it here. Also, you are unable to see it because your system is Intel and mine is Power PC. I am not sure how to send you graphs but if I were to screen capture my Statistics screen and send it to you, it would be clear that SETI has a problem. In checking against MicroSoft machines, there has to be a problem in the code where it is wasting time that should be used for crunching.

---

Yes. This normal. The credits per runtime differs by the projects. The different BOINC projects working together on this issue and make the runtime/credits more comparable between different project.
Also the new SETI app 5.18 and 5.2x are the new mulitbeam applications which clames more credits compared to the older 5.12...5.15. But sometimes, if your WU would be been validated with non multibeam results, the cranted credits are lower.

Understand, I spotted this problem the first day the code was loaded into my systems. I have been watching it for several days now and I have been able to refine the numbers.

The credits are given by the projects. Some projects weight the credits different than other. So you get at one project 10 credits and at other 15 per hour. This is all.

Also, as I have asked before, have you verified your results with other PPC hosts which claims the same credit. The runtimes of the SETI task are variable and so credits are variable. You can only compare WUs with the same claimed credits.

In my years of programming, I know when a program is not working the way it did before and I see it here.

And what excatly is not working as before ? Could you please describe it in detail.
Also, 5.22 is a different application compared than 5.1x.

Also, you are unable to see it because your system is Intel and mine is Power PC. I am not sure how to send you graphs but if I were to screen capture my Statistics screen and send it to you, it would be clear that SETI has a problem. In checking against MicroSoft machines, there has to be a problem in the code where it is wasting time that should be used for crunching.

This has nothing to do with a difference on Intel and PPC Macs. As I have stated in previous posts, this credit difference is OK and normal.

---

[quote]Also, as I have asked before, have you verified your results with other PPC hosts which claims the same credit. The runtimes of the SETI task are variable and so credits are variable. You can only compare WUs with the same claimed credits.

[quote]
Think about what you are saying. This change occured between 51.8 and 5.22 on my system. Nothing else was change on my system other than the code went from 5.18 to 5.22. I have debugged many problems and am aware how changes can go wrong so I keep track of anything that may alter the way my system runs. Now if you say that 5.22 will grant less work for the same amount of effort, it's time we all consider crunching for another project. I am currently sticking with SETI to provide some useful information so the problem can be looked at and resolved. If you are not going to look at what I have provided objectively and instead of trying to poke holes in it, they we are not going to accomplish anything.

---