I have noticed that if you have a parfor loop (1 worker) within which several functions with persistent variabls are called, the functions do not retain the persistent variables if you would recall them after the parfor loop in a regular for loop.
For instance I have the following parfor loop:
=============================MAIN BODY
clear functions
a=[0,0];
parfor (i=1:2,1)
if mod(i,2)==1
a(i) = func1(i);
else
a(i) = func2(i);
end
end
disp(a)
for i=1:2
if mod(i,2)==1
a(i) = func1(i);
else
a(i) = func2(i);
end
end
disp(a)
disp('====')
============================= FUNC1
function result = func1(i)
persistent kapa
if isempty(kapa) kapa = 1; end
result=kapa*i;
kapa = kapa*2;
============================= FUNC2
function result = func2(i)
persistent kapa
if isempty(kapa) kapa = 3; end
result=kapa*i;
kapa = kapa*2;
=============================
Notice I'm using only 1 worker so there would be no conflict with persistent variables being mixed up in the parfor loop.
In other words, my question is: shouldn't persistent variables be retained inside the function no matter who calls them or how they're called (as long as there are no conflicts)? Are persistent variables stored in the workers only and the client has no knowledge about them? And if this is the case, is there a way to make the persistent variables in the workers be known to the client?
I would appreciate any comments.
