Figure 1.
Example of Martian aerocapture corridors with post-atmospheric pass orbital eccentricity contours: (a) ballistic re-entry profile, ; (b) lifted re-entry profile, .
Figure 1.
Example of Martian aerocapture corridors with post-atmospheric pass orbital eccentricity contours: (a) ballistic re-entry profile, ; (b) lifted re-entry profile, .
Figure 2.
Martian and terrestrial aerocapture corridors for multiple hyperbolic excess velocities, . The polynomial fits for low, mean, and high-density corridor boundaries are shown: (a) Martian aerocapture corridor with ; (b) Martian aerocapture corridor with .
Figure 2.
Martian and terrestrial aerocapture corridors for multiple hyperbolic excess velocities, . The polynomial fits for low, mean, and high-density corridor boundaries are shown: (a) Martian aerocapture corridor with ; (b) Martian aerocapture corridor with .
Figure 3.
Coarse robust Martian aerocapture corridor for
used to compute normalization quantities listed in
Table 1 and sixth-degree polynomial fits.
Figure 3.
Coarse robust Martian aerocapture corridor for
used to compute normalization quantities listed in
Table 1 and sixth-degree polynomial fits.
Figure 4.
Percentage error between finely discretized corridor limits (570 points) and computed values using exponential and polynomial constructed from 7 points. (a) Mars, = 1.0 . (b) Mars, = 3.0 . (c) Mars, = 6.0 .
Figure 4.
Percentage error between finely discretized corridor limits (570 points) and computed values using exponential and polynomial constructed from 7 points. (a) Mars, = 1.0 . (b) Mars, = 3.0 . (c) Mars, = 6.0 .
Figure 5.
Convergence property of D-ASTRO for overall optimal mission design, , with magenta lines delineating the boundaries of the aerocapture corridor. (a) Convergence of to . (b) Zoom into global minimum region.
Figure 5.
Convergence property of D-ASTRO for overall optimal mission design, , with magenta lines delineating the boundaries of the aerocapture corridor. (a) Convergence of to . (b) Zoom into global minimum region.
Figure 6.
Aerocapture trajectory profiles resulting from overall optimal mission design, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 6.
Aerocapture trajectory profiles resulting from overall optimal mission design, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 7.
Convergence property of D-ASTRO for minimum fuel mission design, , with magenta lines delineating the boundaries of the aerocapture corridor. (a) Convergence of to . (b) Zoom into global minimum region.
Figure 7.
Convergence property of D-ASTRO for minimum fuel mission design, , with magenta lines delineating the boundaries of the aerocapture corridor. (a) Convergence of to . (b) Zoom into global minimum region.
Figure 8.
contours for minimal fuel trajectory neglecting plane-change maneuvers, , and km.
Figure 8.
contours for minimal fuel trajectory neglecting plane-change maneuvers, , and km.
Figure 9.
Aerocapture trajectory profiles resulting from minimal fuel mission design, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 9.
Aerocapture trajectory profiles resulting from minimal fuel mission design, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 10.
Convergence property of D-ASTRO for minimum heat load mission design, , with magenta lines delineating the boundaries of the aerocapture corridor. (a) Convergence of to . (b) Zoom into global minimum region.
Figure 10.
Convergence property of D-ASTRO for minimum heat load mission design, , with magenta lines delineating the boundaries of the aerocapture corridor. (a) Convergence of to . (b) Zoom into global minimum region.
Figure 11.
Normalized heat load,
. (
a) Complete trajectory analysis. (
b) Predicted by Equation (
15).
Figure 11.
Normalized heat load,
. (
a) Complete trajectory analysis. (
b) Predicted by Equation (
15).
Figure 12.
Aerocapture trajectory profiles resulting from minimal heat load mission design, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 12.
Aerocapture trajectory profiles resulting from minimal heat load mission design, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 13.
Convergence property of D-ASTRO for minimum peak heating rate mission design, , with magenta lines delineating the boundaries of the aerocapture corridor. (a) Convergence of to . (b) Zoom into global minimum region.
Figure 13.
Convergence property of D-ASTRO for minimum peak heating rate mission design, , with magenta lines delineating the boundaries of the aerocapture corridor. (a) Convergence of to . (b) Zoom into global minimum region.
Figure 14.
Aerocapture trajectory profiles resulting from minimal peak heating rate mission design, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 14.
Aerocapture trajectory profiles resulting from minimal peak heating rate mission design, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 15.
Convergence property of MOO strategy for overall optimal mission design (blue) compared with D-ASTRO (green), , with magenta lines delineating the aerocapture boundaries.
Figure 15.
Convergence property of MOO strategy for overall optimal mission design (blue) compared with D-ASTRO (green), , with magenta lines delineating the aerocapture boundaries.
Figure 16.
Aerocapture trajectory profiles resulting from overall optimal mission design using MOO strategy, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 16.
Aerocapture trajectory profiles resulting from overall optimal mission design using MOO strategy, . (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 17.
Aerocapture trajectory profiles resulting from all optimal mission designs presented in this study. Initial conditions correspond to those that result in the lowest cost. (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 17.
Aerocapture trajectory profiles resulting from all optimal mission designs presented in this study. Initial conditions correspond to those that result in the lowest cost. (a) Altitude vs. velocity. (b) Q and vs. time.
Figure 18.
Accuracy evolution of sixth-degree polynomial curves as a function of binary search tolerance used for computing fitting points. (a) Corridor boundaries. (b) Lower-bound fit. (c) Upper-bound fit.
Figure 18.
Accuracy evolution of sixth-degree polynomial curves as a function of binary search tolerance used for computing fitting points. (a) Corridor boundaries. (b) Lower-bound fit. (c) Upper-bound fit.
Figure 19.
Evolution of Euclidean L-2 norm of upper- and lower-boundary fits and execution time of robust coarse corridor for a Martian aerocapture with .
Figure 19.
Evolution of Euclidean L-2 norm of upper- and lower-boundary fits and execution time of robust coarse corridor for a Martian aerocapture with .
Table 1.
Minimum and maximum values of considered metrics for a Martian aerocapture corridor for .
Table 1.
Minimum and maximum values of considered metrics for a Martian aerocapture corridor for .
Variable | Minimum | Maximum |
---|
| 1.15 | 5.15 |
| 0.00 | 3.56 |
Q | 3.42 | 41.53 |
| 3.45 | 46.32 |
Table 2.
Martian aerocapture simulation parameters.
Table 2.
Martian aerocapture simulation parameters.
Parameter | Value | Parameter | Value |
---|
Planetary parameters | Insertion trajectory parameters |
Radius of Mars, | 3390 | km | Hyperbolic excess velocity, | 3.5 | |
Gravitational parameter, | | | Atmospheric interface altitude, | 125 | |
Angular frequency of Mars, | | | Initial Radius, | | |
Vehicle parameters | Initial velocity, | | |
Mass of vehicles, m | 400 | | Initial longitude, | 0.5798 | |
Drag coefficient, | 1.6 | | Initial latitude, | 34.49 | |
Lift-to-drag ratio, | 0.2 | | Initial heading angle, | −18.24 | |
Nose-radius-to-body-radius ratio, | 0.5 | | Insertion flight path angle accuracy, | | |
Table 3.
Target operational orbit.
Table 3.
Target operational orbit.
Target parameter | Semi-major axis, a | Inclination, i | Eccentricity, e |
Value | 4621 | 70 | 0.05 |
Table 4.
Initial conditions used.
Table 4.
Initial conditions used.
Case | Initial Conditions |
---|
() | (deg) |
---|
1 | 59.0 | −60.000 |
2 | 40.6 | −10.113 |
3 | 59.0 | −0.057 |
4 | 3.0 | −0.057 |
5 | 39.6 | −10.852 |
6 | 37.8 | −10.502 |
Table 5.
Convergence properties of optimization algorithm with different initial conditions.
Table 5.
Convergence properties of optimization algorithm with different initial conditions.
Case | Cost | Optimized Parameters | Performance Metrics |
---|
() | () | () | () | () | () |
---|
1 | 0.5280 | 13.03 | −9.756 | 2.472 | 0.777 | 12.608 | 12.805 |
2 | 0.5280 | 13.69 | −9.784 | 2.411 | 0.776 | 13.094 | 13.301 |
3 | 0.5303 | 13.08 | −9.758 | 2.467 | 0.778 | 12.649 | 12.846 |
4 | 0.5283 | 13.10 | −9.759 | 2.465 | 0.778 | 12.665 | 12.862 |
5 | 0.5280 | 13.17 | −9.762 | 2.458 | 0.778 | 12.714 | 12.913 |
6 | 0.5283 | 13.16 | −9.762 | 2.459 | 0.778 | 12.704 | 12.902 |
Table 6.
Optimal results for minimum fuel trajectory.
Table 6.
Optimal results for minimum fuel trajectory.
Case | Cost | () | () | () |
---|
1 | 0.1092 | 40.85 | −10.393 | 0.7163 |
2 | 0.1064 | 48.46 | −10.487 | 0.7070 |
3 | 0.1122 | 34.17 | −10.294 | 0.7259 |
4 | 0.1392 | 7.58 | −9.445 | 0.8087 |
5 | 0.1078 | 44.40 | −10.439 | 0.7117 |
6 | 0.1105 | 37.80 | −10.350 | 0.7205 |
Table 7.
Optimal results for minimum heat load trajectory.
Table 7.
Optimal results for minimum heat load trajectory.
Case | Cost | () | () | Q () |
---|
1 | | 3.00 | −9.6289 | 4.221 |
2 | | 3.00 | −8.7822 | 4.141 |
3 | | 3.00 | −8.7803 | 4.140 |
4 | | 3.00 | −8.7934 | 4.145 |
5 | | 3.00 | −8.7862 | 4.142 |
6 | | 3.00 | −8.7908 | 4.144 |
Table 8.
Optimal results for minimal trajectory.
Table 8.
Optimal results for minimal trajectory.
Case | Cost | () | (deg) | () | (deg) |
---|
1 | | 3.0 | −8.780 | 4.0754 | 0.2000 |
2 | | 3.0 | −8.780 | 4.0754 | 0.2000 |
3 | | 3.0 | −8.780 | 4.0754 | 0.2000 |
4 | | 3.0 | −8.780 | 4.0754 | 0.2000 |
5 | | 3.0 | −8.780 | 4.0754 | 0.2000 |
6 | | 3.0 | −8.780 | 4.0754 | 0.2000 |
Table 9.
Convergence properties of MOO algorithm and D-ASTRO for overall optimal trajectory.
Table 9.
Convergence properties of MOO algorithm and D-ASTRO for overall optimal trajectory.
Case | Strategy | () | () | (m) | () | Q () | () |
---|
1 | MOO | 3.000 | −9.526 | 5.150 | 1.969 | 4.225 | 4.723 |
D-ASTRO | 13.03 | −9.756 | 2.472 | 0.779 | 12.608 | 12.805 |
2 | MOO | 3.007 | −9.635 | 5.145 | 2.062 | 4.228 | 4.818 |
D-ASTRO | 13.69 | −9.784 | 2.411 | 0.776 | 13.094 | 13.301 |
3 | MOO | 3.000 | −9.635 | 5.150 | 2.063 | 4.221 | 4.810 |
D-ASTRO | 13.08 | −9.758 | 2.467 | 0.778 | 12.649 | 12.846 |
4 | MOO | 3.000 | −8.780 | 5.150 | 0.884 | 4.140 | 4.075 |
D-ASTRO | 13.10 | −9.759 | 2.465 | 0.778 | 12.665 | 12.862 |
5 | MOO | 3.000 | −8.780 | 5.150 | 0.884 | 4.140 | 4.075 |
D-ASTRO | 13.17 | −9.762 | 2.458 | 0.778 | 12.714 | 12.913 |
6 | MOO | 3.000 | −9.590 | 5.150 | 2.025 | 4.222 | 4.774 |
D-ASTRO | 13.16 | −9.762 | 2.459 | 0.778 | 12.704 | 12.902 |
Table 10.
Computational performance and suggested optima of D-ASTRO and MOO strategies with and for the Martian test case.
Table 10.
Computational performance and suggested optima of D-ASTRO and MOO strategies with and for the Martian test case.
Weights | Strategy | Execution Time (s) | Function Counts | Time per Function Call (ms) | | |
---|
| D-ASTRO | 1.889 | 1820 | 10.381 | 13.23 | −9.765 |
MOO | 0.381 | 360 | 9.979 | 3.03 | −9.638 |
| D-ASTRO | 2.512 | 2010 | 12.496 | 43.97 | −10.434 |
MOO | 3.066 | 3020 | 10.151 | 40.61 | −10.113 |
| D-ASTRO | 0.564 | 500 | 11.286 | 15.58 | −9.653 |
MOO | 2.788 | 3010 | 9.263 | 12.39 | −9.853 |
| D-ASTRO | 0.506 | 470 | 10.773 | 37.84 | −10.101 |
MOO | 2.927 | 3010 | 9.723 | 12.39 | −9.853 |
| D-ASTRO | 2.033 | 1630 | 12.473 | 41.49 | −10.401 |
MOO | 2.767 | 3010 | 9.192 | 12.40 | −9.163 |
Table 11.
Computational performance and suggested optima of D-ASTRO and MOO strategies without employing polynomial fits to evaluate and . and used as initial guess for Martian test case.
Table 11.
Computational performance and suggested optima of D-ASTRO and MOO strategies without employing polynomial fits to evaluate and . and used as initial guess for Martian test case.
Weights | Strategy | Execution Time (s) | Function Counts | Time per Function Call (ms) | | |
---|
| D-ASTRO | 65.1 | 202 | 322 | 12.22 | −9.719 |
MOO | 90.2 | 304 | 297 | 3.00 | −9.634 |
| D-ASTRO | 48.9 | 162 | 302 | 40.60 | −10.390 |
MOO | 93.1 | 304 | 306 | 21.78 | −8.501 |
| D-ASTRO | 71.0 | 202 | 3528 | 16.00 | −9.657 |
MOO | 109 | 301 | 363 | 12.39 | −9.853 |
Table 12.
Percentage difference in performance metrics when fits and binary search were used to assess the feasibility of candidate points.
Table 12.
Percentage difference in performance metrics when fits and binary search were used to assess the feasibility of candidate points.
Weights | Strategy | Percentage Difference (%) |
---|
| | | |
---|
| D-ASTRO | 4.036 | 0.566 | −5.781 | −5.798 |
MOO | 0.454 | 0.097 | −0.682 | −0.673 |
| D-ASTRO | 4.066 | 0.604 | −5.842 | −5.804 |
MOO | 36.545 | 92.352 | −58.701 | −62.593 |
| D-ASTRO | −1.327 | 0.526 | 1.895 | 1.672 |
MOO | 0.000 | −0.046 | −0.001 | −0.005 |