Skip to content

Dicom Exporter#368

Merged
becker89 merged 6 commits intoe0404:devfrom
wahln:dev_dicomEnhancements
Sep 24, 2019
Merged

Dicom Exporter#368
becker89 merged 6 commits intoe0404:devfrom
wahln:dev_dicomEnhancements

Conversation

@wahln
Copy link
Copy Markdown
Contributor

@wahln wahln commented Aug 25, 2019

Rudimentary dicom export for CT, RTStruct & RTDose. Tested by reimporting exported TG119 + dose into CERR & MITK. Also adds differentiation between full / fraction / beam dose to the import.
May add RTPlan in the future if it makes sense.

@wahln wahln changed the title Dev dicom enhancements Dicom Exporter Aug 25, 2019
@markbangert
Copy link
Copy Markdown
Contributor

This is a nice addition! Is there anybody reviewing this? Did you also run simple consistency checks with matRad only, i.e., exporing with matRad and reimporting with matRad?

@wahln
Copy link
Copy Markdown
Contributor Author

wahln commented Sep 9, 2019

@becker89 wanted to look at it, I guess.. Reimporting in matRad again is the smallest issue, so far it worked with matRad, CERR and MITK. Would a RTPlan export make sense with our generic machines or not?

@markbangert
Copy link
Copy Markdown
Contributor

IMO a DICOM export for particle plans does not make sense. This should be driven by a clear usecase e.g. communication based on HIT basedata with Syngo or Raystation or a likewise scenario at a different institution. Do you have something like this in the pipeline at dkfz?

@wahln
Copy link
Copy Markdown
Contributor Author

wahln commented Sep 9, 2019

We thought a little bit of it... I would see a generic export more as a base code for other people to adapt to their machines.

@markbangert
Copy link
Copy Markdown
Contributor

anyway: @becker89 are you going to review this or should I look at it (might take a while)...

@becker89 becker89 self-assigned this Sep 9, 2019
@becker89
Copy link
Copy Markdown
Contributor

becker89 commented Sep 9, 2019

I will review the code on Thursday or Friday.

@markbangert
Copy link
Copy Markdown
Contributor

markbangert commented Sep 10, 2019 via email

becker89 and others added 2 commits September 23, 2019 16:33
* tested dicom export with Slicer RT (including RT dose)
* tested on Mac OS
*support of multiple contours of the same VOI on a single slice
@becker89
Copy link
Copy Markdown
Contributor

Tested the exported DICOM data with Slicer RT. The vt, cst and the dose cube was correctly exported from matRad and could be successfully imported to Slicer RT.

@becker89 becker89 merged commit bcd8041 into e0404:dev Sep 24, 2019
end


resultName = strcat(doseTypeHelper,'_',num2str(doseInstanceHelper),beamSuffix);
Copy link
Copy Markdown

@mingersming mingersming Oct 30, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the additional underscore mess up resultGUI in the end. You will find a 'resultGUI.physicalDose_' after import in your workspace. If you now try to recalc, you get an 'reference to a non existing field 'w_' ' error dialog.

Unbenannt

In my case this error occurs because of a missing InstanceNumber.
To keep the functionality one could edit '_',num2str(doseInstanceHelper) like beamSuffix in line 84-86 and add this to line 51 or we should accordingly edit the string concatenation/creation of resultGUI.w.

@mingersming mingersming mentioned this pull request Nov 14, 2019
acsevillam pushed a commit to acsevillam/matRad that referenced this pull request Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants