Add DICOM attribute `RTROIInterpretedType` as optional parameter to `add_roi` and `ROIData`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 256
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
RTROIInterpretedType stores information about the type of the contoured volume. Possible values can be found here: https://dicom.innolitics.com/ciods/rt-structure-set/rt-roi-observations/30060080/300600a4
One should be able to pass this parameter to add_roi so that the desired type of ROI can be passed to ds_helper.create_rtroi_observation(roi_data) within add_roi.
(follow-up issue to #70: after that, the RTStructMerger maybe could be changed to the usage of add_roi instead of just appending ROIContourSequence, StructureSetROISequence, RTROIObservationsSequence from one RTStructure to the other one)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the add_roi and ROIData definitions, then trace how add_roi passes data to ds_helper.create_rtroi_observation(roi_data). Check the existing RTROI observation handling and the RTStructMerger follow-up context. Done means the optional RTROIInterpretedType value can be passed through add_roi and ROIData into the created observation without changing existing calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100