...
In the meantime, It would be helpful if anyone who does manage to get, and process, a stock 5.03 AstroPulse task, could post their machine/task link to indicate some kind of baseline, as we're seeing some WU processing time variability that caught us by surprise [Though we're fairly certain it's the amount of client side blanking that causes it].

Jason

I managed to snag a single AP5.03 earlier today. I did 8 of these on Beta in about 80 hours each (Q9450@3.6GHz). I haven't got any records of timings at Stock for the old AP WU's - I think they came in at about 17 hours but can't be sure. But from my Pendings, with r69 they took about 10.5 hours and with r103 about 6.5 hours. I'm currently about 26% of the way through the AP5.03 in 10.75 hours; the "Progress" seems to be pretty linear so far, indicating a total of about 41 hours to complete.

Don't know if this is any help - I'll try to remember to update this when the WU completes.

This is the task and the wingman is running an Intel(R) Pentium(R) D CPU 2.66GHz [x86 Family 15 Model 4 Stepping 7] with multiple projects so I don't anticipate early validation.

F.

---

If you go to the Seti home page, there is an astropulse faq page, that page has a link for advanced users,
which has links for old AP apps, the files you need are in the same directory.

(I'm posting from a sony PSP & can't paste links!)

Claggy

Wow ! that page needs updating 4.35apps !

---

"Red Warrior Needs Food Badly"

You'll need:

astropulse_5.03_windows_intelx86.exe (460 KB)

libfftw3f-3-1-1a_upx.dll (438 KB)

The directory with all the AP 5.03 files is:

Index of /sah/download_fanout

and the direct links are:

astropulse_5.03_windows_intelx86.exe

ap_graphics_5.03_windows_intelx86.exe

libfftw3f-3-1-1a_upx.dll

The bit of the app_info for v5 AP is:

<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>astropulse_5.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>ap_graphics_5.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>astropulse_5.03_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_graphics_5.03_windows_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
</app_version>

You'll need to overwrite your section for astropulse, or add it as an addition,
I'm got entries for v5 AP as well as the last version, so i still get resends.

Claggy

Compliments to Richard for correcting my mistakes in the app_info earlier

Edit: changed the link to AP Graphics

Er no, if you want the eye-candy it'll be

ap_graphics_5.03_windows_intelx86.exe (288 KB)

and likewise in app_info.xml

I'm sorry I assumed the stock apps were both AMD and intel. Which of those are AMD64?

---

"Red Warrior Needs Food Badly"

I'm sorry I assumed the stock apps were bot AMD and intel. Which of those are AMD64?

The stock apps are indeed 'one size fits all' - those are the only Windows apps. They are 32-bit, and will run on either Intel or AMD, 32-bit or 64-bit. Although they are compiled with the vendor-neutral Microsoft compiler, earlier versions were reported to run slowly on AMD chips: these are probably the same, though it's too early for any explicit reporting.

Thank you for the help :)

Whats gonna happen with the un-validated AP tasks?

---

"Red Warrior Needs Food Badly"

...
In the meantime, It would be helpful if anyone who does manage to get, and process, a stock 5.03 AstroPulse task, could post their machine/task link to indicate some kind of baseline, as we're seeing some WU processing time variability that caught us by surprise [Though we're fairly certain it's the amount of client side blanking that causes it].

Jason

I managed to snag a single AP5.03 earlier today. I did 8 of these on Beta in about 80 hours each (Q9450@3.6GHz). I haven't got any records of timings at Stock for the old AP WU's - I think they came in at about 17 hours but can't be sure. But from my Pendings, with r69 they took about 10.5 hours and with r103 about 6.5 hours. I'm currently about 26% of the way through the AP5.03 in 10.75 hours; the "Progress" seems to be pretty linear so far, indicating a total of about 41 hours to complete.

Don't know if this is any help - I'll try to remember to update this when the WU completes.

This is the task and the wingman is running an Intel(R) Pentium(R) D CPU 2.66GHz [x86 Family 15 Model 4 Stepping 7] with multiple projects so I don't anticipate early validation.

F.

Well my first AP5.03 errored out with 30 + 30 after 35 hours and 52 mins. The progress bar throughout seemed to be pretty linear so I believe it was still heading for about 41 hours for completion. Now the long wait to see if it validates.

F.

---

Forgive me, but I seem to be somewhat confused.
I had downloaded the optimised ap apps (seti enhanced and ap) from kwsn.
then a while ago I read somewhere about the new ap_v5 coming out and that it wasn't compatible with ap5 (I supposed it was referred to the optimised version)
so as I ran out of ap wus, I removed the entry to astropulse in app_info.xml.

since then I haven't received any ap (new or old, and I have the feeling it has to do with the removal of the app entry.

now to be able to crunch ap wu's again, and if I want to keep crunching the enhanced seti with the optimised app, do I need to download the ap-v5 app and add the entry in app_info.xml or should boinc realise that I want to crunch the new v5 stock?

can anyone help?

---

Robi

If you've got an altered app_info.xml you'll have to add the piece of the AP V5 to your XML file to be able to receive AP V5 WU's. If you don't add it to the XML boinc will not realise that you want any AP V5 WU's.

---

I haven't touched anything in my settings, and stopped getting any AP work for what appears to be no reason about a week ago. My preferences still say that I want them. I was crunching 5.00, and never tried to change anything to enhanced or tweaked or anything. Pure Vanilla.... I just let it run as is.

Am I missing something?

---

The directory with all the AP 5.03 files is:

Index of /sah/download_fanout

and the direct links are:

astropulse_5.03_windows_intelx86.exe

ap_graphics_5.03_windows_intelx86.exe

libfftw3f-3-1-1a_upx.dll

The bit of the app_info for v5 AP is:

<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>astropulse_5.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>ap_graphics_5.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>astropulse_5.03_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_graphics_5.03_windows_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
</app_version>

You'll need to overwrite your section for astropulse, or add it as an addition,
I'm got entries for v5 AP as well as the last version, so i still get resends.

Claggy

Compliments to Richard for correcting my mistakes in the app_info earlier

Edit: changed the link to AP Graphics

Finally got a message about AP, still haven't recieved a WU yet since making these changes

2/18/2009 5:26:32 PM|SETI@home|Message from server: No work sent
2/18/2009 5:26:32 PM|SETI@home|Message from server: No work is available for SETI@home Enhanced
2/18/2009 5:26:32 PM|SETI@home|Message from server: Your app_info.xml file doesn't have a version of Astropulse.

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_x64_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8_win_x64_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8_win_x64_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>astropulse_5.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>ap_graphics_5.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>astropulse_5.03_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_graphics_5.03_windows_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
</app_version>
</app_info>

---

"Red Warrior Needs Food Badly"

Make sure 'If no work for selected applications is available, accept work from other applications?' is selected,
I did post about it another thread, when the was no astropulse available, i then got issued AP v5.

Claggy

yep, just kinda odd that I got that message.

---

"Red Warrior Needs Food Badly"

Jason, et al...
You expressed interest and curiosity in an astropulse WU completed on an AMD64 using stock 5.03 executable.
Here's an ap 5.03 completed workunit, if the processor time can be of any help to you. WU #413213292, downloaded 2/12 ~05:05 UTC, process time (stock 5.03 for x86_64) on AMD64 was 158:58:51 hrs:min:sec, and completed just moments ago. I'm a Linux system so maybe you're looking for Windows system numbers; I see that my wingman on this WU is Intel/Windows so maybe he'll be done soon.
I have another astropulse WU in my queue which downloaded today (2/18). There are 3 seti enhanced WU's ahead of it so it'll be maybe 6 hours before it starts. It looks like the wingman on it is another Linux OS but Intel CPU so maybe the time numbers on it would also be useful. I'll check the message board in 5 or 6 days, when it is almost done, to see if numbers are wanted (or you can just check my task list, CPU #4774476, around 2/25 to get them).
An interesting observation:-- The estimated time to completion was ~84 hours when the WU downloaded, but as noted above took ~159 hours. The 2nd WU also showed estimated time to completion of ~85 hours BUT after the completed ap WU was uploaded the estimate jumped to 160 hours! Other seti enhanced WU's were estimating ~3:45 before the ap WU upload but are now showing ~6:55 although precess times close to 4 hours are typical. I guess boinc manager re-assessed its estimation parameters based on the giant ap process time. It will average things out eventually I'm sure. It's only an estimate anyway.

Gene

---

yep, just kinda odd that I got that message.

This project now has three applications: setiathome_enhanced, astropulse, and astropulse_v5. When it says your app_info.xml has no application for astropulse it is literally correct.

Note that any work for astropulse is reissued because some host had an error, failed to complete within deadline, etc. The ap_splitter processes are producing work for astropulse_v5.

                                                               Joe

Jason, et al...
You expressed interest and curiosity in an astropulse WU completed on an AMD64 using stock 5.03 executable.
Here's an ap 5.03 completed workunit, if the processor time can be of any help to you. WU #413213292, downloaded 2/12 ~05:05 UTC, process time (stock 5.03 for x86_64) on AMD64 was 158:58:51 hrs:min:sec, and completed just moments ago. ...

Gene

Cheers Gene. From stock times like that, I'm starting to get some idea of the stock application speed on different machines & platforms. I'm hoping validations against stock, of our optimised windows build, start to drift in soon so that we can release and start moving forward. Hopefully our friendly neighbourhood Linux port guy will have the time to port the code soon, and bring those times down to a more reasonable range for you.

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.

Thank you - I must have mistakenly changed acceptance to other apps to no at some time thinking it meant apps that I have not attatched to. Hopefully they will come in now.....mind you, the lack of AP has been good to my stats, helping nudge higher :-)

---