Does this mean, I choose the apps I would like to test and use an app_info.xml file?

Or is this info just for Eric?

What's the difference between HD5 build and HD5 Signals on GPU build?
(Which I should use for R9 FuryX VGA cards?)

- - - - - - - - - -

I want to give 1 GPU app 1 CPU-Core.
On my PC it's '0.119 CPU' with stock SETI@home v8 v8.04 (opencl_ati5_nocal) app.

How should look the app_config.xml file?
I tested a few times, but nothing worked.

Thanks.

---

These builds for open beta testing so you "should" use ALL of them that compatible with your hardware, find better configs, find not working configs and report back. What you asking is just for what they were posted here - to find answers!

EDIT: the difference between SoG and "usual" one:
SoG means Signals on GPU - new computation regime where GPU<=>CPU communications are greatly reduced.
Should result in better GPU utilization... in theory...

---

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

smth wrong with this app on main:

Mac OS/X 10.3+ 8.00 30 Dec 2015, 21:14:57 UTC 0 GigaFLOPS

still no flops...

---

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

Thanks Raistmer,

Finally got it the NV to run.

Now to see if they validate.

Is that "SETI@home v8 8.00 x86_64-apple-darwin" on main?
They all seem to be generating -9 exits.
Same computer.
http://setiathome.berkeley.edu/results.php?hostid=6463983
http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=57003
Beta never sent it a W/U.

---

Yes, My mac over there has been using it

http://setiathome.berkeley.edu/results.php?hostid=7604284

Have not had any problems with it.

Hmmmmm... But the 10.3 (PPC) issue is separate from whatever problem the x86_64 version is having.

In beta the x86_64-darwin version was successful on 90% of hosts (although that seems to have dropped to 85% recently.) It seemed to have its worst problems running on darwin 13.4.0 (I don't know apple's word for that version).

http://setiweb.ssl.berkeley.edu/beta/setiathome_v8_x86_64-apple-darwin.html

---

Hmmmmm... But the 10.3 (PPC) issue is separate from whatever problem the x86_64 version is having.

In beta the x86_64-darwin version was successful on 90% of hosts (although that seems to have dropped to 85% recently.) It seemed to have its worst problems running on darwin 13.4.0 (I don't know apple's word for that version).

http://setiweb.ssl.berkeley.edu/beta/setiathome_v8_x86_64-apple-darwin.html

Eric, the code name for 13.4.0 is "Mavericks" according to the Wiki.

Beta never sent it a W/U.

I can't seen any reason for it not to have been sent v8 work besides...

2016-01-03 21:21:45.3861 [PID=21015]    [version] [AV#655] Don't need CPU jobs, skipping
2016-01-03 21:21:45.3861 [PID=21015]    [version] [AV#656] Don't need CPU jobs, skipping

---

Not sure what happen.

About 10 minutes ago I had a MBv8 error out on my computer.

Following that, I started to receive the following notice in Boinc Manager

Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v8

I looked at the app_info.xml and it's no different from what I put in more than an hour ago.

So I have to think it's related to the error

https://setiweb.ssl.berkeley.edu/beta//result.php?resultid=21602786

I'm also starting to see

This computer has finished a daily quota of xx tasks.

That number goes up as more results are returned but not getting any new work.

Any ideas? I tried closing BOINC and restarting it. Now I'm debating turning off the computer and rebooting.

Edit..

rebooting, will recheck in a few, reboot seems to have cleared that message

testing 123

Any chance a basic app_info.xml can follow with each package?

Most GPU apps updated now so use links from this post:

Here are few MultiBeam v8 apps for public beta testing in anonymous platform mode:

Windows x64 AVX

Windows x64 SSE3

Windows x86 SSE

Windows x86 SSE3

Windows OpenCL NV

Windows OpenCL iGPU

Windows OpenCL ATI HD5 build

Windows OpenCL ATi HD5 Signals on GPU build

Windows OpenCL ATi non-HD5 build

Windows OpenCL ATi APU build

Any chance a basic app_info.xml can follow with each package?

They're always - automatically - included in Raistmer's download packages. Look for a file called 'MB8_win_x64_AVX_VS2010.aistub' or similar.

These app_info segments are intended for Beta testing only, and are not guaranteed to be usable on the main project.

Wow, thanks.

I newer even looked into that file.

Any chance a basic app_info.xml can follow with each package?

They're always - automatically - included in Raistmer's download packages. Look for a file called 'MB8_win_x64_AVX_VS2010.aistub' or similar.

These app_info segments are intended for Beta testing only, and are not guaranteed to be usable on the main project.

Eric, small cosmetic bug discovered and fixerd in OpenCL GPU builds (printing TUNE option values and few others). Nothing serious but please postpone release a little while I rebuild...

I think you replaced one bug with another.

- fprintf(stderr, "TUNE: kernel %d now has workgroup size of (%zd,%zd,%zd)\n",
+ fprintf(stderr, "TUNE: kernel %d now has workgroup size of (%d,%d,zd)\n",

Eric, small cosmetic bug discovered and fixerd in OpenCL GPU builds (printing TUNE option values and few others). Nothing serious but please postpone release a little while I rebuild...

I think you replaced one bug with another.

- fprintf(stderr, "TUNE: kernel %d now has workgroup size of (%zd,%zd,%zd)\n",
+ fprintf(stderr, "TUNE: kernel %d now has workgroup size of (%d,%d,zd)\n",

yep, unfortunately. New rebuild in progress....

---

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

Was going to ask if we could start with multiple instances on a card since I had 300 validated returns, but going to wait now till you publish the new builds so I can retest singularly under those.

Will you have a Windows x86 SSE2 flavor available?

My old ThinkPad with a Pentium M did much better with AKv8c_r2549_winx86_SSE2xjf.exe than it did with stock on v7, and v8 stock looks even worse. (About 19 hours for a "normal" AR on v8 stock vs. about 12 hours for SSE2 on v7.)

Windows x86 SSE2

---

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

The cmdline settings which I used for the SAHv7 ATI r2929 app, I can use them also for the HD5 build and HD5 Signals on GPU build apps?


BTW.
If I start BOINC is see:

OpenCL: AMD/ATI GPU 0: Fiji (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL: AMD/ATI GPU 1: Fiji (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL: AMD/ATI GPU 2: Fiji (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL: AMD/ATI GPU 3: Fiji (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL CPU: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))	

...does this mean that on my system it's possible to use an ATI app which support AVX?
The currently available ATI apps use 'just' SSE2 (on/off the CPU).

Thanks.

---