qurit / qurit/rt-utils

add roi to existing structure set

Open
#52 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
256
Forks
75
PR merge metrics
No merged PRs in 30d

Description

Hi all,

I have two CTs and two structure sets (generated in TPS). I am trying to copy some rois from structutSet1 to structurSet2. The patient is the same, and most of the setting (same CT type, place where CT was taken, ...) just the acquisition date and time differs.

It seems that the append worked, so no error appear and a roi with "name" is added to structurSet2. But when I display the newly added roi, it is just a point and not the structure it should show. It does not matter, which roi I copy, it is always the same point at the same coordinates.

RoiInRTStruct1and2

When I copy the rois from structutSet1 to a new structure set, everything works fine.

Do you have any idea, why this is not working? I also tried to copy a roi from structurSet2 to structurSet2 with a new name. The name is added to structurSet2, but the roi is again a point at the same coordinates, as shown in the image above.

Thanks a lot for your help! Its a great tool by the way

Cheers,
Nadja

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Reproduce copying an ROI between the two existing RTStructs, including copying from a structure set to itself, and compare the resulting geometry with the source ROI. Done means the copied ROI retains its full structure rather than becoming a point.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.