Ascent
Active development · merged contributions
Ascent is rocket operations and telemetry software I'm contributing to through UT's Student Space Technology Association.
Why I'm interested in it
An operator dashboard has to make a physical system understandable. The interesting part for me is the connection between incoming data, what the interface shows, and the decisions an operator needs to make.
Current stage
A teammate had been developing Ascent for roughly a month before I joined. I'm still onboarding, but I've already contributed multiple merged pull requests. I'm preparing to take on a substantial development role as the project continues.
What I want to explore
- Presenting changing telemetry in a way that's easy to follow.
- Making data freshness, connection state, and faults understandable.
- Giving operators the context they need before interacting with the system.
These are areas I want to work on, rather than a list of features I've completed.
What's next
As I build, I'll add a dashboard walkthrough and explain a concrete engineering decision: the requirement, the constraints, the implementation, and how we checked its behavior.