Re: mir/sts transits addendum

From: Bj|rn Gimle <>
Date: Thu, 16 Mar 1995 13:53:04 -0500

>> OK, I figured out Bjorn's table. NORAD means there are many objects in

I suppose Robert Preston did figure it all out, so pardon me for "throwing
yeast into the oven after the bread is baked" as we say in Sweden.

I mentioned that I was using a .tle (.n2l) file from Ted Molczan, with 808
elsets. SkyMap searched all of these, but skipping (on my request) those
with perigee above 2222 km, and range over 9999 km.
So, the result includes the NORAD numbers of the objects found and
predicted, for identification.

>> They Match! (I presume Bjorn's data are in UT/GMT or whatever, 5 hr
SkyMap uses local or UTC for input and output (independent selections)
(and can also use current PC clock value for map projections), but I
choose UTC bacuse Walter's tables used UTC.

>> It looks like Bjorn's program is much better suited to this stuff...
It is Rob Matson's program, but my favourite.

>> Bjorn's result for Mir was:
>> Transit center for NORAD 16609: 22:57:30 264o 2o

The result files for All File Search show: Date, Track start time/ azimuth
/ elevation, and
same triplet for Culmination and End of track, followed by the NORAD number
of the
object predicted. The "o"s after the angles are originally the 8-bit ASCII
value for the
degree symbol. For Transit searches, Culmination is replaced by the Transit
Start/End are affected by elevation/range limits you have set, and by the
of the search interval, and culmination is always between those two, or
equal to one
of them, if it actually is outside your limits.
Received on Thu Mar 16 1995 - 06:14:51 UTC

This archive was generated by hypermail 2.2.0 : Fri Mar 07 2014 - 00:13:50 UTC