Previous to the release of V8, I had been running Lunatics. I decided to drop my app_info.xml so as to allow SETI to install the stock (only for now, right?) version. That worked OK, as I am now running V8 on my CPUs, with an occasional APv7 on my GPUs, along with occasional (resends, I presume) SETIv7.

Question:

On stock, how do I get SETI to run > 1 WU at a time on my GPUs? Since there is no app_info.xml to do the COUNT. And yes, I know about app_config.xml, but how was it done before that existed (was it even possible?)?

Thanks for enlightening me, anyone who can spare the time!

---

It's not a dumb question, but I do know that Seti has had several huge outages in the past, and this is just a smaller one. It will all work out.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

Try using this simple app_config.xml

adjust the cpu usage to what you like.
<app_config>
<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.4</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.4</cpu_usage>
</gpu_versions>
</app>
</app_config>

My dumb question, which I still didn't get a straight answer to from yesterday:

Is there currently any v8 GPU work available? (for those who have installed one of the third-party beta clients)

I'm guessing it's a "no" but just want to make sure. I'm fine with keeping the GPUs busy on Einstein until it goes "yes". Thanks in advance.

---

I've been running Raistmer's OpenCL for NV since yesterday on the Beta site.

Waiting to hear from them when we can try them on Main, but for now only the ATI are official on Main.

Try a search for SSE3_OpenCL_NV

Somewhere in there you should find a link (I lost it).

I'm NOT sure if this is beta only, or working on main.


EDIT: OK Zalster answered that, beta only.

My dumb question is ... How do you join beta?

I only see a login link and no project description for which to join.

use BOINC to add a project and the URL would be http://setiathome.berkeley.edu/beta

BTW, for the longest time I was too embarrassed to ask that question

Thank you woohoo, I'm a member now :D

AFAIK, the correct URL for SETI-Beta in BOINC is http://setiweb.ssl.berkeley.edu/beta/

---

AFAIK, the correct URL for SETI-Beta in BOINC is http://setiweb.ssl.berkeley.edu/beta/

setiathome.berkeley.edu/beta will redirect you to setiweb.ssl.berkeley.edu/beta, so for purposes of typing an addy into your browser both work. For attaching to the beta project the first one _may_ work, but I'd recommend using the latter (and if you're on CLI you definitely need to type in the long one.)

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

My dumb question, which I still didn't get a straight answer to from yesterday:

Is there currently any v8 GPU work available? (for those who have installed one of the third-party beta clients)

I'm guessing it's a "no" but just want to make sure. I'm fine with keeping the GPUs busy on Einstein until it goes "yes". Thanks in advance.

Both Raistmer and Jason are working on OpenCL (ATI and Intel) and CUDA (NV) apps respectively.
We have apps in alpha, we will be moving to beta and hand them over to Eric for public release when we are confident they work properly.
Lunatics installer will follow when we have working optimised CPU apps.
Pre installer release of working GPU apps via the dev's chosen channels is by discretion of the dev concerned and will be announced in the dedicated thread. (i.e. for the time between the app being ready and Eric releasing it as stock [at which point they become available as seti downloads too])

Oh, to answer your question _work_ is available, there is no difference between GPU work and CPU work. What's not available yet is a publicly released GPU app.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Previous to the release of V8, I had been running Lunatics. I decided to drop my app_info.xml so as to allow SETI to install the stock (only for now, right?) version. That worked OK, as I am now running V8 on my CPUs, with an occasional APv7 on my GPUs, along with occasional (resends, I presume) SETIv7.

Question:

On stock, how do I get SETI to run > 1 WU at a time on my GPUs? Since there is no app_info.xml to do the COUNT. And yes, I know about app_config.xml, but how was it done before that existed (was it even possible?)?

Thanks for enlightening me, anyone who can spare the time!

If your version of BOINC does not support app_config.xml you need to use app_info.xml to run more than one task per GPU.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

So, as I understand what you said, before app_config.xml, there was NO way to run > 1 WU per GPU on stock?

I did not know that.

---

So, as I understand what you said, before app_config.xml, there was NO way to run > 1 WU per GPU on stock?

I did not know that.

Unless you use Enstein's GPU utilization factor, that is, that also allowed that.

Claggy

So, as I understand what you said, before app_config.xml, there was NO way to run > 1 WU per GPU on stock?

I did not know that.

Not at SETI. Einstein@Home has a bespoke solution, but for their own project only.

So, as I understand what you said, before app_config.xml, there was NO way to run > 1 WU per GPU on stock?

I did not know that.

Not at SETI. Einstein@Home has a bespoke solution, but for their own project only.

bespoke == tailored to suit (ones needs)

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

Try using this simple app_config.xml

adjust the cpu usage to what you like.
<app_config>
<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.4</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.4</cpu_usage>
</gpu_versions>
</app>
</app_config>

This worked for me, thank you very much!
Now, if I could get some APs to run, I would be overjoyed; have gotten a very few, but nothing like the dozens I used to get when APs were being generated before V8.

---

They have been generating more than the usual amount of AP tasks lately.

The problem is that there are so many hungry computers out there waiting for them, with the introduction of v8 there is no MB tasks for GPUs, so they are getting AP tasks as fast as they can generate them.

Try using this simple app_config.xml

adjust the cpu usage to what you like.
<app_config>
<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.4</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.4</cpu_usage>
</gpu_versions>
</app>
</app_config>

Zalster, is there an app_config for Beta that will allow multiple GPU WUs? I've searched everywhere.

Thanks!

---