[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Distributed networks?
My general phlosophy is to do everything myself if I can do it. I find it
takes more effort sot coordinate others than to just do the work. For
tasks that I cannot do, I do not hesitate to ask others for help. This is
mostly software stuff.
Note that before this group dragged me into linux and perl kicking and
screaming, I was a QBasic programmer using DOS. It would be nice to break
up the image processing into pieces and route them to arbitrary computers,
but doing this is just beyond me. Too bad I do not live on a really high
speed network or I could let some of you have at this task.
From time to time I have considered letting some of you into my network via
the internet. Then some of you could sit on my system vis ssh? and set up
my systems to be more interesting. If some of you want to work at this, it
is still possible. I think there is not much chance that michief makers
will want to process images.
Tom Droege
> [Original Message]
> From: Robert J. Bradbury <bradbury@aeiveos.com>
> To: TASS <tass@listserv.wwa.com>
> Date: 8/26/2004 12:10:14 PM
> Subject: Distributed networks?
>
>
> Something that might work to our advantage...
>
> The folks behind SETI@Home have produced a package
> called BOINC [1] that allows one to allocate fractions
> of your compute resources.
>
> As I don't don't think much of the SETI@Home project I've
> never used my CPU resources for that. Instead I prefer to
> dedicate them to Folding@Home [2]. If it ever gets off the
> ground I intended to use the BOINC platform for Nano@Home [3].
>
> The nice thing about BOINC is that it lets you turn up/down
> the fraction of your CPU(s) dedicated to various projects.
> So one could imagine lots of different people joining the
> TASS project (offering up CPU resources instead of
> attempting to manage the telescope & camera nightmares [at
> least from where I sit...]). Offloading the data processing
> might allow you to be a little more relaxed about when a
> machine goes down the tubes.
>
> When you run into a problem of machines going down you
> could just send a note to the TASS community to ask them
> to up their BOINC priorities for TASS. If enough people
> joined one could perhaps even eliminate home data processing
> (lowering your electricity and A/C requirements presumably...).
> You might have to shift attention a bit to redundancy in
> internet communications (Cable + Satellite?) and a router
> that can deal with that (a Linux gateway machine probably
> shouldn't have problems).
>
> Robert
>
> 1. http://boinc.berkeley.edu
> 2. http://folding.stanford.edu
> Note that I don't think F@H uses BOINC yet but I'm hoping
> they move in that direction...
> 3. http://www.nanoathome.org/
>