I wanna get some Ap data, but I don't get some. What's up? No Ap data available or is my computer not set to get Ap data.

---

I wanna get some Ap data, but I don't get some. What's up? No Ap data available or is my computer not set to get Ap data.

Hard to say.
The server status pages are static at the moment. So it's anyone's guess what they are doing......but they are pumping out work, so that's a good thing.

AP is not the wonderful thing it once was, so not a big deal anymore.

---

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

AP is not the wonderful thing it once was, so not a big deal anymore.

Can you explain that for me?

---

AP is not the wonderful thing it once was, so not a big deal anymore.

Can you explain that for me?

The credits/hour of cpu time are not a big benefit that they once were.

I think they still benefit the servers, as more work out with less static reporting is a good thing. But the meow factor is not so fun now.

---

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

Astropulse is less profitable than ET?
It's interresting.
What's about fundamental research?...

I read the forum. I think that the actually astropulse is not for me and my computer...

---

just a poet

Chris, have you got all these set in your 'Seti@home' preferences? And you haven't overridden them locally?

Run only the selected applications

SETI@home Enhanced: yes
Astropulse: yes
Astropulse v5: yes

If no work for selected applications is available, accept work from other applications? yes

Your computer should be modern enough to run the AP workunits, I can't remember what the cut-off point was for Astropulse, but I think it was a 1.6Ghz Pentium/Amd.

I have received about 20 AP workunits over my 2 computers recently, so there are a few out there.

Regards, Gizbar.

---

A proud GPU User Server Donor!

Nothing else for my main machine at the minute - 2 big 80-hour-ish APs at the minute, though I'd rather do SETI, tho 2*80=160hours therefore a week which is what I've set my cache at...

There are still AP units being sent, but only 3 out of the 100 feeders handle them.

With the MB being almost out of work right now there is lots of demand for the AP units that being created. Matter of luck if you get any.

Ian

Nothing else for my main machine at the minute - 2 big 80-hour-ish APs at the minute, though I'd rather do SETI, tho 2*80=160hours therefore a week which is what I've set my cache at...

Astropulse is SETI.

Multibeam looks for narrow-band signals.
Astropulse looks for broadband signals.

---

I got something like 6 AP data the last 2 days. Guess I'm a lucky guy :)

I got something like 6 AP data the last 2 days. Guess I'm a lucky guy :)

They're being steadily created at about 0.6 tasks per second, and are more numerous than MB for now. My 200 MHz. Pentium MMX is looking for work and has several times received a Scheduler reply indicating if it could do Astropulse it would have gotten one.

                                                                Joe

I guess I've been luckly the only time I run short of work was two weeks last Tuesday , then I do an alternate project. Have enough work so far. Looking at the server status never seem to be correct. Only one or two AP units reported but but several thousand work units of MB finished. Even with the diffence in the numbers one would expect a couple of hundred AP results. Hoping the luck holds out till the new work tapes arrive.
Good wish and the best of luck to those returning to class on Tuesday.

Im down to my last 2 AP on the i7. Ill power down when those get done. Unless i can hook up some more that is.

---

[/quote]

Old James

I guess I've been luckly the only time I run short of work was two weeks last Tuesday , then I do an alternate project. Have enough work so far. Looking at the server status never seem to be correct. Only one or two AP units reported but but several thousand work units of MB finished. Even with the diffence in the numbers one would expect a couple of hundred AP results. Hoping the luck holds out till the new work tapes arrive.
Good wish and the best of luck to those returning to class on Tuesday.

I'm not sure what you mean by the "stats page never seem to be correct."

Someone will correct me, I'm sure, but for each Astropulse work unit split, there are roughly 33 multibeam work units. Put that another way, only 3% of SETI work is AP.

The numbers on the status page are first of all, a little stale. They represent the state of the system when the snapshot was taken.

At times like today, they often show very few available work units, but the interesting numbers are the creation rates. If SETI@Home splits 10 work units per second, but we crunchers request 12 per second, the available work is either zero, or is going to be zero unless something changes.

---

Hmmm...

Well, all I know for sure is I haven't gotten anything 'fresh' from SAH since 0000 hours Saturday Berkeley time. Everything since then has been a resend and none were AP.

Alinator

...
Someone will correct me, I'm sure, but for each Astropulse work unit split, there are roughly 33 multibeam work units. Put that another way, only 3% of SETI work is AP.
...

I can't pass up an invitation like that ;)

The ratio is fairly close to 40:1. An AP WU is exactly 64 blocks of data from the 'tape' file, and there's no overlap between WUs. Each group of 256 MB WUs uses 512 blocks, but the next group starts with an advance of only 409 blocks so there's a 103 block overlap (about 21.6 seconds). If it were continuous data that would give a ratio of 256 * 64 / 409 = 40.05868. Because the data is divided up into 50.2 GB files, the ratio is reduced somewhat. A channel from that size file will usually yield 62 groups of MB WUs and 400 AP WUs, so the ratio is 256 * 62 / 400 = 39.68.

Rounding, we get 2.5% of tasks are AP. The Feeder has 100 slots which can be set to deliver either about 2% or 3% but not 2.5% AP. The number of slots could be adjusted, and if we ever get back to a smooth flow of data perhaps they'll go to 80:2 or 120:3. I'd guess that FC11 should handle the larger shared memory for 124 slots assuming one slot will still be assigned to AP_v5, but don't really know.

                                                                 Joe

I'm not sure what you mean by the "stats page never seem to be correct."

The Astropulse statistics on the Server Status page certainly look odd.

The "Current result creation rate" is averaging (according to Scarecrow) a little over 0.9 results per second: the "Results received" is also around 0.9, but this time per hour. A factor od 3,600 between the two figures might suggest a black hole sucking up results and not returning them....

....but I think the explanation is more prosaic. I think the creation rate, 'out in the field' and so on relate to the current v505 application, but 'Results received' is still the dregs of the previous v5 (503) run. They're still out there, folks!

I've received two in the last 24 hours - they are being crunched as I type. I haven't had any ordinary (Multibeam ?) for ages.

---

...
Someone will correct me, I'm sure, but for each Astropulse work unit split, there are roughly 33 multibeam work units. Put that another way, only 3% of SETI work is AP.
...

I can't pass up an invitation like that ;)

which is why you were invited ;)

The ratio is fairly close to 40:1. An AP WU is exactly 64 blocks of data from the 'tape' file, and there's no overlap between WUs. Each group of 256 MB WUs uses 512 blocks, but the next group starts with an advance of only 409 blocks so there's a 103 block overlap (about 21.6 seconds). If it were continuous data that would give a ratio of 256 * 64 / 409 = 40.05868. Because the data is divided up into 50.2 GB files, the ratio is reduced somewhat. A channel from that size file will usually yield 62 groups of MB WUs and 400 AP WUs, so the ratio is 256 * 62 / 400 = 39.68.

Rounding, we get 2.5% of tasks are AP. The Feeder has 100 slots which can be set to deliver either about 2% or 3% but not 2.5% AP. The number of slots could be adjusted, and if we ever get back to a smooth flow of data perhaps they'll go to 80:2 or 120:3. I'd guess that FC11 should handle the larger shared memory for 124 slots assuming one slot will still be assigned to AP_v5, but don't really know.

                                                                 Joe

Seems like the bigger problem is that we can split AP faster than we can split multibeam, and that the production rate should be closer to the 40:1 target than it is now.

In other words, if you have tapes in the queue, the AP and MB splitters should "use up" the tapes in the same amount of time.

---

Seems like the bigger problem is that we can split AP faster than we can split multibeam, and that the production rate should be closer to the 40:1 target than it is now.

In other words, if you have tapes in the queue, the AP and MB splitters should "use up" the tapes in the same amount of time.

When there are plenty of 'tapes' the MB splitters build up a "Results ready to send" queue fairly quickly, then rest until it starts to get low, rinse and repeat. The AP splitters almost never do. If delivery could be balanced, AP ought to also build up queue then rest for awhile. As things stand, AP work goes out as soon as it's split, and the Feeder ratio seems to me to be the primary reason.

                                                         Joe