Skip to content
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

sigint 11 when calculating voxel dose #14

Open
davide84 opened this issue May 18, 2022 · 2 comments
Open

sigint 11 when calculating voxel dose #14

davide84 opened this issue May 18, 2022 · 2 comments

Comments

@davide84
Copy link

Hi,
I am running the Victre pipeline with minimal changes from git, to get familiar with the parameters.
If I set the parameter "tally_voxel_dose" to YES the Python script ends with an exception of "Projection error".
The file output_projection.out ends with:

Command terminated by signal 11
316.60user 2.20system 5:19.11elapsed 99%CPU (0avgtext+0avgdata 6978648maxresident)k
0inputs+70328outputs (0major+1731728minor)pagefaults 0swaps

The system is Ubuntu LTS 20.04, kernel 5.4, 64 GB of Ram (10% used during simulations), Intel processor and two GeForce 2080i.
My pipeline was compiled with CUDA support and without MPI.

Any idea? Can I provide more data?
Thanks in advance!

@andreubs
Copy link
Member

andreubs commented Jun 1, 2022

Hi Davide.
I usually don't activate the voxel dose tally with VICTRE_MCGPU because the VICTRE phantoms are so large that there is no space in the GPU memory to store the dose to each voxel. Defining a smaller ROI should work but I have not tested it lately.

When is the program failing: (a) during code initialization?, (b) during GPU kernel execution?, (c) in the final result reporting after the kernel?

It would help if you could provide the entire simulation output file to see the size of the ROI and all the error messages written by the program.

   Andreu

@davide84
Copy link
Author

Hi! Sorry for the late reply, this part of the project had to briefly be put on hold.
I have now resumed the work on this part and investigate again the error, I was able to see that it was a memory issue of the GPU - previously I only checked the system RAM, sorry.
With very small ROI regions there is no problem.
Thanks again!

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

No branches or pull requests

2 participants