farkos VS kOS-scripts

An example of the self contained state machine can be found in my warp controller library. An example of the task list method can be seen in my GUI docking script.

As to my profiler this would be the code for it. The script is mostly built for profiling non-branching code as the fundamental methodology is that if kOS only allows CONFIG:IPU instructions per tick and a tick is 0.02s more or less simply run the functions for CONFIG:IPU times and divide the time taken by 0.02 and subtract the loop overhead and you get a decent guess as to the number of instructions.

Because of these issues I have with WARPTO() I ended up writing my own time warp controller which is slightly more involved to use but simple enough. The basic use to warp to say AP would be something like this in code.

Also there is the issue of wildly differing complexity between given tasks and what level of precision a person is going to try to achieve. For instance a maneuver node execution script is one of the simpler scripts you can do in kOS but a "simple" hohmann transfer based rendezvous script (my 13 step outline of such a script) requires orders of magnitude more effort particularly if the person is unfamiliar with a lot of the required concepts, vectors and orbital equations mostly. Or a launch script can be a simple gravity turn%20Flamedout/filtered_engine_list_example.ks) with just a touch of vis-viva for insertion or it can be a complex affair of physics, trig, and vectors to try to spend as little fuel as possible during ascent and yet still only function in a vacuum.

The full code of the integrator I use can be found here. A video where I go over the theory of operation of the landing script and a deorbit script can be found here not the most efficient scripts but I am happy enough with them.