Closed yujanshrestha closed 6 years ago
Let's not sink too much time into getting a fully functioning development environment until we meeting with Nick and the team. Lets focus our efforts for this week on getting more familiar with the code + samseg paper so we can be as confident as possible for our assessment deliverable.
These matlab files need conversion to python:
These matlab runners need equivalent python or c++ runners:
kvlClear.h
kvlCreateImage.h
kvlCreateTransform.h
kvlEvaluateMeshPosition.h
kvlGetAlphasInMeshNodes.h
kvlGetCostAndGradientCalculator.h
'MutualInformation' 'Affine'
'AtlasMeshToIntensityImage' 'Sliding'*
kvlGetOptimizer.h
'L-BFGS'
kvlGetTransformMatrix.h
kvlRasterizeAtlasMesh.h
kvlReadMesh.h ???
kvlReadMeshCollection.h
kvlScaleMesh.h
kvlSetAlphasInMeshNodes.h
kvlSetMeshNodePositions.h
kvlSmoothImageBuffer.h
kvlSmoothMesh.h
kvlStepOptimizer.h
kvlWriteImage.h
These kvl functions may need wrapping to be called from python:
These ITK inclusions may need wrapping:
These VNL inclusions may need wrapping:
The overarching goal of this ticket is to gauge how easy it will be to work with the Matlab code and identify risky areas that could affect the assessment deliverable. A good way to do this is to read through and refactor the code for readability and testability.
Ideally the above should be done in order. First identify good splice points, then refactor.