alt Hacker NewsHey, this is really impressive stuff, talk about a dream job! Two quick questions if you find the time+interest:
1. What does "safe" imply? Type safety, maybe? Or just a general synonym for "few bugs/well tested"?
2. What kind of industry is this primarily envisioned for use in...? I have experience in the satellite industry (GRE and TT&C) but I was surprised to not see the usual buzzwords on this page, namely "TLEs". I get that it clearly does way more than terrestrial orbital work, but AFAIK that's, say, 99.9% of the current space industry.
In other words: is this library for ESA missions??? That would be rad as hell, if so.
also P.S. I love AI art compared to most, but I would def recommend carving out that cool crab and putting on a background of real stars. As you may or not be aware, many scientists have been a tad radicalized about AI, and AI art in particular -- would be a shame if that slowed adoption of a cool project!
Replies
1. Safe as in type-safe, memory-safe, and null-safe in contrast to the state of the art which is mostly C++, Java, and tons of ancient Fortran.
2. At the moment, we are using it for speeding up Python code for telecommunications constellation design.
I want to commission a real human artist to design a logo and header image in the future. The AI art is a nice placeholder.
P.S.: I wish this was my day job. I actually had to quit my job at a major aerospace contractor to be able to work on this project.
Ground Receiving Equipment, Telemetry, Tracking, & Control, and two line rlement sets. Apparently everything you need to predict orbits of a satellite are contained inside TLEs metadata and is considered a good way to share orbital information between disparate parties.