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
First of all, you did an impressive work on this package!
I simply wanted to ask if there was a specific reason behind building the contour sequence around the MediaStorageSOPInstanceUID.
If not, adding an optional argument in order to switch between MediaStorageSOPInstanceUID and SOPInstanceUID could maybe be useful for users.
To give you additional context, here is small change I had to do in order to be able to add a new contour to an existing RTSTRUCT file with respect to the original structure.
Hi @smichi23 thank you for your kind words and for going ahead and making a pull request! I will take a deeper look at it all by Friday and hopefully get it pushed in :)
Hi,
First of all, you did an impressive work on this package!
I simply wanted to ask if there was a specific reason behind building the contour sequence around the MediaStorageSOPInstanceUID.
If not, adding an optional argument in order to switch between MediaStorageSOPInstanceUID and SOPInstanceUID could maybe be useful for users.
To give you additional context, here is small change I had to do in order to be able to add a new contour to an existing RTSTRUCT file with respect to the original structure.
In ds_helper.py
def create_contour_image_sequence(series_data) -> Sequence:
contour_image_sequence = Sequence()
became
def create_contour_image_sequence(series_data) -> Sequence:
contour_image_sequence = Sequence()
Thank you again for this amazing work!
The text was updated successfully, but these errors were encountered: