Thanks again, Alfonso. I updated my CONN with the patch and tried running in parallel again and it worked perfectly without any errors. To answer your question: I didn't use a batch script to run the parallel process -- I simply selected "distributed processing (run on Background process (Windows))" in the GUI, specified the number of parallel processes (I tried it several times with the number ranging from 2-10 and got the error every time), and which outlier detection thresholds to use (I always chose default intermediate). That was it. I hope this is helpful.

Thanks again for your help!

Jeff

Originally posted by Alfonso Nieto-Castanon:

for some reason I am not able to attach the patch here, in any case the current development version of CONN in github (github.com/alfnie/conn) now includes this fix (and this specific patch is in the file conn.m)

Best

Alfonso

 

 

Originally posted by Alfonso Nieto-Castanon:

Hi Jeff,

Thanks for the additional info, this was indeed quite a strange error to debug! if I am interpreting correctly the issue was that in your project info (somehow, I am not sure yet how this happened) the project filename is stored as conn_n21_parallel (the folder) instead of conn_n21_parallel.mat (the file) and that is creating some problems down the stream when running things in parallel. The attached patch should be able to fix this issue, but to make sure I am not missing anything (and to avoid others from running into the same issue) if you could please let me know some specific details on how the parallel process was run (e.g. did you use a batch script) that would be very helpful. 

(note: this patch is for release 25b, to install it simply copy the attached file to your CONN distribution folder overwriting the file with the same name there)

Best

Alfonso

 

Originally posted by johnsojp13:

Hi Alfonso, 

Thanks for your response. To keep things moving forward, I ran outlier detection overnight using the standard, non-parallelized method. But I also tried running a version in parallel just now and the logs are still showing the same errors, so I'm attaching the qlog subdirectory you requested. 

Thank you,

Jeff