I am very happy that you folks are showing interest but I am also terrified because this thing is definitely not ready for primetime, yet. The discerning astrodynamicist and/or rustacean will surely find things which are less than optimal or plain wrong.
I am also preparing for a trip so I won't be able to monitor this thread closely but I'll try to answer question wherever I can.
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!
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.
In hindsight, I guess it's the industry's fault for not pronouncing it "Tee Ell Eee Esses"...
EDIT: And I appreciate the explanation, personally! That's the best part of HN. To be clear to passers-by, a TLES is a string of characters that describes the orbit of a single satellite (artificial or otherwise) based on its position & momentum at some given start second. They have to be updated pretty frequently to account for gradual stochastic drift, which is both an interesting technical problem and a compelling philosophical metaphor.
The example code is helpful for seeing how it'd be used (might be cool to link to it from the README while the docs are still todo)
Tie into visual star navigation
I think the anime Cowboy Bebop has influenced my mind on what it could be like again fantasy but yeah. Mix of older looking hardware seems more tangible like this interface
You might try to Google belite because that sounds awesome, right? My dad told Mr he was selling the plane when he got it back from belite, but decided to fly it one last time.
The engine failed at like 1000' after takeoff and piledrove him into some poor bastard's farm a quarter mile from the airport. The fucking plane could not even glide.
Random ass people driving is bad enough. I have dozens of gigs of dashcam videos of all manner of insane, mad, evil, stupid, degenerate driver in my more recent 100,000 miles traveled in the US.
Yet. Or, as the good science communicators like to say, "as far as we know / as far as our current understanding goes". Looking back in history, almost everything we're taking for granted today was both dreamed by the pas era's "futurists" and deemed impossible by their skeptics. Only time (hah!) will tell, I guess.
https://link.springer.com/book/10.1007/978-3-319-74373-8
My hope that this plus Kerbal Space Program would transform my brain proved that I tend to ignore my limitations.
Great book, though.
Lox started as a vehicle for myself to learn Rust and at that point I did not feel comfortable contributing to an established code base.
Cool project though, I will definitely be playing around with this.
It's written in Rust so it's all about the language instead of the mission.
