Upwards and Onwards (May 28 2009)

... In other matters, the "client connection stats" page is broken...
____________
.

Presently, it really reduces to this: the project default is handing out APs to people that do not want them, when there are not enough for the people that do want them.

Backwards.
____________
--
Classic 82353 WU / 400979 h

...
Ok I know AP pays better, but hey this is about science in the first place, and "credits" in the second place.

Sten-Arne

I don't believe it has much to do with people preferring one application over another.
...

@ Josh C78

Have a look in the NC forum..
http://setiathome.berkeley.edu/forum_forum.php?id=10
There we can talk about crunching speed and so on..

Small answer.. yes.. GTX2xx would give the highest crunching performance.

OCed GTX260 Core216 ~ 8,000 RAC.
Stock maybe ~ 7,000 RAC.
A 98xx would have the half RAC.

So, more shader cores and more shader speed.. more power.

____________

For some months ago i thought of the same thing as you are writing now.

That new users which want to try out Seti@home gets an AP wu with perhaps their laptop 2ghz core2 and thinks cool, i got a realtively fast machine, i can contribute and then finds out that it would take more than 24 hours to process one and aborts and uninstall seti..

I agree with the people that says that new users should have AP unticked as default because the original app simply takes so long that there is a risk that people gets "bored" of not getting a credit ticker that moves up.. The psycological factor is to high there, and if they manage to get an AP result ready and sends it in they would perhaps also notice that credit doesn't get higher at all perhaps for a week and also gets fed of it because their credit wasn't given "in time"..

Many people which are novice doesn't know how this things work, they don't care plunging into forums diging out what and why isn't my credit increasing though i let my computer work for more than a day 24/7..

MB work has a realtively short turnaround (from when you deliver and get awarded) .. Lets start with letting people get their credit ticker roling and when they dig further into our forums they'll discover AP (hey why don't let the server be responsible of knowing when new users first login to the website by displaying a greeting message and then simple guidance of contributing in Astropulse but letting them know that due to the longer WU's it also takes longer until their WU gets validated. And perhaps telling of optimised clients but inform that it requires some dedication and skills.)


Well to summarize it.. AP = off for new users .. Let them discover it thorughout the webserver or forums or their options first and let them tick it for themselves.
Then we'll see more people that wishes to stay with s@h instead of leaving because of not knowing the technology enough behind it.

My 2 cents ppl..

Kind regards Vyper
____________

_________________________________________________________________________
Addicted to SETI crunching!
Founder of GPU Users Group

....
That new users which want to try out Seti@home gets an AP wu with perhaps their laptop 2ghz core2 and thinks cool, i got a realtively fast machine, i can contribute and then finds out that it would take more than 24 hours to process one and aborts and uninstall seti....

Do I understand correctly that they do have a NTPCKR machine already available ? ...

Does "Ahhh..." mean "Yes" ?

Don't forget that the first AP task that user will get will be with the stock app (so ~80 hours for that machine), but it will be estimated by BOINC at DCF=1.0, rather than the DCF=~0.4 typical for stock AP.

If stock apps don't have DCF=~1, it means the run time estimate is WRONG, and the admins should fix it.

Don't forget that the first AP task that user will get will be with the stock app (so ~80 hours for that machine), but it will be estimated by BOINC at DCF=1.0, rather than the DCF=~0.4 typical for stock AP.

If stock apps don't have DCF=~1, it means the run time estimate is WRONG, and the admins should fix it.

Don't forget that the first AP task that user will get will be with the stock app (so ~80 hours for that machine), but it will be estimated by BOINC at DCF=1.0, rather than the DCF=~0.4 typical for stock AP.

If stock apps don't have DCF=~1, it means the run time estimate is WRONG, and the admins should fix it.

Actually, while I agree that DCF should be around 1.0, there is an advantage:

A brand-new computer defaults to 1.0, which means the first work requests will be small, and grow as DCF converges on the right number.

Agreed, but with some concern about AP tasks.
A new host would see the AP tasks at about 2.5 times the actual time. As the tasks are long to start with this could lead the owner who only wants to do a limited number of hours to assume it is more time than they wish to contribute within the deadline limit.