Documentation update 2015-01-13
- Added a software license (BSD-3 in doc/license.txt) and changed readMe.txt to ReadMe.md.
1.0.3 2015-06-04
- Removed a vestigial semicolon from a python unit test.
- Added a software license.
- Changed the ReadMe to a markdown file.
1.0.2 2014-10-15
- Made compatible with more modern C++ compilers, while retaining backwards compatibility, by using boost::tr1 for array.
1.0.1 2014-09-24
- Modernized the exception catching syntax.
1.0.0 2014-09-02
- Added CoordSys.taiFromDate methods.
- Added besslianEpochFromTAI and taiFromBesselianEpoch functions.
- AppGeoCoordSys changed maxAge from 1 second to 0.05 seconds. This will make lunar tracking errors negligible even at a high update rate.
- Added functions appTopoFromAppGeo, appGeoFromAppTopo, obsFromAppTopo and appTopoFromObs, and removed similar methods from AppTopoCoordSys and ObsCoordSys.
- Enhanced the documentation, including a working example and listing most classes and functions on the main source code documentation page, with working links.
0.9.9.4 2014-09-01
- AppGeoCoordSys changed default maxAge (of the cache) from 300 seconds to 1 second. 300 seconds was too long for more accurate lunar tracking.
0.9.9.3 2014-09-01
- Changed CoordSys.setCurrTAI to CoordSys.setCurrDate for self-consistency.
- Changed CoordSys operator== to test isCurrent and updated the unit test accordingly.
- Changed default date of ICRSCoordSys and GalCoordSys from 2000 to 0 (current date).
- Added a unit test for AppGeoCoordSys's cache.
- Added a unit test for coordinate system default constructors.
0.9.9.2 2014-08-31
- Bug fix: AppGeoCoordSys date was not being reliably updated by setCurrTAI.
0.9.9.1 2014-08-29
- Added documentation files doc/index.html, doc/versionHistory.html and readMe.txt and updated doc/main.dox accordingly.
0.9.9 2014-08-27
- Updated timeCoordConv to also time conversion of PVTCoord.
0.9.8 2014-08-27
This is a major refactoring, primarily to fix a bug in computing velocity when converting PVTCoords from apparent geocentric coordinates to apparent topocentric coordinates. Significant changes include:
- Changed PVTCoord to an object that models linear spatial velocity instead of velocity along a great circle. This is a much simpler model and capable of representing the change in distance with time. However, now PVTCoord is only intended to support computation of instantaneous velocity, not to represent the long-term track of a moving object.
- Changed CoordSys to support "current" coordinates, which are represented by date=0. This included adding two new methods: isCurrent() and setCurrTAI(tai), the latter of which allows you to set the current TAI date while computing coordinates without visibly changing anything about the CoordSys (it is a const method; the data that is updated is considered an internal cache). This allows setting the current date without copying data, and allows use of cached apparent geocentric data without excessive recomputation, thus significantly speeding up coordinate conversions for PVTCoords.
- AppGeoCoordSys now automatically avoids recomputing the cache for very nearby times, thus eliminating the need for freezeCache argument of setDate.
0.9.7 2014-08-25
- Minor doc and variable name cleanups.
- Some improvements to tests/testCoordConvAgainstTCC.py.
- Bug fix: examples/timeCoordConv.py failed while timing the computation of apparent geocentric cached data due to unreasonable dates for large numbers of iterations.
0.9.6 2014-08-19
- Enabled generation of Doxygen documentation (by adding missing SConscript and doxygen.config.in files to the doc dir).
- Update the source documentation to make Doxygen happy.
0.9.5 2014-08-13
- Bug fix: parallax was mis-computed, due to using longitude instead of latitude.
- Enhanced tests/testCoordConvAgainstTCC.py (and in the process discovered and fixed a bug in the old TCC).
- Updated documentation to make Doxygen happy.
- Added a separate version.py file.
0.9.3 2014-07-13
First version with version history.