# 2024.12.10 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2024-12-10-weekly-meeting/40596>\
**Category:** Weekly meetings\
**Created:** [December 9, 2024, 8:38pm UTC](https://discourse.slicer.org/t/2024-12-10-weekly-meeting/40596 "2024-12-09T20:38:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sam\_Horvath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sam_horvath/32/3092_2.png) [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)\
**Post date:** [December 9, 2024, 8:38pm UTC](https://discourse.slicer.org/t/2024-12-10-weekly-meeting/40596/1 "2024-12-09T20:38:17Z")

</div>

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](https://ntnu.zoom.us/j/94105383302?pwd=alVLSG1ITVhSUmpqVG9VMkMwOURrUT09)

* * *

> **Weekly Meeting**
>
> **Starts:** December 10, 2024, 11:00am (America/New\_York)\
> **Link:** <https://ntnu.zoom.us/j/94105383302?pwd=alVLSG1ITVhSUmpqVG9VMkMwOURrUT09>

**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

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [December 9, 2024, 11:09pm UTC](https://discourse.slicer.org/t/2024-12-10-weekly-meeting/40596/2 "2024-12-09T23:09:43Z")

</div>

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`](https://github.com/Slicer/Slicer/tree/v5.6.0)) was released November 26th 2023, so it has been over a year now.

> **[Slicer 5.7 Milestone · Slicer/Slicer](https://github.com/Slicer/Slicer/milestone/10)**
>
> Multi-platform, free open source software for visualization and image computing. - Slicer 5.7 Milestone · Slicer/Slicer

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.

> <https://github.com/Slicer/Slicer/pull/7748>
>
> Update Slicer to extension tiers described in https://discourse.slicer.org/t/int…roduction-of-tiers-for-slicer-extensions/34870
> 
> Summary:
> \* Add \`v1.0.1\` of extensions catalog entry schema (add \`tier\` optional metadata)
> \* Misc test fixes and stylistic changes
> \* Add extension tier support \_work-in-progress\_ :hourglass\_flowing\_sand: 
> 
> Next:
> \* \[\] Update https://github.com/girder/slicer\_package\_manager (server & client) to support \`tier\`
> \* https://github.com/girder/slicer\_package\_manager/pull/124
> \* \[\] Update frontend https://github.com/KitwareMedical/slicer-extensions-webapp to report the extension tier and allow filtering by tier
> \* \[\] Update Slicer extension manager to support showing tier 5 extension (hidden by default)
> \* \[\] Update https://github.com/Slicer/ExtensionsIndex/blob/main/.github/PULL\_REQUEST\_TEMPLATE.md based on tier
> \* \[\] Update Slicer extension documentation 
> \* \[\] Update \`.json\` files in extension index based on \`v1.0.1\` schema

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [December 10, 2024, 6:48pm UTC](https://discourse.slicer.org/t/2024-12-10-weekly-meeting/40596/3 "2024-12-10T18:48:27Z")

</div>

### Meeting Notes

#### Extension Contribution

- Clarified confusion regarding the current contribution process for new extensions:
  - Although [PR #7748](https://github.com/Slicer/Slicer/pull/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](https://github.com/MIC-DKFZ/acvl_utils/issues/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](https://github.com/MIC-DKFZ/nnUNet/issues/2589#issuecomment-2528974503).

#### 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](https://github.com/Slicer/Slicer/issues/7179), work is underway to integrate capabilities from [SlicerSandbox’s CPR implementation](https://github.com/PerkLab/SlicerSandbox#curved-planar-reformat).
  - 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](https://github.com/Slicer/SlicerSOFA/pull/22), and created a new pull request: [PR #28](https://github.com/Slicer/SlicerSOFA/pull/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.