I process about 3 WUs a day, and have a cache of 8 WUs in SetiGate,
so it is usually 2 or 3 days before a WU gets processed.
Does this mean that my work will likely never be one of the first two
results returned, and hence it is 'out of date' before it starts?

I now have a broadband connection and could drop SetiGate altogether except
that it is a good record of what I have done.
How do I tweak SetiGate to take advantage of being on-line all the time?

Dave

"David Woolley" <david@djwhome.demon.co.uk> wrote in message
news:T1077695816@djwhome.demon.co.uk...

 They actually send out two or three copies in quick succession.  They
then wait for at least two returned work units to agree with each other.
In the mean time, if the work unit becomes the oldest work unit in the
pool of work units, it will be resent.  When they were last sending them
one at a time, this typically took less than a day.  Once they have
a corroborated result, the work unit becomes eligible for deletion from
the pool, but will only be deleted if space is needed for more.

One copy of the results is retained as the official set of results, and
the identity of the corroborating results' sender is also retained.
Subsequent returns for the work unit are checked against the reference
result and credit given if they agree.

Given average processing times are probably under a day, anything much
over a day to turn round the work unit means that you will get credit,
but your processing will not contribute anything new to the science.
However, if everyone receiving a workunit is equally slow to process
it, you could still be the primary detector after an arbitrary long
period.  Obviously the chances of this drop off rapidly with the number
of copies sent out.

If there really are no new work units going into the pool, no returns
will do any good for the science - they probably do it to keep the
work force motivated.