I did what you told me. Do I have to restart my system for it to take effect? Because I re started BOINC and it did nothing... :(
Printable View
I did what you told me. Do I have to restart my system for it to take effect? Because I re started BOINC and it did nothing... :(
In the event log it should at least mention the fact that it found the app_config.xml
Be sure to have boinc closed down before adding the app_config.xml to the project directory and indeed reboot to let it take effect
NOW the Milky-way race started today and I plum forgot to start running this program. I would like to do the same scenario with Milkyway since its a heavy demand of one CPU as well as Collatz! The link to be inserted into the app+config file should be similar or any change to it other then the link?
No, it is not: http://milkyway.cs.rpi.edu/milkyway/...?id=2787#53305
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.02_windows_x86_64__ope ncl_nvidia.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>102</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>cuda</plan_class>
<coproc>
<type>CUDA</type>
<count>0.5</count>
</coproc>
<cmdline></cmdline>
<file_ref>
<file_name>milkyway_separation_1.02_windows_x86_64 __opencl_nvidia.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.00_windows_x86_64.ex e</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>100</version_num>
<cmdline></cmdline>
<file_ref>
<file_name>milkyway_separation_1.00_windows_x86_64 .exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.84_windows_x86_64__mt.exe </name>
<executable/>
</file_info>
<file_info>
<name>libgomp_64-1.dll</name>
<executable/>
</file_info>
<file_info>
<name>pthreadGC2_64.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>84</version_num>
<plan_class>mt</plan_class>
<avg_ncpus>4</avg_ncpus>
<max_ncpus>4</max_ncpus>
<cmdline>--nthreads=4</cmdline>
<file_ref>
<file_name>milkyway_nbody_0.84_windows_x86_64__mt. exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libgomp_64-1.dll</file_name>
</file_ref>
<file_ref>
<file_name>pthreadGC2_64.dll</file_name>
</file_ref>
</app_version>
</app_info>
I have tried everything and still keep getting BOINC notices telling me it isn't working yet. I think I rebooted my system 10 times.... Thanks for telling me this link. So this link will work on an ATI since they are discussing Nvidia type GPU's as well?
This is my app config for collatz use it on all machines cuda and ati
<app_config>
<app>
<name>solo_collatz</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app>
<app>
<name>mini_collatz</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app>
<app>
<name>large_collatz</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app>
</app_config>
Use full link is
http://boinc.thesonntags.com/collatz...ad.php?id=1009
Milkyway
<app_config>
<app>
<name>milkyway_separation__modified_fit</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app>
<app>
<name>milkyway</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app>
</app_config>
Nvidia Ok Ati i have not manage too get my cards get any work R7 and R9
And it should be in the projects folder för milky way ex \\Acer\boinc\projects\milkyway.cs.rpi.edu_milkyway
My MilkyWay project folder is :
C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_ milkyway
I do *not* use a app_config.xml for my HD 4770, crunching MilkyWay.
Neither do I use one for the GT 630 that is running in my girlfriend's PC, nor the GTX 650 that runs my 2nd Ubuntu box -both times while crunching MilkyWay.
WoW Thanks B I appreciate the feedback and helpful tips. I got reading on that first link B and found myself still reading some 45 replies later. Looks like there is alot to learn in this realm of crunching. Yes I have an R9 and I am going to keep reading to isolate a solution before I proceed. Thanks again Dirk really appreciate the helpful advice!
The tricky part could be the actually creating the file with notepad as you have to set it to all types on save and save it with the name app_config.xml
Notepad likes to make everything a txt file and windows likes to hide the file types usually.
I have recently found you can edit the file and with boinctasks tell boinc to read the file then there is no need to restart boinc. This comes in handy when running multiple cores on a project that doesn't checkpoint very often(WCG Clean energy 2).
Jason I think you mean using this program BOINC Tasks Its best to read the manual before downloading the program. Will I have to load each project into this program. For some reason it does not say anything about this maneuver!
B I completed your install of the app_config.xml into the Milkyway folder. And Viola it works. Now I adjusted the usage parameters to 1.0 from 0.5 as I need the system to operate flawlessly with all the other stuff I am doing at the same time. Thank You Jason, I need to read more about BOINCTasks, that program has me intrigued. Yet I am not sure of all the details till I would download it and try it out. So there is always tomorrow. :blob3:
Great :) Adjusying levels is the key . Boinc task works fine i have been using it for years now.
It is perfect when you want too creat a app_config but the file int the right foler and you will get a message that tells you the right names.
I believe on your main machine setup should be simple. It communicates and gets your pojects and info similar to the way boinc manager does. It is very helpful when managing more machines and even ones with remote locations if the IP doesn't change very often.
Nice tool to test your network security. It utterly fails to detect other BOINC crunching machines on my network (even when BOINC Tasks itself is also installed and active on other machines).
Have you created the two nessesary file wich has too bee in your boinc folder on every machine
gui_rpc_auth.cfg contains the boinc password
remote_hosts.cfg contains the ip of hosts that have right too access boinc
And have you scanned for computers in boinctask
I have scanned for computers, using their IP-address (and address range).
The said *.cfg files were missing though...
Use notepad too create the files
use the same password on all machines makes it easy too manage
Here the link too the manual it explains the proccess
http://www.efmer.eu/boinc/boinc_tasks/manual.html
Example of files
gui_rpc_auth.cfg save with this name
only the password
69eda0552bd85ff3dabfb9xxxxxx
remote_hosts.cfg save with this name
192.168.1.60
192.168.1.61
192.168.1.62
192.168.1.63
192.168.1.64
Thats all the information needed in the files
Dirk or B or Jason - ON my collatz work units I am also running Mini-collatz. To change the app_config.xml so that the computer sees both solo and mini how do I assign the document so one does not cancel out the other?
e.g. like this:
<app_config>
<app>
<name>solo_collatz</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>mini_collatz</name>
<gpu_versions>
<gpu_usage>.5</gpu_usage>
<cpu_usage>.5</cpu_usage>
</gpu_versions>
</app>
</app_config>
I have now downloaded, installed and am operating BOINC Tasks! Nice program. :blob3: What I am yearning to explore is the app_config exploratory options. How do I go about placing these morsels of success into this program. I am yet to find this explained in the Manual ?
There are way too many options to choose from:
<set_cc_config>
<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<task>1</task>
<android_debug>0</android_debug>
<app_msg_receive>0</app_msg_receive>
<app_msg_send>0</app_msg_send>
<async_file_debug>0</async_file_debug>
<benchmark_debug>0</benchmark_debug>
<checkpoint_debug>0</checkpoint_debug>
<coproc_debug>0</coproc_debug>
<cpu_sched>0</cpu_sched>
<cpu_sched_debug>0</cpu_sched_debug>
<cpu_sched_status>0</cpu_sched_status>
<dcf_debug>0</dcf_debug>
<disk_usage_debug>0</disk_usage_debug>
<file_xfer_debug>0</file_xfer_debug>
<gui_rpc_debug>0</gui_rpc_debug>
<heartbeat_debug>0</heartbeat_debug>
<http_debug>0</http_debug>
<http_xfer_debug>0</http_xfer_debug>
<mem_usage_debug>0</mem_usage_debug>
<network_status_debug>0</network_status_debug>
<notice_debug>0</notice_debug>
<poll_debug>0</poll_debug>
<priority_debug>0</priority_debug>
<proxy_debug>0</proxy_debug>
<rr_simulation>0</rr_simulation>
<rrsim_detail>0</rrsim_detail>
<sched_op_debug>0</sched_op_debug>
<scrsave_debug>0</scrsave_debug>
<slot_debug>0</slot_debug>
<state_debug>0</state_debug>
<statefile_debug>0</statefile_debug>
<suspend_debug>0</suspend_debug>
<task_debug>0</task_debug>
<time_debug>0</time_debug>
<trickle_debug>0</trickle_debug>
<unparsed_xml>0</unparsed_xml>
<work_fetch_debug>0</work_fetch_debug>
</log_flags>
<options>
<abort_jobs_on_exit>0</abort_jobs_on_exit>
<allow_multiple_clients>0</allow_multiple_clients>
<allow_remote_gui_rpc>0</allow_remote_gui_rpc>
<client_new_version_text></client_new_version_text>
<client_version_check_url>http://boinc.berkeley.edu/download.php?xml=1</client_version_check_url>
<client_download_url>http://boinc.berkeley.edu/download.php</client_download_url>
<disallow_attach>0</disallow_attach>
<dont_check_file_sizes>0</dont_check_file_sizes>
<dont_contact_ref_site>0</dont_contact_ref_site>
<exit_after_finish>0</exit_after_finish>
<exit_before_start>0</exit_before_start>
<exit_when_idle>0</exit_when_idle>
<fetch_minimal_work>0</fetch_minimal_work>
<fetch_on_update>0</fetch_on_update>
<force_auth>default</force_auth>
<http_1_0>0</http_1_0>
<http_transfer_timeout>300</http_transfer_timeout>
<http_transfer_timeout_bps>10</http_transfer_timeout_bps>
<max_event_log_lines>2000</max_event_log_lines>
<max_file_xfers>8</max_file_xfers>
<max_file_xfers_per_project>2</max_file_xfers_per_project>
<max_stderr_file_size>0</max_stderr_file_size>
<max_stdout_file_size>0</max_stdout_file_size>
<max_tasks_reported>0</max_tasks_reported>
<ncpus>-1</ncpus>
<network_test_url>http://www.google.com/</network_test_url>
<no_alt_platform>0</no_alt_platform>
<no_gpus>0</no_gpus>
<no_info_fetch>0</no_info_fetch>
<no_priority_change>0</no_priority_change>
<os_random_only>0</os_random_only>
<proxy_info>
<socks_server_name></socks_server_name>
<socks_server_port>80</socks_server_port>
<http_server_name></http_server_name>
<http_server_port>80</http_server_port>
<socks5_user_name></socks5_user_name>
<socks5_user_passwd></socks5_user_passwd>
<http_user_name></http_user_name>
<http_user_passwd></http_user_passwd>
<no_proxy></no_proxy>
</proxy_info>
<rec_half_life_days>10.000000</rec_half_life_days>
<report_results_immediately>0</report_results_immediately>
<run_apps_manually>0</run_apps_manually>
<save_stats_days>30</save_stats_days>
<skip_cpu_benchmarks>0</skip_cpu_benchmarks>
<simple_gui_only>0</simple_gui_only>
<start_delay>0</start_delay>
<stderr_head>0</stderr_head>
<suppress_net_info>0</suppress_net_info>
<unsigned_apps_ok>0</unsigned_apps_ok>
<use_all_gpus>0</use_all_gpus>
<use_certs>0</use_certs>
<use_certs_only>0</use_certs_only>
<vbox_window>0</vbox_window>
</options>
</cc_config>
</set_cc_config>
Basically you only need the app_config.xml files for those (sub)projects that use an OpenCL application.
You can best monitor the various project forums/fora to look for tips about the best settings per project.
Most projects leave out much lines, Bitcoin Utopia uses the most at the moment.
I think you have to have both BOINC mgr and BOINC tasks running at the same time. I can not for the life of me get one to work without the other! :sad5:
OK so how to do know what to put in the BOINC Tasks program to make it run, everything comes up with red letters which I am assuming means its not right yet?
This is what I use for Seti@Home under Win7 with a HD 4770 as GPU (didn't make it up myself! Must have come with the Lunatics optimized app!):
Code:<app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</name>
</file_info>
<file_info>
<name>AstroPulse_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE_CPU_r1797.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE_CPU.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_intelx86</platform>
<cmdline></cmdline>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
<cmdline></cmdline>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</name>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</name>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
</app_info>
Please copy your error messages in order to be able to helpQuote:
Originally Posted by Nflight
I finally had a breather in time Dirk: Here is my syntax and it isnt' working, Jason or B you assistance could be useful as the Wow campaign is starting on Friday and I would like to get this to work by then!
<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_enhanced</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app_config>
Your syntax -which misses the second </app>- will only work with two GPUs, but then uses a full CPU core and a GPU per WU. Unless you are crunching with a heavy OpenCL application, that's not a savvy way.
Assuming -dangerous in ICT- that you have but one GPU but want to crunch two WUs at a time change it to:
You'd best use the optimized Lunatics driver, that comes with its own app_config, tailored to the capabilities of your CPU/GPU (look them up before/during the setup).Code:<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.5</gpu_usage>
<cpu_usage>.2</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_enhanced</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.5</gpu_usage>
<cpu_usage>.2</cpu_usage>
</gpu_versions>
</app>
</app_config>
Dirk I found it, took numerous tries but I finally got one cpu and one GPU working for Seti
<app_config>
<app>
<name>astropulse_v6</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
</app_config>
Woo Hoo no more crashing! :blob3:
Let me explain my logic here in doing this Dirk. The old way of just letting it work with one GPU and 8 CPU work Units created a void where sometimes the GPU work units would last nearly 2 hours and 40 minutes. This was what I was seeing most of the time, some would actually fall in the realm of 30 or so minutes but most were very long. Then the App_config fix and walla I now have a surplus of ATI work units waiting to be added over to points as it now take no more then 20 minutes per ATI work unit and an average of 16 minutes for each one of them to be completed. Worth 93 points each makes for a happy cruncher! Too bad the work units waiting to be validated are getting cramped but they will start to fall in place and add numerous points to the competition. Woo Hoo :blob3:
I was talking to my Computer dude about a an upgrade to my GPU, should I wait to see what comes out this summer or go ahead and purchase (3) R9 290 X2's ?
You got big plans, GPU-wise?
Are they all three to go in one system?
Can your PSU take that much power?
Can the cooling take the rise in temperature?
Can your wallet take the KWh?
After six years I am refurbishing my existing computers needs like a new Power Supply, and I am replacing my existing 6 fans with replacements, all are less then optimal cooling effectiveness. I also got a new toy, a new GPU... so things are looking up to lasting another several years if needed.
140mm fans - You still can't go wrong with Noctua. Remember: bigger fans displace more air than smaller fans at the same rpm, and are quieter than smaller fans at the same rpm (rounds per minute).Quote:
Originally Posted by Nflight
700-750 Watt PSUs - Same with Corsair / Seasonic. Go for gold -at least. Try platinum or titanium certification if the budget allows it.
Agree with Dirk's advice. Cooling is very important. I always buy Noctua fans and recently their CPU coolers. Went thought a phase of buying Corsair Hydro series water coolers but had a disaster where one leaked after a few years of continuous usage. It took out 2 GTX970 GPUs and a motherboard. No water for me now :)
sorry to hear about the corsair leaking on your equipment. I have several of those and hope they don't fail taking out equipment like that. Where did it start leaking?Quote:
Originally Posted by vaughan
Radiator sprung a leak and it was at the top of the case so the fluid leaked over most everything.
I do appreciate the replies gentlemen. I have acquired a 1200 Watt PSU from Corsair, it is installed, I also got that GTX-1660 which is OC'd installed and working.. The fans are the problem, I was sourcing all fans from Best Buy but they did not fit and now I am dealing with NewEgg for my Noctua fans, I need the right connector fitting before I order them. Volume of air moving through to cool my system is critical. High volume of air is important for 4 fans, two take care of the water block on the CPU, and the other two need to push the air through the system to cool of my very hot VRAM dealing with Universe. Thank you gentlemen for all your insight...
Seems my 8 week old power supply blew up, now waiting on a replacement. Possibly two more weeks till my return, CIAO