alexmoon/ksp

Kerbal Space Program Mission Plotter

ksp's Issues

Not validating or parsing dates

(Using the website)

I'm trying to calculate transfer windows for a kerbal trapped in orbit around the sun (spawned by a contract). I've got all the orbit info from the save's persistent.sfs, apart from time of periapsis passage. No matter what I enter in the "time of periapsis passage" field, it gets reset to 1/1 0:00:NaN (you can see this if you click save, then close and reopen the edit orbit form).

Looking at celestialbodyform.coffee, it seems the form should be validating the date, but no error is shown no matter what I put there. "foo bar baz" gives no error, for example.

NAN values diplayed

First I would like to thank you for this awesome tool ! I always use this for all my KSP interplanetary missions.

I seem to have found a bug. When I input these variables:
https://alexmoon.github.io/ksp/#/Dres/70000/Kerbin/71/false/optimal/false/13/100

the following values display NaN:

1. Ejection angle
2. Ejection inclination
3. Prograde dV *
4. Normal dV
5. Heading

• Note: an ejection dV is given at 1668m/s

This has never happened to me before, though you might want to know.

Best Wishes
Ernst Smit
E-mail: [email protected]

Custom body/vessel coded for 'longitude of periapsis' while entry field is 'argument of periapsis'.

As in the title, the correct transfer windows are calculated by entering the longitude of periapsis in this field.

Putting your code to good use

First of all I wanted to say this tool is great!

Secondly, I know the code is under the CC BY-SA-NC license and is free to use, but I usually like letting people know when I use their excellent code. Since I didn't know any coffeescript/javascript/jquery/bootstrap/etc before now, I blatantly copied utilized your repo for the beginnings of a RemoteTech2 Network Planner. (You can zoom in and out with the mousewheel, and timewarp with the normal KSP keys).

Incorrect delta-v bounds on colormap

For certain results, the delta-v transfer plot colormap is mostly blue, and according to the scale the red color should correspond to some very large delta-v that doesn't appear on the map.
For example, Kerbin 100km -> Duna 100km from year 1 day 1, mid-course plane change. The delta-v scale is from 1668 m/s (blue) to 765060 m/s (red). But the highest delta-v visible on the plot is around 20000 m/s

The UT conversion mouseover for maneuver dates is wrong.

When I enter the UT date shown in the mouseover into the maneuver editor, the maneuver date set in game is one year plus one day plus one hour earlier than the date shown in the planner.

May I use your orbit class as a library?

Because holy wow, that is some of the most elegant Coffee I've seen. 👍

Tools as webservice

Hi,

I'm working on a Staging Generator ( tell me what and where you want to go, I propose staging assembly to go there) http://s2l.drdamlab.net

I would like if it's will be possible to request your launch window Planner as a webservice which return transfer details ?

Thanks

DrDam

Update for new versions?

I don't know if something has changed in Kerbal universe or it's a bug somewhere in the code, but not all transfer windows are accurate.

Example: Kerbin to Moho, year 2. It calculates optimal launch to day 87, however Moho's orbital position is way off, instead of -215 degrees it's like 5, therefore no encounter (see screens).

Clicking on plot area does not change launch window parameters

Using Mozilla Firefox 31 and Windows 8.1. Using the Launch Window Planner normally, but clicking in the plot area per instructions "Click on any point on this plot to see full details of the selected transfer." does not change any of the details. In other words, the plot is fixed at the lowest delta value and the user cannot select other areas in the plot. I've used this planner before on a different computer (Mozilla, Windows 7) and recall that it worked fine.

It does not calculate for custom orbit

As I understand, I can customize my current orbit in Edit Orbit / Vessel.
I choose:
Origin: Mun
[Vessel]

• Semi-Major: 272.566 km
• Eccentricity: 0.036
• Inclination 101.19
• Longitude: 79.43
• Argument PE: 210
• Time: 1/52 5:38:00 (as I understand, it's time when I'll be in Periapsis)

Destination: Minmus
Checked "No insertion..."
Earliest departure: y1 d52, Ballistic

Click on "Plot it" and nothing happens. On image Departure days have 51 and White graph. There is no dV.
Also when First time "Time of periapsis passage" is blank and clicking Save, Red border and Caption are shown, after entering values still shows border and do not save.

[Suggestion] Ability to calculate a transfer angle bigger than 360°

Since if you would be able to launch at an ascending or descending node but will not encounter the target planet right away, but on the second or third time around you would you can save quite some fuel from not having to change your inclination.

Real Solar System support

Could you add an option for real solar system? I guess anyone can add custom bodies in the calculator as a workaround, but they won't be saved for the future.
I see it as a simple dropdown Kerbol/Sol that loads pre-configured parameters.

I also wonder if there is such a calculator online for actual real solar system, could not find one with a cursory search. If you know of one maybe add a link to the page?

Intermittently not using "date format" selection

It appears the calculator is sometimes not obeying the date selection when toggled to Earth time, the issue is intermittent though and I've only been able to produce the problem once (and switching it back and forth fixed it).

For some screenshots of examples, see discussion here: http://www.reddit.com/28qd0i

Request for license exception to lambert solver

I'm working on a comprehensive maneuver planning library written in kOS. Since I borrow a tiny bit of code from MechJeb, I'm using its (GPLv3) license as well. (Arguably the tiny bit of code I'm using is a small math function which may not qualify for copyright protection by itself, but I'm trying to avoid that issue for the time being -- permission is always better even if not strictly required).

I've recently started working on adding intercepts and transfers to my library, and I've adapted someone else's kOS adaptation of your Lambert solver code for that purpose. However, your code (and theirs by extension) is licensed CC-BY-NC-SA, making it incompatible with GPLv3.

A look through the commit history shows you as the sole author of the Lambert solver; there are other contributors but none that have affected the code in question. Thus, given my understanding of copyright law, you may alter the license/relicense/dual-license it however you choose.

Would you be willing to dual-license the current version of lambert.js/lambert.coffee to also allow GPLv3 usage? (I'll also need to get permission from the author of the kOS port, but their permission is meaningless without yours). My own code will maintain attribution and such, but under GPLv3 I can't ensure that forks continue to do so.

Need a version that uses a 6-hour day

With Trigger Au's decision to switch the Kerbal Alarm Clock to a 6 hour day, 425 day year format, it's added an inconvenience to use this great tool. Now we're forced to manually convert between Kerbal time and Earth time to use this tool and the Alarm Clock in conjunction. It'd be great if you could add a switch to allow us to select between the 24 hour or 6 hour format.

Date wrapping around year 76?

My KSP date is now in year 74, and the otherwise excellent launch window calculator seems to break down. Somewhere around the year 76 the days since epoch seems to wrap, and it starts first to count the day axis in descending order, and further away into the future the graph becomes a mess and it suggests launch dates in year 5 and similar.

Suggestion: Calendar view

First: Thank you for your effort with the KSP, very nice looking and useful site.

I had an idea that I am just not a good enough coder to implement myself: A Calendar view.

Use the calculations you have to determine the dark blue zones on the transfer points, then check each day for which celestial bodies are dark blue.

Since this stuff doesn't really change from game run to game run, you could pre-calculate about 10 years of Kerbal time fairly quickly, I think.

Add colorblind support

At the moment, the plot is hardcoded to use green-red colors, make them toggleable to use grayscale instead, this makes the tool useful to more people

I can't select a destination or plot a graph when I add a custom vessel orbit.

Hi Alex, I am looking forward to using your planner for a tour mission trip that will meet up with my (first!) fuel and mining station that is waiting for a good window to Minmus. ----BEGIN Walloftext-- However, I have a peculiar orbit (somehow the lander overshot on surface escape and I decided to make the orbiter catch up instead of "cheating" fuel to get back to an orbit I already covered), which is 10x120 roughly and oriented with the large end of SMA toward Kerbin. Minmus is in a very difficult position, almost directly in line with the PA. I calculate there are about 1353 m/s absolute max. including the lander's fuel, with none left for Vernor RCS, but I digress. Technically it should be enough to get to Kerbin SOI edge and Minmus, but I would rather meet with the station first.
--END Walloftext--

After copying my orbital data (thank goodness I have a mod now) into an added "Vessel" origin body, the "Destination" option is blocked and clicking "Plot" does nothing. In other words, something broke and I don't know how to get around it or find the info I need without my peculiar orbit data.

Its not working anymore :'(

As seen in the title, the window calculator isn't working anymore. I am not too sure why, but I believe its because the time format of KSP changed from 24 hours a day, to 6 hours a day. I hope you can fix it!

Launch dates do not adhere to Kerbolar calendar

1. Love the simplicity of this thing.

I noticed however that your proposed launch dates adhere to a 365-day year. The Kerbolar year however has 426 days (see also http://wiki.kerbalspaceprogram.com/wiki/Calendar).

Steps to reproduce: Transfer somewhere between Y1, Day 366 and Y1 Day 367 yields maneuver date on Y2, Day 1.

Don't know if this affects your calculations but one might overshoot the actual departure date with this information.