Hi Sophie,

If the job was stopped without any apparent reason, the most likely cause is that the job-scheduler in your cluster environment killed the job because it exceeded the allocated resources (typically either it exceeded the allocated time or it exceeded the allocated memory). To fix that you simply need to "request" more memory and longer times for your jobs. You may do that in CONN's gui 'tools. HPC options. Configuration' menu, selecting the profile named 'Slurm computer cluster', and then adding "in-line additional submit options" box the text:

-t 12:00:00 --mem=8Gb

(the above line will request 12 hours and 8Gb per job, that should typically suffice but feel free to play with those values if needed)
and then clicking 'save' (all) to save that configuration for future jobs as well. If you prefer not to use the GUI you can also do the same thing from Matlab's command line using the command:

conn_jobmanager options cmd_submitoptions '-t 12:00:00 --mem=8Gb' saveall

Let me know if that seems to fix this issue (and if does not, please give me more details about what cluster environment your are using since may of these limitations and policies vary from place to place) 

Hope this helps
Alfonso

Originally posted by sophieb: