archiv~1: Re: SETI log, identify, and track LEO signal sources?

Re: SETI log, identify, and track LEO signal sources?

Brian Wong ( logis@logis.com )
Sat, 21 Nov 1998 19:21:21 -0800 (PST)

On Sat, 21 Nov 1998 MarcusJohn@aol.com wrote:

> In a message dated 11/21/98 5:20:13 PM Eastern Standard Time, logis@logis.com
> writes:
>
> > I think a database of LEO and Geo-sync sats correlated with possible hits
> > is a good idea also. There are existing satellite databases available on
> > the net. You can get the satellites over your area by just entering your
> > latitude, longitude, and time. Just correlate their position at time of
> > passage with your hit candidate. I can't speak for the league, but with
> > such resources available on the web the SL would probably not wish to get
> > into the business of tracking sats. But you can easily do this yourself.
>
> I think the next version of Seti software should have a satellite tracking
> module to help weed out the false hits. Since the satellite Keplerians are
> available on the web, keeping up to date with the thousands of sats up there
> shouldn't be a huge technical problem. Especially if it is done on demand
> only.
>
> John Marcus.
> KE3SW.
> Stonesoup member.

Agreed. A sat tracking module would be of great benefit. RF SETI
searches should know exactly what hardware is passing overhead at all
times. We should know exactly when and where to expect satellite
interference ahead of time.

Actually, correct me if I'm wrong, but I'm quite amazed that professional
searches like Phoenix are surprised by satellite false hits. They must
not be tracking satellites otherwise they would know to ignore them before
the false hits occur. Tracking sats seems an obvious step to perform
before the search begins and should be an integral part of the search
program.

Regards,
Brian Wong
bw@logis.com