Sawmill: A CLI tool for exporting and trimming WPILib DataLogs #7656
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
component: wpiutil
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
While the existing DataLogTool can load multiple DataLogs from local and remote locations and export them as CSVs, that code is heavily tied to the GUI and so substantial code duplication would be inevitable.
Features
Usage
Converting a DataLog to a non-binary format
sawmill export json LOGFILE EXPORT-FILE [--mode <export-mode>]sawmill export csv LOGFILE EXPORT-FILE [--mode <export-mode>]LOGFILE is a valid path to a .wpilog file, and EXPORT-FILE is a valid path to a CSV or JSON file. All directories in EXPORT-FILE must exist, but the file itself will be created if it does not exist.
Extracting an entry
sawmill extract ENTRY LOGFILE EXPORTFILE [--format <export-format>]ENTRY is the case-sensitive name of an entry that exists in LOGFILE. --format must be either "json" or "csv" and defaults to CSV.
Trimming a DataLog
sawmill trim LOGFILE [ENTRY] --start <timestamp> --duration <duration> [--format <export-format>]sawmill trim LOGFILE [ENTRY] --start <timestamp> --end <timestamp> [--format <export-format>]TODO: