Skip to content

Support multiple segmentation groups as processing job inputs - #920

Open
PaulHax wants to merge 1 commit into
Kitware:mainfrom
PaulHax:all-segmentation-groups
Open

Support multiple segmentation groups as processing job inputs#920
PaulHax wants to merge 1 commit into
Kitware:mainfrom
PaulHax:all-segmentation-groups

Conversation

@PaulHax

@PaulHax PaulHax commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Distinguishes singular and plural labelmap inputs using the task spec's new multiple flag (sourced from the Slicer CLI XML multiple attribute):

  • A singular labelmap input binds the actively selected segmentation group, as before.
  • An input with multiple: true binds every segmentation group on the active dataset, serialized and staged one file per group (staged names stay unique when groups share a name).
  • Plurality is derived from the field that actually binds as labelmap after input-type resolution, so union-typed inputs (image/labelmap) can't silently demote a plural input.
  • Zero segmentation groups fails closed for required inputs; the Jobs UI describes singular inputs as the active segment group and plural inputs as all groups on the dataset.

Backend contract bumps to 0.2.0: multiple is an optional boolean on sourceRef parameters, documented in the generated schemas. Absent means singular, so existing backends are unaffected.

Distinguish singular and plural labelmap inputs via the task spec's new
multiple flag (sourced from the Slicer CLI XML multiple attribute):

- A singular labelmap input binds the actively selected segmentation
  group, as before.
- An input with multiple: true binds every segmentation group on the
  active dataset, serialized and staged one file per group; staged
  names stay unique when groups share a name.
- Plurality is derived from the field that actually binds as labelmap
  after input-type resolution, so union-typed inputs cannot silently
  demote a plural input.
- Zero segmentation groups fails closed for required inputs; the Jobs
  UI describes singular inputs as the active segment group and plural
  inputs as all groups on the dataset.

Bump the backend contract to 0.2.0: multiple is an optional boolean on
sourceRef parameters, documented in the generated schemas. Absent means
singular, so existing backends are unaffected.
@netlify

netlify Bot commented Aug 14, 2026

Copy link
Copy Markdown

Deploy Preview for volview-dev ready!

Name Link
🔨 Latest commit e41a649
🔍 Latest deploy log https://app.netlify.com/projects/volview-dev/deploys/6a7f899fef2a5b00070287a2
😎 Deploy Preview https://deploy-preview-920--volview-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant