-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is no "Transfer to another planet" script #16
Comments
Would this same script allow for Mun<->Minmus transfers? |
The math is the same for a Mun-Minus transfer as for an interplanetary
transfer, so in principle, yes.
I have a very feeble understanding of the math, but when I did a bit of
preliminary web research, I encountered a lot of precomputed lookup tables
for ejection angles and transfer windows. Obviously a solution that relies
on those lookup tables would not work for moon-to-moon transfers.
For Kerbin and its satellites, the energy difference between orbits is so
small that it's probably best to just escape Mun, circularize, and perform
a Hohmann to Minus.
For something like the Jool system, however, a robust general solution
would save a *looooot* of fuel over time.
…On Mon, Jan 22, 2018 at 9:12 PM Jack Twilley ***@***.***> wrote:
Would this same script allow for Mun<->Minmus transfers?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEemNKapjStzJYnBQt6E7toJ_3pSs8Bks5tNWo1gaJpZM4QoKLY>
.
|
To transfer to Duna
|
xeger, as you have pointed out a transfer to Duna is similar to a hohmann transfer to the Mun. There are two main differences. Duna has a slightly elliptical orbit. So your hohmann transfer script has to be able to calculate elliptical transfers. The second is calculating a hyperbolic escape trajectory parallel with Kerbin prograde. I don't understand the math. I fudge the numbers a little and correct the burn afterwards. |
Jebediah need to boldly go where no kerbal was gone before!
The text was updated successfully, but these errors were encountered: