We've released the Astropulse version 6 application to the SETI@home project. The only real difference is a couple of minus signs in the code that were added to match changes to the way the data recorder works.

It'll take a while for the credit granted by this application to settle out to a reasonably constant value. If you run optimized applications, I'd suggest you wait a couple of weeks before starting to do Astropulse v6 work just to avoid the possibility that you will be granted an extremely low credit for your work.

---

@SETIEric@qoto.org (Mastodon)

Thanks for the "Heads-up" Eric.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

Questions and problems to Updating for upcoming apps..... in the Number Crunching forum, please.

Is Astropulse V6 going to ever be released for OSX? Or is that just another unsupported feature of SETI BOINC on OSX? I am considering stopping donations to SETI until my chosen platform is completely supported!!!

---

It'll take a while for the credit granted by this application to settle out to a reasonably constant value. ...

"a while" as in years?

For the "old" apps the credit system still seems to be a random number generator ...

Preaching to the choir on that one. The FLOP counting credit system was far more stable than the current one.

---

@SETIEric@qoto.org (Mastodon)

We've released the Astropulse version 6 application to the SETI@home project. The only real difference is a couple of minus signs in the code that were added to match changes to the way the data recorder works.

It'll take a while for the credit granted by this application to settle out to a reasonably constant value. If you run optimized applications, I'd suggest you wait a couple of weeks before starting to do Astropulse v6 work just to avoid the possibility that you will be granted an extremely low credit for your work.

Dear Eric,

Thank you very much for this update.

Keep searching
Best wishes
Byron

Is AstroPulse going to support CUDA? It could really use the GFLOPS. =)

---

We plan that eventually it will support CUDA and OpenCL. Unfortunately Astropulse has lots of twisty turny passages, so I don't expect the speedup will be that huge. It'll probably spend a lot of time using CPU to avoid bogging the GPU down with unproductive stuff.

I'll try to get some Mac builds working next week. It probably won't support graphics when first released, but it will be better than nothing.

---

@SETIEric@qoto.org (Mastodon)

"twisty turny passages" huh? Is that technical phrasing? ;)

"grad student code" seemed too mean. ;)

---

@SETIEric@qoto.org (Mastodon)

We plan that eventually it will support CUDA and OpenCL. Unfortunately Astropulse has lots of twisty turny passages, so I don't expect the speedup will be that huge. It'll probably spend a lot of time using CPU to avoid bogging the GPU down with unproductive stuff.

I'll try to get some Mac builds working next week. It probably won't support graphics when first released, but it will be better than nothing.

Thanks Eric. I know you have a lot to do so I do thank you for the time spent.

---

Based on your post I changed my Preferences to "No" for Astropulse v6 but then shortly thereafter received some downloads. I assume I received them because I had indicated an openness to receive "Other applications" if applications I agreed to were not available. Since I don't run "optimised" I'll do them, and I heve closed the loophole (if that is what happened.
BTW Credit for Astropulse (any version) is slow in coming.
Regards

Yeah, that's always been the problem with Astropulse, since it can take days for a result to be computed, and a computer might not start computing it for a week or more sometimes you'll wait weeks for credit. But in your "Recent Average Credit" it should even out eventually.

---

@SETIEric@qoto.org (Mastodon)

Just got 832.47 credits for an astropulse unit which took 1350353.04 s on my Solaris 11 Virtual Machine. The BOINC client and the app are by Dotsch. My CPU is an Opteron 1210 at 1.8 GHz running SuSE Linux 11.1 32-bit. But the Solaris 11 guest OS is a 64-bit.
Tullio

---

Just got 832.47 credits for an astropulse unit which took 1350353.04 s on my Solaris 11 Virtual Machine. The BOINC client and the app are by Dotsch. My CPU is an Opteron 1210 at 1.8 GHz running SuSE Linux 11.1 32-bit. But the Solaris 11 guest OS is a 64-bit.
Tullio

Congratulations on completing such an epic task with just 18 hours to spare.

But note that your app is the older v505 type. You will have to ask Dotsch to compile the new v6.01 app for Solaris if you wish to continue the quest.

I've been getting 1-2 Astropulse projects per week for quite a few months. Nothing out of the ordinary about them. Suddenly a couple of days ago I got 2 HUGE astropulse projects that were easily 3-4 times the size of any of the previous ones & one was labled "High Priority". What made it high priority?

Carol

---

Those two are of the new version (v6.01). I assume by "HUGE astropulse projects" you mean "AstroPulse tasks with unusually long runtime estimates" ;-)

That estimate is caused by the fact that these tasks are of a "new" application and will be get better with time. But because of that estimate, BOINC "thinks" it won't finish them in time without entering High Priority mode.

So, don't worry, just let them run. When enough tasks have been processed, the estimates will be better and no "High Priority" will occur any longer.

Gruß,
Gundolf

I've been getting 1-2 Astropulse projects per week for quite a few months. Nothing out of the ordinary about them. Suddenly a couple of days ago I got 2 HUGE astropulse projects that were easily 3-4 times the size of any of the previous ones & one was labled "High Priority". What made it high priority?

Carol

Questions like this are usually best asked in the Number Crunching or Q & A sections of this message board. But the point you've raised is a general one, and no doubt others will be wondering the same thing - so let's deal with it here.

In actual practice, you will find that the new tasks run for very much the same length of time as the previous ones. Previously, you would occasionally get a task which finished abnormally quickly: there should be fewer of those, this time.

The 'huge' task size you're seeing is actually just an estimate - and a bad estimate, at that. BOINC is notoriously bad at making initial estimates when something new comes along: even though this change is relatively small, BOINC throws away all its accumulated knowledge of how fast your machine is, how big the tasks really are, and so on: it starts again from scratch.

And, starting from scratch, it's thinking (initially) that you may have difficulty completing the task before the deadline set for its return. That's all that 'high priority' means - 'do this job before any of the others, just in case'. Once it has been running for a few hours, the estimate will become more realistic and that 'high priority' flag should disappear.

That's for this task. It takes some time to persuade BOINC (again) to accept how fast your machine really is. The next Astropulse task you receive will have the same inflated runtime estimate as this one. And the next. And the one after that. You will, I'm afraid, have to complete at least ten Astropulse tasks - possibly more, depending on the luck of the draw - before things return to normal. In the meantime, just ignore these queue-jumpers and let your machine go about its business as usual.

My APv6.0 units run time in 160 hours (est) at first. Then even before it started running the first new APv6.0 an ajustment happened run time 26 hours(est).

bye for now
Dave

---