I say objectively overkill because Euler was computationally faster, even though it took a few more steps.

Also, there’s a really wide range of h parameters that are tied for optimality. Taken together, this makes me think that it’s the lumpiness of the topography that’s the main limit here. But I’m in way over my head mathematically, so I could easily be misimplementing or misinterpreting.

Anyway, this is easily the silliest thing I’ve ever done with ground control points.

Should I finish a devlog about this even though it’s getting a bit out of hand and probably makes errors about the math I had to learn?

Okay, here we are: https://gist.github.com/celoyd/f163e6e582d87a50a6d37743e840dcb8

Posted while running out the door to carve pumpkins. There are probably a few TKs and such, and I didn’t spellcheck it. (Visual Studio Code doesn’t do that, apparently, at least on Ubuntu?)

@vruba so one thing about linear algebra is that (IMO) all programming languages represent it in an extremely fucked up way. I don’t know if I’d really understand it if I’d had to learn it using TensorFlow or some other library rather than on pencil and paper in 1998 the way God and Descartes intended it

@tim That seems fair. i was trying to do stuff in JS, a language that is uh not optimized for that, and it felt pretty uphill at times.

@vruba amazingly not built-in, but this spellcheck plugin is popular: https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker (but I use Vale)

@migurski It does run on touch devices! But there are bits I enjoy that only really come through with a big screen and a pointer.