-
Notifications
You must be signed in to change notification settings - Fork 24
Open
Labels
featureNew feature or requestNew feature or request
Description
Description of task
Create a log panel in the GUI that displays key runtime events, system messages, and operator actions. The log should help with debugging, post-mission analysis, and real-time awareness.
What should be shown in the log?
| Category | Example Entries |
|---|---|
| System Events | GUI startup/shutdown, connection established/lost, recording started/stopped |
| Telemetry Alerts | Signal loss, overheating, leak detection, battery warnings |
| Operator Actions | Surface button pressed, kill switch activated, overlays toggled |
| Recording Events | Data stream recording started/stopped, file saved with timestamp |
| Error Messages | Backend exceptions, failed commands, missing data streams |
| Sensor Updates | New sensor connected, leak detection triggered, calibration complete |
| Integration Logs | Messages from other teams’ systems (e.g. leak detection module, ROS nodes) |
Suggested Workflow
- Create
QTextEditor custom widget for log display - Format log entries with timestamp and category
- Add function to append new log entries from backend or GUI actions
- Implement log filtering (e.g. show only errors or telemetry)
- Optionally allow export of log to file
Specifications
No response
Contacts
No response
Code Quality
- Every function in header files are documented (inputs/returns/exceptions)
- The project has automated tests that cover MOST of the functions and branches in functions (pytest/gtest)
- The code is documented on the wiki (provide link)
Metadata
Metadata
Assignees
Labels
featureNew feature or requestNew feature or request