Can anyone explain the difference between Astropulse and Astropulse v5, does one require more resources or crunch faster than the other?

Just out of curiosity really as I have all 3 selected on my S@H prefs but I only ever seem to get v5 wu's.

---

Bambi

Can anyone explain the difference between Astropulse and Astropulse v5, does one require more resources or crunch faster than the other?

Just out of curiosity really as I have all 3 selected on my S@H prefs but I only ever seem to get v5 wu's.

The application called just 'Astropulse' is older, and was superceded by 'Astropulse_v5' about three months ago. There are still a few of the older-style tasks floating around in the database, waiting for someone with the guts and stamina to finish them off - if you can be that person, so much the better. But no new WUs are being, or ever will be, created for 'Astropulse'.

The newer version, 'Astropulse_v5' is where the action is at the moment. They take longer, but because they do a more thorough search (more work), not because they are intrinsically slower.

In due course, there will be another rotation, and another new app (no name as yet). AFAIK, the plans are that this will do a similar amount of searching as _v5, but more efficiently, so the time they take to crunch should come down significantly.

Send them to me Ill crunch anything! lol I have a WU from CPDN that has 1077 hrs done and another 1564 hrs to go! its a 160 yr model that will wind up with somewhere around 47000 credits when complete

Rick

Cheers for the answer :)

---

Bambi

Out of interest why are AP work units 8mb to download yet the upload is only a few kb? Thanks in advance.

---

Out of interest why are AP work units 8mb to download yet the upload is only a few kb? Thanks in advance.

We're looking for a needle in a haystack.

You download the whole haystack, but only upload the needle.

We're looking for a needle in a haystack.

You download the whole haystack, but only upload the needle.

When a work unit is been progressed sometimes it does a rather large jumps, is this because the frequency is only a few mhx instead of ghz?

---

When a work unit is been progressed sometimes it does a rather large jumps, is this because the frequency is only a few mhx instead of ghz?

No, if the progress jumps up by about 0.34% that's because the optimized app stops doing repetitive pulse finding after the limit of 30 of those have been found. Skipping those sections does cause jumps like that at up to 111 equally spaced places.

Processing the work is like listening to the radio, what frequency it was originally doesn't matter, it's the variations which carry the information.

                                                                 Joe

Thanks for your answer joe.

---

When a work unit is been progressed sometimes it does a rather large jumps, is this because the frequency is only a few mhx instead of ghz?

No, if the progress jumps up by about 0.34% that's because the optimized app stops doing repetitive pulse finding after the limit of 30 of those have been found. Skipping those sections does cause jumps like that at up to 111 equally spaced places.

Is a workunit stopping doing repetitive pulse finding after the limit of 30 if it jumps back about 0.4%. Sometimes it will only jump back by 0.04%

---

When a work unit is been progressed sometimes it does a rather large jumps, is this because the frequency is only a few mhx instead of ghz?

No, if the progress jumps up by about 0.34% that's because the optimized app stops doing repetitive pulse finding after the limit of 30 of those have been found. Skipping those sections does cause jumps like that at up to 111 equally spaced places.

Is a workunit stopping doing repetitive pulse finding after the limit of 30 if it jumps back about 0.4%. Sometimes it will only jump back by 0.04%

No, that one is because for 5.03 the project added processing for repetitive pulses with negative dispersion but didn't update the progress indications. So it does the sections of the code used for that twice each time it's needed (once for negative, again for positive), both times showing the same progress. The 0.04% retraces are due to the checking for short period repetitive pulses, and would happen 777 times during a WU which doesn't reach the 30 limit. The 0.4% retraces are places where it does both short and long period repetitive pulse searching, those are the same 111 places where skipping repetitive pulse finding jumps the progress up by 0.34% to 0.4%. I just estimated that 0.34% earlier, haven't taken the time to actually watch it closely.

                                                                  Joe

With the clearing out of AP v5.03 are we perchance going to v5.05? Just a question.

---

With the clearing out of AP v5.03 are we perchance going to v5.05? Just a question.

I hope not. Although the Windows 5.05 is performing admirably at SETI Beta, the Linux builds have multiple problems. It would be better to get those fixed and tested before release. There are changes in the reporting of signals which will require a new application name (perhaps Astropulse v6?), so it won't be practical to leave Linux on the old version while transitioning Windows to the new.

                                                                 Joe

I think I missed it.
You said we have just cleared the Astro Pulse?
No more AP to crunch? I have been dry for the last 36 hours or so.

Martin

---

I think I missed it.
You said we have just cleared the Astro Pulse?
No more AP to crunch? I have been dry for the last 36 hours or so.

Martin

What most are seeing is resends, until new images can be downloaded. I did see the AP Spillters online for a bit as they got a new image online.

---

Please consider a Donation to the Seti Project.

Thanks Pappa.
I got confused there for awhile.
I only like to crunch AP since my rotation of AP is quite decent.

Martin

---

I read the FAQ' with regards to Astropulse, however it doesn't explain why it takes so much longer to complete. Are the files bigger? It has taken me sixteen hours to complete only thirty percent of the file while a typicel Seti WU only takes around ten minutes. I have been away for awhile and apparently things have changed.

Another Question if I might ask one that is probably outside this thread. but does SLI help or hinder the time it takes to complete a WU?

---

Yes, the files are bigger and go into much more depth. They also pay a lot better giving 1200+ credits for each. As for SLI, it is better to disable it as if it is engaged the project only sees one big card and will only run one WU at a time. If you have more than one processor then without SLI you can run two or more depending on how many processors you have.

---

PROUD MEMBER OF Team Starfire World BOINC

AP are 8Mg in "lenght" compared to about 366Kb for a regular MB (Multi Beam).
SLI will not help in anyway.
For better GPU crunching they have to be run seperately thus improving the effeciency.

Martin

---

I read the FAQ' with regards to Astropulse, however it doesn't explain why it takes so much longer to complete. Are the files bigger? It has taken me sixteen hours to complete only thirty percent of the file while a typicel Seti WU only takes around ten minutes. I have been away for awhile and apparently things have changed.

More important than the "size" others have mentioned, the signal processing is simply different.

Astropulse is looking for wide band (broadband) pulsed signals instead of narrow band signals.

---