NaN values in physicalDose of resultGUI [BUG]

[zperko]

Describe the bug
In some cases the returned physicalDose array contains NaN values, while the none of the beam physical dose arrays (physicalDose_BeamX) have any NaNs in them. Seems like this mainly happens along the edges of the CT (e.g., resultsGUI.physicalDose(:,:,end) or (:,end,:), so it could be a loop end index being incorrect.

To Reproduce
Bit difficult without providing the patient data, but we have seen this for multiple brain cases.

Expected behavior
Should not have NaN values in calculated dose arrays, and the beamwise dose values should correspond to the total dose array.
See the attached screenshot of a normal looking dose and DVHs, but with NaNs in the physical dose.
Screenshots

Desktop (please complete the following information):

• OS: UNIX
• Environment & Version Matlab 2021b
• matRad Version 2.10.1

Additional context

[zperko]

Actually, there are also slices only partially filled with NaNs, so probably not a looping issue. Still though these seem to be always close to the edges of the CT.

[wahln]

Do you know what rsp / HU values are present during dose calculation in these voxels? Might be a little annoying to debug due to the grid's usually being different and the resampling involved. I guess the NaN's are somewhere created in interpolation when a value lies out of range, so this could either be the 3D grid resampling or Hounsfield Look-Up.