Astro-satpass

Changes for version 0.028_01

Date::Manip and Time::y2038 are no longer 'recommended' but 'optional'. This means not telling the tool chain about them, but doing custom checks, and custom, gentler messages about why you might (or might not!) want these modules. Centralize the decision about what time routines to use in Astro::Coord::ECI::Utils, and have it export to the other modules, the tests, the 'satpass' script, and the example scripts. Rewrite t/parse_date.t so that it no longer needs Time::y2038. Instead, it uses precomputed times, which it offsets for the target system's epoch when it runs. The above was done in an attempt to clarify the role of the optional modules, and cases where they might not be desirable. Thanks to Christopher Sylvain for identifying the problems and working with me on their solution. Rewrite the time portions Astro::Coord::ECI::OVERVIEW to better reflect the current state of the time handling. Plus, retitle it so that hopefully it will actually appear in the distribution.

Predict satellite passes over an observer.

Overview of Astro::Coord::ECI and friends

Manipulate geocentric coordinates

Compute the position of the Moon.

Compute the position of a star.

Compute the position of the Sun.

Compute satellite locations using NORAD orbit propagation models

Compute behavior of Iridium satellites

Represent a set of data for the same ID.

Utility routines for astronomical calculations

To install Astro::Coord::ECI, copy and paste the appropriate command in to your terminal.

cpanm Astro::Coord::ECI

perl -MCPAN -e shell
install Astro::Coord::ECI

For more information on module installation, please visit the detailed CPAN module installation guide.

	Global
`s`	Focus search bar
`?`	Bring up this help dialog

	GitHub
`g` `p`	Go to pull requests
`g` `i`	go to github issues (only if github is preferred repository)

	Search terms
module: (e.g. module:Plugin)
distribution: (e.g. distribution:Dancer auth)
author: (e.g. author:SONGMU Redis)
version: (e.g. version:1.00)