Iridflar 1.6 release.

Neil Clifford (
Thu, 23 Apr 1998 19:25:28 +0100 (BST)

Rob Matson has just released Iridflar 1.6 which can (for now) be found

Rob provided the following notes:

This version will run on machines with or without a coprocessor.
Changes since 1.52:

*  Added day of the week to the brief file output

* Configuration files can now be loaded from within IRIDFLAR using the
  "L" key in the Main Menu.  The number of lines per flare (1 or 3) is
  now controlled with the "N" key instead of "L".

* Toggle added to Main Menu to switch between metric and English units.

* Toggle added to Main Menu to switch between metric and English units.
  The parameters affected are the site altitude, satellite range and
  maximum flare ground-point range.

* Corrected internal naming of NORAD #25170 from Iridium 51 to 56. Added
  internal naming for recent launches of 51, 55, and 57-68.  Based on
  new information from Motorola via Dr. T.S. Kelso, it appears that the
  names Iridium 9 and 10 are swapped.  I have changed the internal hard-
  coding so that Iridium 9 is #24838 and Iridium 10 is #24839. Similarly,
  the reported Iridium numbers corresponding to #'s 25104-25108 have
  changed at least twice.  As of April 20 they are named Iridium 50, 56,
  52, 53, and 54 respectively.

* Predictions no longer done for Iridium 21.

* Some users have found ftp sites that provide Iridium two-line element
  sets that have an extra linefeed following the end of each line
  (<CR><LF><LF>).  Worse, this fact may be transparent to the user
  unless he/she happens to open the file in a word processor.  Earlier
  versions of IRIDFLAR would parse such files as being filled with
  comments, and thus no predictions would be made.  Version 1.6 now
  checks for the extra linefeed, and displays a warning if any are found.

* In 1.52, if a flare's brightest point was cutoff by either the minimum
  elevation constraint or maximum mirror angle, then the program would
  be missing a reference ground point from which to compute the bearing
  to the maximum flare point.  This could lead to a fatal division by zero
  error in some cases, or blank values for the bearing in others.
  Additional program logic has been added to handle this case.

* V1.52 failed to check for the existence of the TLE file unless its name
  was changed.  This caused a fatal error when attempting to compute
  flares (since the TLE file could not be opened.)  TLE file existence is
  now verified before computing flares.


Neil Clifford                                       <>