11–20 of 38 posts
https://www.reddit.com/r/spacex/comments/gigmfh/spacex_iss_d... does it in one line but it's kind of cheating.
I would like to see a real autopilot written in javascript that you can paste into the console.
https://www.reddit.com/r/spacex/comments/gigmfh/spacex_iss_d... does it in one line but it's kind of cheating.
Definitely cheating, it's not autopilot. It is just updating your co-ordinates every 500ms on a straight line. I would like to see a real autopilot written in javascript that you can paste into the console.
https://www.reddit.com/r/spacex/comments/gigmfh/spacex_iss_d... does it in one line but it's kind of cheating.
Definitely cheating, it's not autopilot. It is just updating your co-ordinates every 500ms on a straight line. I would like to see a real autopilot written in javascript that you can paste into the console.
[0]: https://gist.github.com/ForestKatsch/01069f29e8316df11774025...
I have a question about control flow of the overall system. Note that I haven't actually run this or debugged it. Or frankly, thought about it for more than a minute or two. Its more of an architectural question. So in dragon.clj there's a case statement to execute commands in the translate function such that the command to go down or left in an abstract calculated sense is implemented as hitting a virtual down or le…
Heh, never thought about it that way! But good question. Yes, it can translate on 2 axes at the same time, since the control loops for each axis run in separate threads, so there is no control locking. The same is with rotation - it can e.g. pitch, roll and yaw at the same time.
https://news.ycombinator.com/item?id=23172281
... and pull the appropriate Interstellar music up in a separate tab.
OK so yes the ISS docking sim is old news, but good lord do I love that UX. I really hope someone has modded it into Kerbal Space Program!
KSP was also 100% the reason I managed dock with the simulator on the first try, because in a way it was more like the 50th-100th try, just using a different interface.
Perhaps better would be to make pure functions to take current telemetry as an argument and return actions as outputs, perhaps all at once or more likely individually for each control. You could then capture all of this inside core.async go-loops to manage the control flow and timeouts, but you could also probably build something simple with one or more agents wrapping the current state and updating a set of commands to be executed later. Another argument for core.async would be to make it easier to funnel all commands into a single channel because I’m not entirely convinced a WebDriver is multithreaded, but perhaps the library manages that for you.
Anyway, cool stuff!