Cannot perform orbit estimation with both geopotential and solid tides force models
Since v9.0 update, the estimation process behaves oddly when both
geopotential and solid tides force models are added to the
propagatorBuilder.
The few first iterations seem correct but after 7 or 8 iterations
approximately the process slows down a lot until being quasi stopped.
No exception is thrown and no message appears in the console.
I think you can experiment this trouble with Orekit's OD test. I have tried with w3b data. You must activate sun and moon solid tides force model and do not hesitate to activate another parameter driver to get enough iterations to make the lag clear.
Actually the problem is the same as when you add twice a force model (sun attraction for instance). As solidTides class contains an attraction force model and then share the same ParameterDriver, the addition of the solid tides and the geopotential force models acts as if it was two same Force models for the orbit determination.
(from redmine: issue id 360, created on 2017-09-01, closed on 2017-11-25)
- Uploads: