I relied on Mechjeb too much in my game, so I did a run using KRPC and built my own autopilot features with it. It was a lot of fun, and I would recommend it.
I thought it would be nice to have actual mission planning in game for things like complex maneuvers, orbital slingshots, Lagrange point orbits, and the like.
Then launch countdowns, maps, exact timed burns that you'd still have to do manually but you could seemingly do so much more.
Or maybe this kind of thing already exists with mods.
Mechjeb does a lot of automation for complex maneuvers like planetary transfers, ascent autopilot, target interception, etc..
You can even do a porkchop plot for interplanetary transfer.
but lagrange points are not possible in KSP because of the Sphere of Influence Model.
and orbital slingshots are not included, I assume because they require an intense bruteforce calculation.
Aha ok! Ambition reignited, it's not that it's trivial but it's very possible to simulate these things and there are plenty of valid shortcuts. The "BMW" astrodynamics books I learned a large chunk of it from was published in 1971. "Sphere of influence" is a lot more "things you have to do with pen and paper" than things you're forced to do with modern computers.
EDIT: This was caused by using an old version uv (0.7.3) updating with `uv self update` to the latest version (0.11.2) resolved it. Original message below:
While the first form seems to work with `pyproject.toml`, it seems like the second form in the global `uv.toml` only accepts actual dates and not relative times. Trying to put a relative time (either in the form "7 days" or "P7D") results in a failed to parse error.
My understanding is they used to be fairly strict about using a set for 2 weeks before changing, but research has shown very little difference in outcomes down to 1 week.
There is some discomfort/soreness for the first few days after switching. My dentist's instructions were to wear each for at least a week and then switch to the next set whenever I wanted after that. Basically at whatever rate I was comfortable/could tolerate. I'm now at set 15 and have switched most of them after a week while a few I delayed a couple of days because I had something happening where I didn't want to worry about any discomfort.
Just to avoid confusion, while SMB as used above may be referring to the owner it typically means "Small and/or Medium Business". Where what counts as small and medium varies a bit but is generally <500 employees and annual revenue <$10 million.
Now we get to guess if it's broken in the same way as gpt, or did it pick up that pattern from all the cases of people posting it on the internet. (In the second case, that's not a good look for their data cleanup process)
I so miss bazaar's UI around merges/commits/branches. I feel like most of the push for squashing is a result of people trying to work around git's poor UI here.
The 650 main memory was a drum; but what IBM called Random Access Memory (and RAM) for this machine was a hard drive. As described in the Manual of Operation linked above. Here are a few quotes:
"Records in the IBM Random Access Memory Unit are stored on the faces of magnetic disks."
"The stored data in the Random Access Memory Unit are read and written by access arms."
"The IBM 355 RAM units provide extemely large storage capacity for data... Up to four RAM units can be attached to the 650 to provide 24,000,000 digits of RAM storage."
The main memory on the other hand:
"The 20,000 digits of storage, arranges as 2000 words of memory on the magnetic drum..."
1. https://ksp-kos.github.io/KOS_DOC/ 2. https://krpc.github.io/krpc/