Can someone please explain this to me, because i don't seem to get it. How is it figured can you do anything to improve your rating etc. Thanks

Running more Work Units is the only way you can increase your Recent Average Credit...

> Can someone please explain this to me, because i don't seem to get it. How is
> it figured can you do anything to improve your rating etc. Thanks
>
>
Well you could re-run your benchmarks and hope you get a better score, but that may not help as your score also relies on the benchmarks of two others.

> Can someone please explain this to me, because i don't seem to get it. How is
> it figured can you do anything to improve your rating etc. Thanks

Rick,

There is a discussion of this in the documentation ... look in the glossary ... you can also look in the FAQ Credit section ...

As part of an "unofficial" effort to document the SETI@Home Powered by BOINC, the following documents have been written to aid you in the use of SETI@Home Powered by BOINC:

Documentation Menu (pdb)
Release Notes =

> Can someone please explain this to me, because i don't seem to get it. How is
> it figured can you do anything to improve your rating etc. Thanks
>
Think of it as a speedometer. The more units and the faster you do them the more RAC.

I don't know this for sure, but I understand it's a weighted average rather than an arithmetic average. The further back in time a result was reported the less "weight" it carries in the computation.

Cheers,

Stephen
<P>Not only are we doing distributed processing, now we're doing distributed debugging.<BR>Who'd a' thunk it? (GRIN)<BR><a> <a><img>

> With P@H down for nearly two weeks now, I would have expected the RAC to drop
> off since no new WUs are being crunched. But it seems to have remained
> constant. Same for some host that I had crunching SETI at one time but have
> switched completely to other projects.

If the database that hosts the data is not being updated by the running of the external processes, RAC is going to be the last value saved. So, that is what you are seeing as all of the external processes are off while they do the update.
<p>
Click Me!

> > > With P@H down for nearly two weeks now, I would have expected the
> RAC to
> > drop
> > > off since no new WUs are being crunched. But it seems to have
> remained
> > > constant. Same for some host that I had crunching SETI at one time
> but
> > have
> > > switched completely to other projects.
> >
> > If the database that hosts the data is not being updated by the running
> of the
> > external processes, RAC is going to be the last value saved. So, that is
> what
> > you are seeing as all of the external processes are off while they do
> the
> > update.
>
> Yes, but currently none of my hosts are crunching SETI and their SETI RACs are
> also remaining constant.
>
> @Stephen
> Yes, it's supposed to be a weighted average. The algorithm is shown <a> href="http://boinc.berkeley.edu/credit.php"> here.[/url] This code is called
> whenever you are granted credit to update the RAC.
>
> But, the point of my question was is this algorithm ever called periodically
> to decay your RAC if you haven't returned any results recently. Apparently it
> is not, but it really should be. (Yes, I understand that would add server
> load, but maybe just calling it once a week for each host would do the
> trick.)
>
> My hosts have all been moved to other projects until the dust settles a bit
> more here. But, viewing my <a> href="http://www.boinc.dk/index.php?page=user_statistics&project=sah&userid=42164">
> charts on boinc.dk [/url] you'll see that my RAC has been constant despite not
> returning any new results for several weeks now. This really is not a fair
> statistic as my ranking should be dropping off to reflect the fact that my
> hosts are not currently active on this project. The situation on Predictor
> is the same. My RAC should drop (unless as mentioned above, the update
> processes are shut down) to reflect that no results have been returned
> recently.
>
> Using the spedometer analogy, if your engine is off, or you're sitting at a
> stoplight, the spedometer should drop off towards zero.
>
It was my understanding that it was SUPPOSED to be called once a week or so on all entities (hosts, users, and teams). It appears from this post that it is not happening.

See Pauls Documentation
Recent Average Credit

----------



Join the Overclockers.com SETI Team!

> Maybe with the high load on the DB, I shouldn't be surprised if that update
> has been shutdown on SETI as well. It would be nice if they created a page
> somewhere that gave a definite list of all normal processes & features
> that are currently disabled. Ie:
>
> Scheduler - running since (date)
> Validator - running since (date)
> Pending Credit Lookup - disabled since (date)
> Results Lookup - disabled since (date)
> Weekly RAC updater process - disabled since (date)
> etc...

I think this suggestion is in the hopper, but, like all else has to wait its turn before we are likely to see an implementation. To be honest, I would much prefer to see more work done on the client end, like the Macintosh and Linux GUI so I could migrate most of my windows PCs to Linux and the Mac too (plan to get a second mac late next year also).

Heck, I would like to see an updated schedule, or even just a note of which stage we are in ... I think we are in M2 of 4, but we still have some M1 tasks in the taskbase the last time I looked. The schedule of course will not be updated beecause as soon as it is published it will be used (as all software development schedules are) as a commitment.

<p>
For BOINC Documentaion: Click Me!

While we are on the topic of RAC's, can anyone please explain why over that last few days, the RAC climbed rapidly, then from today is now starting to taper off? Is this caused by a backlog of credits that have been recently varified, or are there various sized WU's being distributed to suit the pc's benchmarks?

Has anybody else noticed this?

Thanks


Steve.