Operating system: windows
Slicer version: 4.11.20200930
Hello,
In my project I use the VMTK plug in for segmentation. When creating the centerline I wonder if there is a possibility to export the data concerning the diameter and the distance as well as their coordinates at the same time. I explain with VMTK we can have either a table of the centerline concerning the diameters according to the distance or another table with the coordinates of some points of this centerline, but the two tables are not of the same dimension and so we canât just add them to have all the information. is there another way to generate directly a table with all the information (x, y, z, diameter, distance)
Which module gives you the point coordinates of a centerline ? Is it a centerline model or a centerline curve ? The distance from the start of the centerline is available in âCenterline metricsâ module. Is it the module youâre referencing ? You title hints at âVesselness Filteringâ module : can you precise your request ?
Thank you for your feedback, yes indeed the module CENTERLINE METRICS gives me distances and diameters, and the center line curve gives me the coordinates of the points. My question is to know if there is a way to have all this information in a single file.
I thought of exporting both types of information but the problem is that for a given centerline the dimensions of the two information tables are not the same.
The RAS coordinates can be added to the table provided by âCenterline metricsâ, as in the picture below.
If thatâs what you expect, Iâll send a pull request to update the âCenterline metricsâ module.
Please note that this module can work with centerline models created by the âExtract centerlineâ module only. These models have an associated âRadiusâ array, that is actually used by âCenterline metricsâ. The latter module cannot work with centerline curves produced by âExtract centerlineâ because these do not have an associated âRadiusâ array for each constituting point. Besides, a markups curve can be modified in the UI, which would require recomputing all metrics. This computation is done in âExtract centerlineâ, and is quite a tough procedure.
Unfortunately, the pull request didnât gain interest. If you can apply patches to a file, Iâll send you the corresponding patch. You could then update your local copy of Centerlinemetrics.py.
Thank you for your contributions! The interest is absolutely there, but we need to juggle with many things and very hard to respond to all requests in as quickly as they would deserve.
Next time if you donât get a timely response then the best is to add a comment every 2-3 days. You can also @mention the name of the people that you think could help.
This feature has been merged in the repository, please update your SlicerVMTK extension.
However, choosing between âCumulativeâ and âProjectedâ distance will generate a runtime error. A new pull request in awaiting attention. Everything else is OK.
