Addresses issue #182. After changing the hard coded tau_ref_epoch to be in line with default value in system.py, I added a new optional flag to kepler.calc_orbit that automatically throws a warning each time it's called, unless the flag is set to False. I've set the flag to False for every internal orbitize call to calc_orbit so users just using standard orbitize! API will not get this warning. However, users calling it from their own scripts will get this warning, and will need to explicitly turn it off themselves.
How does that sound for a solution to transition out of the default tau_ref_epoch being 0 in calc_orbit?
Addresses issue #182. After changing the hard coded tau_ref_epoch to be in line with default value in system.py, I added a new optional flag to
kepler.calc_orbit
that automatically throws a warning each time it's called, unless the flag is set to False. I've set the flag to False for every internal orbitize call tocalc_orbit
so users just using standard orbitize! API will not get this warning. However, users calling it from their own scripts will get this warning, and will need to explicitly turn it off themselves.How does that sound for a solution to transition out of the default tau_ref_epoch being 0 in calc_orbit?