Wayne Brown wrote:

In alt.sci.seti Martin 53N 1W <ml_news@ddnospamddml1dd.co.uk.dd> wrote:

Wayne Brown wrote:

In alt.sci.seti Martin 53N 1W <ml_news@ddnospamddml1dd.co.uk.dd> wrote:

[...]

Sorry, but no go there. That is the nature of change. Sometimes "backwards compatibility" is too backwards to consider worthwhile.

Yeah, but some of the changes were unnecessary.

[...]

An awful lot was learnt from s@h-classic. The Science and methods move onwards.

Are you telling me that the new "science and methods" couldn't be done
in a single executable called "setiathome" that gets its input from a

[...]

along, just as I used to do with Classic.

Indeed so.

s@h-classic would have been a wasteful nightmare to attempt what is being done with Boinc now, let alone what Berkeley themselves will be doing for s@h with Boinc soon.

I don't care what the client actually is doing "under the hood."
All I care about is that it presents no external difference to the
system on which it runs.  I often used to let the Classic client run

That is precisely one of the major goals that Boinc supports. Once you set it running and tell it your preferences, that's it, you can leave it to run unattended. Meanwhile, the scientists can get results and update their systems without needing to bother you again. Unless you choose otherwise ofcourse.


[...]

I grabbed a perl script called multiseti.pl from somewhere on the net
and made minimal modifications to customize it, and changed my /etc/rc*

There's equivalents for Boinc. The Linux install may already be fully automated. Try looking. (I installed mine a long time ago - things change and improve!)


[...]

Number 2 reason:  I have no interest in participating in any of the other
things BOINC is doing.  I don't want to be part of the BOINC project.

No need to. Just attach to s@h only.

Then why the need to deal with the BOINC infrastructure?  I'd still be
a part of BOINC, even if I weren't doing anything but S@H.  I refuse to
have anything to do with BOINC; I won't even visit their website.

Then you won't have seen what is being done and what can be done.

Briefly, the Boinc infrastructure:

1: Lets Berkeley update the Boinc project client (on your machine(s)) with new algorithms. The first to be run is just a tidy-up of the existing s@h-classic to debug and prove the idea. Then there is s@h-enhanced (x2 sensitivity), then there is s@h for the new 7-beam receiver (ALFA) and the new higher resolution data recorder, and then there is Astropulse...

All for the search for SETI and all possible without you having to touch Boinc beyond just having installed it and attaching to Berkeley.

2: It got around some political blocking for ALL funding to get a little funding which could then indirectly help s@h keep going with a few crumbs;

(3: It has also greatly boosted DC and other projects and increased public awareness and more!)


[...]

Any one of the reasons above would be enough to keep me from
participating.

A lot of people think that the above reasons are rather good and worthwhile.


[...]

Actually, all my spare CPU cycles are going to the GIMPS project now.

[...]

Yes, I run that also but on an even lower priority than Boinc so that I get a general CPU/FPU/memory check from the checksums that GIMPS runs. It might hit prime also :-)


Happy crunchin,
Martin