wahln
commented
4 years ago I think the first message just means that we could not uniquely identify the dose cube that belongs to the pln via dicom uids. It may be that we miss some uid relation here, but usually this should not cause issues during the following import. The pln error is more difficult. When you import a plan via the GUI, the function matRad_importDicom is called. When an RTPlan is selected, this function will try to recreate the steering information of the plan. To do so it needs the base data for the machine. If you select the proton_Generic machine, the import will have wrong machine information as a reference (not the energies etc that you have in your machine etc) and crash. I guess that this behavior is not wanted in some cases. You can work around this error by commenting out the following lines in matRad_importDicom.m:
%% import stf
if isfield(files,'rtplan')
if ~(cellfun(@isempty,files.rtplan(1,:)))
if (strcmp(pln.radiationMode,'protons') || strcmp(pln.radiationMode,'carbon'))
%% import steering file
% pln output because bixelWidth is determined via the stf
[stf, pln] = matRad_importDicomSteeringParticles(ct, pln, files.rtplan);
elseif strcmp(pln.radiationMode, 'photons') && isfield(pln.propStf,'collimation')
% return correct angles in pln
[stf, pln] = matRad_importDicomSteeringPhotons(pln);
else
warning('No support for DICOM import of steering information for this modality.');
end
end
endI hope that this points you in the right direction, my experience with our dicom import for full-fledged proton plans is limited. What I can say is that in general, our GUI only models a very limited part of possible treatment planning workflows (GUIs are extremely resource-intensive to maintain).
bterracino
better0123
yjq111![https://r2.res.outlook.com/owa/prem/images/folder_16x16.png]pt14](https://r2.res.outlook.com/owa/prem/images/folder_16x16.png]pt14){kind=link}
I have a CT series, RT plan RT structure and RT dose file all of which are DICOM format.
When using DICOM import, I get a message "no RT dose file directly associated to plan file. showing all rt dose files." This happens when I have the RT plan file selected. This is followed by a message "Import steering information from DICOM plan. Choose corresponding matured base data for procedure." I selected the proton_generic.mat file for this. After this, the import does not continue and I get the errors below.
If I try to import with the RT dose file highlighted instead of the RT plan, I get the same errors.
=================================================================== importing ct-cube... creating info...Progress: 100.00 % reading slices...Progress: 100.00 %
z-coordinates taken from ImagePositionPatient
Interpolating CT cube...finished!
conversion of ct-Cube to Hounsfield units...finished!
Reading structures...Warning: Contour Breast is empty
Error in matRad_importDicomSteeringParticles (line 86) if sum(currContrSeq.ScanSpotMetersetWeights) == 0
Error in matRad_importDicom (line 115) [stf, pln] = matRad_importDicomSteeringParticles(ct, pln, files.rtplan);
Error in matRad_importDicomGUI>import_button_Callback (line 330) matRad_importDicom(files, dicomMetaBool);
Error in gui_mainfcn (line 95) feval(varargin{:});
Error in matRad_importDicomGUI (line 53) [varargout{1:nargout}] = gui_mainfcn(gui_State, varargin{:});
Error in matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)matRad_importDicomGUI('import_button_Callback',hObject,eventdata,guidata(hObject)) Error while evaluating UIControl Callback.
If I do DICOM import with the patient ID selected, it does not ask me about the steering info and successfully reads in the images and structures however the RT plan information such as gantry angle, couch angle etc. is not read in. Below is what errors for this. (I was able to fix the visible color issue with the help of support).
==================================================================== importing ct-cube... creating info...Progress: 100.00 % reading slices...Progress: 100.00 %
z-coordinates taken from ImagePositionPatient
Interpolating CT cube...finished!
conversion of ct-Cube to Hounsfield units...finished!
Reading structures...Warning: Contour Breast is empty
importing ct-cube... creating info...Progress: 100.00 % reading slices...Progress: 100.00 %
z-coordinates taken from ImagePositionPatient
Interpolating CT cube...finished!
conversion of ct-Cube to Hounsfield units...finished!
Reading structures...Warning: Contour Breast is empty
Error in matRad_plotVoiContourSlice (line 48) colors(i,:) = cst{i,5}.visibleColor;
Error in matRadGUI>UpdatePlot (line 1051) AxesHandlesVOI = [AxesHandlesVOI matRad_plotVoiContourSlice(handles.axesFig,cst,ct,1,handles.VOIPlotFlag,plane,slice,[],'LineWidth',2)];
Error in matRadGUI>reloadGUI (line 371) UpdatePlot(handles)
Error in matRadGUI>btnRefresh_Callback (line 2666) handles = reloadGUI(hObject, handles, ct, cst);
Error in gui_mainfcn (line 95) feval(varargin{:});
Error in matRadGUI (line 81) gui_mainfcn(gui_State, varargin{:});
Error in matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)matRadGUI('btnRefresh_Callback',hObject,eventdata,guidata(hObject)) Error using matRadGUI>UpdatePlot (line 856) Error while evaluating UIControl Callback.
Reference to non-existent field 'visibleColor'.
Error in matRad_plotVoiContourSlice (line 48) colors(i,:) = cst{i,5}.visibleColor;
Error in matRadGUI>UpdatePlot (line 1051) AxesHandlesVOI = [AxesHandlesVOI matRad_plotVoiContourSlice(handles.axesFig,cst,ct,1,handles.VOIPlotFlag,plane,slice,[],'LineWidth',2)];
Error in matRadGUI>reloadGUI (line 371) UpdatePlot(handles)
Error in matRadGUI>btnRefresh_Callback (line 2666) handles = reloadGUI(hObject, handles, ct, cst);
Error in gui_mainfcn (line 95) feval(varargin{:});
Error in matRadGUI (line 81) gui_mainfcn(gui_State, varargin{:});
Error in matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)matRadGUI('btnRefresh_Callback',hObject,eventdata,guidata(hObject)) Error using matRadGUI>UpdatePlot (line 856) Error while evaluating UIControl Callback.
Reference to non-existent field 'visibleColor'.
Error in matRad_plotVoiContourSlice (line 48) colors(i,:) = cst{i,5}.visibleColor;
Error in matRadGUI>UpdatePlot (line 1051) AxesHandlesVOI = [AxesHandlesVOI matRad_plotVoiContourSlice(handles.axesFig,cst,ct,1,handles.VOIPlotFlag,plane,slice,[],'LineWidth',2)];
Error in matRadGUI>reloadGUI (line 371) UpdatePlot(handles)
Error in matRadGUI>btnLoadMat_Callback (line 539) handles = reloadGUI(hObject, handles, ct, cst);
Error in gui_mainfcn (line 95) feval(varargin{:});
Error in matRadGUI (line 81) gui_mainfcn(gui_State, varargin{:});
Error in matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)matRadGUI('btnLoadMat_Callback',hObject,eventdata,guidata(hObject)) Error while evaluating UIControl Callback.
If I try entering the plan info (gantry angle, couch angle etc.) manually and hit calculate influence mx I get the following error messages:
I was wondering if anyone else had any similar issues and might have an idea an idea on how to fix them.