Closed schoffelen closed 1 month ago
My suggestion would be to change in
limo_check_ppool, line 13:
if isempty(N)
into
if isempty(N) || N==1
that par pool check works for me -- what about on your cluster?
Well, I get a little bit further in the pipeline, but now fail due to the fact that parfor apparently attempts to start a parcluster anyhow (if it has not been started before), and does so in my case in the 'Threaded' mode. This causes an error downstream, due to the fact that it's forbidden to run mex-files in a parallel loop in threaded mode...
there is undocumented stuff that I saw on StackOverflow . In limo_check_ppool if 1 (line 37), we can force matlab NOT to start when it sees parpool
ps = parallel.Settings;
ps.Pool
ans =
PoolSettings with properties:
AutoCreate: 1
RestartOnClusterChange: 1
RestartOnPreferredNumWorkersChange: 1
IdleTimeout: 30
PreferredNumWorkers: 12
changing AutoCreate to false
? what do you think
When I try to run https://github.com/SIESTA-eu/wp15/blob/main/usecase-2.4/2.4.A/ERP_Core_WB.m I get the following error:
limo_batch ends up in the section where the default parallel processing is attempted, but running singlethreaded matlab session (by default enforced on the DCCN cluster) the variable 'N' (number of threads) is 1, causing the error. I assume there is a way to define in limo a parameter that avoids the parallel processing, but I would also assume that the limo-code would behave robustly in a singlethreaded application.