Here one can download initial versions of SETI7 optimized binaries for CPU (SSSE3 support required for now, that is, only Intel CPUs supported) and ATi/NV GPUs (SSE3 CPU support required). Low-end ATi GPUs are not supported in this build still. Low-end NV GPUs may require params tuning to avoid driver restarts.

http://files.mail.ru/66TQD2

Binaries for usage on SETI beta project only (don't use them on SETI main project).

Example of app_info.xml:

<app_info>
<app>
<name>setiathome_v7</name>
<user_friendly_name>SETI@home v7</user_friendly_name>
</app>
<file_info>
<name>MB_6.10_win_x86_SSSE3x_CPU_r229_SETI7.exe</name>
<executable/>
</file_info>
	<file_info>
		<name>MB_6.10_win_x86_SSE3_OpenCL_ATi_r229_SETI7.exe</name>
			<executable/>
	</file_info>
	<file_info>
		<name>MultiBeam_Kernels_r229.cl</name>
			<executable/>
	</file_info>
<app_version>
	<app_name>setiathome_v7</app_name>
	<version_num>691</version_num>
	<file_ref>
	<file_name>MB_6.10_win_x86_SSSE3x_CPU_r229_SETI7.exe</file_name>
	<main_program/>
	</file_ref>
</app_version>
<app_version>
	<app_name>setiathome_v7</app_name>
	<version_num>691</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 1 -instances_per_device 1 -hp</cmdline>	
	<flops>20987654321</flops>
	<file_ref>
		<file_name>MB_6.10_win_x86_SSE3_OpenCL_ATi_r229_SETI7.exe</file_name>
		<main_program/>
	</file_ref>
    <file_ref>
        <file_name>MultiBeam_Kernels_r229.cl</file_name>
        <copy_file/>
    </file_ref>
   <coproc>
   <type>ATI</type>
   <count>1</count>
   </coproc>
</app_version>

</app_info>

(example for ATi GPU given).

---

News about SETI opt app releases: https://twitter.com/Raistmer

Thanks!

At least which nVIDIA driver is needed/recommended?

I have only the DLLs of stock S@h Enhanced 6.09 CUDA23, this wouldn't work together, right?
I need to use the DLLs of the currently Lunatics Installer V0.37?

All nVIDIA builds of S@h v7 will be OpenCL, or in future also CUDA? If also CUDA, which nVIDIA driver will be needed/recommended then? I need to leave the 190.38 driver? ;-)


EDIT: Someone could post a completely CPU & nVIDIA app_info.xml example?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC (@ SETI@home). - SETI@home needs your help. -

---

Thanks!

At least which nVIDIA driver is needed/recommended?

OpenCL support starts at 197.xx/recommended should be 266.58 or 267.24,
Don't use the 270.xx drivers at the moment, there seems to be problems with GPU's downclocking,
and possiblily extra CPU usage with OpenCL apps.

I have only the DLLs of stock S@h Enhanced 6.09 CUDA23, this wouldn't work together, right?
I need to use the DLLs of the currently Lunatics Installer V0.37?

DLL's not required, these are OpenCL builds,

All nVIDIA builds of S@h v7 will be OpenCL, or in future also CUDA? If also CUDA, which nVIDIA driver will be needed/recommended then? I need to leave the 190.38 driver? ;-)

These are just initial conversions.

EDIT: Someone could post a completely CPU & nVIDIA app_info.xml example?

There are only 4 things to change in the posted app_info for Nvidia use, the filename (twice),
change the <type>ATI</type> from ATI to CUDA, and change the <plan_class>ati13ati</plan_class> from ati13ati to cuda,
and if you get driver restarts, increase the value for -period_iterations_num 1

Claggy

I installed the CPU app.
To now two results finished (completely with opt. app calculated), but they don't match with the wingmen, a third WU is needed.
Both WUs were restarted. Maybe because of this?

The counter show all, or after a restart a fresh start of the counter (visible in stderr output)?

wuid=3345893
wuid=3345951


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC (@ SETI@home). - SETI@home needs your help. -

---

Both WUs were restarted. Maybe because of this?

Quite possible, will check checkpointing then.

---

News about SETI opt app releases: https://twitter.com/Raistmer

The machine (CPU) finished more results.. (without restart):

Already granted:
wuid=3345766
wuid=3345763
wuid=3345759
wuid=3345746
wuid=3345727

Still pending:
wuid=3345743


It's look like the granted Cr. are lower with r229 (~ 80 - 105 Cr.) than with stock 6.91 app (~ 130 - 160 Cr.) for 0.39x AR WUs.


First the app name confused me (MB_6.10), why not only e.g. SETIv7_win_x86_SSSE3x_r229.exe for the CPU app? ;-)


BTW. My currently app_info.xml (only CPU app)..
<app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>MB_6.10_win_x86_SSSE3x_CPU_r229_SETI7.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>691</version_num>
<file_ref>
<file_name>MB_6.10_win_x86_SSSE3x_CPU_r229_SETI7.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC (@ SETI@home). - SETI@home needs your help. -

---

It's look like the granted Cr. are lower with r229 (~ 80 - 105 Cr.) than with stock 6.91 app (~ 130 - 160 Cr.) for 0.39x AR WUs.

Your host hasn't had its 10 validations yet on this application, (SETI@home v7 (anonymous platform, CPU)), until it gets to it's 11th validation credit granted will be slightly lower,
(i see this with Astropulse_v505 on Seti Main a lot, where my wingman hasn't done 10 validations, Credit tends to be ~500, instead of ~700+)

If you had been running anonymous platform already on v7 and already had an Average processing rate,
and then you added a faster app you might also get a lower amount of Credit awarded until the Average processing rate adjusts,

Claggy

It's look like the granted Cr. are lower with r229 (~ 80 - 105 Cr.) than with stock 6.91 app (~ 130 - 160 Cr.) for 0.39x AR WUs.

Check if both opt and stock apps report same flops number for same AR task (better just for the same task).

First the app name confused me (MB_6.10), why not only e.g. SETIv7_win_x86_SSSE3x_r229.exe for the CPU app? ;-)

Cause name creation automated, will be changed with release.

---

News about SETI opt app releases: https://twitter.com/Raistmer

Sutaru, you don't need to detach/reattach to get Wu's marked up on the Server as being done on Anonymous platform,
if you set NNT, copy all your Beta Wu's to a safe place, then reset the project, then copy the Wu's back, unset NNT,
then when you next ask for work, the Server will resend each task (20 at a time) and it'll update the application name on your host's task pages,
and you won't need to download the Wu's again as you already have them.

All you did by making all those Wu's Abandoned is put those Wu's at the bottom of the Que for resending, now your wingmen will have to wait for months for them to get to the top of the Que again.

Claggy

It's look like the granted Cr. are lower with r229 (~ 80 - 105 Cr.) than with stock 6.91 app (~ 130 - 160 Cr.) for 0.39x AR WUs.

Check if both opt and stock apps report same flops number for same AR task (better just for the same task).

The upper mentioned granted results with r229 and wingmen stock apps:

wuid=3345766
Flopcounter: 50650142779621.570000
Flopcounter: 50655584499397.953000 (setiathome_v7 6.91 DevC++/MinGW (5 restarts))

wuid=3345763
Flopcounter: 50650844457707.055000
Flopcounter: 50651188795832.468750 (setiathome_v7 6.92 XCode GCC 4.0.1 (Apple Inc. build 5494) i386)

wuid=3345759
Flopcounter: 50650966625717.891000
Flopcounter: 50660287849054.961000 (setiathome_v7 6.91 DevC++/MinGW (9 restarts with 4x No heartbeat from core client for 30 sec - exiting)

wuid=3345746
Flopcounter: 50650873789047.578000
Flopcounter: 50652240737578.453000 (setiathome_v7 6.91 DevC++/MinGW (1 restart))

wuid=3345727
Flopcounter: 50649778750214.086000
Flopcounter: 50650117069607.406000 (setiathome_v7 6.91 DevC++/MinGW)

You meant it like this?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC (@ SETI@home). - SETI@home needs your help. -

---

It's look like the granted Cr. are lower with r229 (~ 80 - 105 Cr.) than with stock 6.91 app (~ 130 - 160 Cr.) for 0.39x AR WUs.

Check if both opt and stock apps report same flops number for same AR task (better just for the same task).

Flopcounter is redundant, no longer linked to credit awards in any way. But best to keep it in, both in stderr_txt for sanity-checks like this, and as <fpops_cumulative> in the reported result in case Eric decides to reinstate manual credit awards.

A bit confused, as usual, have a SETI Beta account on my Q6600+ GTX470 host,
but also want to create account on WIN7 rig (i7-2600 + 2 HD5870).

Although it's 64bit BOINC, this should work, right?
Ehh, sorry got it, my bad. :)

---

You dont have to create a new account.
Just use the same email adress and attach.

---

With each crime and every kindness we birth our future.

Just suspended all WU’s dropped in app and restarted. BIONC
Granted credit:
wuid=3341133
wuid=3341137
wuid=3341151
wuid=3341153
wuid=3341127
wuid=3341145
wuid=3341142
wuid=3341139
wuid=3341138

Completed, validation inconclusive.

wuid=3341157
wuid=3341156
wuid=3341140

Michael

---

A computer program will always do what you tell it to do, but rarely what you want it to do.

Too long, >10 hours, behind puter, isn't always good, but got 1 XP x86 (Q6600+GTX470), updated, also attached a Bêta Account on my i7-2600+2 HD5870,
WIN7 x64, both are downloading and running.

Looking OK.

---

You meant it like this?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC (@ SETI@home). - SETI@home needs your help. -

yes. So, opt app reports less flops and will recive less credit until "new credit system" will average all to nothing ;)

---

News about SETI opt app releases: https://twitter.com/Raistmer

yes. So, opt app reports less flops and will recive less credit until "new credit system" will average all to nothing ;)

The fpops_cumulative from the flopcount is no longer used for anything server-side, and the difference in reported value is much less than 1% anyhow.

Apps which don't have 10 completed/validated are treated differently in the credit calculations, so are anonymous platform apps. They're minority cases and there's less statistical data applicable.

                                                                Joe

yes. So, opt app reports less flops and will recive less credit until "new credit system" will average all to nothing ;)

The fpops_cumulative from the flopcount is no longer used for anything server-side, and the difference in reported value is much less than 1% anyhow.

Apps which don't have 10 completed/validated are treated differently in the credit calculations, so are anonymous platform apps. They're minority cases and there's less statistical data applicable.

                                                                Joe

If so why I bother to keep them in code? LoL.
flops calculations eat CPU cycles, will drop them completele then.

---

News about SETI opt app releases: https://twitter.com/Raistmer

in rev 229 checkpointing is broken, so either try to complete tasks w/o restarts or suspend until next build arrives (or revert to stock if you can't wait ;) )

---

News about SETI opt app releases: https://twitter.com/Raistmer

yes. So, opt app reports less flops and will recive less credit until "new credit system" will average all to nothing ;)

The fpops_cumulative from the flopcount is no longer used for anything server-side, and the difference in reported value is much less than 1% anyhow.

Apps which don't have 10 completed/validated are treated differently in the credit calculations, so are anonymous platform apps. They're minority cases and there's less statistical data applicable.

                                                                Joe

If so why I bother to keep them in code? LoL.
flops calculations eat CPU cycles, will drop them completele then.

Flopcounts are not currently used for anything server-side, ever since David (inadvertently) broke Eric's credit script. Best to check with Eric about future plans before you break it permanently, deliberately.