Smarter trajectory handling

[cadojo]

Trajectories could be better!

Right now, they're just Vectors of Orbit structures. This could be so much better for many reasons, including lots of memory allocation necessary to get a high degree of precision for trajectory calculations, and more.

Ideas for Improvement

• Allow for returning ODESolution structures from propagate with a odesolution=Val{true} switch, and manually add methods for applying astrodynamics calculations

I don't like that solution. Is there another?

OrbitalTrajectories.jl

While watching Julia-related talks online, I found the OrbitalTrajectories.jl talk. Turns out OrbitalTrajectories also uses DifferentialEquations for propagating orbits (no surprises there). What is interesting is that the ODESolution object is returned directly from the propagation. That allows for interpolating by epoch, and access to DifferentialEquations helper methods.

Conclusion

• The Trajectory design by OrbitalTrajectories is far more robust. This should be the default, and a simple Vector of Orbit structures should be available via vec=Val{true}

[cadojo]

This was introduced in v0.10!