2025.08.19 Weekly Meeting

Community Weekly meetings
1

This morning, we will be having our next weekly hangout at 10:00 AM ET until 11:00 AM ET.

Anyone is welcome to join at this link: https://bit.ly/slicer-googlemeet-hosted-by-kitware

Agenda:

  • Release status
  • Outstanding pull requests

Please post to this thread to put a topic on the agenda! We will try to prioritize agenda items during the meeting.

Thanks
Sam and J-Christophe

2

Meeting Notes

Slicer-trame

VTK Python Packaging Limitation
The current VTK Python package on PyPI is monolithic and does not support the installation of additional VTK-based modules (e.g., vtk-addons, vtk-webcore) that could extend the vtk namespace. This limits modular packaging and downstream development, such as that needed for slicer-trame.

Next Steps
@Thibault_Pelletier will investigate how to restructure the VTK packaging infrastructure to support namespace extension, in a way similar to how the trame namespace is currently extended.

Relevant Resources

DICOM Anonymization

Overview
The team discussed various tools for DICOM anonymization, especially in the context of IDC workflows and hospital data sharing.

Feedback from @lassoan

  • KitwareMedical/dicom-anonymizer was tested but lacks support for advanced features, such as:

    • Preserving specific private tags (issue #96)

  • Instead, PyDICOM’s built-in anonymization tools were used.

  • The most advanced tool identified was DCIA, which includes ~1000 rules tailored for private tag handling.

Feedback from @pieper

  • There’s a need to anonymize DICOM consistently across multiple series (e.g., keeping the same anonymized birthdate).
  • Steve developed a JavaScript-based tool using DCMJS and dicom-curate, especially useful in contexts where software installation is not feasible.

Additional Resource

ViewNode & RenderWindow in the Context of SegmentEditor Refactoring

Background
The discussion centered on improving the Segment Editor’s integration with the rendering system without depending on the Qt layer.

Key Points

  • Discussed PR #8604, which addresses cleaner access to rendering components via the MRML scene.

  • It was agreed that:

    • A dedicated displayable manager for the Segment Editor should be added.
    • Rendering-specific properties (e.g., vtkRenderer) should not be stored directly in view nodes.

Planned Enhancements

  • Introduce a new helper method:
    vtkMRMLApplicationLogic::GetViewDisplayableManagerByClassName()

Relevant Usage Examples

Markup Integration

  • Plan to refactor the Scissors effect to use Closed Curve Markups.
  • Effects should be able to query which view nodes are currently mapped in the layout to determine relevant display contexts.