This is the first time I have seen this.
Does anyone know if the AP's are being run down before the new version is instigated?
I have not even had any resends in a little while,
but I do have about 35 still to be validated.

---

This is the first time I have seen this.
Does anyone know if the AP's are being run down before the new version is instigated?
I have not even had any resends in a little while,
but I do have about 35 still to be validated.

There is no new version. The reason there is no new AP work, is that the project is having problems getting data from Arecibo and to Berkeley. Some problems with the storage disks.

Sten-Arne

... and another problem (fixed some weeks ago) that sent out Astropulse more quickly than it should have.

So, AP "got ahead" of MB, and now we're doing mostly MB until these tapes are done, and we move to fresh tapes.

---

I thought that I had read somewhere that they were beta testing a new version that was being more specific in looking for smaller pulses.I must have mixed up somewhere.

---

This is the first time I have seen this.
Does anyone know if the AP's are being run down before the new version is instigated?
I have not even had any resends in a little while,
but I do have about 35 still to be validated.

There is no new version. The reason there is no new AP work, is that the project is having problems getting data from Arecibo and to Berkeley. Some problems with the storage disks.

Sten-Arne

There isn't a new version in service yet, but it's getting close. FiveHamlet is right - there have been tests going on at Beta.

And if you look at the applications page, you'll see that the franework was set up on 10 June. But no data yet, so I guess it's on the back burner while they sort out the MB splitters.

Thanks for that Richard I thought the old grey stuff was giving out on me.lol

---

I thought that I had read somewhere that they were beta testing a new version that was being more specific in looking for smaller pulses.I must have mixed up somewhere.

The new version is also much faster. I don't think it has much to do with a lack of Astropulse.

---

There isn't a new version in service yet, but it's getting close. FiveHamlet is right - there have been tests going on at Beta.

And if you look at the applications page, you'll see that the franework was set up on 10 June. But no data yet, so I guess it's on the back burner while they sort out the MB splitters.

I'm reasonably sure that there have been at least two 'tapes' pulled back from NERSC and split for AP since June 10. That ought to mean at least several thousand AP_v505 tasks have been sent out, but with the 9 million or so MB tasks over the same period it's not surprising that the AP_v505 work hasn't been seen. Many who frequent these forums won't see any because their app_info.xml files don't yet have a suitable application listed. Those few of us trying to Beta test the optimized AP_v505 app may have missed the boat, IIRC those newly split 'tapes' were soon after June 10.

User "Taiwanese Taipei" posted that there was an AP_v505 WU on June 12, though those hosts are hidden so it wasn't confirmed.

EDIT: Found one! WU 457793346

name ap_30mr09ad_B0_P1_00012_20090611_11967.wu
application Astropulse v505
created 11 Jun 2009 17:45:06 UTC

                                                                Joe

I did miss the boat for new ap_v505 tasks, but I did go and grab the stock app and libfftw and add them both to my app_info a few days ago just in case luck of the draw worked in my favor. Still nothing yet, but we'll see with time.

---

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

What's funny about this whole thing was the resistance to AP when it first appeared. Many complained that AP WUs took too long to crunch. They may take longer, but the payoff in credit per hour makes it worthwhile. They go away and I watch my RAC fall. In the SETI world that doesn't matter, everyone is hit equally, but if you care about your standing in the BOINC world (like that pays the bills or something useful - HA!) then it matters.

In any case, we see new AP WUs when we see them. Happy crunching!

---

What's funny about this whole thing was the resistance to AP when it first appeared. Many complained that AP WUs took too long to crunch. They may take longer, but the payoff in credit per hour makes it worthwhile. They go away and I watch my RAC fall. In the SETI world that doesn't matter, everyone is hit equally, but if you care about your standing in the BOINC world (like that pays the bills or something useful - HA!) then it matters.

In any case, we see new AP WUs when we see them. Happy crunching!

The initial resistance to AP was because they took so long and didn't have an Opt. App. to make them 'profitable' credit-wise. Once Lunatics did their magic, the cr/hr on AP went WAY up and demand followed accordingly.

The initial resistance to AP was because they took so long and didn't have an Opt. App. to make them 'profitable' credit-wise. Once Lunatics did their magic, the cr/hr on AP went WAY up and demand followed accordingly.

True, and once the server-side credit adjustment adapts to Astropulse v505 the credits will be much less, at SETI Beta they've come down to around 683. That's because the stock AP_v505 is more efficient because I contributed some of Raistmer's work. Feel free to throw brickbats my way, I'm more concerned with productivity than credits. I'm not unsympathetic to those who enjoy the credit competition, just thought I should drop a warning here for those who might not have seen the credit decrease coming.

                                                               Joe

Where does one get the v5_05 app from? I can't seem to find it anywhere or am I having a blonde moment.

---

What's funny about this whole thing was the resistance to AP when it first appeared. Many complained that AP WUs took too long to crunch. They may take longer, but the payoff in credit per hour makes it worthwhile. They go away and I watch my RAC fall. In the SETI world that doesn't matter, everyone is hit equally, but if you care about your standing in the BOINC world (like that pays the bills or something useful - HA!) then it matters.

In any case, we see new AP WUs when we see them. Happy crunching!

The initial resistance to AP was because they took so long and didn't have an Opt. App. to make them 'profitable' credit-wise. Once Lunatics did their magic, the cr/hr on AP went WAY up and demand followed accordingly.

Exactly.....
And the same process will take place when the 'new' AP is released....at least for the kitties.
Credit analysis will take place, and the kitties will feed at the kibble bowl that offers the best return credit-wise on their crunching.
Could be that the Lunatics crew will find the stock app a hard act to follow this time...LOL.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Where does one get the v5_05 app from? I can't seem to find it anywhere or am I having a blonde moment.

For those running stock applications, BOINC would get it whenever needed. The optimized version hasn't been released yet. We're still Beta testing it and will release it when we're sure it's good. So those running optimized as you are will have to wait awhile.

If you're really anxious, it is possible to download the stock AP_v505 and edit your app_info.xml so the Scheduler could send an AP_v505 WU to your host. But since very little work has been split for AP_v505 you probably wouldn't see one soon anyhow.

                                                                 Joe

Where does one get the v5_05 app from? I can't seem to find it anywhere or am I having a blonde moment.

For those running stock applications, BOINC would get it whenever needed. The optimized version hasn't been released yet. We're still Beta testing it and will release it when we're sure it's good. So those running optimized as you are will have to wait awhile.

If you're really anxious, it is possible to download the stock AP_v505 and edit your app_info.xml so the Scheduler could send an AP_v505 WU to your host. But since very little work has been split for AP_v505 you probably wouldn't see one soon anyhow.

                                                                 Joe

I did the latter method. Have not seen a 505 yet, but I should be able to do it with stock if one comes my way.

---

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

Where does one get the v5_05 app from? I can't seem to find it anywhere or am I having a blonde moment.

For those running stock applications, BOINC would get it whenever needed. The optimized version hasn't been released yet. We're still Beta testing it and will release it when we're sure it's good. So those running optimized as you are will have to wait awhile.

If you're really anxious, it is possible to download the stock AP_v505 and edit your app_info.xml so the Scheduler could send an AP_v505 WU to your host. But since very little work has been split for AP_v505 you probably wouldn't see one soon anyhow.

                                                                 Joe

Hello Joe,

Do you know whether units will still be distributed for the 'old' ap version (5.03) once there are new tapes?

I'm asking because I'm running a little test on running astropulse and cuda together on an i7 and I've had to postpone my testing because I ran out of astropulse units. I guess that what I really want to know is whether I will be able to resume my testing once new tapes are split for astropulse work, or whether all the new work will have to be crunched using the new 5.05 application .... That would mean a premature end to my tests :-)

Regards,
John.

Do you know whether units will still be distributed for the 'old' ap version (5.03) once there are new tapes?

I'm asking because I'm running a little test on running astropulse and cuda together on an i7 and I've had to postpone my testing because I ran out of astropulse units. I guess that what I really want to know is whether I will be able to resume my testing once new tapes are split for astropulse work, or whether all the new work will have to be crunched using the new 5.05 application .... That would mean a premature end to my tests :-)

Regards,
John.

I do not expect any more AP_v5 (5.03) work to be split. There will be reissues of tasks for existing WUs for awhile, but there are only 79,121 AP tasks "out in the field" and some of those are already AP_v505.

Once we get the optimized 5.05 out, you should be able to resume testing. It is very little changed from optimized 5.03, the reason 5.05 has to be treated as a different application is adjustments to how signals are reported rather than changes to the science algorithms.

                                                                 Joe

Once we get the optimized 5.05 out, you should be able to resume testing. It is very little changed from optimized 5.03, the reason 5.05 has to be treated as a different application is adjustments to how signals are reported rather than changes to the science algorithms.

                                                                 Joe

Okay, thanks for the answer. I guess I'll just have to make sure results are comparable when I resume testing. A test within a test ....

Regards,
John.

the reason 5.05 has to be treated as a different application is adjustments to how signals are reported rather than changes to the science algorithms.

Is the way the signals stored going make processing of work units faster & dose anyone know if the work units still going to be 8MB in size to download?

---

the reason 5.05 has to be treated as a different application is adjustments to how signals are reported rather than changes to the science algorithms.

Is the way the signals stored going make processing of work units faster & dose anyone know if the work units still going to be 8MB in size to download?

AP tasks are still 8MB, and probably always will be. The Seti (MB) tasks have always been ~350KB.

The default Ver 5.05, over on the Beta site, is quicker than the default 5.03 app. Takes ~90k sec compared to ~130k sec, on my quad.

edit] optimised app takes 43k sec +/- 20%, depending on blanking or repetitive pulses.