garycourt / korc Goto Github PK

Some engine parameters were changed, two new engines were added: http://wiki.kerbalspaceprogram.com/wiki/Parts#Propulsion

Currently it is only possible to define a minimum TWR for the whole rocket.

Sometimes (or maybe even most of the time), this is overkill and we only need a high TWR for launch (probably from Kerbin) and lower TWR for later phases (e.g. circularization burn, mun transfer, mun landing). For non-trivial missions this has the potential to significantly reduce engine mass (or increase efficiency) in upper stages (and transitively in lower stages and thereby total rocket mass).

I therefore suggest to allow the configuration of staged TWR constraints (where the staging does not necessarily correlate with the rocket staging). To keep the UI simple a plain text field could be provided where the staged TWR constraints are entered in a special syntax, e.g.:

4000:2.0 1.0

("TWR >= 2.0 for the first 4000m/s, TWR >= 1.0 for the remainder")

proposed ABNF (like in RFC 4234):

staged_TWR_constraint = *constraint default_constraint
constraint = dV_spec ":" simple_constraint
default_constraint = simple_constraint
dV_spec = FLOAT
simple_constraint = lower_bound
lower_bound = FLOAT

maybe, if you need an upper TWR limit, which I think that is rarely necessary:

simple_constraint = lower_bound ["-" upper_bound]
upper_bound = FLOAT

Ideally, I'd lie to be able to optimize to find the most delta-v for a given maximum mass / TWR / burn time / part count / cost. Currently the only way to do so is to optimize for mass and iterate minimum delta-v until you get something close to the maximum mass.

It would be nice to have more kinds of fuels than just LF+Ox: There's the Xenon engine&tanks in stock kerbal, plus Argon and Liquid Hydrogen on the Near Future mods.

Does this use a genetic algorithm? If not, how difficult would it be to implement one?

Based on the current code, it looks like you’re using a brute-force search, which, if I’m not mistaken, has been proven to be a massively inefficient (on the order of O(n!)) last-resort search...

5m parts were added: http://forum.kerbalspaceprogram.com/threads/51037-0-24-KW-Rocketry-v2-6b-Available-New-5m-Parts!-21-07-2014

Summary

A page feature to allow settings to be auto-saved. This may even open up the possibility to allow users to store multiple configurations to calculate from.

Description

When users play in Science or Career Mode, they often have to configure the Page Settings/Filter in order to display the correct parts, or in some instances need to an alternate configuration to match the environment/situation. Currently, whenever the page is (forced) reloaded or re-visited, everything is lost.

This may require further investigation, but after a bit of searching I came across this Page[1] which was working on a jQuery Cookie Issue[2]. The goal was fairly simple, and experimental, but it seems like they succeeded.

They wanted to Invert the Page colors by having users click 'Invert Colors' at the Top-Right. The Page then updates, and stores the setting via cookie. After that, users can navigate and/or re-open the Page with the same settings.

References

• [1] BP Local | BP - GitHub Pages
• [2] StackOverflow - Github Pages & jQuery Cookie; State Saved on Page Level Only

Ideally, I'd like to be able to optimize for mass with a maximum cost. You can do it the other way around (optimizing for cost with a maximum mass), but there's no way to optimize for mass with a maximum cost. That I know of, at least.

I forked this repo and added some extra content to it. I am editing kspcalc.js, but am having trouble finding a method to force the first stage to be a booster. Any ideas?

Some rockets suggested will include stages with twinboar/mammoth engines, followed by another stage. This is very difficult to build. If users were able to limit the quantity of a certain part that were allowed in a build, this could be made less of an issue.

Allowing limitations on quantities of specific parts could also reduce the number of possible combinations, and possibly allow for a faster optimized rocket.

It appears that the thrust numbers for parts like the Terrier are now too high (240+ vac thrust) instead of 60. These don't seem to match results from the game.

This calculator should really support:

• All the tanks (spaceplane parts, wings, etc.)
• The LV-N (and possibly other aero engines)
• Monopropellant engines & tanks

I downloaded the KORC repo and opened it as a local file. When I opened index.html I got a web worker error saying that my browser doesn't support it, when it works on github.io. Any solutions?

Hi, would it be possible to link automatically to the wiki for the stock parts?

The wiki should have an article for each stock part, so you can simply link to http://wiki.kerbalspaceprogram.com/wiki/%part name% if the part is a stock one.

When I'm using this calculator, I'm sometimes not sure about what part your calculator is talking about. And a simple link would usually work fine.

Fabian