Questions and Answers :
Macintosh :
Upgrading s@h from 513 to 517 x problems with bug combining s@h_ppc_v6 and s@hβ
Message board moderation
Author | Message |
---|---|
neubaum Send message Joined: 19 Aug 06 Posts: 29 Credit: 118,710 RAC: 0 |
After attaching to s@h (setiathome_5.17_powerpc-apple-darwin ) I uppgraded the 517 client to seti_enhanced-ppc-v6 and (after some minor problems) found it cruching on satisfacorily until I attached to s@hβ and got problems due to some bug in BOINC, problems that at the moment are intractable to me ( see thread 33446 though). Anyhow, I aborted the delivery of new tasks from s@hβ, reinstalled BOINC from back-up and after that my s@hWU:s are crunched by setiathome_5.13_powerpc-apple-darwin! Why 513 and not 517? I'd like to have 517 back on s@h! As to the upgrading to seti_enhanced-ppc-v6 and resuming running s@hβ I can wait for a proper debugging of BOINC or whatever it takes for a safe run of s@h and s@hβ together. |
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 |
Where do get the SETI 5.17 ? - 5.17 is only for testing in the BETA project, and not for use in the main project. If you wan't to use the optimized app by Alex Kan, you need to stop the boinc client, and put the app_info.xml and the binary into the projects/setiathome.berkeley.edu folder. But attention, if you place the app_info.xml, the boinc client send back all the WUs in the cache and the WUs in progress. |
neubaum Send message Joined: 19 Aug 06 Posts: 29 Credit: 118,710 RAC: 0 |
Where do get the SETI 5.17 ? - 5.17 is only for testing in the BETA project, and not for use in the main project. Well I guess you haven't read my correspondence with Odysseus (thread 33446) and I'm not sure it really eludicates the matter. Anyhow, when I reinstalled BOINC from my backup, after I'd removed the upgraded Alex Kahn binary and the app_info.xml from the projects/setiathome.berkeley.edu folder, the 513 client was installed, as it should according to you. The problem is that I was stunned by how the graphic display looked like. I'd never seen it before ... these one-dimensional waves moving foreward, the flat progression-bar and no nice green frame and so on. I was used to those happily marching two-dimensional bars getting slimmer and slimmer. As I remember it I successfully attached to s@h for some day or so before I upgraded to seti_enhanced-ppc-v6. The problems began when I attached to s@hβ. A bug in BOINC Odysseus wrote. I got lost after that. The only explanation I can come up with is that I never looked at the graphic display before upgrading to seti_enhanced-ppc-v6 and that Kan's app builds on (or is?) the 517 or at least use the same graphic display. I have a good visual memory but could perhaps be wrong about how swift I was to upgrade. I'm pretty sure though that when I attached to the project s@hβ I was allready used to the 517-graphic display. I guess these two projects are not actually ment to be run in parallell and that s@h BETA (517 ) should be replacing the old s@h (513) some day. I think I'd like to upgrade oncemore to seti_enhanced-ppc-v6. My question is, must I not detach completely from BETA (and lose it's creds) to avoid any conflict between BETA and the ordinary s@a. Odysseus seems to run them together without problem. I guess I was not able to follow his instructions correctly (thread 33446 again). Maybe there is a problem still residing in BOINCs main folder, in one of all those xml-file, as long as I keep s@h BETA in my library and it sufaces once again when I put Kan's app_info.xml file back again with the binary. |
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 |
Thank you for the clarifications. It is posible to use the SETI main and the SETI Beta app within one installation. - I have it running successfull on HPUX, too. I am not shure, but it looks like your problems are caused from the applications mismatch (both applications are named setiathome_enhanced) between the two different projects. My app_info.xml from the main project : <app_info> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>setiathome-5.12.hppa2.0w-hp-hpux11i</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>512</version_num> <file_ref> <file_name>setiathome-5.12.hppa2.0w-hp-hpux11i</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>517</version_num> <file_ref> <file_name>setiathome-5.12.hppa2.0w-hp-hpux11i</file_name> <main_program/> </file_ref> </app_version> </app_info> And from the BETA project : <app_info> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>setiathome-5.17.hppa2.0w-hp-hpux11i</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>512</version_num> <file_ref> <file_name>setiathome-5.17.hppa2.0w-hp-hpux11i</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>517</version_num> <file_ref> <file_name>setiathome-5.17.hppa2.0w-hp-hpux11i</file_name> <main_program/> </file_ref> </app_version> </app_info> |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.