-
Notifications
You must be signed in to change notification settings - Fork 149
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
Eliminate legacy interface and obsolete large_data option #755
Conversation
e043801
to
83a4b9b
Compare
Codecov Report
@@ Coverage Diff @@
## main #755 +/- ##
==========================================
- Coverage 97.14% 93.01% -4.13%
==========================================
Files 42 41 -1
Lines 7941 7387 -554
==========================================
- Hits 7714 6871 -843
- Misses 227 516 +289
... and 12 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
9917860
to
6908e95
Compare
6908e95
to
5f876b3
Compare
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.
Looking good! Just some questions. :)
2fc764e
to
05b70a8
Compare
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.
LGTM! 👍
One comment: I wonder whether for the changelog, there should be a more substantial message that this is a breaking change in the next major stingray version?
05b70a8
to
524d846
Compare
Good point. I now marked the change as breaking in the |
Those interfaces were already largely discouraged. The large_data infrastructure was incomplete and buggy, while the legacy interface was very slow.
This PR is in preparation of our next major release, where we can afford breaking some minor things. It eliminates these two mechanisms, making the code lighter and avoiding confusion in users.
While doing this, I had to also revise a little the mechanism of
save_all
, that needed the legacy interface and allowed to load all the sub-periodograms of the averaged periodogram in memory. It was used also from _create_matrix in DynamicalPowerspectrum. The result is not bad, because to do this we are basically avoiding creating a bunch ofAveragedPowerspectrum
object for each sub spectrum.