Message boards :
Number crunching :
how to install newly compiled seti app in linux?
Message board moderation
Author | Message |
---|---|
Ben Send message Joined: 15 Jun 99 Posts: 54 Credit: 60,003,756 RAC: 150 |
So I finally managed to compile the seti app for Ubuntu Cosmic using AMD opencl /ROCm but I don't know how to get it installed. The files generated are: 6016952 Nov 15 16:08 MBv8_8.18r3400_sse3_clGPU_x86_64-pc-linux-gnu 6752544 Nov 15 16:08 setiathome-8.18.x86_64-pc-linux-gnu.debug 6752544 Nov 15 16:08 seti_boinc What should my app_config.xml look like for instance? Also, if I want seti to run on both GPU and CPU how do I do that? setiathome already downloads a working opencl astropulse: astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100 Thank you. |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
You will have to write your own app_info.xml so that you can call out your own MB application. https://boinc.berkeley.edu/wiki/Anonymous_platform for the structure documentation for creating your own anonymous platform. You will have to define your application filename references in the file. I'm not sure what your seti_boinc file is though? Your own version of the boinc client or Manager? Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
RueiKe Send message Joined: 14 Feb 16 Posts: 492 Credit: 378,512,430 RAC: 785 |
So I finally managed to compile the seti app for Ubuntu Cosmic using AMD opencl /ROCm but I don't know how to get it installed. That is great progress to get a seti MB app to compile in a newer linux release. I had put a significant amount of work to get the CPU app to compile, but found that it produces invalid results. I hope to get back to working with it again. I have also tried running the current optimized app on a system with ROCm drivers but got sporadic invalid results. Very curious how yours will workout. Perhaps having an app compiled with the ROCm library will make a difference. I suggest you bench test it with a number of WUs before you put it in production. Here is my linux app_info file: <app_info> <app> <name>setiathome_v8</name> </app> <file_info> <name>MBv8_8.04r3306_sse42_linux64</name> <executable/> </file_info> <app_version> <app_name>setiathome_v8</app_name> <version_num>805</version_num> <platform>x86_64-pc-linux-gnu</platform> <cmdline>-nographics </cmdline> <file_ref> <file_name>MBv8_8.04r3306_sse42_linux64</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>804</version_num> <platform>x86_64-pc-linux-gnu</platform> <cmdline>-nographics </cmdline> <file_ref> <file_name>MBv8_8.04r3306_sse42_linux64</file_name> <main_program/> </file_ref> </app_version> <app> <name>setiathome_v8</name> </app> <file_info> <name>MBv8_8.22r3584_sse2_clAMD_HD5_x86_64-pc-linux-gnu</name> <executable/> </file_info> <file_info> <name>MultiBeam_Kernels_r3584.cl</name> </file_info> <file_info> <name>mb_cmdline_VegaOptimized_ati5_SoG.txt</name> </file_info> <app_version> <app_name>setiathome_v8</app_name> <platform>x86_64-pc-linux-gnu</platform> <version_num>822</version_num> <plan_class>opencl_ati5_sah</plan_class> <coproc> <type>ATI</type> <count>1</count> </coproc> <avg_ncpus>0.5</avg_ncpus> <max_ncpus>0.99</max_ncpus> <file_ref> <file_name>MBv8_8.22r3584_sse2_clAMD_HD5_x86_64-pc-linux-gnu</file_name> <main_program/> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_VegaOptimized_ati5_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> </app_info> GitHub: Ricks-Lab Instagram: ricks_labs |
Ben Send message Joined: 15 Jun 99 Posts: 54 Credit: 60,003,756 RAC: 150 |
Thanks this helped a bunch. |
©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.