Message boards :
Number crunching :
astropulse GPU
Message board moderation
Previous · 1 · 2 · 3
Author | Message |
---|---|
Vipin Palazhi Send message Joined: 29 Feb 08 Posts: 286 Credit: 167,386,578 RAC: 0 |
Thanks for the info Claggy. |
JarrettH Send message Joined: 14 Nov 02 Posts: 97 Credit: 25,385,250 RAC: 95 |
How do you install the Astropulse GPU app? Simple instructions would be enormously helpful. Thanks :D |
Mike Send message Joined: 17 Feb 01 Posts: 34250 Credit: 79,922,639 RAC: 80 |
Just download the new AP package from there. http://setiathome.berkeley.edu/forum_thread.php?id=70723 Shut down Boinc. Copy all files to you project directory. Open **NV_r1761.aistub and copy appinfo section and paste it into your appinfo.xml. Restart boinc. With each crime and every kindness we birth our future. |
JarrettH Send message Joined: 14 Nov 02 Posts: 97 Credit: 25,385,250 RAC: 95 |
Thank you! And how do you figure out the number of compute units your GPU has? Will it just start running my Astropulse units on the GPU from now on? I had Astropulse work prior. Do I have to remove the old Astropulse V6 CPU references? High end cards (more than 12 compute units) -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096 -hp Mid range cards (less than 12 compute units) -unroll 10 -ffa_block 6144 -ffa_block_fetch 1536 -hp entry level GPU (less than 6 compute units) -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -hp Would my 550 Ti be more entry or mid-range? <app> |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Thank you! Read the stderr.txt of a completed task, it'll say how many compute units your GPU has. Rather than putting cmdline parameters in the app_info, put them on the ap_cmdline_win_x86_SSE2_OpenCL_NV.txt file instead, means you can change them, any they will take on the next app start, rather than the next Boinc restart, at the moment you put the cmdline parameters in only the 2nd <app_version> section, and will so end end being unused: <app> Claggy |
JarrettH Send message Joined: 14 Nov 02 Posts: 97 Credit: 25,385,250 RAC: 95 |
Ohhh I see. Do I need to add the cmdline tags around it when placed in ap_cmdline_win_x86_SSE2_OpenCL_NV? I'll check for that file, but here's a workunit: http://setiathome.berkeley.edu/result.php?resultid=2815964854 multiProcs 4 ? |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Ohhh I see. Do I need to add the cmdline tags around it when placed in ap_cmdline_win_x86_SSE2_OpenCL_NV? No you don't need any tags, just -unroll 10 -ffa_block 6144 -ffa_block_fetch 1536 -hp will do. Double check once you complete an OpenCL task, it should be 4 too. Claggy |
©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.