-
Notifications
You must be signed in to change notification settings - Fork 38
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
Removal of Redundant Features in Libraries #minor #322
Conversation
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #322 +/- ##
==========================================
+ Coverage 53.59% 58.93% +5.34%
==========================================
Files 30 29 -1
Lines 8426 7625 -801
Branches 3677 3135 -542
==========================================
- Hits 4516 4494 -22
+ Misses 1264 575 -689
+ Partials 2646 2556 -90
☔ View full report in Codecov by Sentry. |
Shouldn't we wait until we have E features merged from LibV7 before removing them? |
tests/test_basic.py
Outdated
@@ -1435,8 +1435,8 @@ def test_spikecount_stimint1(): | |||
spikecount_stimint + 2) | |||
|
|||
|
|||
def test_spikecount_libv4peakindices(): | |||
"""basic: Test Spikecount in combination with LibV4 peak_indices""" | |||
def test_spikecount_libv5peakindices(): |
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.
Shouldn't we just remove this test altogether with the DependencyV5_LibV4peakindices.txt file?
It is testing features that are no longer present.
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.
Yes you're right. Initially I thought this test is different and it adds more value however it is using the same data and retrieving the same result as in test_peak_indices
.
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.
Ok I deleted that and added another test for setDependencyFileLocation
since we need a test for checking the case when setDependencyFileLocation
works.
Good point. Since there were also no tests for the E features I removed them in the PR but we can wait actually. Shall I revert that single commit? |
Yes, let's revert that commit, and wait for LibV7 features to remove them |
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.
Great! Looks good to me!
Alright merging... 🚀 |
Removal of Redundant Features in Libraries
Context:
This PR removes unused or untested features from active maintenance, aiming to cut down on the number of features we have to maintain and to make sure the ones we do keep are consistent in dealing with missing values, exceptions, and other edge cases that are currently compromising our scientific results.
It addresses the ongoing work documented in Issue #321.
Modifications:
LibV4
has a single function calledpeak_indices
.LibV5
already has an improved version of it.depolarized_base
in LibV3:LibV1::peak_indices
is removed, as theLibV5
implementation is in use.LibV2::E6-E40
protocols are neither utilised nor tested; the membrane systems team uses theLibV7
implementation.LibV1::spike_width1
is discarded, asLibV5::spike_half_width
is in use.LibV1::rest_voltage_value
is removed, asLibV5::voltage_base
is in use.LibV1::min_AHP_values
is removed asLibV5::min_AHP_values
is in use.LibV1::AHP_depth_abs
is removed, asLibV5::AHP_depth_abs
is in use.LibV1::min_AHP_indices
is removed, asLibV5::min_AHP_indices
is in use.Note:
While these features and functions are removed from active maintenance, it's important to note that their implementations remain accessible within the version control system, preserving the ability to revisit or reactivate them in future developments.