Christian timetagger refactoring #6
Merged
+3,462
−1,107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes several improvements to the timetagger handling and Terascan logic to improve stability and enable persistent automated scans:
Timetagger Queue Redesign
The timetagger no longer drops counts. It now uses a continuously running queue, which buffers incoming events. The GUI scrapes this queue whenever it updates, decoupling GUI refresh rate from timetagger data acquisition. This implementation has been tested by Arya over a two-week period and appears stable.
Persistent Scan Logic in
terascan_logic
The
terascan_logic
module now supports persistent scanning. It continually checks whether a scan should be running and ensures the scan resumes as needed until completion. The module remains locked during scanning and only unlocks once it is confident the scan has finished successfully.Separation of Logic and GUI in Terascan
Refactored
terascan_logic
andterascan_logic_gui
to allow automated scans to be triggered purely throughterascan_logic
, without GUI interaction. This avoids crashes when modifying scan behavior from code and makes the logic module safe for headless operation.