See Matt's post

---

I don't think we know when AP will be turned back on again. I think we're waiting for the current batch of WUs out in the field to crunch and be completely done before releasing a new client.

This is what Matt wanted to do during the v4.36 -> v5.00 changeover, but somebody came along behind him the next day and turned the splitters back on, so they just kind of rode it out and dealt with issues as they arose.

---

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

On Beta there's the new v5.01 in test now. Vonkorff wrote:

Workunits need to have certain segments "blanked" (covered over) when those segments contain pulses of radar that come from the Earth rather than space.

This version of Astropulse is supposed to blank workunits using "shaped" noise (that has the same frequency distribution as the rest of the data) instead of "white" noise (that has all frequencies equally, and therefore tends to cause false signals because it contrasts with the rest of the data.)

If this version works, the next steps are:

1. Introduce this client in the public project
2. Introduce the new splitter that also uses shaped noise.
3. If this results in a lot less false signals, we can start storing more signal data in our database.

Key words:"If this version works". At the moment I'm crunching a 5.01 WU and on a E7500 it takes approx. 120 HOURS to finish. This is a lot and frankly I think a lot of users will terminate these jobs or simply run out of time before it's due.

Secondly, because of the new splitters the WU's probably aren't interchangeable between 5.00 and 5.01. So you'd like to finish 5.00 units first and only then start issuing new 5.01 WU's. Like Cosmic_Ocean said, it gave a lot of (backstage) problems when they switched from v4 to v5.

---

My BOINC client just got a (single) AP unit!

Guess the splitter is back online! :)

---

My BOINC client just got a (single) AP unit!

Guess the splitter is back online! :)

Nope, you just became 4th wingman on that unit.

---

same here... a re-issued AP, but I'll take it (better not to worry about the queue going dry for a while).

Also, still having a few AP WU's crunching, lucky on the fastest host, which does them in ~7 - 8 hours. Using latest optimized AP 5.0 version.
An X9650 @ 3.7GHz, FSB 1640MHz. WIN XP64 ; BOINC 6.5.4 , which gets, after a few weeks, the right amount off WU's. The cache setting has little effect on this version, I noticed.
It doesn't run dry or uses High Priority Mode, now.
The last AP WU's, are 2nd, 3rd (or even 4th), sended out.

---

same here... a re-issued AP, but I'll take it (better not to worry about the queue going dry for a while).

Also, still having a few AP WU's crunching, lucky on the fastest host, which does them in ~7 - 8 hours. Using latest optimized AP 5.0 version.
An X9650 @ 3.7GHz, FSB 1640MHz. WIN XP64 ; BOINC 6.5.4 , which gets, after a few weeks, the right amount off WU's. The cache setting has little effect on this version, I noticed.
It doesn't run dry or uses High Priority Mode, now.
The last AP WU's, are 2nd, 3rd (or even 4th), sended out.

On this resent Workunit 391121691 I have received the 5th copy.

I was wondering why I was getting AP work units on two of my computers, this thread tells me why. I never checked to see if they were re issued work units

---

Same here, my Quad has been blessed with an re-issued AP.

But that means that the splitters are not used when it is not the original 'release' of the WU ? Could someone explain ?

It was originally split, sent out to two people, finished and reported. They either weren't similar enough or one of them timed out so they went out to a third machine. This process doesn't require spliting again. This will continue until they get two results that agree or they reach the limits.

---

PROUD MEMBER OF Team Starfire World BOINC

Same here, my Quad has been blessed with an re-issued AP.

But that means that the splitters are not used when it is not the original 'release' of the WU ? Could someone explain ?

Reading the last part of the Server Status page gives an initial insight into how a workunit and its results/tasks are processed though the system.

Same here, my Quad has been blessed with an re-issued AP.

But that means that the splitters are not used when it is not the original 'release' of the WU ? Could someone explain ?

There's just one file on the server for each WU, the URL to download it is given to each host told to crunch it. With AP WUs being 8 MB, it would be very inefficient to have more than 1 copy on the server, and it would be even worse to have to go back and make a new one from the raw data.

                                                                  Joe

It would have been a nice gesture on the part of the project managers to
place a sticky in the Number crunching forum as to why there are no AP wu's.

See Tech News Feb 02

Is Astropulse finished, was it a dumb idea to begin with, is a new app in
the works, or what?

See AP V5.01

"We The People" are not mushrooms!

I don't think i should have to go to the Beta site or Technical News to
find out what's going on, especially when AP at one time was 1/2 of the
Seti menu. If you're gonna change things at least let us know.

Actually, I think "Technical News" is exactly the right place to go for, well, technical news.

But I agree, it would be nice to actually have a 'hard news' thread, as well as Matt's entertaining and informative blogging.

There is new technical news in Technical News.

I totally understand why the AP splitters are disabled right now. But it sure would be nice to turn the VALIDATORS back on and clear that backlog of ~190K results pending validation.

Whether data is going to be reprocessed or not under 5.01 or later revisions, users should get their credit for God knows how many CPU-hours already invested. I don't crunch S@H solely for the credit, but it IS part of the mix.

---

Best wishes:)

I totally understand why the AP splitters are disabled right now. But it sure would be nice to turn the VALIDATORS back on and clear that backlog of ~190K results pending validation.

Whether data is going to be reprocessed or not under 5.01 or later revisions, users should get their credit for God knows how many CPU-hours already invested. I don't crunch S@H solely for the credit, but it IS part of the mix.

The fact that the validators are off does not mean that they'll stay off.

... and I don't think there is any decision by the project to end Astropulse. If they know that they've got an extra load (explained in the technical news) and they know there is no new AP going out, they know the AP validator queue is not growing, so stopping it allows extra time for the Informix database to add new fields.

---

I prefere to run Astropulse and I still have over 100 AP work units waiting to be validated. The fact is that anytime there is even a hint of a problem with the system, Astropulse is taken offline.

Seti lacks the resources to run both projects together adequately. Both in available bandwidth and computer hardware.

[edit]looks like Astropulse is coming online now with version 5.03!

---

Boinc....Boinc....Boinc....Boinc....

FYI, Astropulse 5.03 was released and workunit generation is back on. However, because the results are not compatible with 5.02, it was added as a new application (astropulse_v5).

---

@SETIEric@qoto.org (Mastodon)

FYI, Astropulse 5.03 was released and workunit generation is back on. However, because the results are not compatible with 5.02, it was added as a new application (astropulse_v5).

Thanks for staying late and getting AstroPulse back online Eric.

---

Boinc....Boinc....Boinc....Boinc....