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

Only a single frame is supported when the source image has no Frame of Reference UID. #284

Open
efimfurman opened this issue May 14, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@efimfurman
Copy link

I am trying to create a segmentation on a multiframe ultrasound image.
I am getting a failure: Only a single frame is supported when the source image has no Frame of Reference UID.

It seems to be a valid multiframe image - is there a workaround, or perhaps it's something that will be fixed int he future?

@efimfurman
Copy link
Author

I was following the second example here: https://highdicom.readthedocs.io/en/stable/usage.html

@CPBridge
Copy link
Collaborator

Hi @efimfurman thanks for your question.

The issue here is not whether the ultrasound image is valid, it's whether it has a frame of reference UID (which basically means whether it exists within a defined 3D frame of reference coordinate system like most MRI or CT images do).

This is related to the fact that we need to choose some indexing scheme to index the frames of the new segmentation image in the multiframe functional groups related attributes. Unfortunately this is extremely flexible and rather complicated and it is not really feasible to support all possibilities and as such so far, we have only implemented some of the common cases (single frame images without a frame of reference such as x-rays, 3D images indexing spatially such as CT and MRI, tiled images indexed by x and y offsets, such as whole slide images).

Why is your ultrasound image multiframe? Is it a video? In which case, using time as the index is likely to make the most sense. If this is the case, then this is on our list as the next indexing scheme to implement, as others have asked for it in the past. Unfortunately I can't tell you when I'll get around to this though

@CPBridge CPBridge added the enhancement New feature or request label May 15, 2024
@CPBridge CPBridge self-assigned this May 15, 2024
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

2 participants