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

Pull request to add in support for morphological operations #47

Closed
wants to merge 11 commits into from

Conversation

venkatesh20
Copy link

Hi,

I believe users would greatly benefit from performing morphological operations (erosion, dilation, opening, closing, morphological gradient, top_hat and black_hat) on medical images, and have added these in preprocessing.py. I have also added in opencv as a dependency in setup.py and requirements,txt.

All these have been edited under dltk/contrib. I would appreciate if you could take a look and merge it if you think it would help the DLTK platform.

@coveralls
Copy link

coveralls commented Aug 11, 2019

Coverage Status

Coverage remained the same at 9.62% when pulling 470ce30 on venkatesh20:master into f94d3bb on DLTK:master.

added in changes to elastic transform code to apply same changes to image-mask pair or different changes, based on random seed value provided by user. Also allowed processing an list of images rather than a single image, and returning the same processed list to the caller.
fixing indentation
fixing pep8 issues
fixing pesky w503 issues
@mrajchl
Copy link
Contributor

mrajchl commented Sep 3, 2019

Hi,
thanks for your PR. The main reason why we do not have these features, is because we would have to include opencv as a dependency, which adds a huge overhead. Secondly, opencv is optimised for 2D operations and these typically do not translate well into 3D. There are some operations available on SimpleITK e.g. sitk.BinaryMorphologicalClosing. Can you get the same functionality without adding opencv?

@venkatesh20
Copy link
Author

hi, thanks for your response. No worries, i can try to achieve the same functionality with SimpleITK without resorting to using opencv, for the reasons you mentioned above. i will close this PR. Could you also take a look at the other change i made to augmentation.py (for which i have commented under #31)? Thanks.

@venkatesh20 venkatesh20 closed this Sep 3, 2019
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.

None yet

3 participants