2025.08.05 Weekly Meeting

Community Weekly meetings
1

Tomorrow, 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:

  • Next release (proposal)
    • Identify outstanding issues & move remaining ones into a new milestone called 5.11
      • Qt6 & Icon refresh for Slicer 6.0
    • Release as version 5.10
    • Agree on schedule

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

I can’t attend, but want to point out to this (i it is not resolved by then):

3

I would like to review this error in the build of SlicerSOFA in connection with the new Linux build system: SlicerPreview - Build Summary

Build command:

/usr/bin/cmake --build . --config "Release"; /usr/bin/cmake --build . --config "Release" --target "packageupload"

Error:

Error: could not load cache

I can’t reproduce this error when building locally with the dockbuild script and the extensions index.

4

Meeting Notes

Welcome New Attendees

  • Ekaterina Golubeva

    • Research topic: Aneurysm segmentation
    • Interested in visualizing multiple scenes
    • Exploring options such as VMTK for vascular modeling

vtk-sdk-python-distributions

  • Integration is in progress and expected to be finalized later today.

Next Slicer Release

  • Moving forward with Slicer 5.10
  • Issues from milestone 5.9 are being re-assigned to a new 5.11 milestone
  • Target date is end of August
  • Outstanding issues
    • Address issue preventing from launching Slicer on macOS (see details below)
    • Investigate symbol loading issues on Linux (see details below)
    • Build Qt 5.15.17 from source on all platform (see details below)

Qt6 Integration & Release

  • The Qt6-based release will be deferred until after the Slicer 5.10 release is complete.

Symbol Loading Issues on Linux

  • Investigating GSSAPI symbol conflicts involving libtirpc on modern Linux systems (e.g., Ubuntu 25.04).
    See #8626 for the top-level tracking issue.

  • The issue arises when Slicer is launched and libtirpc.so.3 attempts to resolve versioned GSSAPI symbols that are missing from Slicer’s bundled stub (libgssapi_krb5.so), resulting in an error such as:

    undefined symbol: GSS_C_NT_USER_NAME, version gssapi_krb5_2_MIT

  • The stubbed GSSAPI library was originally introduced to avoid OpenSSL version conflicts between the system GSSAPI and Slicer’s internally built OpenSSL.
    See PR #8598 for background.

  • Current efforts are focused on:

    • Identifying what introduces the libtirpc dependency (e.g., Qt, ITK, Python, or transitive system libraries). See #8626
    • Evaluating whether the krb5-gssapi-stub should be improved or removed
    • Avoiding the need for developers or users to build Qt from source unless absolutely necessary

  • Related discussion: See this post by @Davide_Punzo

  • Documentation update:
    A new section will be added to the Linux build instructions covering known issues and workarounds specific to Ubuntu 25.04.
    See #8627

Qt5 Version Update from 5.15.2 to 5.15.17

To help address issues such as #8579, we are considering building Qt 5.15.17 from source on all platforms used to generate official Slicer Preview packages.

This effort is tracked in #8624.

Issue running Slicer on macOS due to Python issues

  • Discussed issue #8618. Waiting this is addressed, this script allows to start Slicer on macOS.

Reusing Endoscopy Module for Colonoscopy

  • @mau_igna_06 is investigating adapting the Endoscopy module for colonoscopy applications.

  • Recent updates to the module (see PR #6502) support:

    • Arbitrary camera poses
    • Key frame interpolation

Limitations:

  • Does not currently integrate with the Sequences module
  • May not be the ideal path forward for colonoscopy workflows

Alternative: Consider the Animator module from the SlicerMorph extension.

SlicerSandbox & SlicerSurfaceToolbox Contributions

@mau_igna_06 submitted the following contributions:

Segment Editor Effects Refactoring

Extension Build Issues

5

Basically the use-case I’m exploring is:

  1. Segment colon on a pre-op CT and create corresponding 3D models
  2. Load saved video from colonoscopy as a sequence
  3. Be able to explore the lumen of the colon 3D model creating keyframes for the 3D view camera while the colonoscopy sequence is playing.
  4. After enough keyframes are created, use vtkCameraInterpolator to save the camera proxyNode inside a sequenceNode that will go to the same sequenceBrowserNode as the endoscopic video.
  5. If the above works well, check if the same workflow could be used with live endoscopic video

And I’m adding a demo video for this PR today