Open joelgeorgem opened 4 years ago
Sir, Actually the asteroids orbit the sun, so should I give the same frame as given in the paper and input Gravitational parameter of the sun? I tried to convert orbital elements of the Asteroids as given in Zheng et.al. 2015, to the ECI frame but for that, we need more information about the orbit.
I did not notice that the data is for asteroids. Yes, use for μ the value that corresponds to Sun. Everything else remains the same. If you want the initial and final positions and velocities directly, then use the corresponding table in the paper that I have mailed you. And of course, since the time scales are different, use higher time steps.
Sir, I made use of the positions and velocities from the paper you sent and the orbital elements from Zheng et.al for orbit propagation. I am encountering some errors and currently, I am rectifying them. I will inform you soon when the code is fully working.
Sir, I used the radius and velocity values given in the paper that you sent. But in order to propagate the asteroids position and velocity over time, I needed time period and specific angular momentum of the asteroids which I calculated using the eccentricity and mean anomaly data from Zheng et.al paper. I took the chaser's initial position as given in Ahn & Bang. I ran the greedy algorithm for 2 cases,
Results for case 1:
Results for case 2:
The paper got the best sequence as 1 2 3 4 with a dv of 6.36 km/s. Looking at Table 5, from Ahn and Bang, it is clear that they have been coasting for atleast 2000 days before making a transfer and from the debris data we know that coasting can reduce the total dv. So I tried to use the coasting time they have used but the chaser's initial orbit's parameters are not given in the paper and I was not able to propagate the orbit.
(r,v) is equivalent to orbital parameters. There will be subroutines available that will do this; or you can write one on your own.
Sir, I used the (r,v) values and included the conversion formulas to necessary orbital elements in our code itself. I ran the code for the 1st case in table 5 of Ahn and Bang paper. It is the transfer from chaser to the 1st asteroid with 2033.48 days as coasting time and 169.08 days as transfer time. We got dv=1.658 km/s and the paper got a dv of 1.53 km/sec.
Coasting seems to be important for asteroid rendezvous problem. Our initial studies showed that coasting does not help much in debris removal problem. However, the study was done before we got a "correct" code for Lambert transfer. Can we repeat the study now and see whether the result still holds?
Sir, Actually our initial study showed that coasting did not help in minimizing the transfer time. Later we found that dv minimum does depend on coasting time and for different coasting times we get a different and sometimes a better dv min. I also ran the corrected code now whose results are as below,
coasting time = 139968 secs dv_min=0.0592 km/s
coasting time = 189968 secs dv_min=0.3639 km/s
coasting time = 239968 secs dv_min=0.8665 km/s
coasting time = 289968 secs dv_min=0.4610 km/s 9968 secs
coasting time = 439968 secs dv_min=0.9044 km/s
For the above case, what is the dv_min for zero coasting time?
Sir, For zero coasting time and for the same range of transfer time, dv_min is 1.9594 km/sec.
Then we should consider coasting time also while computing ΔV. We should pre-compute extremal field maps and use them as lookups in our algorithm.
Yes Sir. I will read about the extremal field maps. Do you have any good source from where I can learn about them as I am not exposed to them previously?
I guess EFM is just a fancy name for a 3D plot of ΔV as a function of coasting time and transfer time. The term appears in publications by Junkins at TAMU.
Yes Sir. When I tried to search for some good sources to learn I ended up getting only journals. I will make a 3D plot (dv_min, transfer_time, coasting_time) and will send it shortly.
Not dv_min, but dv. A 3D plot of (transfer_time, coasting_time, dv). We will compute dv_min from this.
Yes sir, I am making some modifications to the code. I will finish them and plot the graph.
Sir, I encountered some problems (like memory and dimension errors) while making the grid points and it took me some time to make clean data (without nan and zero values) and rectify the errors. I did a 3-D mesh for the transfer between debris 2 to debris 14. The coasting time varies from 5000 secs to 150000 secs with an increment of 50 secs. For each coasting time, the transfer time varies from 500 secs to 10000 sec with an increment of 50 secs.
Can you clip the max value of dv to 1 and replot the figures? For example, if dv is the 3D matrix containing the data, then do dv(dv>1)=1;
and plot dv.
Sir, The figures are attached below.
Sir, The paper with the debris data is using Lambert Rendezvous with drift and for the transfer from debris 2 to debris 14 they used: Coasting time = 139968s, transfer time=2592s, dv=0.0598 km/s.
I ran our Lambert algorithm with a stepsize of 1sec for coasting time and got the minimum transfer as: Coasting time = 139892s, transfer time = 8400s, dv=0.0571 km/s. This dv is lower than than the dv in the paper.
Why is it that the transfer time in your simulations is starting at 4000?
Sir, I did the simulation with the number of revolutions set to 1 (since it took a long time for the code to run if I took all 3 revolution case). In this transfer case, I randomly checked some points throughout the range of coasting time and transfer time and the dv was minimum only for the m=1 case. For m=1, usually the lower transfer time returns no dv, that's why there are no data points before 4000s.
Sir, I wrote the Particle Swarm Algorithm (particle_swarm.m) for our problem. Initially, I took 10000 points and 1000 iterations. But the global minimum is obtained in less than 80 iterations. In this way, it is quite faster to obtain the minimum dv.
Use the data in Table 3 of the second paper that we told we will read. Run our greedy algorithm on it. Compare the results.