Devlog 4 - UI Overhaul, Resilient Data Importing, and OpenRocket Export Compatibility!

Overview

I’ve spent more time improving FlightScope’s usability and flexibility, focusing on a cleaner code structure, a more resilient data importing pipeline, and compatibility with OpenRocket simulation exports.

What’s New

• Refactored the backend by separating dashboard, database, and data importing logic into dedicated modules.
• Improved the CSV upload flow to handle more file formats and clean incoming telemetry automatically.
• Added compatibility with OpenRocket CSV exports, including automatic unit detection and conversion for feet, meters, and Gs.
• Added safeguards to flight event detection to make analysis more reliable.
• Created a GitHub README! Go check it out, it’s linked at the bottom of the devlog :)

Challenges

Getting OpenRocket compatibility working was more difficult than expected due to differences in column names, units, and CSV formatting. I redesigned the import pipeline to standardize telemetry data before it reaches the database, making FlightScope much more flexible.

Next Steps

• Continue refining the FlightScope UI and overall user experience.
• Add support for more telemetry formats.
• Expand flight analysis and visualization tools.
• Make an online demo for you all to try out! (I could have written another 3 devlogs just about my challenges with this… we will save it for next time.)

FlightScope is now fully documented on GitHub:
https://github.com/zombieking1555/FlightScope

devlog 4 in the bag, now that’s some type stuff. And check this demo:

Devlog 3 - Flight Simulation Overhaul, Data Trimming, and Flight Event Detection!

Overview

Spent more time improving FlightScope’s flight data pipeline, with a focus on making the test flights more realistic, trimming extra idle data, and detecting key flight events more reliably.

What’s New

• Reworked the flight simulator to generate more realistic telemetry, including pre-launch idle, boost, coast, parachute descent, and post-landing idle.
• Added acceleration support throughout the database and telemetry pipeline.
• Implemented automatic detection and annotation for launch, burnout, apogee, parachute deployment, and landing.
• Trimmed pre-launch and post-landing idle data so plots focus on the active flight window.
• Regenerated test flights with updated simulation parameters.

Challenges

Getting event detection to work reliably took some tuning, especially with noisy acceleration data. Landing detection also needed a little extra care so the plots would stop cleanly at touchdown instead of including a lot of extra idle data.

Next Steps

• Tune detection thresholds more easily from the UI.
• Add tests for the event detection logic.
• Continue improving the database and telemetry handling.

FlightScope is really coming along! I’m excited to see where this project takes me until the next devlog.

Devlog 2 - Database Initialization, Dashboard Pages, and More!

Overview

Spent more time developing FlightScope, focusing on improving the local flight database structure and making smaller quality-of-life changes to keep the app scalable and easier to maintain.

What’s New

• Added automatic database initialization so flights.db is created locally instead of being stored in GitHub.
• Added a Database Manager page to view, manage, and delete individual flight records after upload.
• Refactored several backend functions to improve consistency and prepare the app for future features.

Challenges

Removing flights.db from GitHub was more challenging than expected (thanks, .gitignore). This led to the creation of create_db.py, which removes the dependency on a tracked database file and allows FlightScope to generate a local database automatically on startup.

Next Steps

• Expand the FlightScope dashboard with richer flight analysis and visualization tools.
• Support additional CSV data fields for more detailed and comprehensive flight reviews.

It’s been real, see you next devlog.

Devlog 1 - Streamlit uploader + SQLite storage + basic flight plotting

Overview

Added a Streamlit app that lets me upload flight CSVs, stores telemetry in a local SQLite database, and plots Altitude vs Time. I also added a small test data script that generates synthetic 200 Hz flight logs so I can quickly test the interface without real rocket data.

What’s new

• Streamlit CSV uploader for flight data
• SQLite database for storing flight metadata and telemetry
• Altitude vs Time interactive plot using Plotly
• Synthetic flight generator (test_data_writer) producing 200 Hz test flights

Data pipeline

• Upload CSV → validate → parse numeric values
• Store flight metadata in flights table
• Store time-series data in telemetry table
• Query SQLite → render plots in Streamlit

Challenges / friction

• CSV validation required enforcing numeric types for altitude and velocity
• Handled missing or invalid data during import
• Added duplicate filename detection to prevent overwriting flights
• Admin “Clear Database” flow required Streamlit session_state + rerun handling due to UI reset behavior

Design decisions

• Chose SQLite + pandas for simplicity and local-only operation
• Avoided external database dependencies to keep setup lightweight
• Kept CSV import as the ingestion layer for flexibility
• Added synthetic test data generator to speed up UI development and debugging

Next Steps

• Improve the upload UX (showing row counts and import status)
• Add per-flight summary stats
• Allowing CSV export from the database.

Having a lot of fun with this project, see you in the next devlog!

First devlog for a project I’m working on - likely last for this project.
I wanted to create this project to learn the flow of creating and shipping for the Stardance challenge. Almost everything I did here was entirely new to me: coding in JS, using API keys and tokens, and SSHing to host my bot on Nest. Luckily, I was able to figure out how to have my coding time properly logged to have enough to devlog. My 37 minutes reflect the time I spent tidying the project for shipment, not the 2 and a half hours spent figuring out how to parse a command into API parameters. This Slack bot was a lot of fun, looking forward to devlogging again on my next project.