Is your roadmap more "Satsearch for broader range of spacecraft mass classes" or "generate initial mission and spacecraft architecture from simple input parameters"?
Thanks! The goal is for it to be primarily an architecture tool, although right now it leans more towards SatSearch as I think that will get eyes faster and because there needs to be a decently robust component library for the architecture tools to work. The idea is that you can set your primary mission parameters and CONOPs, and then to get immediate feedback on spacecraft performance metrics as you trade/change hardware in the Master Equipment List. Maybe the best way to think of it is as "PCPartPicker for spacecraft".
For example if you add/change a radio transmitter, you can see in real-time how that changes your system mass, power, and link margins, or be alerted if your flight computer doesn't support your radio's data interface.
This (hopefully) lets a spacecraft systems engineer iterate through trades more quickly, track performance and margin evolution over a program lifecycle, or quickly develop a baseline for a given mission class.
Definitely quite a bit of work to go to get there but feel free to create an account and poke around and break things.
Is your roadmap more "Satsearch for broader range of spacecraft mass classes" or "generate initial mission and spacecraft architecture from simple input parameters"?