Excellent. Thank you TBar and Richard!


For CUDA - those files are not available yet?

Also, is there a download area I can check in to see when files are added?

Thanks to JohnDK and Richard.

I seem to be up and running, have downloaded and got a couple running, lets see how they go.

Was not overly ammused when I looked at the new V8ts 29 out of 33 are VLAR's, I am only crunching on 2 of 4 cores atm cause of AP's.

---

Kevin

A GPU app for Seti V8 ATI/AMD MB8_r3299 for windows is now available on my website.

http://mikesworldnet.de/download.html

Use at your own risk.

You can use same comand line values as for V7.


This is what i`m using in my appinfo.xml

<app>
<name>setiathome_v8</name>
</app>
<file_info>
<name>MB8_win_x86_SSE2_OpenCL_ATi_HD5_r3299.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-3-4_x86.dll</name>
<executable/>
</file_info>
<file_info>
<name>mb_cmdline_win_x86_SSE2_OpenCL_ATi_HD5.txt</name>
</file_info>
<app_version>
<app_name>setiathome_v8</app_name>
<version_num>800</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB8_win_x86_SSE2_OpenCL_ATi_HD5_r3299.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-3-4_x86.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE2_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v8</app_name>
<version_num>800</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB8_win_x86_SSE2_OpenCL_ATi_HD5_r3299.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-3-4_x86.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE2_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>

---

With each crime and every kindness we birth our future.

Where would I find the necessary files for Linux?

I'd suggest the files from Beta. I'm not sure if the files on Main are the Updated ones or the OLD 8.00 version. You Really want the 8.04 version...

http://boinc2.ssl.berkeley.edu/beta/download/setiathome_8.04_x86_64-pc-linux-gnu

http://boinc2.ssl.berkeley.edu/beta/download/setigraphics_8.04_x86_64-pc-linux-gnu

http://boinc2.ssl.berkeley.edu/beta/download/bl_bkg_804.jpg

http://boinc2.ssl.berkeley.edu/beta/download/setiathome-8.04_README

http://boinc2.ssl.berkeley.edu/beta/download/seti_804.jpg

http://boinc2.ssl.berkeley.edu/beta/download/bl_804.jpg


The 32-bit version;

http://boinc2.ssl.berkeley.edu/beta/download/setiathome_8.04_i686-pc-linux-gnu

http://boinc2.ssl.berkeley.edu/beta/download/setigraphics_8.04_i686-pc-linux-gnu

app_info.xml;

<app_info>
  <app>
     <name>setiathome_v8</name>
  </app>
    <file_info>
       <name>setiathome_8.04_x86_64-pc-linux-gnu</name>
       <executable/>
    </file_info>
   <app_version>
     <version_num>804</version_num>
     <platform>x86_64-pc-linux-gnu</platform>
        <avg_ncpus>1.000000</avg_ncpus>
        <max_ncpus>1.000000</max_ncpus>
    <file_ref>
        <file_name>setiathome_8.04_x86_64-pc-linux-gnu</file_name>
        <main_program/>
    </file_ref>
    <file_ref>
        <file_name>setigraphics_8.04_x86_64-pc-linux-gnu</file_name>
        <open_name>graphics_app</open_name>
    </file_ref>
    <file_ref>
        <file_name>bl_bkg_804.jpg</file_name>
        <open_name>sponsor_bkg</open_name>
    </file_ref>
    <file_ref>
        <file_name>seti_804.jpg</file_name>
        <open_name>seti_logo</open_name>
    </file_ref>
    <file_ref>
        <file_name>bl_804.jpg</file_name>
        <open_name>sponsor_logo</open_name>
    </file_ref>
  </app_version>
</app_info>

I copied "setiathome_8.04_x86_64-pc-linux-gnu" to my setiathome directory and edited my app_info. I don't run the screen saver so I only used that one file. When I restart BOINC, I get the following error in the event log:

Fri 01 Jan 2016 07:56:34 PM EST | SETI@home | Found app_info.xml; using anonymous platform
Fri 01 Jan 2016 07:56:34 PM EST | SETI@home | [error] State file error: bad application name

Also after restarting BOINC, the application file itself disappears from the directory. The file permissions are correct, and the file name in app_info matches the actual file name. Not sure what I'm doing wrong or what I've missed. Below is my app_info.xml (new sections in red)

Any help would be appreciated.

<app_info>

<app>
<name>setiathome_v8</name>
</app>

<file_info>
<name>setiathome_8.04_x86_64-pc-linux-gnu</name>
<executable/>
</file_info>

<app_version>
<version_num>804</version_num>
<platform>x86_64-pc-linux-gnu</platform>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>

<file_ref>
<file_name>setiathome_8.04_x86_64-pc-linux-gnu</file_name>
<main_program/>
</file_ref>
</app_version>

<app>
<name>astropulse_v7</name>
</app>

<file_info>
<name>ap_7.05r2728_avx_linux64</name>
<executable/>
</file_info>

<app_version>
<app_name>astropulse_v7</app_name>
<version_num>705</version_num>
<platform>x86_64-pc-linux-gnu</platform>
<plan_class></plan_class>
<cmdline></cmdline>

<file_ref>
<file_name>ap_7.05r2728_avx_linux64</file_name>
<main_program/>
</file_ref>
</app_version>

<app>
<name>astropulse_v7</name>
</app>

<file_info>
<name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100</name>
<executable/>
</file_info>

<app_version>
<app_name>astropulse_v7</app_name>
<version_num>708</version_num>
<plan_class>x86_64-pc-linux-gnu</plan_class>
<cmdline>-unroll 18 -oclFFT_plan 256 16 256 -ffa_block 16384 -ffa_block_fetch 8192 -tune 1 64 8 1 -tune 2 64 8 1 -hp</cmdline>
<avg_ncpus>0.15</avg_ncpus>
<max_ncpus>0.30</max_ncpus>

<coproc>
<type>CUDA</type>
<count>1.0</count>
</coproc>

<file_ref>
<file_name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100</file_name>
<main_program/>
</file_ref>
</app_version>

<app>
<name>setiathome_v7</name>
</app>

<file_info>
<name>MBv7_7.05r2550_avx_linux64</name>
<executable/>
</file_info>

<app_version>
<app_name>setiathome_v7</app_name>
<version_num>705</version_num>
<platform></platform>
<plan_class></plan_class>
<cmdline></cmdline>
<file_ref>
<file_name>MBv7_7.05r2550_avx_linux64</file_name>
<main_program/>
</file_ref>
</app_version>

<app>
<name>setiathome_v7</name>
</app>

<file_info>
<name>setiathome_x41zc_x86_64-pc-linux-gnu_cuda60</name>
<executable/>
</file_info>

<file_info>
<name>libcudart.so.6.0</name>
<executable/>
</file_info>

<file_info>
<name>libcufft.so.6.0</name>
<executable/>
</file_info>

<app_version>
<app_name>setiathome_v7</app_name>
<version_num>704</version_num>
<plan_class>cuda60</plan_class>
<avg_ncpus>0.15</avg_ncpus>
<max_ncpus>0.30</max_ncpus>
<cmdline></cmdline>

<coproc>
<type>CUDA</type>
<count>1.0</count>
</coproc>

<file_ref>
<file_name>setiathome_x41zc_x86_64-pc-linux-gnu_cuda60</file_name>
<main_program/>
</file_ref>

<file_ref>
<file_name>libcudart.so.6.0</file_name>
</file_ref>

<file_ref>
<file_name>libcufft.so.6.0</file_name>
</file_ref>
</app_version>

</app_info>

That happens a lot when using a Stock App in an App_Info. The first time you start BOINC it deletes the Stock App. Have you tried quitting BOINC, replacing the File, then restarting BOINC? It usually only happens the first time, after that it stops deleting the File.

Yes, I've tried a few times. I even tried renaming it to "setiathome_8.00_x86_64-pc-linux-gnu and changing the version number to 800 in app_info, thinking maybe it didn't like the 8.04/804. No luck.

Yes, seems to do the same if you change the name to MB_8.04_x86_64-pc-linux-gnu.
It's almost as if someone placed a block against using the Linux version 8 App on Main and then either forgot to remove the block or simply doesn't want that App on Main.
Strange, never seen that before.

Same thing happens with the App from Main;
http://boinc2.ssl.berkeley.edu/sah/download_fanout/setiathome_8.00_x86_64-pc-linux-gnu
I dunno, guess we'll have to wait and see...

Meanwhile, my Mac doesn't seem to be having any problem using the Apps I compiled,
http://setiathome.berkeley.edu/results.php?hostid=6796479&offset=60&appid=29

I received two notifications yesterday on my android devices about the update.
But however, it did not show in the play store when I searched for it.
Any idea why is that?

---

The proud owner of IGCSE World.

@ Fawkesguy,

Look at the line immediately following

<app_version>

In every case, it's an <app_name> - EXCEPT the one you added in red. It'll be

<app_name>setiathome_v8</app_name>

of course.

@ TBar - he quoted your post, which is where the error came from. Please proof-read, or better yet test, before posting.

Actually it's in the beginning. This Works;

   <app>
      <name>setiathome_v8</name>
   </app>
      <file_info>
         <name>setiathome_8.00_x86_64-pc-linux-gnu</name>
         <executable/>
      </file_info>
     <app_version>
     <app_name>setiathome_v8</app_name>
     <platform>x86_64-pc-linux-gnu</platform>
     <version_num>800</version_num>   
      <file_ref>
        <file_name>setiathome_8.00_x86_64-pc-linux-gnu</file_name>
        <main_program/>
      </file_ref>
   </app_version>

I received two notifications yesterday on my android devices about the update.
But however, it did not show in the play store when I searched for it.
Any idea why is that?

You received the notifications about Seti@Home releasing version 8:
the BOINC Notification wrote:

SETI@home version 8 has been released.
This version finally gives us the ability to process data from multiple sources, including the Green Bank Telescope. That means we'll be ready for data from Breakthrough Listen when it's available.

Unless you installed the previous science application through the anonymous platform -highly unlikely on an Android device- the Seti applications will update automatically.

the BOINC Notification also wrote:

We're releasing the versions for CPUs first. We'll release versions for graphics processing units (GPUs) and Android devices as they come available. We're releasing slowly so as not to overtax our download server. This update will happen automatically, unless you use a special version you got from another web site.

You will therefore have to have patience, the applications will be sent to your devices automatically when they become available. But as you can read from the notification, the CPU versions are now released, the GPU and Android versions come later.

What you normally update through the Google Play store is the BOINC version. BOINC 7.6.22 got upgraded to recommended on Windows and Macintosh on the 31st of December 2015, there is no newer version yet for Android. Not until after the BOINC developers have managed to find an Android developer.

---

Soops, my bad. :)
Washing my eyes with hot tea now.

---

Since we seem to have had some confusion over exactly what caused the state file errors overnight, here's a definitive (but minimal) app_info for Windows. If you stick to this - especially to the 800 version number - future upgrading via the installer will be much more likely to work properly.

<app_info>
    <app>
        <name>setiathome_v8</name>
    </app>
    <file_info>
        <name>setiathome_8.00_windows_intelx86.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3-3-4_x86.dll</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>800</version_num>
        <file_ref>
            <file_name>setiathome_8.00_windows_intelx86.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
</app_info>

App_info with graphics support:

<app_info>
    <app>
        <name>setiathome_v8</name>
    </app>
    <file_info>
        <name>setiathome_8.00_windows_intelx86.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3-3-4_x86.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>setigraphics_8.00_windows_intelx86.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>bl_bkg_800.jpg</name>
    </file_info>
    <file_info>
        <name>seti_800.jpg</name>
    </file_info>
    <file_info>
        <name>bl_800.jpg</name>
    </file_info>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>800</version_num>
        <file_ref>
            <file_name>setiathome_8.00_windows_intelx86.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>setigraphics_8.00_windows_intelx86.exe</file_name>
            <open_name>graphics_app</open_name>
        </file_ref>
        <file_ref>
            <file_name>bl_bkg_800.jpg</file_name>
            <open_name>sponsor_bkg</open_name>
        </file_ref>
        <file_ref>
            <file_name>seti_800.jpg</file_name>
            <open_name>seti_logo</open_name>
        </file_ref>
        <file_ref>
        <file_name>bl_800.jpg</file_name>
            <open_name>sponsor_logo</open_name>
        </file_ref>
    </app_version>
</app_info>

Download links for all files (only the first two are needed when running without graphics, all are needed with graphics)

http://boinc2.ssl.berkeley.edu/sah/download_fanout/setiathome_8.00_windows_intelx86.exe
http://boinc2.ssl.berkeley.edu/sah/download_fanout/libfftw3f-3-3-4_x86.dll
http://boinc2.ssl.berkeley.edu/sah/download_fanout/setigraphics_8.00_windows_intelx86.exe
http://boinc2.ssl.berkeley.edu/sah/download_fanout/bl_bkg_800.jpg
http://boinc2.ssl.berkeley.edu/sah/download_fanout/seti_800.jpg
http://boinc2.ssl.berkeley.edu/sah/download_fanout/bl_800.jpg

Save the graphics .jpg files to disk if your browser doesn't do so automatically, and copy all files to the setiathome.berkeley.edu project folder.

Well yay. Took a while for my BOINC to ask for work, because of a low 'fraction of time BOINC is running' value. 10.6% due to not having had BOINC on for two weeks or so. :)

Anyway, work request:
02/01/2016 11:01:05 | SETI@home | No tasks sent
02/01/2016 11:01:05 | SETI@home | No tasks are available for AstroPulse v7
02/01/2016 11:01:05 | SETI@home | No tasks are available for SETI@home v8
02/01/2016 11:01:05 | SETI@home | Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v8.
02/01/2016 11:01:05 | SETI@home | Tasks for CPU are available, but your preferences are set to not accept them
02/01/2016 11:01:05 | SETI@home | Tasks for NVIDIA GPU are available, but your preferences are set to not accept them
02/01/2016 11:01:05 | SETI@home | Tasks for Intel GPU are available, but your preferences are set to not accept them

---

Unless you installed the previous science application through the anonymous platform -highly unlikely on an Android device- the Seti applications will update automatically.

Cause Mateusz SETI MultiBeam v7 app faster than stock, compatible with more types of Android devices and comes with NativeBOINC that still more convenient than stock... I would say it's quite likely thing - Anonymous platform under Android.

Thanks to JohnDK and Richard.

I seem to be up and running, have downloaded and got a couple running, lets see how they go.

One validated and the other awaiting validation, the rest will have to wait untill I clear the AP's in the queue.

---

Kevin

Richard, thanks for your app_info segment.
Went in just fine here, mixed in with the Lunatics build, on the one machine I'll allow for testing.
Assuming I needed to call libfftw3f-3-3-4_x86.dll rather than the 64 bit version given the v 8.00 executable?
Think I'll grab some sleep and see how it does....

---

Assuming I needed to call libfftw3f-3-3-4_x86.dll rather than the 64 bit version given the v 8.00 executable?

Yes, so far none of the developers have managed to get a 64-bit app working, so everything is 32-bit for the time being. So that means linking the 32-bit (x86) version of libfftw too.

Assuming I needed to call libfftw3f-3-3-4_x86.dll rather than the 64 bit version given the v 8.00 executable?

Yes, so far none of the developers have managed to get a 64-bit app working, so everything is 32-bit for the time being. So that means linking the 32-bit (x86) version of libfftw too.

Great. Thanks!

---

Thanks Richard for the app_info details.

I was scratching my head why I couldn't get v8 files with ReadConfigFiles, then tried a BOINIC restart, and poof, it worked.

It is running now, but I do see a 1C temp increase with 1 V8, and 3 AP tasks running on CPU.