Jean-Guy If you look you will see this is only the app and app version.
If this is working and you go to the colored app_info files in first post you should be able to paste this into that file after the last </app_version> and before the </app_info>
Curious about 2. too
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
Thanks for the above info OldChap. I am now running a stress test on my GPU crunching rig. When it is successfully completed I will likely switch the app_info file to depict the info that you and Retro77 have provided (likely using modded 1 for <max ncpus>).Originally Posted by OldChap
For my edification, can you please tell me how you guys get those sliding windows in your posts for displaying app_info files or BOINC manager log entries?
Thanks,
Jean-Guy
When posting goto Go Advanced next to Post Quick Reply and at top of page with the options for Bold and underline etc towards the right side you will see # which wraps Code tags around whatever text etc that you write.
Of course you can type it straight in too using [ code ] and [ /code ] (without the spaces)
I am running that full app_info on one rig right now and it is crunching CPU just fine....then when it gets an odd GPU task or two it picks those up and runs them too in a similar fashion to running without an app_info. If a bunch of GPU tasks arrive it should revert to running GPU but with a core set aside for completing the cpu work. Once GPU is running I will go to the profile that this rig runs on and de-select the projects that run cpu etc.
Last edited by OldChap; 11-23-2012 at 11:19 AM.
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
Code:Thanks again OldChap, your timely responses are much appreciated... Jean-Guy
As with many of the folks at XS WCG, you too seem endued with a penchant for disseminating information, so I am sure that such edifying morsels will be passed on in future to folks in need.
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
Hey Jean-Guy:
1.) I had the x86 portion in there but I got errors about missing files. It DL them when I didn't have the app_info in there, only the x86_64 ones.
2.) Because I really cannot find a good definition for what they are supposed to be. I run the .125 so I can get 8 tasks running on the 2600k CPU. I had them both at .125 and it tried to run all 80 tasks I had in my queue at once
edit: with the recent word that HCC GPU tasks are trickling in, I am going to add the HCC info to the top. Is there any mods I need to do to the DFSL section in order to do what you are doing OldChap?
Last edited by retro77; 11-23-2012 at 12:37 PM.
If yours runs DSFL without app_info and you then add it and it still runs then all is good ....it is just a trial and error.
I got mine running all the projects in the coloured app_info normal first then added the big app_info and restarted....all ran OK except HCC CPU but that may have been due to having none already loaded. You could do the same but adding yours too to the list both before and after running app_info.
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
Hello again Retro77,
I am still a bit confused about what you say at 2. ... below:
My understanding is that <avg_ncpus> controls the number of CPU cores activated. For example, on a 2600K which already has 8 cores with HT, an <avg_ncpus>0.8</avg_ncpus> will give you 10 cores. The 10 = 1/number of threads you wish to run multiplied by the number of cores available so for 8 cores and 10 threads this would be 1/10*8=0.8. Your <max_ncpus> should be set at <max_ncpus>1.0</max_ncpus> if you only want 8 CPU cores. If you indeed entered <avg_ncpus>0.125</avg_ncpus> in your app_info file you then created 64 CPU cores [where X (# CPU cores wanted)=(1 x 8) / 0.125]1.) I had the x86 portion in there but I got errors about missing files. It DL them when I didn't have the app_info in there, only the x86_64 ones.
2.) Because I really cannot find a good definition for what they are supposed to be. I run the .125 so I can get 8 tasks running on the 2600k CPU. I had them both at .125 and it tried to run all 80 tasks I had in my queue at once
With a 2600K (HT active in BIOS), you already have 8 CPU cores available and thus only need to mod the <counts> #. Your settings should be:
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
<count>.125</count> (assuming one card this number is 1/number of threads you wish to run so 1 / 8=0.125)
In summary, "ncpus" entries are for the # of CPU core desired. The "count" entries control the number of GPU threads on each GPU(s) that is/are present on your MB.
For your consideration,
Jean-Guy
Ok, I updated my app info:
Its running 11 tasks with thisCode:<app> <name>dsfl</name> <user_friendly_name>Drug Search for Leishmaniasis</user_friendly_name> </app> <file_info> <name>wcgrid_dsfl_vina_6.25_windows_x86_64</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</name> <executable/> </file_info> <app_version> <app_name>dsfl</app_name> <version_num>625</version_num> <platform>windows_x86_64</platform> <avg_ncpus>.8</avg_ncpus> <max_ncpus>1</max_ncpus> <api_version>6.25</api_version> <file_ref> <file_name>wcgrid_dsfl_vina_6.25_windows_x86_64</file_name> <main_program/> </file_ref> <file_ref> <file_name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</file_name> <open_name>AutoDockVina64.exe</open_name> </file_ref> <file_ref> <file_name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</file_name> <open_name>graphics_app</open_name> </file_ref> </app_version>
edit: This is now running 8:
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
Last edited by retro77; 11-23-2012 at 03:15 PM.
Retro77,
You are getting closer to your wish. Something is causing an extra 11th task to be running but I cannot tell from the partial app_info file you posted above. Your app_info file seems to be missing this red portion:
Please post your full app info file and insure you do not have multiple entries for ncps and count settings.Code:<avg_ncpus>1.0</avg_ncpus> <max_ncpus>1.0</max_ncpus> <coproc> <type>ATI</type> <count>.125</count> </coproc>
Excuse the initial partial response. Computer locked and I had to reboot it. Overclock not quite perfect yet...
Last edited by jeanguy2; 11-23-2012 at 05:00 PM.
I was only running the DSFL so now ATI in it. But I added the HCC GPU and this is what I am running:
I am getting this in the event viewer:Code:<app_info> <app> <name>hcc1</name> <user_friendly_name>Help Conquer Cancer</user_friendly_name> </app> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name> <executable/> </file_info> <file_info> <name>hcckernel.cl.7.05</name> <executable/> </file_info> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <plan_class>ati_hcc1</plan_class> <avg_ncpus>1.0</avg_ncpus> <max_ncpus>1.0</max_ncpus> <coproc> <type>ATI</type> <count>.125</count> </coproc> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name> <main_program/> </file_ref> <file_ref> <file_name>hcckernel.cl.7.05</file_name> <open_name>hcckernel.cl</open_name> </file_ref> </app_version> <app> <name>dsfl</name> <user_friendly_name>Drug Search for Leishmaniasis</user_friendly_name> </app> <file_info> <name>wcgrid_dsfl_vina_6.25_windows_x86_64</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</name> <executable/> </file_info> <app_version> <app_name>dsfl</app_name> <version_num>625</version_num> <platform>windows_x86_64</platform> <avg_ncpus>1</avg_ncpus> <max_ncpus>1</max_ncpus> <api_version>6.25</api_version> <file_ref> <file_name>wcgrid_dsfl_vina_6.25_windows_x86_64</file_name> <main_program/> </file_ref> <file_ref> <file_name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</file_name> <open_name>AutoDockVina64.exe</open_name> </file_ref> <file_ref> <file_name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</file_name> <open_name>graphics_app</open_name> </file_ref> </app_version> </app_info>
Its working on a bunch of DSFL [CPU].Code:11/23/2012 5:55:41 PM | World Community Grid | No tasks sent 11/23/2012 5:55:41 PM | World Community Grid | No tasks are available for Drug Search for Leishmaniasis 11/23/2012 5:55:41 PM | World Community Grid | No tasks are available for Help Conquer Cancer 11/23/2012 5:55:41 PM | World Community Grid | No tasks are available for the applications you have selected. 11/23/2012 5:55:41 PM | World Community Grid | This computer has finished a daily quota of 1 tasks
Hello Retro I am Back,
Had to go and watch one my grandson play hockey. When I read your app_info file I see "<avg_ncpus>1</avg_ncpus>" for both hhc and DSFL. With these setting you will have the standard 8 CPU cores available from your 2600K. The count you have set for hcc is "<count>.125</count>. It is requesting 10 hcc threads. No count is set for GSFL. This appears to be interpreted by the software has requesting 1 threads. In summary you appear to have requested a total of 11 threads (10 hcc + 1 GFSL). To match the 8 cores available on your 2600K try managing the thread count settings for both hcc ans GFSL. Possible options:
1- hcc = <count>.25</count> and GFSL = <count>.25</count> This should yield 4 hcc thread and 4 GFSL threads for a total of 8.
2- hcc = <count>.166</count> and GFSL = <count>.5</count> This should yield 6 hcc thread and 2 GFSL threads for a total of 8.
Try and see if it works. Make sure that your online WCG profile matches the tasks that your are requesting. The library entries you posted could be due to lost WUs, you may have to exit and restart BOINC without the app_info file to reset it and then re-add the app_info file after deleting tasks that you do not want.
Good luck, I got to get back to fine tuning my overclock.
Last edited by jeanguy2; 11-23-2012 at 07:47 PM.
When I run this:
My video driver crashes.Code:<app_info> <app> <name>hcc1</name> <user_friendly_name>Help Conquer Cancer</user_friendly_name> </app> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name> <executable/> </file_info> <file_info> <name>hcckernel.cl.7.05</name> <executable/> </file_info> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <plan_class>ati_hcc1</plan_class> <avg_ncpus>1.0</avg_ncpus> <max_ncpus>1.0</max_ncpus> <coproc> <type>ATI</type> <count>.166</count> </coproc> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name> <main_program/> </file_ref> <file_ref> <file_name>hcckernel.cl.7.05</file_name> <open_name>hcckernel.cl</open_name> </file_ref> </app_version> <app> <name>dsfl</name> <user_friendly_name>Drug Search for Leishmaniasis</user_friendly_name> </app> <file_info> <name>wcgrid_dsfl_vina_6.25_windows_x86_64</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</name> <executable/> </file_info> <app_version> <app_name>dsfl</app_name> <version_num>625</version_num> <platform>windows_x86_64</platform> <avg_ncpus>1</avg_ncpus> <max_ncpus>1</max_ncpus> <count>.5</count> <api_version>6.25</api_version> <file_ref> <file_name>wcgrid_dsfl_vina_6.25_windows_x86_64</file_name> <main_program/> </file_ref> <file_ref> <file_name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</file_name> <open_name>AutoDockVina64.exe</open_name> </file_ref> <file_ref> <file_name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</file_name> <open_name>graphics_app</open_name> </file_ref> </app_version> </app_info>
And this: [if it's different, drinkin']
:
Code:<app_info> <app> <name>hcc1</name> <user_friendly_name>Help Conquer Cancer</user_friendly_name> </app> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name> <executable/> </file_info> <file_info> <name>hcckernel.cl.7.05</name> <executable/> </file_info> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <plan_class>ati_hcc1</plan_class> <avg_ncpus>1.0</avg_ncpus> <max_ncpus>1.0</max_ncpus> <coproc> <type>ATI</type> <count>.166</count> </coproc> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name> <main_program/> </file_ref> <file_ref> <file_name>hcckernel.cl.7.05</file_name> <open_name>hcckernel.cl</open_name> </file_ref> </app_version> <app> <name>dsfl</name> <user_friendly_name>Drug Search for Leishmaniasis</user_friendly_name> </app> <file_info> <name>wcgrid_dsfl_vina_6.25_windows_x86_64</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</name> <executable/> </file_info> <app_version> <app_name>dsfl</app_name> <version_num>625</version_num> <platform>windows_x86_64</platform> <avg_ncpus>1</avg_ncpus> <max_ncpus>1</max_ncpus> <count>.5</count> <api_version>6.25</api_version> <file_ref> <file_name>wcgrid_dsfl_vina_6.25_windows_x86_64</file_name> <main_program/> </file_ref> <file_ref> <file_name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</file_name> <open_name>AutoDockVina64.exe</open_name> </file_ref> <file_ref> <file_name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</file_name> <open_name>graphics_app</open_name> </file_ref> </app_version> </app_info>
Hello Retro7,
Sorry to see you are having such a hard time. I have been busy setting back a GPU ATI hcc1 WUs only app_info configuration on my rig. Are you still interested in running DSFL CPU WUs or are you switching back to ATI hcc1 GPU WUs only?
If you still want ATI hcc1 GPU anf DSFL then try this:
I adjusted the count in the ATI_hcc1 section to run 5 GPU WUs and deleted the count entry from the DFSL section. My thoughts are that if 5 CPU cores are taken up to assist GPU ATI_hcc1 WU processing, 3 cores should remain for DFSL processing. Make sure DFSL is selected in your online WCG profile. If regular hcc CPU WUs show up try deselecting hcc in online WCG profile.Code:<app_info> <app> <name>hcc1</name> <user_friendly_name>Help Conquer Cancer</user_friendly_name> </app> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name> <executable/> </file_info> <file_info> <name>hcckernel.cl.7.05</name> <executable/> </file_info> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <plan_class>ati_hcc1</plan_class> <avg_ncpus>1.0</avg_ncpus> <max_ncpus>1.0</max_ncpus> <coproc> <type>ATI</type> <count>.2</count> </coproc> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name> <main_program/> </file_ref> <file_ref> <file_name>hcckernel.cl.7.05</file_name> <open_name>hcckernel.cl</open_name> </file_ref> </app_version> <app> <name>dsfl</name> <user_friendly_name>Drug Search for Leishmaniasis</user_friendly_name> </app> <file_info> <name>wcgrid_dsfl_vina_6.25_windows_x86_64</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</name> <executable/> </file_info> <file_info> <name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</name> <executable/> </file_info> <app_version> <app_name>dsfl</app_name> <version_num>625</version_num> <platform>windows_x86_64</platform> <avg_ncpus>1</avg_ncpus> <max_ncpus>1</max_ncpus> <api_version>6.25</api_version> <file_ref> <file_name>wcgrid_dsfl_vina_6.25_windows_x86_64</file_name> <main_program/> </file_ref> <file_ref> <file_name>wcgrid_dsfl_vina_prod_x86_64.exe.6.25</file_name> <open_name>AutoDockVina64.exe</open_name> </file_ref> <file_ref> <file_name>wcgrid_dsfl_gfx_prod_x86_64.exe.6.25</file_name> <open_name>graphics_app</open_name> </file_ref> </app_version> </app_info>
Hope this helps you,
Jean-Guy
Would one of you that is running HCC as well as HCC GPU please post your app_info. I think I have corrupted mine and I just do not see how.
11/24/2012 12:20:26 PM | World Community Grid | [error] State file error: missing application file wcg_hcc1_img_7.05_windows_intelx86
Last edited by OldChap; 11-24-2012 at 04:31 AM.
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
OC that's not an issue with your app_info, it's telling you that file is missing from the folder: www.worldcommunitygrid.org
If you only have 8 threads available and you want to also run HCC CPU at the same time (I found this counter-productive in my tests) you would change the avg_ncpus and max_ncpus tags inside the GPU section ... not the CPU section. This way each GPU task requires slightly less than 1 cpu thread but when the CPU tasks run they will use a full thread.
Making the following changes to the app_info posted below *should* run 8 gpu and 1 cpu at the same time
Code:<avg_ncpus>0.875000</avg_ncpus> <max_ncpus>0.875000</max_ncpus>
8 Conurrent ATI WUs ... without the above changes ... modify at your own risk
I added the flops tag to help BOINC calculate better estimates, you'll have to tweak to match your runtimes.
commented version of the same app_infoCode:<app_info> <app> <name>hcc1</name> <user_friendly_name>XtremeSystems Crunches Cancer</user_friendly_name> </app> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86</name> <executable/> </file_info> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name> <executable/> </file_info> <file_info> <name>hcckernel.cl.7.05</name> <executable/> </file_info> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>3250000000.000000</flops> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <plan_class>ati_hcc1</plan_class> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>30000000000.000000</flops> <coproc> <type>ATI</type> <count>0.1250000</count> </coproc> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name> <main_program/> </file_ref> <file_ref> <file_name>hcckernel.cl.7.05</file_name> <open_name>hcckernel.cl</open_name> </file_ref> </app_version> </app_info>
Code:<app_info> <! I find comments inside the actual XML to be helpful --> <!-- Start of the HCC app definition --> <!--if you are running either or both HCC on CPU and GPU you only need to list the app 1 time --> <app> <name>hcc1</name> <user_friendly_name>XtremeSystems Crunches Cancer</user_friendly_name> </app> <! End of the HCC app definition --> <!-- Start of files required for HCC CPU --> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86</name> <executable/> </file_info> <!-- End of files required for HCC CPU --> <!-- Start of files required for HCC GPU --> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name> <executable/> </file_info> <file_info> <name>hcckernel.cl.7.05</name> <executable/> </file_info> <!-- End of files required for HCC GPU --> <!-- Start of app_version for HCC CPU --> <!-- I added the flops tag to help BOINC calculate better estimates --> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>3250000000.000000</flops> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86</file_name> <main_program/> </file_ref> </app_version> <!-- End of app info for HCC CPU --> <!-- Start of app_version for HCC GPU --> <!-- I added the flops tag to help BOINC calculate better estimates --> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <plan_class>ati_hcc1</plan_class> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>30000000000.000000</flops> <coproc> <type>ATI</type> <count>0.1250000</count> </coproc> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name> <main_program/> </file_ref> <file_ref> <file_name>hcckernel.cl.7.05</file_name> <open_name>hcckernel.cl</open_name> </file_ref> </app_version> <!-- End of app info for HCC GPU --> </app_info>
Last edited by Snow Crash; 11-24-2012 at 05:14 AM.
Cheers SC I have the bit about cores and threads in gpu sorted. The commenting is v. useful and the idea of flops I hope will resolve the runtime estimate and thus allow the cache to run at maximum.
I will run without app_info for a while to try to resolve the HCC for CPU error. This probably came about through setting up this stuff while HCC was on hold. (he said hopefully)
It seems a shame that wu files are held in same place as rig files as saving would be easier if not
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
I had some time to give this a try again and now I got it working. This is my app_info file for running 4 WU's on a ATI card and HFCC WU's on the CPU.
Code:<app_info> <app> <name>hcc1</name> <user_friendly_name>Help Conquer Cancer</user_friendly_name> </app> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name> <executable/> </file_info> <file_info> <name>hcckernel.cl.7.05</name> <executable/> </file_info> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <plan_class>ati_hcc1</plan_class> <avg_ncpus>1.0</avg_ncpus> <max_ncpus>1.0</max_ncpus> <coproc> <type>ATI</type> <count>.25</count> </coproc> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name> <main_program/> </file_ref> <file_ref> <file_name>hcckernel.cl.7.05</file_name> <open_name>hcckernel.cl</open_name> </file_ref> </app_version> <app> <name>hfcc</name> <user_friendly_name>Help Fight Childhood Cancer</user_friendly_name> </app> <file_info> <name>wcg_hfcc_autodock_6.40_windows_intelx86</name> <executable/> </file_info> <file_info> <name>wcg_hfcc_autodock_graphics_6.40_windows_intelx86</name> <executable/> </file_info> <file_info> <name>hfcc_protease_6.40.dat</name> </file_info> <file_info> <name>hfcc_image05_6.40.tga</name> </file_info> <file_info> <name>hfcc_text01_6.40.tga</name> </file_info> <file_info> <name>hfcc_image02_6.40.tga</name> </file_info> <file_info> <name>hfcc_image01_6.40.tga</name> </file_info> <file_info> <name>hfcc_image04_6.40.tga</name> </file_info> <file_info> <name>hfcc_image03_6.40.tga</name> </file_info> <file_info> <name>hfcc_image06_6.40.tga</name> </file_info> <file_info> <name>hfcc_image07_6.40.tga</name> </file_info> <app_version> <app_name>hfcc</app_name> <version_num>640</version_num> <platform>windows_intelx86</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>889972551.983820</flops> <api_version>6.3.3</api_version> <file_ref> <file_name>wcg_hfcc_autodock_6.40_windows_intelx86</file_name> <main_program/> </file_ref> <file_ref> <file_name>wcg_hfcc_autodock_graphics_6.40_windows_intelx86</file_name> <open_name>graphics_app</open_name> </file_ref> <file_ref> <file_name>hfcc_image05_6.40.tga</file_name> <open_name>prog_left.tga</open_name> </file_ref> <file_ref> <file_name>hfcc_text01_6.40.tga</file_name> <open_name>Courier-Bold.txf</open_name> </file_ref> <file_ref> <file_name>hfcc_image02_6.40.tga</file_name> <open_name>GFX_top.tga</open_name> </file_ref> <file_ref> <file_name>hfcc_image01_6.40.tga</file_name> <open_name>GFX_bot.tga</open_name> </file_ref> <file_ref> <file_name>hfcc_image04_6.40.tga</file_name> <open_name>prog_fill.tga</open_name> </file_ref> <file_ref> <file_name>hfcc_protease_6.40.dat</file_name> <open_name>protease.dat</open_name> </file_ref> <file_ref> <file_name>hfcc_image03_6.40.tga</file_name> <open_name>IBM_logo.tga</open_name> </file_ref> <file_ref> <file_name>hfcc_image06_6.40.tga</file_name> <open_name>WCG_logo.tga</open_name> </file_ref> <file_ref> <file_name>hfcc_image07_6.40.tga</file_name> <open_name>boinc_logo2.tga</open_name> </file_ref> </app_version> </app_info>
Thanks Jean-Guy, that started working but my video driver crashes. Not sure if I've got a hardware problem or not here. Seems like others are able to get this to work just fine but I am having no luck in crunching more than one GPU task at a time.
ran furmark:
Last edited by retro77; 11-24-2012 at 07:43 AM.
Well Hello again Retro,
Glad to see that you were able to move the yardstick forward. Looks like your video card or its driver may need a little TLC. Can you add your system details to your signature block to give pertinent troubleshooting sys data. Your above FurMark data (27 Oct 2012) indicate that you conducted a successful test,. I see that you are using WIN 8, an i7 2600K @ 3502MHz, 8 gigs of RAM and a possible OC video card. Your low CPU setting (i7 2600K @ 3502MHz 3.5 GHz) is holding your video card back. You need to eventually OC that CPU to 4.2 GHZ or greater to maximize your video card effectiveness.
Here are a few questions for you:
1- Have you fully stress tested your whole sytem? (memtest86+ and Prime 95)?
2- Whitout app_info, can you run 7 CPU WUs and one (ATI GPU hcc1) WUs?
I would try the easy possible fix first:
1- if video card OC return it to stock and see if it will run.
2- raise pwr setting on video card
3- switch to BOINC Beta v7.0.36
4- Update video driver from 12.10 to latest 12.11 beta (12.11 beta 4 is positively commented upon by BOINC crunchers)
Good luck,
Jean-Guy
Last edited by jeanguy2; 11-24-2012 at 10:09 AM.
Made some changes to the big app_info :
SC's annotated HCC is now in
Rob B's HCCC is in
Retro's DSFL is in.
Nice work gentlemen
Incidentally, I have run the whole thing (less hccc) as a test. All that I removed was nVidia as I have ati cards. It is all good, so for those of you with a preference for one or two projects and more cores/threads than your GPU can handle all you need to do is remove those projects that you do not have already loaded on the rig and do not wish to run.
Last edited by OldChap; 11-24-2012 at 06:47 PM.
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
I'm on 12.11 beta 8 for my 7970 at stock 1100/1650, no issues yet..
Also I have a GTX670 in the system too, at 1302/1702
All along the watchtower the watchmen watch the eternal return.
I'm trying to run this on my AMD APU. What do I set the platform to instead of Intel? And do I modify the file info from intelx86 to x86_64?
<name>wcg_hcc1_img_6.56_windows_intelx86__ati_hcc1 </name>
Edit: My App_info wasn't taking affect after closing BOINC. Apparently, even after exiting the program, it was still open under task manager as a running task. I shut it down and everything worked.
Last edited by 0ne.shot; 11-24-2012 at 11:15 PM.
Jean-Guy: To answer your questions:
1- Have you fully stress tested your whole sytem? (memtest86+ and Prime 95)? Nope
2- Whitout app_info, can you run 7 CPU WUs and one (ATI GPU hcc1) WUs? I don't think I've tried with out app_info
I would try the easy possible fix first:
1- if video card OC return it to stock and see if it will run. It's a stock OC from ASUS
2- raise pwr setting on video card do this in the BIOS?
3- switch to BOINC Beta v7.0.36 I'm running 7.0.36
4- Update video driver from 12.10 to latest 12.11 beta (12.11 beta 4 is positively commented upon by BOINC crunchers) I'm running 12.10 as I've heard they work with someone else running W8. I've tried 12.11 beta4 and beta 8. Video driver crashes after about 11 seconds.
Thanks
Posting Permissions
Reply With Quote
Bookmarks