-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to resolve errors when importing nii format data for dose calculation #735
Comments
Which branch are you using exactly at the moment? It is indeed due to the 6th column. The 6th column stores objectives for planning / optimization, and matRad will use only targets with an objective (i.e. a prescription) to generate the spot grid. Here you see the condition with Lines 53 to 58 in a5b8762
The A short workaround for you is to just assign an objective to your structure "target":
This one prescribes 60 Gy in n fractions (depending on what you have set in |
Thank you for your quick reply. I am using the branch feature/niftireader. I tried the method you suggested and have successfully run it.
|
Thanks, I will close this issue. |
Hello, first of all, thank you very much for your last help in importing nii format data into matRad. However, I recently encountered some errors while using this data. When running matRad_example5_protons.m, an error occurred at the statement stf = matRad_generateStf(ct,cst,pln);

matRad: Generating stf struct...
Error using matRad_generateStf (line 135)
Could not find target.
I checked the difference between my cst data and the example cst data, and found that the sixth column of data used in the example was not present when importing with matRad_importPatient.m. However, it seems that this column of data is necessary for finding the target in matRad_generateStf.m. Therefore, I would like to ask how I should import and set this part of the data?
The text was updated successfully, but these errors were encountered: