Lunatics has just released an upgrade to Astropulse 5.0 for Windows, rev103.

This upgrade is optional, but does show a significant performance increase.

Please see release post here:
http://setiathome.berkeley.edu/forum_thread.php?id=31810&nowrap=true#856092

and @ Lunatics:
http://lunatics.kwsn.net/index.php

Thanks and Have fun!
Lunatics Team

Lunatics has just released an upgrade to Astropulse 5.0 for Windows, rev103.

This upgrade is optional, but does show a significant performance increase.

Please see release post here:
http://setiathome.berkeley.edu/forum_thread.php?id=31810&nowrap=true#856092

and @ Lunatics:
http://lunatics.kwsn.net/index.php

Thanks and Have fun!
Lunatics Team

Just a quick Q.

<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

Is the app_info with the file.

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>

Ive just changed the app name in my app info to the above, however, does libfftw3f-3-1-1a_upx.dll have to be mentioned????

---

does libfftw3f-3-1-1a_upx.dll have to be mentioned????

Yes

super :)

---

Alright, just installed on my main cruncher. Three APs with r69 were already in progress, resume seems to play nicely.

The three WUs are:
- wuid=394799177 (75.110%)
- wuid=395584062 (32.550%)
- wuid=395743486 (12.050%)

Those percentages are at the time of posting this.

Not expecting anything abnormal, but the possibility is always there of course.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

does libfftw3f-3-1-1a_upx.dll have to be mentioned????

Yes

Nope. Not unless you use Cuda or Stock application in there. (See stderr.txt text message right next to my name. FFTW is statically linked now. )

i.e. To clarify, Optimised Astropulse r103 for Windows no longer requires the fftw DLL to be present, nor reference to it in the app_info file in its application section. [Edit: But it won't hurt to leave it there either...](As long as you left the file there to match of course).

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

OK, I downloaded this and stopped boinc and copied the app_info and new .exe over to my projects folder.
It is running well and seems faster, but..

All my CUDA workunits have disappeared, I now have only AP WU's and although in messages I have CUDA co-prcessor found, my GPU is no longer crunching, probably because there are no longer any CUDA units. I have about 50 AP units, but my cache was set to 10 days
tried setting CPU to 3 in the cc_config file, but it has made no difference. How do I get BOINC to download CUDA work units again.

---

OK, I downloaded this and stopped boinc and copied the app_info and new .exe over to my projects folder.
It is running well and seems faster, but..

All my CUDA workunits have disappeared, I now have only AP WU's and although in messages I have CUDA co-prcessor found, my GPU is no longer crunching, probably because there are no longer any CUDA units. I have about 50 AP units, but my cache was set to 10 days
tried setting CPU to 3 in the cc_config file, but it has made no difference. How do I get BOINC to download CUDA work units again.

By Putting entries in the app_info for setiathome Cuda as well as AstroPulse.

Claggy

I will re-pack CUDA/opt AP package soon, after that you could use it to run both CUDA app and latest CPU AstroPulse opt app (r103 is faster, sometimes considerably faster than prev release, so it not nessesary but worth to update to it)

How do I get BOINC to download CUDA work units again.

Right now you have full cache for SETI project.
So you should crunch some AP tasks before you will be able to get new MB tasks for CUDA app.

OK, will crunch away..
Just looking at the time for ap with the new revision - its alot faster - well done guys, your work is really appreciated amongst all us crunchers :-)

---

I have repackaged the combined packages with the new app and hopefully they will have them up soon.

---

Edit correction...figured out myself!

---

... r103 is faster, sometimes considerably faster than prev release, so it not nessesary but worth to update to it

First off, thanks and well done to the developers of the new release of the AP optimised app.

I would be interested to know from the developers what the new optimised features are, and which systems are likely to see the largest performance enhancement.

---

Revision 103 is primarily a minor performance update, with some attempts to mitigate some persistent known issues related to boincapi/AstroPulse file handling, arising from stock:
- '0'd statefile' occurrences are further reduced over r69 / stock.
- 'Exited with no finished file' warning likelihood is reduced.
- Chance of truncated stderr.txt & result files is reduced.
- annoying XML parse warnings in stderr.txt are blocked.
Additionally,
- FFTW library is now statically linked in, and so it is no longer required to include the DLL or app_info references to it (though if the app_info file does reference it the file must be present, but will not be used).
- special handling of tasks that have reached the repeating pulse limit (30) which are prevalent it seems, now process them faster.

Performance figures, depending on selected build and target platform, have been seen to range from about 1.2x to 1.5x r69 release (3x-4x stock).

It should be noted that significant Berkeley stock changes appear to be in the pipeline, so the lifespan of this build may be relatively short. Possibly even from a week to a couple of months. On that note, is not considered a mandatory update, as processed results are fully compatible with those of r69 & stock version 5.

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Well done to all involved.

I'm seeing on my first batch of 4 AP with r103 approx 1.5x performance on r69.

I did have a bit of a hiccup when I installed last night - all my AP stock, both in progress and waiting to run went to computation error. Yes, I know, I should have backed up & isolated myself from the net but for the first time in ages I didn't:(

As far as I could see I had done everything OK, this wasn't the first time I've updated an app, after all. Never mind - worse things happen at sea.

So I would encourage anyone running r69 to try r103 but learn from my mistake.

It should be noted that significant Berkeley stock changes appear to be in the pipeline, so the lifespan of this build may be relatively short. Possibly even from a week to a couple of months.

Hi Jason,

Would that be the cuda version of AP by any chance?

---

BOINC blog

It should be noted that significant Berkeley stock changes appear to be in the pipeline, so the lifespan of this build may be relatively short. Possibly even from a week to a couple of months.

Hi Jason,

Would that be the cuda version of AP by any chance?

Hope yes. In debugging/development now.
(but not connected with current Berkeley's changes in code Jason wrote about)

It should be noted that significant Berkeley stock changes appear to be in the pipeline, so the lifespan of this build may be relatively short. Possibly even from a week to a couple of months.

Hi Jason,

Would that be the cuda version of AP by any chance?

The upcoming changes I was referring to in the stock application relate to additional processing of the signal in the existing non-cuda application. At this point I have no idea how much longer this would make processing, or how long before they are introduced at beta.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

After borking my entire seti install (my mistake) with these last night, I will try again tonight.
I dump the .exe into the projects directory - last night I did the same with the app_info as well and it all went wrong, I lost all my cuda WU's and then had problems rolling back, when I did, I was getting 'no registered app' errors as well as 'no work available' messgaaes from the server.
In the end I completely uninstalled and re-installed from stock
I am now running stock with the 6.6 manager and 6.08 CUDA client.
Do I merge the existing app_info with the one in the R103 directory I downloaded?
Just want to check so I dont bork everything again!!

---