ASCOM.Astrometry Namespaces |
This namespace contains all ASCOM astrometry components together with associated enums and structures. The astrometry components (Transform, NOVAS-COM and Kepler) are located in the ASCOM.Astrometry.Components namespace while unified enums and structures are in the ASCOM.Astrometry namespace and serve all three components.
Namespace | Description |
---|---|
ASCOM.Astrometry | ASCOM.Astrometry NamespaceSummaryThis namespace contains all ASCOM astrometry components together with associated enums and structures. The astrometry components (Transform, NOVAS-COM and Kepler) are located in the ASCOM.Astrometry.Components namespace while unified enums and structures are in the ASCOM.Astrometry namespace and serve all three components. Transform is a new component while those familiar with the Kepler and NOVAS-COM components will recognise find all of their functionality in this namespace. Further information is given in the "Which NOVAS" topic at the head of this help file. |
ASCOM.Astrometry.AstroUtils | ASCOM.Astrometry.AstroUtils NamespaceSummaryThis namespace contains miscellaneous tested astronomy components to reduce development time and improve consistency of operation. |
ASCOM.Astrometry.Exceptions | ASCOM.Astrometry.Exceptions NamespaceSummaryThis namespace contains all astrometry related exceptions |
ASCOM.Astrometry.Kepler | ASCOM.Astrometry.Kepler NamespaceSummaryThis namespace contains all Kepler related items |
ASCOM.Astrometry.NOVAS | NOVAS-C: Naval Observatory Vector Astrometry SubroutinesIntroductionThis component is a .NET presentation of the subroutines and function in the US Naval Observatory NOVAS 2 library. The following is extracted from its accompanying pdf document, which is also included in the ASCOM distribution The Naval Observatory Vector Astrometry Subroutines, NOVAS, is an integrated package of source-code modules for computing a wide variety of common astrometric quantities and transformations. The package can provide, in one function call, the instantaneous coordinates (apparent, topocentric, or astrometric place) of any star or planet. At a lower level, NOVAS also provides general astrometric utility transformations, such as those for precession, nutation, aberration, parallax, and the gravitational deflection of light. The computations are highly precise. NOVAS-C uses, as input, astrometric reference data that is expressed in the International Astronomical Union (IAU) J2000.0 system. In particular, NOVAS-C 2.0 supports (but is not limited to) data that conforms to the ICRS. ICRS-compatible data includes the Hipparcos and Tycho Catalogues, the ACT Reference Catalog, the International Celestial Reference Frame (ICRF), the Jet Propulsion Laboratory’s DE405 planetary ephemeris, and Earth orientation measurements from the International Earth Rotation Service (IERS). The algorithms used by the NOVAS-C functions are based on a vector and matrix formulation that is rigorous, consistent with recent IAU resolutions, and does not use spherical trigonometry or form “day numbers” at any point. Objects within and outside the solar system are treated similarly and the position vectors formed and operated on by these functions place each relevant object at its actual distance (in AU) from the solar system barycenter. Objects at unknown distance (parallax zero or undetermined) are placed on the “celestial sphere” herein defined to be at a radius of 10 megaparsecs (2.06 ´ 1012 AU). NOVAS-C contains three levels of functions: basic, utility, and supervisory. Basic level functions supply the values of fundamental variables, such as the nutation angles and the heliocentric positions of solar system bodies, for specific epochs. Utility-level functions perform transformations corresponding to precession, nutation, aberration, etc. Supervisory-level functions call the basic and utility functions in the proper order to compute apparent, topocentric, or astrometric places of stars or solar system bodies for specific dates and times. If desired, the user can interact exclusively with the supervisory-level functions and not become concerned with the details of the geometry or physical models involved in the computation. Credits
.NET ImplementationThe NOVAS class has been implemented as a STATIC class because it does not store state of any kind and just provides access to the NOVAS code library (see the NOVAS Class entry for more detailed information). Method and enum names are identical to those in NOVAS2 except for omission of underscore characters and use of camelcase. There are also a few new structures and enums but these should be self explanatory. One significant parameter difference is that position and velocity vectors are returned as structures rather than double arrays. This was done to make type checking more effective. Testing of the high level supervisory functions has been carried out using real-time star data from the USNO web site. Values provided by this NOVAS2 implementation agree on average to about 50 milli arc-seconds with current USNO web site values. This class is 32/64bit agnostic and transparently operates in both environments. |
ASCOM.Astrometry.NOVASCOM | ASCOM.Astrometry.Components NamespaceUtilities UpdateThe Platform 5.0 NOVASCOM and Kepler components have been combined into one namespace (ASCOM.Utilities.NOVASCOM) for this release. This removes duplication of enums and structures between the two components and improves interoperability. For backward compatibility, the 32bit COM Kepler and NOVASCOM components are also included in the platform and are accessible through their original namespaces of ASCOM.Kepler and ASCOM.NOVASCOM respectively. This is to ensure that existing applications continue to work, unchanged, with the new platform. The re-factored NOVASCOM classes (not the original COM component classes) such as Planet and Earth now have internal Kepler components by default so it is no longer necessary to create these separately and attach them as ephemeris objects. If you do attach ephemeris objects, they will be used in place of the internal objects just as in the original COM components. No other functions in the NOVASCOM and Kepler components has not been altered and testing shows a numeric result correspondence with the original COM components of than 1 part in 1E-9. NOVAS-COM Release Notes - V2.1 (July 2007)NOVAS-COM V2.1 is the third production release of a Component Object Model (COM) implementation of the U. S. Naval Observatory Vector Astrometry Subroutines (NOVAS) package. By encapsulating NOVAS within a COM component, the functions of NOVAS become available to most Windows scripting and programming environments. This component may be used by Visual Basic programs, scripts in any ActiveX Scripting language such as VBScript, JScript, Perl, Python, even an Excel spreadsheet. Thus, the proven accuracy of these USNO algorithms is accessible to end-user observatory automation and data reduction script writers. Credits
IntroductionNOVAS-COM was developed according to the ASCOM Initiative's quality and behavior guidelines. Every effort has been taken to provide a quality stable component. Errors are signaled via automation exceptions with clear error messages. The component has a dual interface, and thus can be used in demanding high performance applications without the speed penalty of the dispatch interface. For more information on the ASCOM Initiative and the logo requirements, see the ASCOM Initiative Web Site. NOVAS-COM provides for the computation of a wide variety of common astrometric quantities and transformations. The component can provide, in one or two method calls, the instantaneous coordinates (apparent, topocentric, or astrometric place) of any star. With the addition of acompatible ephemeris component such as the Kepler Orbit Engine, NOVAS-COM can also compute the instantaneous coordinates of major and minor planets. Ignoring ephememeris approximations, the computations provided are precise to better than one milliarcsecond. The NOVAS-COM component is an easy-to-use facility that can be incorporated into data reduction programs, telescope control systems, and simulations. The internal NOVAS subroutines are, in fact, identical to those now used in the production of the Astronomical Almanac. The internally used subroutines are available in ANSI standard Fortran and C versions. The algorithms used by the NOVAS-COM routines are based on a vector and matrix formulation which is rigorous, consistent with recent IAU resolutions, and does not use spherical trigonometry or form "day numbers" at any point. Objects within and outside the solar system are treated similarly and the position vectors formed and operated on by these routines place each relevant object at its actual distance (in AU) from the solar system barycenter. Objects at unknown distance (parallax zero or undetermined) are placed on the "celestial sphere" herein defined to be at a radius of 10 megaparsecs (2.06E12 AU). A description of the algorithms used, along with definitions of terms and related information, can be found in Kaplan, et al. (1989) Astron. J. 97, 1197. NOVAS-COM uses as input astrometric reference data that is expressed in the IAU J2000.0 system. In particular, NOVAS supports (but is not limited to) data that conforms to the International Celestial Reference System (ICRS). ICRS-compatible data includes the Hipparcos and Tycho Catalogues, the ACT Reference Catalog (obsolete, use Tycho-2), the International Celestial Reference Frame (ICRF), the Jet Propulsion Laboratory DE405 planetary ephemeris, and Earth orientation measurements from the International Earth Rotation Service (IERS). The list of ICRS-compatible data of various types is continually expanding. NOVAS-COM can also be used with data conforming to the FK5 system. NOVAS-COM's internal support for solar system body calculations is limited to an the four largest planets, and is used is used for barycenter computations only. In order to use NOVAS-COM's Planet object for major and minor planets, you must furnish an ephemeris source which implements a simple COM interface. When attached to an instance of the NOVAS-COM Planet object, the ephemeris component is responsible for supplying heliocentric J2000-equatorial rectangular coordinates of the planet at the given terrestrial time. One such compatible ephemeris component is the Kepler Orbit Engine, developed by the NOVAS-COM author. See the ASCOM Initiative web site in the downloads section. Delta-T calculationsNOVAS-COM allows the client to directly specify the value of delta-t to used in various situations, as a property of some of its objects. NOVAS-COM also contains an internal utility subroutine that approximates the value of delta-T (TT-UT1) based on a 4th order Bessel interpolation of observed values taken from the Astronomical Almanac and USNO Delta T historical tables. Tables within the delta-t subroutine contain data from 1620.0 through 2007.0. Predictions for 2007.0 through 2050.0 are made using a NASA derived polynomial. Entries prior to 1955 are corrected for secular tidal acceleration as used in JPL's DE403 ephemeris. If the client does not directly set the delta-t property, this internal utility is used. Kepler Ephemeris Engine Programmer's ReferenceIntroductionThis document describes the first production release of the Kepler Ephemeris Engine, an ASCOM component which provides ephemerides for solar system bodies, given their orbital elements. It was written as a companion to the NOVAS-COM vector astrometry engine, providing the ephemerides needed for planetary astrometric calculations, and for high-precision aberration calculations. It provides heliocentric J2000 equatorial cartesian vectors for position and velocity given a set of orbital elements and a terrestrial time. NOVAS-COM can be used to transform these coordinates to Earth-centered ("astrometric") or topocentric coordinates for observational use. You can download NOVAS-COM from the ASCOM Downloads Page. Credits
Ephemeris CalculationsKepler does not integrate orbits to the current epoch. If you want the accuracy resulting from an integrated orbit, you must integrate separately and supply Kepler with elements of the current epoch. Orbit integration is on the list of things for the next major version. Kepler uses polynomial approximations for the major planet ephemerides. The tables of coefficients were derived by a least squares fit of periodic terms to JPL's DE404 ephemerides. The periodic frequencies used were determined by spectral analysis and comparison with VSOP87 and other analytical planetary theories. The least squares fit to DE404 covers the interval from -3000 to +3000 for the outer planets, and -1350 to +3000 for the inner planets. For details on the accuracy of the major planet ephemerides, see the Accuracy Tables page. Date and Time SystemsFor a detailed explanation of astronomical timekeeping systems, see A Time Tutorial on the NASA Goddard Spaceflight Center site, and the USNO Systems of Time site. Julian dates Hourly Time Values UTC Time Scale UT1 Time Scale TT Time Scale Development ProcessDevelopment and refinement of this component will be evolutionary rather then revolutionary. The ephemeris engine interface specification will not be blessed as an "ASCOM Standard" until
Discussions between ASCOM members regarding this component, the ephemeris generator interface specification and other issues are conducted on the ASCOM-Talk mailing list. Instructions for joining the list are at the ASCOM web site, or just click here to subscribe. |
ASCOM.Astrometry.SOFA | ASCOM.Astrometry.SOFA NamespaceSummaryThis namespace contains funcitonality based around SOFA (Standards of Fundamental Astronomy) routines in forms that are easily accessible from both 32bit and 64bit .NET and COM applications |
ASCOM.Astrometry.Transform | ASCOM.Astrometry.Transform NamespaceSummaryThis namespace contains all Transform related items |