@@ -56,43 +56,34 @@ my %opt = $bldr->args ();
my @exe_files;
my @clean_files;
-print <<eod;
+print <<"EOD";
The following executable can be installed:
satpass is a scriptable program to predict satellite passes
over a given observer.
-If you do not want this, run Build.PL with the -n option. If you want to
-install without being asked, run Build.PL with the -y option.
+If you do not want this, run Makefile.PL with the -n option. If you want
+to install without being asked, run Makefile.PL with the -y option.
>>>> NOTICE <<<<\a\a\a
-I plan to eliminate the question about whether to install the satpass
-script in the first release after August 1 2014. The default behavior
-will be NOT to install. At some time after this the name of the package
-will change to Astro-Coord-ECI, like it should have been all along.
+As of release 0.066, this script no longer asks whether
+the satpass script should be installed, since it is being deprecated
+(slowly) in favor of Astro::App::Satpass2. If you want the satpass
+script installed, you should run this script with the -y option. You can
+make this the default in your CPAN client by installing the preferences
+file eg/Astro-Coord-ECI.yml in .cpan/prefs.
-Unless you are running MSWin32 or VMS (which are special-cased), I will
-assume you are running some version of U*ix, and behave accordingly.
-
-eod
+EOD
my @possible_exes = qw{satpass};
-if ($opt{n}) {
+if ( $opt{n} ) {
print "Because you have asserted -n, the executables will not be installed.\n\n";
- }
- elsif ($opt{y}) {
+} elsif ( $opt{y} ) {
print "Because you have asserted -y, the executables will be installed.\n\n";
@exe_files = @possible_exes;
- }
- else {
- foreach (@possible_exes) {
- push @exe_files, $_
- if $bldr->prompt ("Do you want to install $_?", 'n') =~ m/^y/i
- ;
- }
- }
+}
if (@exe_files) {
if ($^O eq 'MSWin32') {
@@ -1,3 +1,11 @@
+0.066 2014-10-16 T. R. Wyant
+ Update Iridium 42 (OID 25077) to failed, per Kelso.
+ Regenerate canned magnitude table.
+ Croak on encountering JSON key SATNAME. This was replaced by
+ OBJECT_NAME during the REST interface's beta.
+ Remove installer question about installing satpass, per documented
+ deprecation schedule.
+
0.065 2014-07-27 T. R. Wyant
No changes since 0.064_03.
@@ -2,6 +2,7 @@ bin/satpass
Build.PL
Changes
eg/almanac
+eg/Astro-Coord-ECI.yml
eg/azimuth
eg/closest
eg/convert_tle
@@ -4,7 +4,7 @@
"Tom Wyant (wyant at cpan dot org)"
],
"dynamic_config" : 1,
- "generated_by" : "Module::Build version 0.4206",
+ "generated_by" : "Module::Build version 0.421",
"license" : [
"perl_5"
],
@@ -45,39 +45,39 @@
"provides" : {
"Astro::Coord::ECI" : {
"file" : "lib/Astro/Coord/ECI.pm",
- "version" : "0.065"
+ "version" : "0.066"
},
"Astro::Coord::ECI::Mixin" : {
"file" : "lib/Astro/Coord/ECI/Mixin.pm",
- "version" : "0.065"
+ "version" : "0.066"
},
"Astro::Coord::ECI::Moon" : {
"file" : "lib/Astro/Coord/ECI/Moon.pm",
- "version" : "0.065"
+ "version" : "0.066"
},
"Astro::Coord::ECI::Star" : {
"file" : "lib/Astro/Coord/ECI/Star.pm",
- "version" : "0.065"
+ "version" : "0.066"
},
"Astro::Coord::ECI::Sun" : {
"file" : "lib/Astro/Coord/ECI/Sun.pm",
- "version" : "0.065"
+ "version" : "0.066"
},
"Astro::Coord::ECI::TLE" : {
"file" : "lib/Astro/Coord/ECI/TLE.pm",
- "version" : "0.065"
+ "version" : "0.066"
},
"Astro::Coord::ECI::TLE::Iridium" : {
"file" : "lib/Astro/Coord/ECI/TLE/Iridium.pm",
- "version" : "0.065"
+ "version" : "0.066"
},
"Astro::Coord::ECI::TLE::Set" : {
"file" : "lib/Astro/Coord/ECI/TLE/Set.pm",
- "version" : "0.065"
+ "version" : "0.066"
},
"Astro::Coord::ECI::Utils" : {
"file" : "lib/Astro/Coord/ECI/Utils.pm",
- "version" : "0.065"
+ "version" : "0.066"
}
},
"release_status" : "stable",
@@ -89,5 +89,5 @@
"http://dev.perl.org/licenses/"
]
},
- "version" : "0.065"
+ "version" : "0.066"
}
@@ -5,7 +5,7 @@ author:
build_requires:
Test::More: '0.88'
dynamic_config: 1
-generated_by: 'Module::Build version 0.4206, CPAN::Meta::Converter version 2.141520'
+generated_by: 'Module::Build version 0.421, CPAN::Meta::Converter version 2.142690'
license: perl
meta-spec:
url: http://module-build.sourceforge.net/META-spec-v1.4.html
@@ -19,31 +19,31 @@ no_index:
provides:
Astro::Coord::ECI:
file: lib/Astro/Coord/ECI.pm
- version: '0.065'
+ version: '0.066'
Astro::Coord::ECI::Mixin:
file: lib/Astro/Coord/ECI/Mixin.pm
- version: '0.065'
+ version: '0.066'
Astro::Coord::ECI::Moon:
file: lib/Astro/Coord/ECI/Moon.pm
- version: '0.065'
+ version: '0.066'
Astro::Coord::ECI::Star:
file: lib/Astro/Coord/ECI/Star.pm
- version: '0.065'
+ version: '0.066'
Astro::Coord::ECI::Sun:
file: lib/Astro/Coord/ECI/Sun.pm
- version: '0.065'
+ version: '0.066'
Astro::Coord::ECI::TLE:
file: lib/Astro/Coord/ECI/TLE.pm
- version: '0.065'
+ version: '0.066'
Astro::Coord::ECI::TLE::Iridium:
file: lib/Astro/Coord/ECI/TLE/Iridium.pm
- version: '0.065'
+ version: '0.066'
Astro::Coord::ECI::TLE::Set:
file: lib/Astro/Coord/ECI/TLE/Set.pm
- version: '0.065'
+ version: '0.066'
Astro::Coord::ECI::Utils:
file: lib/Astro/Coord/ECI/Utils.pm
- version: '0.065'
+ version: '0.066'
requires:
Carp: '0'
Data::Dumper: '0'
@@ -59,4 +59,4 @@ requires:
resources:
bugtracker: https://rt.cpan.org/Public/Dist/Display.html?Name=Astro-satpass
license: http://dev.perl.org/licenses/
-version: '0.065'
+version: '0.066'
@@ -25,7 +25,7 @@ my @clean_files;
Astro::Coord::ECI::Recommend->recommend();
-print <<eod;
+print <<"EOD";
The following executable can be installed:
@@ -37,31 +37,22 @@ to install without being asked, run Makefile.PL with the -y option.
>>>> NOTICE <<<<\a\a\a
-I plan to eliminate the question about whether to install the satpass
-script in the first release after August 1 2014. The default behavior
-will be NOT to install. At some time after this the name of the package
-will change to Astro-Coord-ECI, like it should have been all along.
+As of release 0.066, this script no longer asks whether
+the satpass script should be installed, since it is being deprecated
+(slowly) in favor of Astro::App::Satpass2. If you want the satpass
+script installed, you should run this script with the -y option. You can
+make this the default in your CPAN client by installing the preferences
+file eg/Astro-Coord-ECI.yml in .cpan/prefs.
-Unless you are running MSWin32 or VMS (which are special-cased), I will
-assume you are running some version of U*ix, and behave accordingly.
-
-eod
+EOD
my @possible_exes = qw{satpass};
-if ($opt{n}) {
+if ( $opt{n} ) {
print "Because you have asserted -n, the executables will not be installed.\n\n";
- }
- elsif ($opt{y}) {
+} elsif ( $opt{y} ) {
print "Because you have asserted -y, the executables will be installed.\n\n";
@exe_files = @possible_exes;
- }
- else {
- foreach (@possible_exes) {
- push @exe_files, $_
- if prompt ("Do you want to install $_?", 'n') =~ m/^y/i
- ;
- }
- }
+}
if (@exe_files) {
if ($^O eq 'MSWin32') {
@@ -37,7 +37,7 @@ $clipboard_unavailable = $IO::Clipboard::clipboard_unavailable;
# Initialization
#
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use constant LINFMT => <<eod;
%s %s %8.4f %9.4f %7.1f %-4s %s
@@ -0,0 +1,8 @@
+---
+comment: "Install satpass"
+match:
+ module: "Astro::Coord::ECI::TLE"
+pl:
+ args:
+ - "-y"
+
@@ -10,6 +10,12 @@ almanac
and height (meters) on the command. The option -help gets you
brief help.
+Astro-Coord-ECI.yml
+ This CPAN client prefs file causes the satpass script to be
+ installed by default. To use this file, place a copy of it in your
+ CPAN client's preferences directory (e.g. .cpan/prefs for the 'cpan'
+ client and a Unix-like operating system.)
+
azimuth
This Perl script finds the next time the Sun passes a given azimuth
(defaulting to 180 degrees) at Number 10 Downing Street.
@@ -17,7 +17,7 @@ use Pod::Usage;
use POSIX qw{strftime};
use Time::Local;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
Getopt::Long::Configure( 'pass_through' ); # Numbers may be negative.
@@ -12,7 +12,7 @@ use Astro::Coord::ECI;
use Astro::Coord::ECI::Sun;
use Astro::Coord::ECI::Utils qw{ deg2rad rad2deg };
-our $VERSION = '0.065';
+our $VERSION = '0.066';
my $time = time;
@@ -23,7 +23,7 @@ use Getopt::Long 2.33;
use Pod::Usage;
use POSIX qw{strftime};
-our $VERSION = '0.065';
+our $VERSION = '0.066';
my %opt;
@@ -9,7 +9,7 @@ use Astro::Coord::ECI::TLE;
use Getopt::Long 2.33;
use Pod::Usage;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
my %opt;
@@ -18,7 +18,7 @@ use Astro::Coord::ECI::Utils qw(deg2rad rad2deg SECSPERDAY);
use Astro::SpaceTrack;
use POSIX qw{strftime};
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use constant TIMFMT => '%d %b %H:%M:%S';
@@ -15,7 +15,7 @@ use Pod::Usage;
use POSIX qw{ strftime };
use Time::Local;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
# Map -want-events values to TLE event codes.
my %wanted_event_map = (
@@ -12,7 +12,7 @@ use HTTP::Date;
use LWP::UserAgent;
use Pod::Usage;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
my %opt;
@@ -14,7 +14,7 @@ use Getopt::Long 2.33;
use Pod::Usage;
use XML::Writer;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
my %opt = (
latitude => 52.069858, # Degrees north of Equator
@@ -5,7 +5,7 @@ use 5.006002;
use strict;
use warnings;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use base qw{ Exporter };
@@ -11,7 +11,7 @@ use Astro::Coord::ECI::Utils qw{ __default_station PIOVER2 SECSPERDAY };
use Exporter ();
use POSIX qw{ floor };
-our $VERSION = '0.065';
+our $VERSION = '0.066';
our @EXPORT_OK = qw{
almanac almanac_hash
@@ -43,7 +43,7 @@ package Astro::Coord::ECI::Moon;
use strict;
use warnings;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use base qw{Astro::Coord::ECI};
@@ -50,7 +50,7 @@ package Astro::Coord::ECI::Star;
use strict;
use warnings;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use base qw{Astro::Coord::ECI};
@@ -50,7 +50,7 @@ package Astro::Coord::ECI::Sun;
use strict;
use warnings;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use base qw{Astro::Coord::ECI};
@@ -121,7 +121,7 @@ use warnings;
use base qw{Astro::Coord::ECI::TLE};
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use Astro::Coord::ECI::Sun;
use Astro::Coord::ECI::Utils qw{:all};
@@ -140,7 +140,7 @@ our @CARP_NOT = qw{
Astro::Coord::ECI
};
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use constant ERR_NOCURRENT => <<eod;
Error - Can not call %s because there is no current member. Be
@@ -113,16 +113,17 @@ actually be visible above the threshold to be reported. This is actually
how the attribute would have worked when introduced if I had thought it
through clearly.
-Use of the L<SATNAME> JSON attribute to represent the common name of the
-satellite is deprecated in favor of the L<OBJECT_NAME> attribute, since
+Use of the C<SATNAME> JSON attribute to represent the common name of the
+satellite is deprecated in favor of the C<OBJECT_NAME> attribute, since
the latter is what Space Track uses in their TLE data. Beginning with
0.053_01, JSON output of TLEs will use the new name.
Beginning with release 0.056_01, loading JSON TLE data which specifies
-L<SATNAME> produces a warning the first time it happens. As of version
-0.061 there is a warning every time it happens. Six
-months later, loading JSON TLE data which specifies L<SATNAME> will
-become a fatal error.
+C<SATNAME> produces a warning the first time it happens. As of version
+0.061 there is a warning every time it happens. As of version 0.066
+loading JSON TLE data which specifies C<SATNAME> is a fatal error. Six
+months after this, all code referring to C<SATNAME> will be removed,
+meaning that the key will be silently ignored.
=head1 DESCRIPTION
@@ -229,7 +230,7 @@ package Astro::Coord::ECI::TLE;
use strict;
use warnings;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use base qw{ Astro::Coord::ECI Exporter };
@@ -7613,7 +7614,7 @@ encoded with a four-digit year.
if ( exists $hash->{SATNAME} ) { # TODO Deprecated
warnings::enabled( 'deprecated' )
- and carp 'The SATNAME JSON key is deprecated ',
+ and croak 'The SATNAME JSON key is deprecated ',
'in favor of the OBJECT_NAME key';
exists $hash->{OBJECT_NAME}
or $hash->{OBJECT_NAME} = $hash->{SATNAME};
@@ -8547,7 +8548,7 @@ sub _next_elevation_screen {
},
'25077' => {
'comment' => '',
- 'status' => 0,
+ 'status' => 2,
'name' => 'Iridium 42',
'class' => 'Astro::Coord::ECI::TLE::Iridium',
'type' => 'iridium',
@@ -8945,7 +8946,7 @@ sub _next_elevation_screen {
#
# $ eg/visual -merge
#
-# Last-Modified: Sat, 14 Jun 2014 22:30:35 GMT
+# Last-Modified: Thu, 14 Aug 2014 22:25:22 GMT
%magnitude_table = (
'00694' => 3.5,
@@ -104,7 +104,7 @@ package Astro::Coord::ECI::Utils;
use strict;
use warnings;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
our @ISA = qw{Exporter};
use Carp;
@@ -143,7 +143,7 @@ package Astro::Coord::ECI;
use strict;
use warnings;
-our $VERSION = '0.065';
+our $VERSION = '0.066';
use Astro::Coord::ECI::Utils qw{:all};
use Carp;
@@ -27,8 +27,10 @@ my %mth;
my $fail = 0;
my $test = 0;
-my $ua = LWP::UserAgent->new ();
-my $asof = timegm( 0, 0, 17, 8, 3, 114 );
+my $ua = LWP::UserAgent->new(
+ ssl_opts => { verify_hostname => 0 }, # Necessary until Perl recognizes McCants' cert.
+);
+my $asof = timegm( 0, 0, 0, 16, 9, 114 );
foreach (["Mike McCants' Iridium status",
'http://www.prismnet.com/~mmccants/tles/iridium.html',
@@ -188,7 +190,7 @@ EOD
25041IRIDIUM 40 [+]
25042IRIDIUM 39 [+]
25043IRIDIUM 38 [-]
-25077IRIDIUM 42 [+]
+25077IRIDIUM 42 [-]
25078IRIDIUM 44 [-]
25104IRIDIUM 45 [+]
25105IRIDIUM 24 [-]
@@ -259,7 +261,7 @@ content="text/html; charset=iso-8859-1">
<h1 align="center">Iridium Constellation Status</h1>
-<p align="center"><strong>** Updated April 8th. 2014 **</strong></p>
+<p align="center"><strong>** Updated 08 September 2014 **</strong></p>
<p align="left">For a summary of the Iridium launch sequence, see
my <a href="iridium_launch.htm">Iridium Launch Chronology</a>.
@@ -269,59 +271,37 @@ Failures</a>.</p>
<p><strong>Latest changes </strong>(see below for earlier
changes): </p>
-<p>*** By early 2014, Iridium 45 (25104, 1997-082A) is no longer
-maintaining its place in orbital plane 2. Iridium 45 may have
-started migrating towards orbital plane 3. Its place in orbital
-plane 2 has been taken by Iridium 23 (24906, 1997-043D).***</p>
-
-<p>*** By early 2014, Iridium 29 (24944, 1997-051A) has ceased to
-maintain its position in the constellation, and has presumably
-failed. There is currently no spare available in plane 3 to
-replace it. ***</p>
-
-<p>*** On 20 November, 2012, Iridium 96 (27376, 2002-005E),
-previously spare in orbital place 3, began migrating towards
-orbital plane 4, which had no on-orbit spare, This left orbital
-place 3 without a spare. The migration took around twelve months.
-Iridium 96 took over from failed Iridium 4 (24796, 1997-020E).
-Iridium 96 was raised to operational altitude several months
-before its arrival in plane 4 and appears to have been brought
-into use at that time. ***</p>
-
-<p>*** On 13 November, 2012, Iridium 94 (27374, 2002-005C), which
-had been migrating over the past year from orbital place 3,
-arrived at orbital plane 2, and was immediately raised to
-operational altitude to replace Iridium 23 (24906, 1997-043D)
-which had evidently failed, though retaining at least some
-functionality. Iridium 23 initially remained at operational
-altitude a few seconds behind Iridium 94, but was later moved to
-replace Iridium 45. ***</p>
+<p>*** At the end of August 2014, Iridium 98 (27451, 2002-301B) ,
+whch had been spare in orbital plane 6 since migrating from plane
+4, was raised to operational altitude a few seconds behind
+Iridium 42 (25077. 1977-077). It is so far unclear whether Irdium
+42 has failed.***</p>
<pre>Orbital <-------- Operational satellites --------> Spares
Plane
-Plane 1: <a href="iridium74and21.htm">21</a> 72 75 70 62 63 64 65 66 67 68 14; <a
+Plane 1: <a href="iridium74and21.htm">21</a> 72 75 70 62 63 64 65 66 67 68 14; <a
href="iridium74and21.htm">74</a> (note: Iridium 74 is probably a partial failure)
-Plane 2: 22 <a href="iridium94.htm">94</a> 76 25 23 46 47 20 49 <a
-href="iridium11and26.htm">11</a> 3 45 (migrating?) (note: Iridium 23 is probably a partial failure)
-Plane 3: 55 <a href="iridium28and95.htm">95</a> <font
-color="#FF0000"><em>29</em></font> <a href="iridium30and31.htm">31</a> <a
-href="iridium30and31.htm">30</a> 32 <a
-href="iridium33collision.htm">91</a> 57 58 59 60 (note: Iridium 29 has probably failed)
-Plane 4: 19 34 35 <a href="iridium36and97.htm">97</a> <a
-href="iridium5and51.htm">5</a> 6 <a href="iridium7and51.htm">51/7</a> 8 96 37 61
-Plane 5: 50 56 52 53 <a href="iridium9and84.htm">84</a> 10 54 12 13 83 <a
+Plane 2: 22 <a href="iridium94.htm">94</a> 76 25 23 46 47 20 49 <a
+href="iridium11and26.htm">11</a> 3 45 (migrating to plane 3?) (note: Iridium 23 is probably a partial failure)
+Plane 3: 55 <a href="iridium28and95.htm">95</a> <font
+color="#FF0000"><em> </em></font> <a href="iridium30and31.htm">31</a> <a
+href="iridium30and31.htm">30</a> 32 <a
+href="iridium33collision.htm">91</a> 57 58 59 60 (note: Iridium 29 has evidently failed)
+Plane 4: 19 34 35 <a href="iridium36and97.htm">97</a> <a
+href="iridium5and51.htm">5</a> 6 <a href="iridium7and51.htm">51/7</a> 8 96 37 61
+Plane 5: 50 56 52 53 <a href="iridium9and84.htm">84</a> 10 54 12 13 83 <a
href="iridium16and86.htm">86</a> <a href="iridium91.htm">90 (launched to plane 3, but has been migrated to plane 5)</a>
-Plane 6: 18 42 40 39 80 <a href="iridium17and77.htm">77</a> 15 81 <a
-href="iridium38and82.htm">82</a> 41 43 <a
-href="iridium98.htm">98 (launched to plane 4, but has been migrated to plane 6)</a></pre>
+Plane 6: 18 42/98 40 39 80 <a href="iridium17and77.htm">77</a> 15 81 <a
+href="iridium38and82.htm">82</a> 41 43 </pre>
<pre>Original <----- Failed -----> <- Failed -> <em>Note that some of the failed</em> <em>satellites have drifted from the original orbital planes</em>
Orbital (but still in orbit) (decayed) <em> </em>
Plane <em> </em>
Plane 1: 73t
Plane 2: 69t 24t 71t <a href="iridium11and26.htm">26</a> 48d
-Plane 3: <a href="iridium28and95.htm">28</a> <a
-href="iridium33collision.htm"><font color="#FF0000">33</font></a>t 27d <em>Iridium 33 was fragmented by the collison with Cosmos 2251 on February 10, 2009</em>
+Plane 3: <a href="iridium28and95.htm">28</a> 29<font
+color="#FF0000"> </font><a href="iridium33collision.htm"><font
+color="#FF0000">33</font></a>t 27d <em>Iridium 33 was fragmented by the collison with Cosmos 2251 on February 10, 2009</em>
Plane 4: 4 <a href="iridium36and97.htm">36</a>t
Plane 5: 2t 914t 911t <a href="iridium16and86.htm">16</a>t 85d <a
href="iridium9and84.htm">9</a>d <em>Iridium 2 has drifted far from</em> <em>its original launch plane, and continues to drift</em>
@@ -390,14 +370,20 @@ which originally belonged to (the second) Iridium 11. </p>
<p><a name="Recent changes"><strong>Recent changes</strong></a>: </p>
+<p>At the end of August 2014, Iridium 98 (27451, 2002-301B) ,
+whch had been spare in orbital plane 6 since migrating from plane
+4, was raised to operational altitude a few seconds behind
+Iridium 42 (25077. 1977-077). It is so far unclear whether Irdium
+42 has failed.</p>
+
<p>By early 2014, Iridium 45 (25104, 1997-082A) is no longer
-maintaining its place in orbital plane 2. Iridium 45 may have
-started migrating towards orbital plane 3. Its place in orbital
-plane 2 has been taken by Iridium 23 (24906, 1997-043D).</p>
+maintaining its place in orbital plane 2. Iridium 45 appears to
+be migrating towards orbital plane 3. Its place in orbital plane
+2 has been taken by Iridium 23 (24906, 1997-043D).</p>
-<p>By early 2014, Iridium 29 (24944, 1997-051A) has ceased to
-maintain its position in the constellation, and has presumably
-failed. There is currently no spare available in plane 3 to
+<p>By early 2014, Iridium 29 (24944, 1997-051A) had ceased to
+maintain its position in the constellation, and had presumably
+failed. At that tme, there was no spare available in plane 3 to
replace it..</p>
<p>On 20 November, 2012, Iridium 96 (27376, 2002-005E),
@@ -419,7 +405,7 @@ seconds behind Iridium 94, but was later used to replace Iridium
45 (25104, 1997-02A).</p>
<p>In mid 2012, Iridium 4 (24796, 1997-020E) ceased to maintain
-its position in the constellation. Plane 4 currently has no
+its position in the constellation. At that time, Plane 4 had no
on-orbit spare</p>
<p>In late July 2012,<a href="iridium7and51.htm"> Iridium 51
@@ -469,11 +455,10 @@ presumably failed on station.</p>
<p>(January 2008) <a href="iridium91.htm">Iridium 90</a> <a
href="iridium90and%2091.htm">[previously labelled as Iridium 91]</a>
<a href="iridium91.htm">which had been manouvering since mid
-October2005 has now arrived in orbital plane 5</a></p>
+October2005 has arrived in orbital plane 5</a></p>
<p>(May 2007) <a href="iridium98.htm">Iridium 98, which had been
-manouvering since late June 2005, has now arrived in orbital
-plane 6</a></p>
+manouvering since late June 2005, has arrived in orbital plane 6</a></p>
<p>In early January 2007, Iridium 97 (27450,2002-031A), a spare
satellite in orbital plane 4, entered the operational
@@ -20,8 +20,8 @@ EOD
is last_modified(
'http://celestrak.com/SpaceTrack/query/visual.txt' ),
-'Sat, 14 Jun 2014 22:30:35 GMT',
-'Celestrak visual.txt Last-Modified';
+ 'Thu, 14 Aug 2014 22:25:22 GMT',
+ 'Celestrak visual.txt Last-Modified';
is last_modified( mccants => 'vsnames' ),
'Fri, 19 Apr 2013 21:54:32 GMT',