[Date Prev][Date Next][Thread Prev][Thread Next] - [Date Index][Thread Index][Author Index]
Re: AO-40 current ALON/ALAT
- Subject: Re: [amsat-bb] AO-40 current ALON/ALAT
- From: Jonathan NAYLOR <Jonathan.Naylor@xxxxxxxxxx>
- Date: 24 Dec 2001 09:48:34 +0100
- Alternate-Recipient: Allowed
- Conversion: Allowed
- Disclose-Recipients: Prohibited
- Original-Encoded-Information-Types: IA5-Text
- X400-Content-Type: P2-1988 ( 22 )
- X400-MTS-Identifier: [/c=FR/admd=ATLAS/prmd=SG/; 023123C26EBE2025-MTAFEDDEF]
- X400-Originator: Jonathan.Naylor@socgen.com
- X400-Received: by mta MTAFEDDEF in /c=FR/admd=ATLAS/prmd=SG/; Relayed; 24 Dec 2001 09:48:34 +0100
- X400-Received: by /c=FR/admd=ATLAS/prmd=SG/; Relayed; 24 Dec 2001 09:48:34 +0100
- X400-Recipients: non-disclosure;
Hi Joe
I did that with mtrack and sure enough the squint values it gave me were
much more reasonable.
My next question is this: Why did I need to make this input data change
for mtrack, does it indicate a bug in the squint angle calculation, or
is it because AO-40 is somehow different from AO-13 ? I originally wrote
the program in AO-13 days and the squint angles then seemed accurate.
The fact that QuikTrack gets it wrong makes me feel slightly better.
I would be interested to know as I would like to get mtrack accurate in
this respect without asking users to have to modify the input data before
entering it.
Happy Christmas from a white Zurich.
Jonathan
----
Via the amsat-bb mailing list at AMSAT.ORG courtesy of AMSAT-NA.
To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org
AMSAT Home