Like a textbook example of what I described in my last post, this post of yours betrays your own emotional attachment and bias. I've made no statement proclaiming the superiority of Classic, nor any suggesting that BOINC is crap and should be thrown in the bit bucket. That was not only mean-spirited, it was irrelevant. Maybe mark could cut them a check for a million or two to keep classic around? When it comes time to fill out a new grant proposal, we all drop everything and work on that, for example.Ĭan they have a life, or are they expected to be chained to their desks 24/7 to be able to play down what you see is a problem, whereas they rightly say you are misunderstanding what BOINC was made for? (Attaching to other projects, we can't hammer it in enough!) No administrative staff, no tech writers. Outside of current academics (Kevin and Josh) working on other applications of SETI data, and students helping Dan build hardware that's it here at the lab. Dan, the project director, is spending a lot of time building spectrometers for other projects because that's where the money is. Eric works overtime on other non-SETI projects when he's not building the next client. David and Rom (and other various programmers) strictly work on BOINC code. Court is busy dealing with various long term network/systems projects that Jeff and I can't handle since we're diagnosing, debugging, programming, or maybe actually getting science done. Bob, the main database guy, actually only works half time. We've both been here working on SETI long before came around, so we both are well versed in every aspect of the "big picture" around here. Me and Jeff are continually up to our necks dealing with everything. I leave this as an exercise for the reader to figure out why. I can't be bothered to go into detail why. And it's not so easy to add news items to the page. Don't have the staff or the money to add the staff. Yes, we can do better in the PR department. Sad but true, and I personally find this painful but part of the big picture. I don't have this time and neither does anybody else around here. If I dealt with all these, that would occupy about 15-20% of my time.
#Teambeam upload not finished how to#
I end up with dozens of e-mails a day from people who figured out how to reach me. This isn't good for making our participants happy of course, but we do our best with what we got and so far our user base has stuck with us through the painful periods (thank you!!!).īOINC was written so you can connect to other projects when there are server issues with a specific project. Things break, deep breaths are taken, and they get fixed eventually.
The current crises are just par for the course in the history of our SETI project and public resource computing. Try reading Matt Lebofsky's post (the person you're trying to tell how to run things )): Let the little sacks of ego-and-id sort it out for themselves. I hope this will finally be a lesson learned for the SETI admins: the next time you have a problem, deal with it expediently and promptly, and to hell with anyone's feelings. The ONLY things that matter are honesty, truth and the search for it, efficiency, and just plain getting the job done! It's not the job of others to predict or guess what you might happen to "feel" about something and try to help you deal with it or "soften the blow": it's YOUR JOB to deal with your own emotional filters and baggage, and especially stop blaming others for your own misbegotten reactions to things. Guys, guys! Have you learned nothing in six years? If there's one thing I've learned it's that human emotions aren't worth a damn, people's "feelings" don't matter.
#Teambeam upload not finished full#
Instead, I suspect, they worried too much about the feelings of the "crunchers" and left distribution active, knowing full well it would only make the problem worse and more protracted. I think the SETI admins could have avoided much of the recent disillusionment and vitriol and hatred if they had been much more proactive in solving the bottleneck, by taking the bull by the horns immediately and turning off workunit distribution on the 3rd or 4th, right when the problem first surfaced. a result - just ONE, mind you, but a result nonetheless - was successfully uploaded this afternoon while I watched reruns of Stargate SG-1 and Atlantis. (yes, I know, that's not possible without the original computer that downloaded them, but that may be too bulky for you. As the crows fly I'm only a stone's throw away from Berkeley in Sacramento, not that it matters in terms of their network.ĭownload them onto a USB stick and bring them over. Me, I have yet to be able to upload ANYTHING to SETI since December 3rd.
0 kommentar(er)
