9 ms·
Lisp in Space
- tabtab 5y agoDave Bowman: "My God, it's full of parentheses!"
- spzb 5y agoCan’t help but read the title as “Lisp in spaaaace”. Too much muppets show in my youth obviously.
- lisper 5y agoThat's how I read it too! :-)
- AnimalMuppet 5y agoToo much Muppets Show? There is no such thing!
- fithisux 5y agoThere should be a lisp only curated list like lobste.rs
- jjtheblunt 5y agoreddit /r/lisp or similar?
- chuchana 5y agoSomething like planet.lisp.org?
- adamgordonbell 5y agoDoes anyone know how they now debug things in Space? If they are using compiled C programs it seems like it would be very hard to make changes. Is the key just to not need to make any changes? Or is this a case of Greenspun's tenth rule, where they've built REPL like functionality on-top of C?
- monocasa 5y agoThe cases I've seen deploy relatively full binaries, not patches. And they don't typically even have a REPL, as doing brain surgery on a satellite (that's already in a bad way if you're debugging something) is rarely the best option. So lots of telemetry logging, with 'feature flags' to turn on different logs. Then a change and code push once root cause is found, or a new build with new telemetry gathering if it's still not clear. I'm sure just about every model for code structure has someone doing it though.
- adamgordonbell 5y agoOk cool, I guess you can send enough data with earth satellites to resend a full binary.
- ncmncm 5y agoProbably the best "debugging in space" story is Don Eyles hacking the Apollo moon lander program that was in "core rope ROM" to work around a hardware failure on Apollo 14. It is findable online, but he published a book "Sunburst and Luminary" (Fort Point Press, 2019) about the whole process of getting the moon landing code ready in time to use, and the hack. As I understand it (I just got the book, haven't read it yet) the Apollo Guidance Computer, one each in the Command Module and the LEM, was programmed by Margaret Hamilton (inventor of Software Engineering as we know it today) with a real-time executive and interpreter emulating a saner machine, and Eyles coded the landing to the interpreter. Because it was interpreted code, it was patchable, and he came up with a patch on the fly that the astronauts punched into the AGC by hand, and saved the mission. Margaret Hamilton's real-time executive itself saved the day when Apollo 11 crew left some extra stuff turned on, by accident, that the system had not been tested with and that burned excess CPU cycles during the landing. When it trapped a scheduling failure, it checkpointed important state and was able to resume the important tasks where they left off. That happened several times during the landing.
- oumua_don17 5y ago>> And unfortunately at the time, I was not very skilled at playing politics and so I was a little bit more blunt about this than I should have been If you were to handle it today, how would you do it differently? Any advice to an engineer to learn the art of selling more powerful tech against a lesser one when the latter is more popular?
- sharedptr 5y agoIs CL being used in new projects these days?
- trenchgun 5y agoCouple of recent projects which I am aware of: A browser: https://nyxt.atlas.engineer/ https://nyxt.atlas.engineer/ An editor: https://github.com/lem-project/lem https://github.com/lem-project/lem A window manager: https://github.com/stumpwm/stumpwm https://github.com/stumpwm/stumpwm A GUI framework: https://github.com/rabbibotton/clog https://github.com/rabbibotton/clog A compiler for quantum computing: https://github.com/quil-lang/quilc https://github.com/quil-lang/quilc APL embedded in Common Lisp: https://github.com/phantomics/april https://github.com/phantomics/april More projects can be found at: https://www.libhunt.com/topic/common-lisp https://www.libhunt.com/topic/common-lisp
- sgt 5y agoI listened to this last night in bed and went to sleep dreaming of LISP REPL's in space. Quite an enjoyable podcast, thank you.
- adamgordonbell 5y agoRon's story about working on the Mars Rover prototypes is mind-blowing to me. He used DSL's written in LISP and compiled to run on embedded devices and did self-driving tech all back in the 80s. Also, debugging software running 150 million miles away is something I'm sad yet relieved I'll never get to do. Also the photos he dug up and scanned are neat to see.
- lisper 5y agoRon Garret here. AMA.
- jrumbut 5y agoI'm sorry to say I know little about you or the subject (so I apologize if either answer is obvious or addressed elsewhere) however since you're here: What would you like to see NASA do differently? What do you think of Racket (the programming language)?
- lisper 5y agoGood questions. I have been away from NASA for almost 20 years now so I can't really say what I think they should do differently because I don't really know what they are currently doing. A lot can change in 20 years, and I'm sure a lot has, but I'm no longer in the loop so I can't really say anything constructive about this. I've never used Racket but from what I can tell it's a fine system. I'm partial to Common Lisp myself, never really resonated as much with Scheme, though I do admire the elegance of the language. But if it works for you, go for it.
- costigan 5y agoI think lisp is still used in various nooks and crannies of NASA. As a small example, I was the payload software engineer for the LCROSS mission (a robotic mission in 2009 that demonstrated there was water ice near the moon's south pole). The software that ran on the payload computer was in C, but there was a very simple, ad hoc scripting language provided by the company that provided that payload computer. Because this language was very simple, I wrote a higher-level DSL and a simulator of the computer in common lisp and then wrote all of the instrument command sequences in that DSL. Lisp's simple, flexible syntax and macros made it easy to express patterns of commanding and timing for this. What the commands did is described in the last (topmost) blog entry here: https://blogs.nasa.gov/lcrossfdblog/ https://blogs.nasa.gov/lcrossfdblog/ . These days, I'm working on the VIPER rover, and the commanding approach for it is very manual, as Ron described. VIPER will be a moon rover, so the turn-a-round time for commanding is much shorter than it would be for a MARS rover, and teleoperation from Earth is a very reasonable and lower-risk solution than autonomy. Still, some of the systems used in self-driving vehicles today to evaluate the environment around the vehicle will be used by VIPER, but to provide advice and situational awareness for the drivers. No lisp involved.