Sorry, forgot you said it was just doing APs.

---

PROUD MEMBER OF Team Starfire World BOINC

This thread is too valueable to be lost in the archives - I see others have been looking for it so....

BUMP^

Very timely. The optimised Windows applications for Astropulse v505 have just been posted at Lunatics. Look for 'rev 168' for the new v505 compatible applications: the download packages also still contain r112 applications so you can help finish off the remnants of the previous run. A full multi-coloured announcement will no doubt follow when we can find Gecko_R7 (he's the only one with a key to the paint-spray closet ;-) ).

From what I've been able to read so far (not been successful in snagging a v505 on the main project yet myself), those running CUDA should put in the same flops value for v505/r168 as they did for v503/r112. I think this is a mistake by the project: the new stock application is considerably faster than the old stock application, so the estimates should have been changed - but for the time being, work with what you've got.

Very timely. The optimised Windows applications for Astropulse v505 have just been posted at Lunatics. Look for 'rev 168' for the new v505 compatible applications: the download packages also still contain r112 applications so you can help finish off the remnants of the previous run. A full multi-coloured announcement will no doubt follow when we can find Gecko_R7 (he's the only one with a key to the paint-spray closet ;-) ).

From what I've been able to read so far (not been successful in snagging a v505 on the main project yet myself), those running CUDA should put in the same flops value for v505/r168 as they did for v503/r112. I think this is a mistake by the project: the new stock application is considerably faster than the old stock application, so the estimates should have been changed - but for the time being, work with what you've got.

As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)

---

GPU Users Group

Very timely. The optimised Windows applications for Astropulse v505 have just been posted at Lunatics. Look for 'rev 168' for the new v505 compatible applications: the download packages also still contain r112 applications so you can help finish off the remnants of the previous run. A full multi-coloured announcement will no doubt follow when we can find Gecko_R7 (he's the only one with a key to the paint-spray closet ;-) ).

From what I've been able to read so far (not been successful in snagging a v505 on the main project yet myself), those running CUDA should put in the same flops value for v505/r168 as they did for v503/r112. I think this is a mistake by the project: the new stock application is considerably faster than the old stock application, so the estimates should have been changed - but for the time being, work with what you've got.

As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)

I think it will be considered v5

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)

I think it will be considered v5

Not possible. The preference depends on the same ID in the database as what's listed on the Applications page. v5 and v505 are different applications, and since the preference for v505 has not yet been added the 'If no work for selected applications is available, accept work from other applications?' will be needed.

                                                               Joe

As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)

I think it will be considered v5

Not possible. The preference depends on the same ID in the database as what's listed on the Applications page. v5 and v505 are different applications, and since the preference for v505 has not yet been added the 'If no work for selected applications is available, accept work from other applications?' will be needed.

                                                               Joe

Thanks Joe. I have that option ticked. I had them all ticked but have changed it temporarily to not include MB to see if I could get a 505. Seems like they are splitting a few more tonight although the current tape seems to have a lot of bad data. I'm guessing the network is maxed out again - nothing much moving at all although I did pick up a few 503 resends earlier. I assume they aren't actually creating any new 503s now?

Run only the selected applications
SETI@home Enhanced: no
Astropulse: yes
Astropulse v5: yes
If no work for selected applications is available, accept work from other applications? yes
Use Graphics Processing Unit (GPU) if available yes
Use Central Processing Unit (CPU) yes

---

GPU Users Group

Will this 505 app be also included in the opti app. installer?
BR,

---

Will this 505 app be also included in the opti app. installer?

In due course, but it's not ready yet. Jason reckoned it should take at most a week from now.

If tapes are being split as the server status shows,then why is is that even though I have all the boxes ticked to accept any work I am getting the Project has no jobs message.I was sent 1000 Cuda the other day but the schedular is not running them it is doing 2 Aqua cuda tasks that have a deadline of 2 months.
Are the tasks being sent to hosts that are nearer the server because thier pings are shorter?
Been like this for a couple of weeks.

---

As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)

I think it will be considered v5

Not possible. The preference depends on the same ID in the database as what's listed on the Applications page. v5 and v505 are different applications, and since the preference for v505 has not yet been added the 'If no work for selected applications is available, accept work from other applications?' will be needed.

                                                               Joe

Does anyone know when this option to select v505 will be added?

I've borked my app_info file :-(

I downloaded the new AP v5.05 package from Lunatics and pasted their app_info into my existing one. It was a straight paste and i was getting errors on starting the client so I did a little bit of trimming. When I start the client I get the following errors

[error] State file error: bad application name astropulse
[error] State file error: duplicate app version: astropulse_v5 windows_intelx86 503

My app_info is as follows
<app_info>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>6743308755.375</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>7792267895.1</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>5244795698.625</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<flops>2800000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>

XML is NOT my forte, Can someone please tell me what's wrong ?

Thanks
Brodo

[error] State file error: bad application name astropulse
[error] State file error: duplicate app version: astropulse_v5 windows_intelx86 503

My app_info is as follows
<app_info>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>6743308755.375</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>7792267895.1</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>5244795698.625</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<flops>2800000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>

You have two AstroPulse v5 sections: one at the beginning and one after v505. Remove the section in red and it should work.

---

Good morning peoples.

5.20 am in the UK here, posting a question quickly before I go to work in the hope it'll be answered before I get home.

I'm currently running 2 systems. A Ph. II 955 with Boinc 6.6.36 and Raistmer's v9 opp apps, and a Ph. 9850 with the lunatics unified installer, again with Boinc 6.6.36. Both machines run cuda too, the 955 with a 9800GTX+, the 9850 with an 8600 GTS.

The 9850, in asking for work yesterday failed on downloading a v505 astropulse saying that it didn't have the correct info in app_info, whereas the 955 doesn't even ask for such work. I am currently running down the work on the 955 so that I can change over to the unified installer on this machine too. It's much easier than doing it manually. I had success setting up Raistmer's opp app on one machine, on the other I couldn't get it to work, so went with the unified installer. Go figure...

Has the v505 been optimized yet, and if it has, how can I add the information to my app_info to start doing the new work units? I'm happy to add it to both machines but I don't want to add it, then change it in a couple of weeks when an optimized app comes out if it's not been done yet.

Any info or help will be greatly appreciated.

[edit] I've seen the app_info in Ozz's previous post, would a cut and paste with the correct section be sufficient? [/edit]

Regards, Gizbar.

---

A proud GPU User Server Donor!

[error] State file error: bad application name astropulse
[error] State file error: duplicate app version: astropulse_v5 windows_intelx86 503

My app_info is as follows
<app_info>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>6743308755.375</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>7792267895.1</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>5244795698.625</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<flops>2800000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>

You have two AstroPulse v5 sections: one at the beginning and one after v505. Remove the section in red and it should work.

Also remove the purple part, that's the other error.

                                                              Joe

Worked a treat !!
Thanks Ozzfan and Joe for your help

Brodo

[edit] I've seen the app_info in Ozz's previous post, would a cut and paste with the correct section be sufficient? [/edit]

As long as you also download the new AP v5.05 application as well, then yes, it would work.

---

From the top post in this thread

6. Browse your client_state.xml file (its in the BOINC data directory) and look for the entry <p_flops>. We need to use this number. Do NOT change this file.

7. Browse the BOINC log file to get the estimated speed of your GPU. This is usually given at the top of the log in Gflops. My 9800GT was estimated at 60Gflops.

8. For each of the apps multiply the p_flops value by the factor below and put this into the appropiate flops entry in the app_info given below. For multibeam 608 you need the estimated Gflops.

Astropulse 500 flops = p_flops x 2.25
Astropulse 503 flops = p_flops x 2.6
Multibeam 603 flops = p_flops x 1.75
Multibeam 608 flops = Est.Gflops x 0.2 (eg 60,000,000,000 x 0.2 = 12,000,000,000)

9. Make sure you have all the programs listed above in the projects\Setiathome.berkeley.edu folder. If not copy them there.

10. Save your app_info in the projects\Setiathome.berkeley.edu folder.

Question re the p-flops/fpops value in the client_state.xml file
I believe this is calculated by the client. Is it an average taken over X number of days or is it the value at the last shutdown of the client ?

The reason I'm asking is that I've just upgraded the processor in one of my CUDA machines and so have to change the value in the app_info file. But I've also been using ReSchedule to move CPU tasks to the GPU and need to know if the value has been influenced by doing this as I'm trying correct for the resulting imbalance

Regards
Brodo

Question re the p-flops/fpops value in the client_state.xml file
I believe this is calculated by the client. Is it an average taken over X number of days or is it the value at the last shutdown of the client ?

The reason I'm asking is that I've just upgraded the processor in one of my CUDA machines and so have to change the value in the app_info file. But I've also been using ReSchedule to move CPU tasks to the GPU and need to know if the value has been influenced by doing this as I'm trying correct for the resulting imbalance

Regards
Brodo

The <p_fpops> value in the <host_info> section at the top of client_state.xml. is taken from the BOINC benchmarks. They are run once every five days, and once every time you change BOINC version. If you change your CPU, it would probably be best to run the benchmarks manually once you've made sure that the new CPU is working properly - made any speed and bus timing changes necessary in the BIOS. And I suggest you run the benchmarks at a time of your own choosing, after all the Windows startup processes have finished, and when you know that the CPU isn't doing any hard work except BOINC.

Your CUDA card shouldn't change speed (unless you change the card too!).

When you're running with an app_info.xml, I don't think BOINC calculates anything to do with speed as tasks finish (except DCF): and I haven't had any problems with estimates after rebranding, though I've only tried moving from CUDA to CPU, not the other way round.

And finally, to add to the original advice: use the same speed estimate for Astropulse v505 as you did for v503.

I've updated the instructions on my blog, now that AP 505 is with us.

I have also installed the V12 optimised cuda app without the VLARkill as I am also running ReSchedule to shift the VLAR's from cuda to cpu. I have yet to add that to my instructions/app_info. Perhaps its time to start a new thread called "app_info for AP503, AP505, MB603 and MB608" :-)

---

BOINC blog