Closed MatthewGrim closed 6 years ago
The bug in the orbit data function should allow the generic data set to be generated once the omitted simulations at 2537.0km perigee have finished running. Another thing I now need to check is that the results generated from the original data sets from Darian are correct, subject to the new functions that should be more robust. Hopefully this does not change any of the data we have been using in the IAC paper.
With the above changes made and the defensive checks the IAC results are regenerated as they were previously. I think the reason for this is that the bug may have been introduced when I edited Darian's code, but also could be because the data set was generated with an older version. Either way, it doesn't matter, the results are replicated and the pipeline works.
The next thing to do it to test the 3 satellite data set when it has been generated.
I've now started to run a final data set from 800km to 10000km to get the whole parameter space on one plot. Once that's done, no more simulations should be run. Let's focus on getting results.
The results for both the equatorial and polar orbits to a target at 45 degrees North are shown below, using a simple J4 Perturbation.
The results are believable for the equatorial plane but show some strange characteristics for the polar sims. It doesn't make sense to me that the orbits above 5000km with three satellites would perform less well than with two. Something seems to be wrong here, and I need to investigate it. From what I can tell, the way I have set up the simulations is correct. Other than that this could be something to do with the postprocessing. I would be very surprised if the results are as they should be but the oversimplified propagator may be a reason for this.
The data sets have been generated and consolidated into a single program. The next phase is to try to debug the simulation results that I have to try to find a reason for the strange behaviour we currently have.
So far, the scripts for the sps design tool have been developed iteratively. While this may have saved some time in the short term. The differences between the scripts are becoming unwieldly, and need to be consolidated into a single tool. This issue documents the development of this single tool.