1)
Message boards :
Number crunching :
Got Multiple WU's to run on my GTX 660TI but lost std CPU Apps
(Message 56755)
Posted 5 Jan 2013 by TeeVeeEss Post: In BOINC 7.0.42 you can use app_config.xml in stead of app_info.xml. Set the Milkyway-project to No New Work (NNW), finish all your current Milkyway-tasks. Stop BOINC. Delete your app_info.xml (first backup a copy!) and create the file app_config.xml in the same directory with content: <app_config> <app> <name>milkyway</name> <gpu_versions> <gpu_usage>0.5</gpu_usage> <cpu_usage>0.05</cpu_usage> </gpu_versions> </app> </app_config> Start BOINC. This should allow crunching CPU-tasks if you have selected those in your Milkyway-preferences. Personally I don't crunch Milkyway on the CPU. The GPU does it much more efficient, so i have not tested the above. So please report back if the above app_config.xml allows the CPU-crunching. If not: ask some other person for the extra CPU-lines needed in the app_info.xml. Edit: the complete app_info.xml for CPU-crunching is already in another thread: http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3064&nowrap=true#56288 |
2)
Message boards :
Number crunching :
Computation errors
(Message 56753)
Posted 5 Jan 2013 by TeeVeeEss Post: First set the project to No New Work (NNW). When all Milkyway-work is finished: reset the Milkyway-project. Stop BOINC. Check if the project-directory (..\projects\milkyway.cs.rpi.edu_milkyway) is empty. If not: manually delete all files in that directory. Close down your computer: shut down and power off. Start your computer. Start BOINC. Allow new work for Milkyway. If your N-Body CPU-tasks still end in error after 0 seconds: ask someone else for help in this thread :) |
©2025 Astroinformatics Group