Skip to content
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

Remove spikeextractors dependency #196

Merged
merged 9 commits into from
Aug 22, 2022
Merged

Conversation

CodyCBakerPhD
Copy link
Member

ROIExtractors does not test or make use of any of the methods inherited from the BaseExtractor imported from the legacy spikeextractors. This removes it from the minimal installation and base ImagingExtractor.

@CodyCBakerPhD CodyCBakerPhD self-assigned this Aug 20, 2022
@codecov
Copy link

codecov bot commented Aug 20, 2022

Codecov Report

Merging #196 (00d666d) into master (3f08c50) will decrease coverage by 0.74%.
The diff coverage is 39.39%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #196      +/-   ##
==========================================
- Coverage   73.25%   72.51%   -0.75%     
==========================================
  Files          33       33              
  Lines        2176     2190      +14     
==========================================
- Hits         1594     1588       -6     
- Misses        582      602      +20     
Flag Coverage Δ
unittests 72.51% <39.39%> (-0.75%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/roiextractors/example_datasets/toy_example.py 6.94% <0.00%> (-1.39%) ⬇️
src/roiextractors/extraction_tools.py 61.76% <13.63%> (-5.36%) ⬇️
src/roiextractors/imagingextractor.py 81.11% <100.00%> (-0.21%) ⬇️
src/roiextractors/segmentationextractor.py 87.36% <100.00%> (-0.52%) ⬇️

Copy link
Collaborator

@h-mayorquin h-mayorquin left a 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 and a move the right direction.

Are we still using the decorator for video arguments somewhere? The casting code that you added is related to it but I am not sure that decorator is needed anymore.

@CodyCBakerPhD
Copy link
Member Author

Are we still using the decorator for video arguments somewhere? The casting code that you added is related to it but I am not sure that decorator is needed anymore.

No, we got permission a while back to do away with those completely.

But the casting function I had to port over was something inherited from spikeextractors for some extraction tool function, I didn't looks too deep into it but some time we should really review that module and see what we can do away with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants