New to OC'ers - Seti team question(s)

Hi all. Semi-tech type person here but have been away from tower PC's for about 7 years now (I was travelling alot). Now that I'm not travelling, I built myself a nice rig.
I've been running Seti@home for the past few days now (this obviously doesn't include time long ago when I had towers) after completing my overclocks and burn tests. Here are my questions...

1) Can one be on multiple Seti teams? Such as yours and the Planetary Society's or do I have to choose?

2) Why does it seem as though my Radeon 7950 is not being stressed by Seti? My understanding is that it should be supported.
Thanks

2500k @ 4.6
Asus Maximus IV Gene-Z/Gen3
16 Gb G.Skill Ripjaws @ 1600
XFX HD7950 DD @ 975 & 1330
All stable @ 60C under load

1: I don't know, I never tried it but I think it is one team only.

2: by default only 1 instances are running on each video card (or multiple in Xfire/SLi). You need to make BOINC run more than one on GPU.

The easiest way to do this is to start with Lunatic optimized files. Then after you installed the optimized files, look for app_info.xml in BOINC data directory and open them with text editor program (do not use XML editor, BOINC does not use standard XML coding) and I'll let someone explain the change:

Voodoo Rufus said:

Change everything that says this:

<type>CUDA</type>
<count>1</count>

to this:

<type>CUDA</type>
<count>.5</count>

1/.5 = 2 instances
1/.33 = 3 instances
1/.25 = 4 instances
and so on.

Click to expand...

Here's how I've got my app_info set up for a radeon 5850. This still may not stress your 7950 100%, so some further modifications may be needed. Please note, youll need to have run the Lunatics optimizer prior to using this file.

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b2_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AK_v8b2_win_x64_SSE41.exe</file_name>
<main_program/>
</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>AK_v8b2_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</name>
<executable/>
</file_info>
<file_info>
<name>AstroPulse_Kernels_r521.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>506</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_intelx86</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 2 -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096</cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.ex e</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r521.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_intelx86</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 2 -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096</cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.ex e</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r521.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>506</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_x86_64</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 2 -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096</cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.ex e</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r521.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_x86_64</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 2 -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096</cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.ex e</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r521.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r409_SSE.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r390.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 20 -instances_per_device 2</cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.ex e</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
<copy_file/>
</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.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 20 -instances_per_device 2</cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.ex e</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
</app_info>

I do not believe a single SETI Account can belong to more than one team with the current project software.

Welcome back to SETI!

Thanks for the timely replies - I will be adding lunatics optimizer to my system and get that running.
Again, Thanks