2024.12.10 Weekly Meeting

Community Weekly meetings
1

Tomorrow, we will be having our next weekly hangout at 11:00 AM ET until 12:00 PM ET, AFTER the Project Week Prep Call. We will be reusing the same link from the Project Week call.

Anyone is welcome to join at this link: Launch Meeting - Zoom

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

2

A check-in regarding Slicer stable 5.8.0 would probably be good. Maybe go over things in the 5.7 development milestone again? I looked back and saw that the last minor version bump (5.6.0) was released November 26th 2023, so it has been over a year now.

I assume we may want to wrap up the following PR about extensions tiers (it is not currently in the development milestone) because we have begun accepting more Tier 1 extensions into the Slicer extensions index.

1 Like
3

Meeting Notes

Extension Contribution

  • Clarified confusion regarding the current contribution process for new extensions:
    • Although PR #7748 has not yet been integrated, contributors are already expected to provide extensions as .json files. As noted above by @jamesobutler, we will finalize the pull request as soon as possible.
  • Discussed supporting the installation of extensions directly from a GitHub URL (e.g., downloading a ZIP file) and outlined associated challenges.

nnUNet-Related Issues

  • See the related issue: acvl_utils Issue #4.
  • Crash on Import: The nnunetv2.inference module crashes with the error No module named 'blosc2' due to a buggy release of acvl_utils. See details in nnUNet Issue #2589.

Auto3DSeg

  • @pieper and @lassoan discussed the training process for the segresnet model.
  • @pieper will post identified issues to the extension repository based on his experience so far.

Curved Planar Reformation (CPR)

  • In the context of Slicer Issue #7179, work is underway to integrate capabilities from SlicerSandbox’s CPR implementation.
    • The current SlicerSandbox approach relies on the ResampleScalarVectorDWIVolume CLI.
    • We discussed adding an API to support registering “resampler” in the Slice logic class implemented in Libs/MRML/Logic.
    • Future Goals: Develop support for various use cases, including:
      • Data fitting in GPU memory.
      • Data fitting only in RAM.
      • Data that does not fit in memory.
    • Initial Focus: Register a resampler using the existing ResampleScalarVectorDWIVolume CLI.

SlicerSOFA

  • @RafaelPalomar rebased the branch jcfr/SlicerSOFA@improve-build-system, initially contributed via PR #22, and created a new pull request: PR #28.
    • The updated pull request further simplifies Boost integration, removing the need for a pre-built or installed Boost tree.
    • @jcfr will review and help finalize the build-system updates.