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
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?
The text was updated successfully, but these errors were encountered:
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
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?
The text was updated successfully, but these errors were encountered: