But every SETI MB WU, ran on GPU, makes 'room' for one on CPU, or
any Project of your choise.
(Running r234 for MB, period_iterations1 and 2 per GPU {2x EAH5870s},
is acceptable, in terms of Screen Lag) Average runtime for CPU,
is smaller then the GPU time or runtime, in some cases, depending
on Gaussian fitting, they can take some more Total Elapsed Time.

(And I've changed Use 87.5% of CPU, i7-2600+ HT -1 =7 cores, which is also
loaded 100%.)

Result for Bêta MB WU, with r 234. Quite a few 'inconclusives', but they simply can't
be checked. Well therefore it's called Bêta testing :)
Results.

Naam	06no10ac.27632.6611.11.13.96.vlar_1
Werkeenheid	3217061
Aangemaakt	16 Jan 2011 | 2:31:33 UTC
Verzonden	19 Mar 2011 | 15:25:24 UTC
Ontvangen	22 Mar 2011 | 10:46:34 UTC
Server status	Binnen
Uitkomst	Geslaagd
Client status	Gereed
Afsluit status	0 (0x0)
Computer ID	45894
Rapporteren voor	5 May 2011 | 3:32:04 UTC
Loop tijd	10,605.22
CPU tijd	9,207.86
Validatie status	Fout in WU - controle overgeslagen
Punten	0.00
Programma versie	SETI@home Enhanced
Anoniem platform (CPU)
Stderr output

<core_client_version>6.10.56</core_client_version>
<![CDATA[
<stderr_txt>
Windows optimized S@H Enhanced application by Alex Kan
Version info: SSSE3x (Intel, Core 2-optimized v8-nographics) V5.13 by Alex Kan
SSSE3x Win32 Build 76 , Ported by : Jason G, Raistmer, JDWhale

     CPUID: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz 
     Speed: 4 x 2405 MHz 
     Cache: L1=64K L2=4096K
  Features: MMX SSE SSE2 SSE3 SSSE3 
 
Work Unit Info:
...............
Credit multiplier is :  2.85
WU true angle range is :  0.011633

Flopcounter: 38730390419365.523000

Spike count:    0
Pulse count:    11
Triplet count:  1
Gaussian count: 0
called boinc_finish

</stderr_txt>
]]>

Well that is the wrong one, Results ATI vs nVIDIA.

Stock
vs ATI optimized.
Ehh, back on topic...............;^0
(Feel free to place {or delete} in SETI Bêta, sorry)

Ehh and why not use SETI Main, for hosting the LUNATICs Installer V0.38
(Probably why no 3rd party app. is published on SETIs WEB Site, policy/copyright
issue/responsebillity/et(c.))

---

But every SETI MB WU, ran on GPU, makes 'room' for one on CPU, or
any Project of your choise.
(Running r234 for MB, period_iterations1 and 2 per GPU {2x EAH5870s},
is acceptable, in terms of Screen Lag)

Result for Bêta MB WU, with r 234. Quite a few 'inconclusives', but they simply can't
be checked.
Results.

complain to Raistmer in the appropriate thread on the seti BETA project

(Feel free to place {or delete} in SETI Bêta, sorry)

It's impossible to move posts cross-project. You'll have to repost there.

Ehh and why not use Bêta for hosting the LUNATICs Installer V0.38

At no time will Lunatics produce an installer for the Beta project.
Installers are strictly for the public on main.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

AFAIK, x38e CUDA app got the 'CPU fallback function' back again, which is normal for the stock CUDA apps.
At the stock CUDA apps I can make <cmdline>-def , for to disable the test for this function. ~ 1 sec faster CPU preparation time of the CUDA WU on my systems.
The x38e support also <cmdline>-def ?


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

---

Have it installed : V0.38 and BOINC 6.12.26 (64bit) too.
This host
.
Looking OK, runs 2 days already.

---

BTW.

x38e support also <cmdline>-hp like Raistmer's OpenCL apps?

Which <cmdline>'s are possible with x38e?

It would be a big deal to add the -hp and/or -def <cmdline>'s to x38e?


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

---

I'll refer back the questions about cmdline parameters to the developers - I'll try and make sure the documentation is complete when the time comes to make a release announcement specifically concerning the applications. It's already looking as if x38e will be replaced by a newer version before that time comes.

In the meantime, this thread is about testing the installation process using v0.38beta - please focus your discussions on that.

I'll refer back the questions about cmdline parameters to the developers - I'll try and make sure the documentation is complete when the time comes to make a release announcement specifically concerning the applications. It's already looking as if x38e will be replaced by a newer version before that time comes.

In the meantime, this thread is about testing the installation process using v0.38beta - please focus your discussions on that.

Newer that x38e?

f?

Gee?

My, but you boyz are moving fast.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I'll refer back the questions about cmdline parameters to the developers - I'll try and make sure the documentation is complete when the time comes to make a release announcement specifically concerning the applications. It's already looking as if x38e will be replaced by a newer version before that time comes.

In the meantime, this thread is about testing the installation process using v0.38beta - please focus your discussions on that.

Newer that x38e?

f?

Gee?

My, but you boyz are moving fast.

f doesn't need a CPU with SSE2 and greater capability ;-)

Claggy

My, but you boyz are moving fast.

That'll be boyz and gurlz, I thank you (look who started this thread).

There will be an installer Beta _v10 soon, to robustify and clean up the BOINC closedown/restart process - but x38f won't be part of this release cycle. Maybe if we have to go to a Beta _v11.

X32f ?? You mean X38f?

---

PROUD MEMBER OF Team Starfire World BOINC

X32f ?? You mean X38f?

Correct - edited. Sorry about that. Thanks.

I'll refer back the questions about cmdline parameters to the developers - I'll try and make sure the documentation is complete when the time comes to make a release announcement specifically concerning the applications.
(...)

Thanks.

f doesn't need a CPU with SSE2 and greater capability ;-)

Claggy

Your AthlonXP 3200+ don't have SSE2? ;-)

There are speed differences between usage of SSE2 and no usage of CPU extensions (I guess only for the CUDA WU preparation time on CPU?)?


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

---

yes the sse2 started with the amd athlon 64 3200+ 754 chip and a few server chips

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

robustify

Nice. Damn I need a whiteboard with Word Of The Day on it...

robustify

Nice. Damn I need a whiteboard with Word Of The Day on it...

Really cool word there......
Robustify.

Luv it.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Just an idea..

Why not add the Lunatics URL (http://lunatics.kwsn.net) to the apps <stderr_txt> (which is shown online in the stderr output)?

More advertisement - and for free. ;-)


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

---

For those not Lunatics Beta testers but are following this thread, I noticed I was getting a lot of inconclusive results so I mentioned it on Lunatics. Here is a portion of Jason Gs reply.

The main reasons for this are improvement to accuracy of spikes & the chirp, as well as the better triplet handling we already inherited from Joe's improvement to reduce -12's

The purpose of doing so is quite deliberate, as we introduce code to both GPU & CPU codebases, stock and optimised, that agree better between CPU & GPU going into V7. That means that while there will be initial expected extra inconclusives, going into V7, as more applications adopt the improvements, CPU & GPU apps will agree very tightly making inconclusives somewhat rarer.

So it's a transitional period of sorts, designed to bring everything into better agreement going into V7.

So far, those inconclusive results have validated fine with the third wingman so, sorry for the inconvenience of having to wait for an extra wingman before getting your credit. It is for the greater good! :-)

---

PROUD MEMBER OF Team Starfire World BOINC

Attention all beta testers please.

Installer v0.38 (v12b, release candidate) is now available.

Everybody please retest and REPORT.

We've updated the CUDA MB with a SSE compliant version (prior builds were all SSE2) and the BOINC stop/restart has been reworked. That has proved to be fairly complicated, especially getting BOINC back running.

We want to release TOMORROW and we'd like to be reasonably sure, that it works with all windows flavours on all boinc versions.

So, please please please, run, check that BOINC stop/restart worked and REPORT.


If all goes well, we'll be able to release tomorrow, if we need to head back to the drawing board or don't get enough feedback to be sure it works, we are looking at end of July for the next release window.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

Installed the first version of V0.38 installer some days ago.
Also been away a few days, when looking at my hosts, I noticed
the, too low, amount of Watts, this XP64 rig, normally uses.
(385Watt, not the 265Watt it showed.
One hundred Watts less(?), a quick check shows, no CUDA load
on the GTX480 and a LOT of errors, infact all CUDA processing,
did not take place at all.
GPUz (0.53) showed no load ? and a (strange) message need 0.25CUDA and task manager shows a load of 12% per CPU core!
With 4 CPU and 4 GPU (CUDA) WU's.

For the moment, I reïnstalled, the previous v0.37 on BOINC 6.12.26.
GPUz still shows the same capabillities, but also 99% load, doing now
4 at a time.

15/06/2011 15:22:48 | | NVIDIA GPU 0: GeForce GTX 480 (driver version 25896, CUDA version 3010, compute capability 2.0, 1536MB, 1345 GFLOPS peak)
15/06/2011 15:22:48 | SETI@home | Found app_info.xml; using anonymous platform
15/06/2011 15:22:48 | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 3311912; resource share 200
15/06/2011 15:22:48 | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 5499627; resource share 600
15/06/2011 15:22:48 | GPUGRID | URL http://www.gpugrid.net/; Computer ID 78963; resource share 200
15/06/2011 15:22:48 | | General prefs: from http://climateprediction.net/ (last modified 13-May-2011 21:56:13)
15/06/2011 15:22:48 | | Computer location: home
15/06/2011 15:22:48 | | General prefs: no separate prefs for home; using your defaults
15/06/2011 15:22:48 | | Reading preferences override file
15/06/2011 15:37:27 | SETI@home | [coproc] Insufficient CUDA for 02my11aa.29071.2112.9.10.18_1: need 0.250000
15/06/2011 15:38:27 | SETI@home | [coproc] Insufficient CUDA for 02my11aa.29071.2112.9.10.18_1: need 0.250000
15/06/2011 15:39:27 | SETI@home | [coproc] Insufficient CUDA for 02my11aa.29071.2112.9.10.18_1: need 0.250000
15/06/2011 15:40:27 | SETI@home | [coproc] Insufficient CUDA for 02my11aa.29071.2112.9.10.18_1: need 0.250000
15/06/2011 15:41:27 | SETI@home | [coproc] Insufficient CUDA for 02my11aa.29071.2112.9.10.18_1: need 0.250000
15/06/2011 15:56:05 | SETI@home | Starting task 02my11aa.9982.7020.15.10.163_1 using setiathome_enhanced version 608
15/06/2011 15:56:27 | SETI@home | Started upload of 02my11aa.9982.7020.15.10.163_1_0
15/06/2011 15:56:32 | SETI@home | Finished upload of 02my11aa.9982.7020.15.10.163_1_0


Host 5499627.

---

try a reinstall of the lunatics. Perhaps you didnt install the Fermi apps

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope