-
Notifications
You must be signed in to change notification settings - Fork 57
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
RTStruct FrameOfReferenceUID is not matching with the reference CT #29
Comments
Changing the first code block to the following made my code start working... code repo not updated at github... donno how... From
To
|
Hi Jinkoo, when we first created this library, we made the assumption that any ROI's added would be contained within a new FrameOfReferenceUID, not an existing one. I'm thinking as a fix, we could add another parameter to the RTStruct builder in order for users to input a their own frame of reference uid. Otherwise, it would just create a new one. What do you think? |
An ROI created based on an image would normally share the same FOR of the
base image. I modified the code already for my application, so I am good. I
am not quite familiar with Git, so I didn't publish it, but I believe I
made a post re: what & where I modified. Thank you.
…On Wed, Aug 25, 2021 at 11:03 PM Asim Shrestha ***@***.***> wrote:
Hi Jinkoo, when we first created this library, we made the assumption that
any ROI's added would be contained within a new FrameOfReferenceUID, not an
existing one. I'm thinking as a fix, we could add another parameter to the
RTStruct builder in order for users to input a their own frame of reference
uid. Otherwise, it would just create a new one. What do you think?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#29 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJP72GKZBBUP2QETBOJOSDT6WVHXANCNFSM5COQCGIQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
I'm writing to second the opinion of the OP. In our experience, when an RTSTRUCT is created it needs to be associated with a "parent" DICOM image set. It is customary, and multiple image viewing platforms rely on the convention, that the RTSTRUCT will have the same FrameOfReferenceUID as the parent DICOM series the contours are to be displayed over. |
This commit solved my problem, too. |
Thanks for the input folks! Will ensure this gets pushed in later today |
It sounds like a good alternative... Or, by default use the FOR of the
base image for the new ROI unless provided. Either way should be okay.
Thank you!
…On Wed, Aug 25, 2021 at 11:03 PM Asim Shrestha ***@***.***> wrote:
Hi Jinkoo, when we first created this library, we made the assumption that
any ROI's added would be contained within a new FrameOfReferenceUID, not an
existing one. I'm thinking as a fix, we could add another parameter to the
RTStruct builder in order for users to input a their own frame of reference
uid. Otherwise, it would just create a new one. What do you think?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#29 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJP72GKZBBUP2QETBOJOSDT6WVHXANCNFSM5COQCGIQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Hi my code is simple, like below. It runs fine, but I see the FrameOfRefernceUID in the output file (RS.new.dcm) is difference from the FrameOfRefceUID of the reference CT dicom series. So, I cannot import the RS file to my application. Is this a bug?... any suggestion would be greatly appreciated. Thanks! Jay.
The text was updated successfully, but these errors were encountered: