Add script and CSV for plotting benchmarking results #82
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
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.
This PR adds a hacky script that can be used to plot the benchmarking results from the waveform_suite_summary_file generated by #57 .
It also adds metadata for the waveforms from the suite that we ran benchmarking of the formats against. The plotting script uses some of this metadata to create scatter plots.
The plotting script should be cleaned up if it is going to continue to be used. I wanted to add it here as a record of the code used to create the plots shown in recent meetings (including the 20240613 meeting where the working group made the suggestion to go with WFDB as the base format for waveforms in CHoRUS).