Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3D Slicer integration of DL models #3

Open
3 of 10 tasks
che85 opened this issue Nov 17, 2021 · 1 comment
Open
3 of 10 tasks

3D Slicer integration of DL models #3

che85 opened this issue Nov 17, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@che85
Copy link
Member

che85 commented Nov 17, 2021

We are planning on integrating our DL models to be used with 3D Slicer

Dependencies

Functional Requirements

  • support multiple valve types:

    • tricuspid
    • mitral
    • cavc
    • others
  • support multiple user input variants (user decides/ system autodetects from available data):

    • mid-systolic frame + annulus
    • multiple cardiac cycle phases + annulus
    • mid-systolic frame + annulus + commissural landmarks
    • others

MONAILabel limitations (v0.2)

From my understanding, MONAILabel does currently not allow posting multiple user inputs images (multiple frames + labels).

image

All the inputs to our FCNs are voxel data with the same dimensions/origin/orientation. We could stack all that data (mid-systolic frame + annulus + APC + ASC + PSC) on the client-side and unstack and assign keys on the server-side and proceed with the pre-transforms as planned.

@che85 che85 added the enhancement New feature or request label Nov 17, 2021
@che85 che85 self-assigned this Nov 17, 2021
@che85 che85 changed the title 3D Slicer integration ( 3D Slicer integration of DL models Nov 17, 2021
@che85
Copy link
Member Author

che85 commented Dec 1, 2021

Just to confirm, we are able to use the current rest API for running inference by just stacking multiple user inputs into one 4D volume and sending it to the server.

I am currently working on integrating everything into 3D Slicer and need to preprocess the data to match the FCN required input volume dimensions etc.

All the above-shown use cases should be covered by stacking the user inputs into a 4D volume

che85 added a commit that referenced this issue Dec 14, 2021
…ng heart valves (issue #3)

- depends on SlicerHeart extension
che85 added a commit that referenced this issue Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant