Today was a day mostly spent tracking down little problems involving BOINC, Astropulse beta, the Astropulse 5.00 release, the beta SETI@home splitter, raw data pipeline flow, data drives reporting wrong capacities to the OS... Lots of bizarre problem solving.

As for Astropulse 5.00 and an "official" statement (which was requested in the last thread) I just have to step back a moment and tell everybody that these threads are for entertainment purposes only and nothing I say should be considered official. I just work here and happen to suffer from hypergraphia. I do understand this is the most dynamic form of news on this site and so I nag the others to add content here and elsewhere. They never do, and I end up looking like the de facto spokesperson.

In practice, due to the incredible web of resource dependencies behind the scenes here, I have to keep tabs on pretty much every aspect of the whole BOINC/SETI@home/Astropulse family of projects since each program, server, budget constraint, etc. affects everything else. Jeff has to do the same. Nevertheless we can only keep track of so much, and what I believe is going to happen doesn't always necessarily happen.

That said.. from what I know and understand Astropulse queues did drain last week and the new client was released on Friday or Saturday. The vader choke hampered this a little bit, but shouldn't have affected progress on this front that much. Josh is a little puzzled about current results, or lack thereof. That was part of the problem solving today. I still have no real handle on the current Astropulse plans - just temporarily offering my mysql/BOINC expertise to the "Astropulse committee" (Josh and Eric) and then getting back to work on something else.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

According to the graphs kindly maintained by Scarecrow, the queues never got very dry:



(there are long-term records of the other Server Status Page metrics on that site, too).

My machine, using the optimized 4.35 AP app has downloaded work as recently as today, marked to be crunched by the 4.35 app. I don't know if there's a minimum version for the new work, or if the scheduler still allows the older app to crunch the newer work or if I'm messing up science by doing this unintentionally.

Josh is a little puzzled about current results, or lack there of

Do more people need to be crunching AP work units when they are available?

---

... these threads are for entertainment purposes only and nothing I say should be considered official. I just work here and happen to suffer from hypergraphia. I do understand this is the most dynamic form of news on this site ...

And as often (too often?) posted, much appreciated by the s@h audience. The technical detail and mechanics mentioned put a little real-world life into mind bogglingly numbing big numbers. It also helps to lessen the ignorant irritation for those 'high stress credits hogs' when things can't or simply don't run smoothly.

Perhaps hypergraphia is a good thing!

;-)

Regards,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

. . . Thanks for the Updates Matt [i am quite sure Eric appreciates iT Sir]

---

BOINC Wiki . . .

Science Status Page . . .

Matt,

I'm sorry, I should have said a big "thank you" for devoting so much of this thread opener to my AP question. I don't post thanks as a matter of routine, but believe me, your hypergraphia is much appreciated in the community.

In your unofficial role as rapporteur to the Astropulse committee, could you endeavour to find out what they would like us to do with resent v4 tasks, please? It's a little bit tricky, now that the decision to install AP 5.00 as a version upgrade, rather than

<app_name>Astropulse</app_name>
<app_name>Astropulse_5</app_name>

an application upgrade seems to have become a fait accompli.

Josh is a little puzzled about current results, or lack there of

Josef Segur was monitoring this over the weekend, and has - as always - a clear diagnosis which Josh will be able to read at KSWN when their server is back up - you're not the only one with server problems, Matt!