Menu

#7 direct transfer may not be working in intercept.ks

1.0
open
nobody
None
2021-12-26
2021-05-28
No

Discussion

  • Stäphen Goedzal

    Potentially fixed in upcoming r83 by using fancy maths to calculate acceptable direct transfer angle.
    I say "fancy", its just (target soi radius/target altitude) *2 :p

    Untested for bodies outside Kerbin though. Should be close at least. Needs testing.

     
  • Stäphen Goedzal

    This is a long standing problem caused by the phasing burn not being executed perfecly accurately. Nor should it be. That's why they do "Trajectory Correction Maneuvres" IRL. And why tcm.ks in obtlib exists.

    Errors in the first burn cause exponential errors in the following nodes..
    It turns out we can't chain nodes like intercept.ks does. it needs to be split into something like "phasefor.ks", and the resulting transfer.

    tcm.ks (if we get it fixed) could potentially handle the final transfer. I see little need for a dedicated transfer.ks.

     
  • Stäphen Goedzal

    It's also possibly caused by the orbit change after the phasing burn. Due to underflow (I guess) this puts the time to burn off by quite a bit. The easiest solution is still to split it up.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.