vtkMRMLModelDisplayNode (00000267D9D32A80): SetSliceIntersectionVisibility method is deprecated, please use SetVisibility2D instead

Support
1

Call for help

I use must-segmentator to create a VOI segmentation in liver, I got the warning message like this

[VTK] Warning: In vtkMRMLDisplayNode.cxx, line 996

[VTK] vtkMRMLModelDisplayNode (00000267D9D32A80): SetSliceIntersectionVisibility method is deprecated, please use SetVisibility2D instead

[Qt] int __cdecl qSlicerSubjectHierarchySegmentsPlugin::getDisplayVisibility(__int64) const : No display node for segmentation

[Qt] int __cdecl qSlicerSubjectHierarchySegmentsPlugin::getDisplayVisibility(__int64) const : No display node for segmentation

[Qt] int __cdecl qSlicerSubjectHierarchySegmentsPlugin::getDisplayVisibility(__int64) const : No display node for segmentation

[Qt] int __cdecl qSlicerSubjectHierarchySegmentsPlugin::getDisplayVisibility(__int64) const : No display node for segmentation

[VTK] Warning: In vtkMRMLSegmentationNode.h, line 228

[VTK] vtkMRMLSegmentationNode (00000267D0BEA100): vtkSegmentation::SetMasterRepresentationToClosedSurface() method is deprecated, please use SetSourceRepresentationToClosedSurface method instead

however, I got a sphere segmentation, but it can not be found in further calculation

How could I solve this problem? thank you all.

2

The first warning is probably the one that has been fixed very recently: BUG: Fix deprecated function calls by cpinter · Pull Request #36 · SlicerIGT/SlicerMarkupsToModel · GitHub

The ones to follow are from the segments plugin, maybe getting the visibility by the SH model is premature, but these are just warnings and have no effect on anything, so I haven’t considered it a priority.

The last error may come from your side as various functions have been deprecated (the word “master” was replaced with “source” in function names to make it more inclusive), but most of the usages have been updated as well. Again, no chance of indicating actual error.

3

thank you~

just as you said, it is a different problem, this warning has nothing to do with the result.