I refuse to participate in the nastiness.

I asked a legitimate question as one suggested. If you don't or can't answer the question, please don't bother to respond.

ront

---

ront, the only reliable information is on the project home page. The validator had problems over the weekend, and everything locked up as a result. "Staff" is aware, and working on it.

Almost everything you read on these Forums is speculation (other than posts from "the staff"). Some informed, most not. It should only be considered as entertainment.

---

Thank you for your response.

You are quite right and.....generally I do disregard most of what I read.

Perhaps, indeed probably, I share some of the frustration of the others. However, I do realize that beating up on "staff" will avail nothing.

In any event, once again, "staff" has worked their magic, and the system seems to be up and running.

I extend my appreciation and thanks to them...and to you.

ront

---

Well, then, how about a post when changes are being made on the Production system(s), so we users can at least know why things have gone crazy...this last outage, with the server-side changes - sure would have been nice to know it was coming, and even the reasons for it, and the way the changes were intended to work. (Then we would understand what to look for). Easy to do, if you have written a design document - if you haven't, not so much.

Then maybe you should personally try to contact the person who implemented the Boinc changes--DAVID ANDERSON. It is quite well known (historically) that he makes changes without consulting Eric and his staff in any manner-this leaves Eric and his staff to pick up the pieces and the victims of improperly placed blame. Other part of this is that David is equal or above Eric in level so there's nothing Eric can do.

I agree with people that things can be handled better but we need to find a way to make people above Eric (ie DA) acknowledge and accept that.

That's exactly the point I and others made over in the I'm Done Here thread in Number Crunching.

Most of the time, those of us who know where to look (Homepage Notices, Server Status page) know when there is a problem, what might be the cause, and whether or not it is being worked by the Seti@Home staff. We also recognize how much time Over and Above normal working hours Matt, Jeff, and Eric put in to keep this project running (not to mention copious amounts of chewing gum, hook-up wire, and duct tape - or the IT equivalent).

Most of us do not expect minute-by-minute updates during the troubleshooting and repair, especially those of us who have been in similar situations, whether in IT or other lines of work. A simple note, like today's, when they get the chance, will suffice.

But when MAJOR CHANGES are coming, it is not just nice, it is NECESSARY for those of us actually doing the crunching to get a heads-up on it, so we can watch for problems and report them. That is a MANAGEMENT responsibility, and in this case, MANAGEMENT (Dr. Anderson) failed to do his job. Change is much easier to deal with if you know what's coming, than when it jumps up out of the roadside culvert and smacks you upside the head with a club.

Yes, direct communication with Dr. A is called for, just in case he doesn't read these boards (or get a summary from the Moderators or Eric & Matt). Hopefully, learning will take place, and we won't go through this upheaval the next time a major change to BOINC or the server software comes down.

Donald
Infernal Optimist / Submariner, retired

I am certain I will not see it.

But what I would really appreciate seeing:

An acknowledgement that they installed untested bad code.

An apology to everyone (staff and volunteers alike) from anyone
involved in that DECISION.

And a promise not to do so again(i.e. TEST IT FIRST!)

Things can still go wrong. It is impossible to see what hardware
needs are if it keeps getting sent bad code. And either cripple a project.

I made the wrong assumption, that after several years seti@home would be past
initial beta testing. Instead I walked into a fresh batch of alpha testing.

This is not what I thought I agreed to do.

I salute those who attempt to maintain the hardware, but unless the incoming code is debugged before system wide implementation, It is fixing the engines on the titanic.

And there are way too many people blowing off those of us aggravated by it.

---

Janice

Been around this clubhouse long enough to realize that this effort is at best poorly managed and completely undisciplined in it's operation.

With that said unless and if these boys are wholesale let out to pasture and a professional serious bunch come into place nothing is going to change at SETI.

I would think that configuration management and documented baselines exist so that issues are predictable and manageable. Instead I hear MAtt (the only person diciplined enough to try and keep us informed as to what's happening) complain about changes and ancillary impacts and unforeseen problems all the time.

Long ago and far away I worked on spacetrack radar. We were confounded by jamming and interference and much was done to filter out and remove known signals and unknown interferers. Over 30 years ago... Long before highspeed digital computations etc. Yet SETI is recently touting its ability to filter out interferers and such from its signal analysis as if it's something new, just discovered, etc.

I'm a reluctant partner in SETI as it's the only game being played in the realm. But it doesn't mean I'm happy...

Aw well... rant rant rant... I feel better now never mind...

---

Never engage stupid people at their level, they then have the home court advantage.....

NOTE: This is addressed TO NO PARTICULAR INDIVIDUAL...

After following these posts for years this is the first time that I have felt compelled to remark on the inane, uninformed, or simply rude commentary coming from some posters.

I am trying to be polite...

If you have a problem with an organization or person, and can not resolve it directly, go over-their-head to someone with the authority to address the issue.

In the current case I would advise that you contact http://boinc.berkeley.edu/anderson/ as a first step.

---

NOTE: This is addressed TO NO PARTICULAR INDIVIDUAL...

After following these posts for years this is the first time that I have felt compelled to remark on the inane, uninformed, or simply rude commentary coming from some posters.

I am trying to be polite...

If you have a problem with an organization or person, and can not resolve it directly, go over-their-head to someone with the authority to address the issue.

In the current case I would advise that you contact http://boinc.berkeley.edu/anderson/ as a first step.

I don't think you have quite grasped what the problem is.
The problem(s) have arisen because there has been new BOINC code installed on the Seti servers. It is this new BOINC code that is causing the problems.
As Dr.Anderson is the person responsible and probably the programmer for this new code, certainly CreditNew is his.
Therefore my question to you is who is above Dr.Anderson, and what are the contacts to that person/organisation.

The link provided is the U.C. Berkley page for Dr. Andersen, the developer of BOINC.

It is there, as stated, for any who wish to contact him directly.

As others here have mentioned he is the man to contact with any concerns regarding BOINC.

Just trying to aim folks in the right direction...

---

I have a wonderful idea. Why don't all the critics just donate some money to provide more manpower and equipment and help keep things running smoothly?

I have a wonderful idea. Why don't all the critics just donate some money to provide more manpower and equipment and help keep things running smoothly?

Thats the best idea I've heard so far! :-) Still wish I had money to donate to SETI. Damn bills.

---

The link provided is the U.C. Berkley page for Dr. Andersen, the developer of BOINC.

It is there, as stated, for any who wish to contact him directly.

As others here have mentioned he is the man to contact with any concerns regarding BOINC.

Just trying to aim folks in the right direction...

See what happens when I post after 30+ hours without sleep... I spell The Man's name incorrectly! It is Anderson not Andersen. Duh!

---

I have a wonderful idea. Why don't all the critics just donate some money to provide more manpower and equipment and help keep things running smoothly?

Money is a chunk of the answer but not all...David Anderson will make code changes despite whatever $ is donated.

---

With that said unless and if these boys are wholesale let out to pasture and a professional serious bunch come into place nothing is going to change at SETI.

Again placing the blame on those not responsible for the situation, not helpful and not appropriate.

---

Perhaps, but more staff will certainly help react with greater expediency.

Perhaps, but more staff will certainly help react with greater expediency.

Would that mean, that greater financial resources were needed?

---

Don't take life too seriously, as you'll never come out of it alive!

Thanks for the front page updates... :)

Just in case people haven't seen this recent post from the front page:

Update: Our upload server disk array crashed last night, but has been recovered. However, the project will remain down until we process a large backlog of results.

---

Yes, it would mean greater financial resources are required. Keep in mind, this project keeps going by donations. So anything that people can spare, no matter how small, will be appreciated I am sure. I plan on donating a bit when I get my paycheck at the end of the month.

It would really be nice to see a professor from Berkeley out looking for grants again as well. Back in the early days of the project, before they moved over to BOINC, there was a bit of grant money, and things were on less of a shoe string budget.

Yes, Blurf. However checking the results awaiting validation from the server status page indicates that the process is going very slowly. My take is that the results from all our chewing won't be uploaded for several days. Fortunately I have enuff work units in my cache to keep me going with S@H as well as a few from Einstein, and believe it or not, LHC!

---