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

Add joint smoothing option to labelmap to surface conversion #4604

Open
slicerbot opened this issue Mar 13, 2020 · 4 comments
Open

Add joint smoothing option to labelmap to surface conversion #4604

slicerbot opened this issue Mar 13, 2020 · 4 comments
Assignees
Labels
Priority: Medium Issues that we plan to fix but there are available workarounds Type: Enhancement Improvement to functionality
Milestone

Comments

@slicerbot
Copy link
Collaborator

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.

@slicerbot slicerbot added this to the Slicer 4.11.0 milestone Mar 13, 2020
@lassoan lassoan added Priority: Medium Issues that we plan to fix but there are available workarounds Type: Enhancement Improvement to functionality labels Mar 26, 2020
@lassoan lassoan modified the milestones: Slicer 4.11.0, Backlog Mar 26, 2020
@lassoan
Copy link
Contributor

lassoan commented Mar 26, 2020

Since we now support shared labelmaps, it could be easier to develop this feature, but the design might be still quite complicated.

@lassoan
Copy link
Contributor

lassoan commented Mar 28, 2021

@Sunderlandkyl do I remember correctly that you have implemented this?

@Sunderlandkyl
Copy link
Member

Not sure, I'll check and see.

@lassoan
Copy link
Contributor

lassoan commented Dec 12, 2023

The option seems to be implemented but when enabled then no surface is visible in 3D and nothing is visible in slice views (if the closed surface representation is chosen to be displayed in slice views).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium Issues that we plan to fix but there are available workarounds Type: Enhancement Improvement to functionality
Development

No branches or pull requests

3 participants