-
Notifications
You must be signed in to change notification settings - Fork 4
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
Use this repository from 3D Slicer #2
Comments
Does this also entail incorporating the "vtkPlanarContourToClosedSurfaceConversionRule" and "vtkPlanarContourToRibbonModelConversionRule" (from https://github.com/SlicerRt/SlicerRT/blob/master/DicomRtImportExport/ConversionRules/) into PolySeg? |
It could, but this ticket is about making PolySeg an external module instead of just a sub-directory within the 3D Slicer source code. We keep those converters (especially the ribbon related ones) in SlicerRT, because they only apply to RT scenarios, and so far PolySeg was only available within Slicer. |
That said it's very easy to add it for your own purposes. Just add the files to your branch working copy, add them in the CMakeLists.txt as well, register them where the others are registered and you're done. |
@cpinter Thank you. I managed to compile "vtkPlanarContourToClosedSurfaceConversionRule" into my working branch of PolySeg. Just to make sure. Below is what I did - does this look correct to you?
The other two ribbon-related conversion rules depend on "vtkSlicerRtCommon.h" and various Slicer MRML libraries further down the dependency line, so I didn't get them complied into PolySeg. (Fortunately, for my purpose, I only needed the Contour --> ClosedSurface conversion.) I see why those conversions rules have been allocated to the SlicerRT repo, as a way of making sure PolySeg only has very simple dependency requirements. |
Yes, this seems right to me.
|
Currently this library as used from within Slicer (https://github.com/Slicer/Slicer/tree/master/Libs/vtkSegmentationCore), which is a duplication. It would be better to have only one repository to ease maintenance and facilitate dissemination. Considering that this library does not depend on Slicer, and can potentially be used in other projects, it should be this one.
The text was updated successfully, but these errors were encountered: