Probably this would be fixed in your next build, may I ask if I just add
[ ] for the
T1BstFile argument in the
Compute function just like the call from row 334, i presume would be the same right?
Indeed. Thank you for reporting this bug.
I pushed this fix here: https://github.com/brainstorm-tools/brainstorm3/commit/bbce380362dc31a9cc510ab31b9e453b721e752b
Update Brainstorm to get it.
I was thinking to compute them parallelly in Matlab, for example, I made a script for running all subjects in a
Parfor loop, each physical core runs one subject, would this be feasible? My main concern is that since the head model estimation in Brainstorm is depending on open-source software like
DUNEuro for FEM, do you think it allows us to run in this way?
Running DUNEuro with a
parfor loop in Brainstorm would not work, because
bst_duneuro.m saves files in the temporary folder, and calling it twice at the same time would overwrite the same files.
Even if this were possible (using different users from the same computer, for instance), you would quickly run into memory limitations, as both the FEM mesh generation and the FEM leadfield computation are very memory consuming. Open a resource monitor to track the execution of a single instance.
In general, for MATLAB code, running in parallel is not always faster that running single instances sequentially, as many basic MATLAB functions for matrix processing are already multi-threaded, and far more optimized and less memory expansive than a plain parallel execution.