2025.07.15 Weekly Meeting

[Sam_Horvath (Sam Horvath (Kitware))]

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

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

---

Agenda:

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

[pieper (Steve Pieper (Isomics, Inc.))]

Can we do a big picture review of all the C++ style rules?

[Sam_Horvath (Sam Horvath (Kitware))]

Sure? Today might be a little diifciult, as I have a conflicting meeting.

Spolier alert for style rules: Most of our “rules” are part of the Qt Fusion style, we just swap the color palettes. So, most of the relevant style rules are not present anywhere in the code.

[Sam_Horvath (Sam Horvath (Kitware))]

Relevant file: Slicer/Base/QTGUI/qSlicerStyle.cxx at main · Slicer/Slicer · GitHub

Both dark and light palettes are defined here

Fusion style source: qfusionstyle.cpp source code [qtbase/src/widgets/styles/qfusionstyle.cpp] - Codebrowser

[pieper (Steve Pieper (Isomics, Inc.))]

I’d also like input on this issue: SampleData downloads broken in Mac 5.9 (urllib missing https) · Issue #8541 · Slicer/Slicer · GitHub

[jcfr (Jean Christophe Fillion Robin (Kitware))]

Meeting Notes

Welcome New Attendees

• Timon Schnauffer (@TSatMGB)
• Sara Razzaq

CTK Updates

• It is considered sensible to:

  • Add Q_PROPERTY declarations with a NOTIFY signal where appropriate.
  • Ensure all classes that inherit from QObject explicitly include the Q_OBJECT macro.

clang-format Integration

• As part of enforcing automatic style formatting, comments were added to preserve alignment and wrapping:

  • // comments and clang-format off/on markers were used to exclude specific regions from formatting.

• Relevant commits:

  • 2d10f6bd0: STYLE: Add // comments to preserve wrapping before clang-format integration
  • a06c4eb35: STYLE: Use clang-format off/on to preserve alignment and readability

OpenSSL & macOS

• SampleData download is currently broken in Slicer 5.9 on macOS due to missing https support in urllib.
• Tracking issue: #8541

Mean Skull Thickness from CT

• Timon Schnauffer (@TSatMGB) joined to discuss the use of the BoneThicknessMapping extension.
• Related discussion: Mean Skull Thickness from CT

Use of Slicer for Aorta Segmentation in Clinical Setting

• Sara Razzaq (Tufts Medical Center) plans to use Slicer for pre- and post-operative aorta segmentation.

• Tufts IT requires a security risk assessment contact.

• We clarified:

  • As an open-source project, Slicer does not have a formal point of contact for security forms.

  • Suggested referencing:

    • Slicer security policy
    • Commercial use partners
    • OpenSSF Scorecard

Segment Editor Refactoring for Web Integration

• @Thibault_Pelletier reported progress on refactoring SegmentEditorEffect logic:

  • Shifting logic from Qt to VTK, enabling easier integration in Trame-based (web) applications.

nnInteractive and Slicer

• @pieper spoke with the nnInteractive team:

  • Current models include training data licensed under non-commercial Creative Commons, restricting their use in commercial settings.
  • The maintainers are open to retraining with unrestricted datasets, but there is currently insufficient data available.

Using nnInteractive to Refine TotalSegmentator Output

• @pieper tested whether nnInteractive can be used to refine rough or low-resolution TotalSegmentator segmentations.

• Feedback from Fabian Isensee (lead author of nnInteractive) was positive, though this use case hadn’t been formally tested.

• Results:

  • Left: Native TotalSegmentator output at 1.5mm resolution (from input with 3.75mm slice spacing).
  • Right: After upsampling the labelmap and refining using nnInteractive, improved results were obtained by selecting a segment and adding just one point.