how to save every iteration into workspace
1 Ansicht (letzte 30 Tage)
Ältere Kommentare anzeigen
tarek abousaleh
am 12 Mär. 2018
Bearbeitet: dpb
am 12 Mär. 2018
my code would save just the last iteration.
for c=1:170
name1 = strcat(folder_name1,'/',filesStruct1(c).name);
alpha = (((double(dicomread(name1)).*pi)./(4096)) - (pi./2))
dicomwrite(alpha, (strcat('Results/',filesStruct1(c).name)));
save(mfilename)
end
can you please edit my code so it saves alpha 170 times with 170 different 256*240 matrices thanks in advance
0 Kommentare
Akzeptierte Antwort
Stephen23
am 12 Mär. 2018
Bearbeitet: Stephen23
am 12 Mär. 2018
Use fullfile rather than string concatenation. To store the imported images in a loop simply preallocate a cell array before the loop, and then use indexing:
N = 170;
C = cell(1,N);
for k = 1:N
name = fullfile(folder_name1,filesStruct1(c).name);
alpha = double(dicomread(name1))*pi/4096 - pi/2
dicomwrite(alpha, fullfile('Results',filesStruct1(c).name));
C{k} = alpha;
end
save(mfilename,'C')
3 Kommentare
Stephen23
am 12 Mär. 2018
Bearbeitet: Stephen23
am 12 Mär. 2018
@dpb: you forgot to consider the cell array itself. If the cell array itself has to be enlarged, then it must be moved in memory, and thus causes a performance penalty. Note that this has nothing to do with the contents of the cells (as you assumed), but is solely because of the cell array itself (which is essentially an array of pointers to other arrays) changing size and requiring to be moved in memory.
This topic is explained the MATLAB documentation:
and similarly for structures, which was discussed in some detail in Loren Shure's blog:
and on this forum, e.g.:
Note also that the MATLAB preallocation documentation clearly recommends using cell to preallocate cell arrays.
The critical information to understanding this is to appreciate that any cell array or structure array is already an array in its own right (of pointers), and that means that expanding them repeatedly will be slow. Always preallocate cell arrays and structure arrays.
dpb
am 12 Mär. 2018
Hadn't researched the cell/structure array sufficiently. I had presumed they would be implemented more like a linked list than actual arrays and therefore "not so much" a performance hit. So OP needs to put an allocation step after determining the size in my above answer... :)
Weitere Antworten (2)
dpb
am 12 Mär. 2018
Bearbeitet: dpb
am 12 Mär. 2018
n=length(filesStruct1); % presuming filesStruct1 is returned from DIR()
alpha=cell(n,1); % listen to the pundits and preallocate even cell array :)
for c=1:n
name1 = fullfile(folder_name1,filesStruct1(c).name);
alpha{c} = double(dicomread(name1)*pi)/4096 - pi/2;
end
...
NB: the "curlies" {} to create cell array alpha.
Alternatively you could read the first to determine
[r,c]=size(alphaOne); % first in case possibly use differing size arrays
alpha=zeros(r,c,n); % preallocate a 3D array, put each into slice (plane)
alpha(:,:,1)=alphaOne); % save first
clear alphaOne % minor cleanup; don't need any longer
for c=2:n % now do the rest
alpha(:,:,c)= ........
...
This way one has a default double array instead of cell array so can save a dereferencing step in use or, depending on what is to be done, making calculations across the various planes is much simpler if that were to be wanted/required...
Siehe auch
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!