Finally got around to adding some new code to the server status page to show multibeam splitter progress. Pretty simple right now, but it shows how many beam polarization pairs have been split (or are in process of being split) on any given file. There are 7 beams, 2 polarizations per beam, so 14 total pairs. We're keeping a lot of multibeam data on line at any given time, so the list is rather long... I'll get around to condensing that information somehow someday.

Why 50GB files? Why not fill the whole drive (usually at least 500GB) with one file? Well.. it's a bit easier to deal with smaller files in general, but the main reason is for better transfer down to HPSS for archiving - the file transfer utilities provided by HPSS seem to barf at file sizes greater than 50GB. So there ya go. Plus our data acquisition rate in classic used to be about 50GB a day, so we're used to handling that number when referring to data rates.

- 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

The splitter status list looks neat. Thanks for updating that code. Now we can see splitter progress as well. The list isn't too long; actually it's about the same length as the server list.

Good News Sir! Thanks for the Post Matt . . .

MATT, ARE WE HAVING PROBLEMS IN GRANTING CREDIT? I HAVE NEVER HAD SO MANY PENDING WORK UNITS, OVER 600+ HOURS. MY PERCEPTION IS THAT IT STARTED BUILDING UP AFTER THE LAST BACKUP OUTAGE, COULD BE WRONG ON THAT.

---

MATT, ARE WE HAVING PROBLEMS IN GRANTING CREDIT? I HAVE NEVER HAD SO MANY PENDING WORK UNITS, OVER 600+ HOURS. MY PERCEPTION IS THAT IT STARTED BUILDING UP AFTER THE LAST BACKUP OUTAGE, COULD BE WRONG ON THAT.

There's nothing Matt can do.

The other systems need to return their results before you can be granted credit.

---

Thank you to all, who have helped via all these theads for me to become a better wingwomen. I check the progress of my wingpeople twice a day to run units that are waiting for completion/validation/credits. Evenso most of you recommend to let BOINC do it's thing, it worked for me. And hopefully for my wingperson, not getting any work during my suspends will be appreciated.

---

Pluto will always be a planet to me.

Seti Ambassador
Not to late to order an Anni Shirt

Thank You Matt for the updated status page! Love the splitting status bar graphs.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I like it...

Clean, simple (to me), straightforward and informative.

What more could we need? (Don't actually answer that please)...

---

Never surrender and never give up. In the darkest hour there is always hope.

MATT, ARE WE HAVING PROBLEMS IN GRANTING CREDIT? I HAVE NEVER HAD SO MANY PENDING WORK UNITS, OVER 600+ HOURS. MY PERCEPTION IS THAT IT STARTED BUILDING UP AFTER THE LAST BACKUP OUTAGE, COULD BE WRONG ON THAT.

Remember that work used to go out to three systems, and credit was granted when two returned their results. You'd get credit when the faster of the other two returned their work.

Now, work is sent to two, and credit is granted when two return that work.

If you are paired with a fast system, you'll get your credit quickly. If you are paired with someone who carries a large queue, it will take a while.

It is the same for everyone.

---

MATT, ARE WE HAVING PROBLEMS IN GRANTING CREDIT? I HAVE NEVER HAD SO MANY PENDING WORK UNITS, OVER 600+ HOURS. MY PERCEPTION IS THAT IT STARTED BUILDING UP AFTER THE LAST BACKUP OUTAGE, COULD BE WRONG ON THAT.

Remember that work used to go out to three systems, and credit was granted when two returned their results. You'd get credit when the faster of the other two returned their work.

Now, work is sent to two, and credit is granted when two return that work.

If you are paired with a fast system, you'll get your credit quickly. If you are paired with someone who carries a large queue, it will take a while.

It is the same for everyone.

And if you get a WU like this one, none of the above apply.

Sometimes there's a difference between theory and practice.

My pendings are at record high, 5550 (about three daysworth at current RAC). I have my cache set at one day. Maybe I should increase that to two days. But then, if Seti data supply ceases, I'll just get that much more Einstein to crunch which will, sooner or later, reduce the RAC.

---

And if you get a WU like this one, none of the above apply.
Sometimes there's a difference between theory and practice.

Thanks for this Richard - I hope Matt can investigate and find any others like it.

Matt, could you justify why deadlines are so unreasonably long, at *8* weeks?

Andy.

And if you get a WU like this one, none of the above apply.
Sometimes there's a difference between theory and practice.

Thanks for this Richard - I hope Matt can investigate and find any others like it.

Don't hold your breath - the idea of a "News" bulletin is one-way: they talk, we listen.

I think your original plan - the one involving a housebrick - is more likely to get results.

And if you get a WU like this one, none of the above apply.
Sometimes there's a difference between theory and practice.

Thanks for this Richard - I hope Matt can investigate and find any others like it.

Matt, could you justify why deadlines are so unreasonably long, at *8* weeks?

Andy.

It has already be acknowleged that the 'to completion' estimates are on the long side since MB came online. Matt does not need to 'justify' anything. An adjustment is in order, and I suspect that it will be done when enough data is in place to do so.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I think your original plan - the one involving a housebrick - is more likely to get results.

:-)

In fact I had a 'pet' housebrick that I reserved for such occasions... but it was just such a beautiful and unusual specimen, I couldn't bring myself to damage it!

Exwife probably threw it away with everything else I treasured...

An adjustment is in order, and I suspect that it will be done when enough data is in place to do so.

Mark, I'm sure there's enough data now! As you know, it's so annoying when someone just buggers off and leaves the rest of us high and dry for another couple of months.

The BOINC system needs a heartbeat detector so that if someone doesn't make *any* contact at all for a week, then all uncrunched WUs are returned to the pool.
If they are actively crunching through their cache, then deadlines could be extended for any WUs in progress but at risk of not completing.
The worst that can happen is that if they do come back, then they have to download some new WUs. An itsy bitsy inconvenience compared to our enduring frustration!

Some people have obviously gone AWOL, and an admin override to return WUs to the pool would be nice.

Make it clearer in the docs, that it is very unpolite to leave a project in limbo.

Oh, and while I'm at it, implementing redirect after post when submitting a message here is the correct way to write a bulletin board, to avoid double posts and paying twice etc.

Andy.

An adjustment is in order, and I suspect that it will be done when enough data is in place to do so.

Mark, I'm sure there's enough data now! As you know, it's so annoying when someone just buggers off and leaves the rest of us high and dry for another couple of months.

The BOINC system needs a heartbeat detector so that if someone doesn't make *any* contact at all for a week, then all uncrunched WUs are returned to the pool.
If they are actively crunching through their cache, then deadlines could be extended for any WUs in progress but at risk of not completing.
The worst that can happen is that if they do come back, then they have to download some new WUs. An itsy bitsy inconvenience compared to our enduring frustration!

Some people have obviously gone AWOL, and an admin override to return WUs to the pool would be nice.

Make it clearer in the docs, that it is very unpolite to leave a project in limbo.

Oh, and while I'm at it, implementing redirect after post when submitting a message here is the correct way to write a bulletin board, to avoid double posts and paying twice etc.

Andy.

If you're looking for a canidate to flush, how about this guy He's holding 52 hostages, I'm one of them.

---

An adjustment is in order, and I suspect that it will be done when enough data is in place to do so.

Mark, I'm sure there's enough data now! As you know, it's so annoying when someone just buggers off and leaves the rest of us high and dry for another couple of months.

The BOINC system needs a heartbeat detector so that if someone doesn't make *any* contact at all for a week, then all uncrunched WUs are returned to the pool.
If they are actively crunching through their cache, then deadlines could be extended for any WUs in progress but at risk of not completing.
The worst that can happen is that if they do come back, then they have to download some new WUs. An itsy bitsy inconvenience compared to our enduring frustration!

Some people have obviously gone AWOL, and an admin override to return WUs to the pool would be nice.

Make it clearer in the docs, that it is very unpolite to leave a project in limbo.

Oh, and while I'm at it, implementing redirect after post when submitting a message here is the correct way to write a bulletin board, to avoid double posts and paying twice etc.

Andy.

If you're looking for a canidate to flush, how about this guy He's holding 52 hostages, I'm one of them.

Add me to the list also... I can't even find this person in the user list!

---

If you're looking for a canidate to flush, how about this guy He's holding 52 hostages, I'm one of them.

That guy has a dual core 6600 which would probably knock spots off my little farm.

Except for a small hiccup when installing "chicken apps" on my systems, they just keep crunching away.

I needed to detach 1 from the project due to selling it, but before doing so, read the threads & asked questions.

Some of these guys can't really be in it for the science.

Tslking of rac, the servers are down again. Is this going to become a regular weekend thing?

---

the servers are not down they sre just having to deal with a large volume of traffic due to small work units and 10 day caches