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

[Feature Request] DICOM SEG export #3550

Closed
Tracked by #3491
sedghi opened this issue Jul 19, 2023 · 2 comments
Closed
Tracked by #3491

[Feature Request] DICOM SEG export #3550

sedghi opened this issue Jul 19, 2023 · 2 comments

Comments

@sedghi
Copy link
Member

sedghi commented Jul 19, 2023

What feature or change would you like to see made?

DICOM SEG is a standard for storing segmentation data in DICOM images. It is used to represent the boundaries of different structures in an image, such as organs or tumors.

In v2 we used dcmjs/adapters for exporting DICOM SEG data. However, this adapter only supported exporting SEG data for wadouri, and not wadors.

In v3, the loading of segmentation data is considerably slower than in v2. For example, the totalSegmenter case, which is a 400 MB full-body SEG, takes 1 minute to load in v3, but only 20 seconds to load in v2.

Why should we prioritize this feature?

Improved performance and adaptability

@fedorov
Copy link
Member

fedorov commented Jul 20, 2023

How is this related/different from #3523?

Also, the title says "DICOM SEG export", but the description talks about performance of import, not export.

@sedghi
Copy link
Member Author

sedghi commented Jul 20, 2023

It is for our own tracking purposes. the issue above talks above export too

In v2 we used dcmjs/adapters for exporting DICOM SEG data. However, this adapter only supported exporting SEG data for wadouri, and not wadors.

any how, yes it will be the export and import together.

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

No branches or pull requests

3 participants