-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix length error in sonify.time_frequency #374
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #374 +/- ##
==========================================
+ Coverage 88.31% 88.32% +0.01%
==========================================
Files 19 19
Lines 2875 2878 +3
==========================================
+ Hits 2539 2542 +3
Misses 336 336
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Test failure is unrelated, appears to be a resurgence of a heisenbug in bsseval on osx. 🤦 |
I added one more test here to cover the case where the input length is shorter than the provided input. Otherwise I think this is good to go. We shouldn't let the OSX failure block merging this PR. |
Lol, rerunning the tests passed this time with no changes. OSX is great. |
This PR fixes #371 by separating out the slicing logic for time_frequency generation.
I've unskipped the test that was previously failing and things seem good to go.