I’m trying to use the orbit determination tutorial in order to see if Orekit could be used in place of other software (software from GMV in my case). I rewrote and reorganized the code in order to make it more understandable and maintainable but didn’t touch the core of the orbit determination.
My problem is that the OD takes a lot of time to compute : when it takes 30-60s max to compute in GMV, it can take up to 1800s in Orekit with the same data (1240 AzEl measurements distributed on 10 days).
I tested with different number of measurements (from 400 to 2000) and different distribution in time for the measurements (measurements distributed on 2 days or on 5 days).
What seems to matter is only the period of time : the computing time was of ~17s per evaluation for the 2 days period (~8.5s/evaluation/day) while it was of ~55s for the 5 days period (~11s/evaluation/day).
My question is : what can I do to optimize the OD computing time ? Do you have any idea of modifications in the code itself ? In the parameters ? Is it possible the use some parallelization ?
Annex question : how will the DSST OD work ? What will it use ?
Thanks in advance !