I have two machines running Seti 7 using CPU and GPU. Both were set up woth Lunatics as Cuda42 (both had Fermi cards). One now has a Kepler card, but is still running Cuda42.

Looking in the app_info.xml file, I see entries for Cuda 22, 23, 32, 42 and 50 for the application. Further, unless I am missing something, looking at these entries, they all seem to be identical in terms of the app exe and dll files.

So how does BOINC know to run Cuda42? And what does that mean, exactly, if all the entries are the same?

---

You could choose manualy the right app for your hosts if you use the lunnatics installer, is simple, safe and easy to configurate.

---

I have two machines running Seti 7 using CPU and GPU. Both were set up woth Lunatics as Cuda42 (both had Fermi cards). One now has a Kepler card, but is still running Cuda42.

Looking in the app_info.xml file, I see entries for Cuda 22, 23, 32, 42 and 50 for the application. Further, unless I am missing something, looking at these entries, they all seem to be identical in terms of the app exe and dll files.

So how does BOINC know to run Cuda42? And what does that mean, exactly, if all the entries are the same?

All the different entries in the app_info are there to pick up all the various stock apps WU's so that none are abandoned.

---

All the different entries in the app_info are there to pick up all the various stock apps WU's so that none are abandoned.

I know that; I was referring to the fact that entries for all possible CUDA variants for SETI 7 also appear in app_info, and I was trying to find out how BOINC figures out which one to use.

---

All the different entries in the app_info are there to pick up all the various stock apps WU's so that none are abandoned.

I know that; I was referring to the fact that entries for all possible CUDA variants for SETI 7 also appear in app_info, and I was trying to find out how BOINC figures out which one to use.

It depends how your original work was branded, ie was it Cuda22, Cuda23, Cuda32, Cuda42 or Cuda50, and once the work is sent as anonymous platform work, then it is usually the top entry (changing app_info values may change that)

Claggy

If you don´t use the Lunnatics installer to manualy choose the best apps, who make the choice for you is the SETI Server.

To make simple to understand, it´s know what GPU you have and send all types of WU compatible to your hosts (because that you receive all the possible cuda option on your host) and wait their completion, then after few attemps it choose what is the best one for your looking their results (mainly what takes less time to compleate).

In theory that works, but in some cases it takes a long time to make the right choice or for some unknown reason it decides that the best WU is diferent from the optimal (example keep sending cuda42 to a keppler host that was the case on one of my hosts).

Most of the advanced crunchers choose to use the lunnatics installer instead because it allow you to go direct and choose the best apps for your system manualy.

---

It depends how your original work was branded, ie was it Cuda22, Cuda23, Cuda32, Cuda42 or Cuda50, and once the work is sent as anonymous platform work, then it is usually the top entry (changing app_info values may change that)

Claggy

So BOINC goes through the app_info, and uses the first entry it finds that fits?
So if I moved CUDA50 ahead of CUDA42 in my app_info, it would run as cuda50? But, as I mentioned earlier, all those seti 7 Cuda entries have the same app and dll entries (for cuda42, I believe), so that would make no difference.

@Juan - I knew that, it was not the question I was asking, I was asking about Lunatics and how it communicates with BOINC at run time.

---

It depends how your original work was branded, ie was it Cuda22, Cuda23, Cuda32, Cuda42 or Cuda50, and once the work is sent as anonymous platform work, then it is usually the top entry (changing app_info values may change that)

Claggy

So BOINC goes through the app_info, and uses the first entry it finds that fits?
So if I moved CUDA50 ahead of CUDA42 in my app_info, it would run as cuda50? But, as I mentioned earlier, all those seti 7 Cuda entries have the same app and dll entries (for cuda42, I believe), so that would make no difference.

It would visually say Cuda50 in Boinc Manager, but the actual app being run would be whatever is specified in your app_info, in your case the Cuda42 app, there's no point in swapping them around, unless you want to mislead yourself,

You could duplicate one of the app_version sections and put it first, and rename the <plan_class> to 'The Jason G Carlos Fandango Cuda app' and Boinc Manager should display it as that, but it still would be the Cuda42 app that ran,

Whatever you do, the task list will still only say 'SETI@home v7 Anonymous platform (NVIDIA GPU)'

Claggy

It would visually say Cuda50 in Boinc Manager, but the actual app being run would be whatever is specified in your app_info, in your case the Cuda42 app, there's no point in swapping them around, unless you want to mislead yourself,

You could duplicate one of the app_version sections and put it first, and rename the <plan_class> to 'The Jason G Carlos Fandango Cuda app' and Boinc Manager should display it as that, but it still would be the Cuda42 app that ran,

Whatever you do, the task list will still only say 'SETI@home v7 Anonymous platform (NVIDIA GPU)'

Claggy

So: If I knew the names of the files to run in an actual Cuda50 situation, if I edited the first entry in the setiathome_7 list and put those names there, it would run the actual cuda50 programs, is what you are saying (I think), so all I would need to know would be a) the filenames and b) get copies of those files into the correct directory?

---

So: If I knew the names of the files to run in an actual Cuda50 situation, if I edited the first entry in the setiathome_7 list and put those names there, it would run the actual cuda50 programs, is what you are saying (I think), so all I would need to know would be a) the filenames and b) get copies of those files into the correct directory?

The files you need are, cudart32_50_35.dll, cufft32_50_35.dll and Lunatics_x41zc_win32_cuda50.exe. They all live in your \...\boinc_data\projects\setiathome folder. You may also need, libfftw3f-3-3_upx.dll. These are all included in the Lunatics installation pack.

You will also have to make the appropriate alterations to you app_info file.

T.A.

Cuda 50 is running just fine on my dual 680 rig using the Lunatics installer.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Cuda 50 is running just fine on my dual 680 rig using the Lunatics installer.

Just out of curiousity, how many WUs do you run simultaneously on each 680?

---