200 days without a glitch...
17 Jan 2006 4:47:45 UTC
Topic 190623
(moderation:
Congratulations to the project team for the preparation and maintenance which allowed the servers to work flawlessly for so long. 200 days of constant data flows and crunching. Wow... It's hard to believe.
200 days without a glitch...
)
Thanks!! We've worked very hard behind the scenes to try and keep everything working smoothly for our volunteers. We've not always succeeded but this is always on our minds.
Bruce
Director, Einstein@Home
RE: Thanks!! We've worked
)
My thanks also. This might properly be considered part of the "social engineering" that helps motivate volunteers. Different things motivate different people, but I, for one, appreciate a dedication to and accomplishment of smoother operation more than a downloadable certificate.
RE: Thanks!! We've worked
)
Well done, as a newbie your reliability is appreciated.
RE: ...that helps motivate
)
Me too
~~gravywavy
RE: RE: Thanks!! We've
)
I'll second that. I like the work Bruce and the project people do here. And as smooth segue to another point 8-). Trog Dog, how would you like to join a great Aussie team? Click on the hyperlink in my sig for BOINC@Australia. We are the number one Australian team and need help to move up a couple of spots to stay ahead of UK BOINC Team. We gotta beat the Brits! ;-)
Join the #1 Aussie Alliance on Einstein
I´m running E@H for almost a
)
I´m running E@H for almost a year now, and can hardly remember any outage. Really impressive how smooth E@H runs, compared to many other projects. No hanging apps, no "no work from project" - it´s just always running.
That´s why we, over at Synergy, recommend E@H to people who have problems to get BOINC running because they are trying with projects that are down, have no work ect. "Try with E@H, that always works."
Big compliment to the project administrators! Perhaps you can go and give other projects some tips, like SETI or Predictor... :)
100% BOINC - 100% SYNERGY. JOIN BOINC SYNERGY!
On the other hand, it has
)
On the other hand, it has been at least 15 minutes since Bruce said he would look at FLOPS counting ... I think we have waited LONG ENOUGH! :)
Sorry guys, could not resist! :)
Better still, they also gave us an optimized app that really makes the G5 shine!
RE: On the other hand, it
)
Paul, the main problem is that I haven't figured out how to determine the flops/intops counts that I should claim!
Director, Einstein@Home
RE: Paul, the main problem
)
Lord Bruce, I hope you knew I was kidding! :)
Send me the code and I will tell you ... 1,000,000 for Paul, 10,000 for everyone else, 1,000,000 for Paul, 8,000 for everyone else ... :)
Did you ask the SETI@Home guys how they did it?
I had thought to try to unravel the logic in my copious free time and add to the WIki write-up about the API, again, one of the places where the developer documentation falls short ... but I have not gotten there yet ... sigh ...
If you figure something out, let me know ...
RE: Paul, the main problem
)
To be on the safe side, integer_ops = 0, since AFAIK you needs v5.3.2 or later client to report intops.
For floating_point_ops, you only needs v5.2.6 or later, except for v5.3.1 that is older. ;)
As for how much you should claim, to be consistent with Seti_Enhanced would guess on around 6.3e12 for this albert-wu.
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."