Questions and Answers :
Unix/Linux :
Migrating to self-compiled seti-client?
Message board moderation
Author | Message |
---|---|
frank_0987923 Send message Joined: 31 Jan 04 Posts: 1 Credit: 304,920 RAC: 0 |
Hi, maybe this question was already answered but i didn't find anything. I run boinc+seti for a while now, first the downloaded binarys and now boinc runs self-compiled. How can i get boinc to use my self-compiled seticlient instead of the downloaded one? Yes, i read the part with app_info.xml but i don't want to touch the running configuration. Is there an existing way to test the new config without touching the old one? regards, frank |
Ned Slider Send message Joined: 12 Oct 01 Posts: 668 Credit: 4,375,315 RAC: 0 |
If you don't want to mess with your existing configuration, just set up a new directory and test from there. Also, before you start using your self-compiled seti client, I would run the test reference work unit and compare the results.sah file to a run with the standard seti client. We found that when using certain maths optimisations for the compile the client produced invalid results. It may be faster but if the results are invalid you're wasting your time and you won't get any credit. Ned *** My Guide to Compiling Optimised BOINC and SETI Clients *** *** Download Optimised BOINC and SETI Clients for Linux Here *** |
Hans Dorn Send message Joined: 3 Apr 99 Posts: 2262 Credit: 26,448,570 RAC: 0 |
Just make sure you set "Connect to network about every 0.1 days", because the new client won't process your currently cached WUs. Regards Hans |
©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.