# How do I make a series of variables A1, A2, A3, ... A10?

518 views (last 30 days)
Doug Hull on 18 Jan 2011
Edited: Stephen23 on 16 Oct 2017
How do I make variables like this in a loop?

Doug Hull on 18 Jan 2011
Please don't do this! You will find that MATLAB arrays (either numeric or cell) will let you do the same thing in a much faster, much more readable way. For example, if A1 through A10 contain scalars, use:
A = zeros(1,10); % Not necessary, just much faster
for i=1:10
A(i) = % some equation
end
Now refer to A(i) whenever you mean Ai. In case each Ai contains a vector or matrix, each with a different size, you want to use cell arrays, which are intended exactly for this:
for i=1:10
A{i} = 1:i;
end
Note that each A{i} contains a different size matrix. And be careful to use the curly braces for the subscript!
Another way to have your cake and eat it too is to use structures instead of cell arrays. The fields of the structure can be the variable names you want. And you can index into them with dynamic field references. For example:
names = {'fred' 'sam' 'al'};
for ind = 1:length(names)
s.(names{ind}) = magic(length(names{ind}));
end
In this case, you end up with the variable s, a structure, containing fields specified by the strings stored in the cell array names.
Now, if you still really want to create variables with dynamically generated names, you need to use EVAL. With EVAL, you use MATLAB commands to generate the string that will perform the operation you intend. For example, eval('A=10') has the same effect as A=10, and eval(['A' 'B' '=10']) has the same effect as AB=10, only the EVAL method executes much more slowly. So in a loop, you could use:
for i=1:10
eval(sprintf('A%d = [1:i]', i));
end
Notice how much more obfuscated this is. In addition, this can cause difficult-to-troubleshoot problems in your code, particularly if you try to dynamically create a variable with the same name as a function:
function y = mysin(x)
eval('sin = 5;');
y = sin(x);
Calling this function with "y = mysin(1)" will not return y = 5 (the first element of the sin variable created by EVAL) -- it will return the sine of 1, because when the function was parsed there was no variable named sin and so the usage of sin on the last line was parsed as a call to the built-in SIN function. The fact that a variable named sin existed at runtime is irrelevant; the parsetime "decision" takes precedence.
Repeat: don't create variables at runtime using EVAL unless you have a very good reason, such as someone gives you a MAT file with 2000 variables named A1428, for example. Even in that case, you can avoid EVAL:
% Assume the MAT-file example1.mat contains 2000 variables, A1 through A2000
% S is now a struct array with 2000 fields, S.A1 through S.A2000.
% To access A1428, use:
x1 = S.A1428;
% If the "index" of the variable you want to access is stored in a variable:
k = 1428;
x2 = S.(sprintf('A%d', k));
x3 = S.(['A', num2str(k)]);
[From the MATLAB FAQ of Ancient Times]
Matthew on 19 Jul 2013
Omg thanks so much. The structure did it nicely for me :)

Pedro Inácio on 14 Oct 2017
Dear all, After read in different threads in Matlab forums, I found different solutions, which I believe they do not provide the real answer to: "Is possible to dynamically change variables names?"
The answer is Yes, and it does not need the use of eval.
I'm posting a solution to solve the question with comments step-by-step (It can be integrated in a for loop).
% NEW VARIABLE NAME
ID = 'new_NIF';
% FISCAL NUMBER SAVED IN MATLAB WORKSPACE
old_NIF = 555888222;
% CREATE A NEW PROVISORY STUCTURE
provisory_struct.(ID) = old_NIF;
% CREATE A NEW PROVISORY MAT FILE NAME
provisory_file_name = fullfile(pwd,'save_provisory_data.mat');
% SAVE THE PROVISORY STRUCTURE FIELDS AT THE
% PROVISORY MAT FILE
save(provisory_file_name,'-struct','provisory_struct');
% DELETE PROVISORY STRUCTURE VARIABLE
clear('provisory_struct');
% LOAD OUR NEW VARIABLE NAME
% DISPLAY NEW VARIABLE CONTENT
fprintf(1,'OLD NIF: %d\nNEW NIF: %d\n',old_NIF,new_NIF);
% DELETE PROVISORY FILE
delete(provisory_file_name);
Jan on 14 Oct 2017
@Perdro: Saving the data to a file and relaoding them directly into the workspace has exactly the same drawbacks as eval'ing it directly, but in addition a massive delay due to the slow disk access. Of course, it "works", as eval does also. But it causes more troubles than it solves.
This topic has been discussed frequently and exhaustively in many forums. Your idea, that these discussions "do not provide the real answer", is off track.