"Si." <spammers@get.stuffed> wrote in message
news:cfif33$g5u$1@thorium.cix.co.uk...

Just thought I'd let you know that I have been accepted onto the BOINC
climate prediction beta test - however it requires BOINC version 4.02.

At the moment SETI won't work on version 4.02 (according to the CP web

site)

and CP will not on version 3.20.

I'm not going to start the CP beta until 4.02 is released for SETI.

<OT>

Si -

CPDN BOINC is going "public" on 26 Aug.

From the 'news' section of thier website:

<begin>

BOINC launch set for 26th August!

Sylvia Knight
13.08.04

Climateprediction.net will move onto the BOINC (Berkeley Open Infrastructure
for Network Computing) software platform on 26th August.
Members of the project team will be in Oxford, Stockholm and Berkeley for
the launch. A press release will be available nearer the time.
New participants in climateprediction.net will be encouraged to use the new
platform, however existing participants will be able to continue using the
version of the experiment they are currently running, which will be
supported indefinately.
Mac and Linux users will be able to participate for the first time.

</end>

Linkage: http://www.climateprediction.net/rostra/news.php?r=1&t=2&id=62

It looks like those of us that run both CPDN & SETI may now be in the
not so envious position of having to run only one proj or the other on any
given machine, if SAH2 BOINC's core client (3.20) doesn't upgrade to v4.x
w/i two weeks, allowing it to run the CPDN client, as well.

I now have CPDN classic runnuing on all my machines concurrent w/SAH2,
running 50/50, and set up so CPDN automatically gets 100% resources if I
have no SAH2 WU's (not that THAT, would ever happen).

Yikes!

</end OT>

Sorry, everybody, for the CPDN stuff. This seems to be starting to be a bit
of an issue here, as questions come in concerning other BOINC projects. I've
tried to avoid any other proj discussions, as much as possible. I think this
issue MAY grow as BOINC's popularity and proj base grows.

Here are some scenarios I can envision to (possibly) avoid this:

1]  Tossing 'cross project' BOINC topics to comp.distributed. - At this time
c.d. seems to be centered on the more theoretical aspects of DC, but we
all know n/g's morph & evolve. The group is already created, and would need
to hit 'critical mass' as far as BOINC is concerned. This would probably
take a conscious effort by alt.sci.seti subscribers steering non-SAH BOINC
projects to c.d. This also assumes a.s.s. subscribers find non-SAH BOINC
projects off-topic, which MAY NOT be a valid assumption (though I believe
it most likely is). I'd assume SAH specific BOINC topics would remain
in a.s.s., along with a fair amount of general BOINC topics which do not
directly pertain to other proj's.

2] Create an alt.sci.bionc n/g specifically for the discussion of BOINC and
BOINC proj's. - This could help keep cross proj discussion out of
alt.sci.seti, but MAY siphon off some of alt.sci.seti's traffic. Or,
alt.sci.boinc may never hit critical mass, and become, in effect, still
born. I've done some quick metrics a while back, and there appears to be the
required '10 posts per day' needed to justify tossing out some RFD's, or
even a proposal in alt.config. I personally DO NOT have the time to devote
myself to the efforts required to successfuly proponent a new n/g at the
moment, though that may change, in time. If there was enough interest, I'd
make an effort to find some time, but I can't control my near term personal
events, ATM.

Pls. note: This is NOT an 'official' RFD ! ! !

3] 'Keep on, keepin' on' - AKA as 'do nothing': The usual outcome of this
type of discussion, and not nescessarily a poor choice, either (and the
easiest choice, as well).

Any opinions???
-- 
Strat