[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

*Subject*: Re: starship-design: Massively Distributed Computing for SETI*From*: Ben Franchuk <bfranchuk@jetnet.ab.ca>*Date*: Fri, 16 Mar 2001 22:30:35 -0700*CC*: starship-design@lists.uoregon.edu*References*: <001d01c0afba$a23edae0$0100a8c0@broadsword>*Reply-To*: Ben Franchuk <bfranchuk@jetnet.ab.ca>*Sender*: owner-starship-design@lists.uoregon.edu

"L. Parker" wrote: > This means we must know the exact speed, course and distance of the sail at > all times, constantly update the targeting data for the sail, the beam > source, and the sail's destination, all in four dimensions, one of which has > at least one harmonic component if not two to compute a continually changing > target solution and frequency solution for the beam. > > Any way we approach this, the solution is going to be compute intensive, and > it involves many of the same types of calculations being done by the SETI > team, which was why I found the article so interesting. > > Lee This may be true but the beam's does not need to updated that much, I guess once a minute and that is mostly with the feq of the beam. -- "We do not inherit our time on this planet from our parents... We borrow it from our children." "Luna family of Octal Computers" http://www.jetnet.ab.ca/users/bfranchuk

**Follow-Ups**:**RE: starship-design: Massively Distributed Computing for SETI***From:*"L. Parker" <lparker@cacaphony.net>

**References**:**RE: starship-design: Massively Distributed Computing for SETI***From:*"L. Parker" <lparker@cacaphony.net>

- Prev by Date:
**RE: starship-design: Massively Distributed Computing for SETI** - Next by Date:
**RE: starship-design: Massively Distributed Computing for SETI** - Prev by thread:
**RE: starship-design: Massively Distributed Computing for SETI** - Next by thread:
**RE: starship-design: Massively Distributed Computing for SETI** - Index(es):