I’ve been thinking, it’d be handy to have a J2-only perturbation readily available for (Field)NumericalPropagator. Of course the feature itself is already available, but the idea would be to avoid the overhead of HolmesFeatherAttractionModel. Thoughts?
How do we handle the case where a user add both force models (i.e., J2 and HolmesFeatherstone)? Do we throw an exception at propagator.addForceModel(…) level?
I guess there will be no exceptions, just like I believe nothing is thrown when one adds the same third body twice. We’ll just need to be extra clear with the documentation.