You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What feature or change would you like to see made?
Implement support for stack segmentation, enabling segmentation directly within stack viewports instead of converting to volume viewports
Leverage the stack segmentation capabilities already available in Cornerstone 3D
Extend stack segmentation support to various image types, such as ultrasound, MG, DX, and CR
Research and design the interaction between segmentation and other viewports (e.g., displaying segmentation on PET when segmented on CT)
Consider adding a control or button in the viewport "More" menu to toggle the display of segmentation across different viewports
Why should we prioritize this feature?
Stack segmentation is a crucial feature for efficient and accurate segmentation workflows, particularly for modalities like ultrasound and other 2D image types. By prioritizing this feature, OHIF will enable users to perform segmentation directly within stack viewports, eliminating the need for conversions and providing a more intuitive and streamlined experience.
Designing the interaction between segmentation and other viewports will ensure a cohesive and consistent experience across different data types and modalities.
The text was updated successfully, but these errors were encountered:
What feature or change would you like to see made?
Why should we prioritize this feature?
Stack segmentation is a crucial feature for efficient and accurate segmentation workflows, particularly for modalities like ultrasound and other 2D image types. By prioritizing this feature, OHIF will enable users to perform segmentation directly within stack viewports, eliminating the need for conversions and providing a more intuitive and streamlined experience.
Designing the interaction between segmentation and other viewports will ensure a cohesive and consistent experience across different data types and modalities.
The text was updated successfully, but these errors were encountered: