BOINC and SETI using app_info.xml. For what and for what reason??

For the n-th time:
There is NO stock SETI@home v7 Linux CUDA app for now:
http://setiathome.berkeley.edu/apps.php

(i.e. there is NO such Linux CUDA executable on the servers)

OK! So we are using the app_info.xml to tell SETI servers (and Asteroid servers in my case, but this is another case for another thread) which applications we would like to receive and run.

No - not 'receive'
When app_info.xml is present BOINC server (the Software that runs on SETI@home servers) will NOT send you ANY applications.
You need to already have them.
Server will send only tasks (for the applications specified in app_info.xml)

Before app_info.xml
Looking at the applications appointed my cruncher "halifax" without the use of app_info.xml, I can see this:
http://setiathome.berkeley.edu/results.php?hostid=7238932
http://setiathome.berkeley.edu/host_app_versions.php?hostid=7238932

Under jobs, I can see the following being crunched:
SETI@home v7 v7.01
AstroPulse v6 v6.03
AstroPulse v6 v6.01

Under Applications I can see:
AstroPulse v6 6.01 i686-pc-linux-gnu
AstroPulse v6 6.03 86_64-pc-linux-gnu
SETI@home v7 7.01 i686-pc-linux-gnu
SETI@home v7 7.01 x86_64-pc-linux-gnu

So right now this cruncher "halifax" is doing both 32bit jobs and 64bit jobs of both AstroPulse and SETI@home!?!?

All are for CPU

I found this, and I guess its something like that which needs to be added to my app_info.xml file. But I cant find the files for Linux.

Read again:
http://setiathome.berkeley.edu/forum_thread.php?id=74153&postid=1487416#1487416

... and go 3 links deep to get the apps (packed in .7z files).

Here's the content as I guess it needs to be:

No, it's very old.
The 'content' is in the above linked .7z files
(If you had looked at them all this post had to be unnesessary)

I'm not sure where to put the files. The app_info.xml, yes, but not the others. I have read that they go into the projects directory. But where is this when only using the boinc-client. I need to find that too.

The 'projects directory' is in the BOINC Data directory which is listed in the first lines in Messages tab on BoincTasks:

1 15-03-2014 08:26 Starting BOINC client version 6.10.58 for windows_intelx86
2 15-03-2014 08:26 log flags: file_xfer, sched_ops, task, benchmark_debug, dcf_debug
3 15-03-2014 08:26 Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3
4 15-03-2014 08:26 Data directory: H:\BOINC-Data


Look in your Messages to find your 'Data directory'
Every app_info.xml is for one project only:
- app_info.xml for SETI@home go to SETI@home directory (<BOINC_Data>\projects\setiathome.berkeley.edu\)
- app_info.xml for Asteroids@home go to Asteroids@home directory (<BOINC_Data>\projects\asteroidsathome.net_boinc\)

At the same directory you put the apps (they now exist there, the stock apps)

Conclusion!?
Using the app_info.xml we can crunch data using our GPU's! But where else is the advantage in using app_info.xml? Is there other advantages?

Copy from my previous post:

* What all of the above (if you use all the 3 packages) will give you:

Optimized SETI@home v7 CPU SSE3 app (MBv7_7.05r1848_sse3_linux64_CPU0.7z) - faster than the stock app
SETI@home v7 CUDA app so your NVIDIA can do SETI@home tasks - the only way for now (as already noted there is no stock SETI@home CUDA app for Linux)
Newer AstroPulse OpenCL app for NVIDIA (I think it have less CPU usage than the stock (which is of the same author))

And I use app_info.xml to be able to use on my computer:
on the CPU: only SETI@home v7 SSE2
on the ATI AMD GPU: only AstroPulse OpenCL

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

For the n-th time:
There is NO stock SETI@home v7 Linux CUDA app for now:

When I say "SETI@home" I mean SETI in general! Not the application seti@home v.... or what its called..

(i.e. there is NO such Linux CUDA executable on the servers)

So no GPU crunching for any SETI jobs!

This is for?

Linux/x86_64 6.07 (cuda_opencl_100) 19 Jun 2013, 23:27:06 UTC
Linux/x86_64 6.07 (opencl_ati_100) 19 Jun 2013, 23:27:06 UTC
Linux/x86_64 6.07 (opencl_nvidia_100) 19 Jun 2013, 23:27:06 UTC

Fact!
app_info.xml is not for me ;) Over and out... GPU is crunching for Asteroid just fine and we'll keep it like this for now. Maybe I was a little too fast getting in to this.

By the way, the 2 new system I build with CPU/GPU's - rig 1 runs SSE3 and CUDA55 for Asteroid and rig 2 runs AVX and CUDA55 for Asteroid.
Both system runs only SETI@home v7 v7.01 for SETI. This is how it has been since the 18th. It's funny how one system gets one type and the other another type. Same systems, but not quite the same GPU's. Both Linux64bit/CUDA5.5

.

---

Project Headless CLI Linux Multiple GPU Boinc Servers
Ubuntu Server 14.04.1 64bit
Kernel 3.13.0-32-generic
CPU's i5-4690K
GPU's GT640/GTX750TI
Nvidia v.340.29
BOINC v.7.2.42

This is for?

OpenCL AstroPulse v6 (2 for NVIDIA, 1 for ATI AMD)
(difference between cuda_opencl_100 and opencl_nvidia_100 is only in the name (the same app for different BOINC versions))
(if you look up - for ATI AMD there are Linux OpenCL applications also for SETI@home v7)

Linux CUDA executable for SETI@home v7 exists but not as stock (not on the servers)
(CUDA is of course for NVIDIA only)

app_info.xml is not for me ;)

So you can use Linux CLI (which I can't), managed to use >20 lines of commands to install NVIDIA CUDA drivers
and you find it too difficult to merge 3 text files in a text editor and copy some files to SETI@home directory? ;)
(you probably want me to do the combined package ;) - which will not take much time (and will need only 'copy everything to SETI@home directory' and maybe chmod +x))

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)