I did not found any tool for 3D object thickness measurement in ITK…
So I used a composition of ITKBinaryThinning3D and EuclideanDistance to compute the distance from medial axis to the outside as the object thickness. the ultimate goal is to retro-propagate the medial axis thickness to adjacent voxels, but hey walk before you run
I’m trying to build an ITK composite filter with that could wrap in a single instruction such behavior
I started a module : ITKThickness3D but how to point another “remote” module in its project cmake conf ?
Since ITK 5 requires C++11, we cannot provide a Python 2 wheel on Windows because binary compatibility with the Python 2 distribution requires Visual Studio 2008.
I created a pull request to work around this issue, but I will continue to investigate. There may be interaction with the remote modules and their use in the build. Would you like to submit ITKBinaryThinning3D as a remote module in ITK? This means adding a file to ITK/Modules/Remote similar to the other files there by submitting a pull request. The community would also benefit from improved awareness and access to your module.
Sure I would, I’ll look into it since I never did such thing … (might disturb you again through the process ).
Maybe I should work a bit on the itk::LocalThicknessImageFilter3D<TInputImage, TOutputImage> prior to remote module ?
if you have a starting point / doc / example(s) for such contributions …
should I do it also for ITKBinaryThinning3D since it does not appear in the list (however published in the Insight Journal) ? (or merge both modules…)
If I read correctly the documentation I should submit an IJ paper prior to the remote module. But then I might wait a bit longer to add the LocalThicknessImageFilter3D…
For ITKBInaryThinning3D, It could be directed to the original since I only provided the wrapping.
Also all the remote modules listed are hosted inside github.com/InsightSoftwareConsortium. I have no problem transfering the repo to kitware, but how does this work for maintenance (e.g. build/deploy new wheels as for ITKBoneMorphometry not available for python 3.7)?
Since there is already an IJ article for the thinning filter, you might not need to do a lot of work to adjust the current repo to the model. You could go through the steps described in the module template, examine the differences with the current repo and apply them.
My concern is more about the maintenance of the pull request on ITK including the remote.cmake file.
Should I do point to my own T4mmi repo or should I transfer it to InsightSoftwareConsortium ?
In the second case who will maintain PyPI up-to-date ?
Is it better to decompose a module in separate filters (i.e. one for thinning, one for medial thickness, one for local thickness transform) or group them (got second thoughts using someone else implementation in a module with my name on it) ?
The module template has been updated over time. So some update of modules created some time ago might be needed.
It is better to transfer the repositories. After transferring the repo to InsightSoftwareConsortium, we will give you write permissions on it (in case you don’t retain them). And you will be the maintainer of that repo. Its address will have changed and more people will have write access, but that should be it. So you should maintain PyPI up to date.
I think it is better to group the filters - that’s what modules are for. Especially given there is some overhead for each module.