sorry Josef and Demian, I received no email notifications for either of your messages, google group seems to have some issues in the past few months.
I believe this issue is related to an OpenCL driver-side memory leakage that I have found previously, please see
and stackoverflow questions I posted at
if you had run mmclab/mcxlabcl on your nvidia hardware, the memory keeps on increasing in a loop, and perhaps had caused the gpu failure.
one workaround is to call each mmclab/mcxlabcl call in a separate session, using something like
matlab -nojvm -nodesktop -r "addpath('/path/to/mcxlabcl'); run_my_mcxlabcl_cmd(srcpos1, srcdir1, ...); exit"
matlab -nojvm -nodesktop -r "raddpath('/path/to/mcxlabcl'); un_my_mcxlabcl_cmd(srcpos2, srcdir2, ...); exit"
...
or
octave-cli --eval "addpath('/path/to/mcxlabcl'); run_my_mcxlabcl_cmd(srcpos1, srcdir1, ...); exit"
octave-cli --eval "addpath('/path/to/mcxlabcl'); run_my_mcxlabcl_cmd(srcpos2, srcdir2, ...); exit"
...
where replacing the path to mcxlabcl/mmclab's path, and srcpos/srcdir to each of your source positions/directions. It is a bit verbose, but should work.
I am planning to add multi-source support to mcx/mmc, so that one can simulate more than 1 src in one kernel call. Will let you know when this feature is ready.
Qianqian