How i plot vector in workspace but i have only name the vector i want plot

HI

in my workspaceworkspace i have vectors, now i find the vector i want plot in this code:

namesWorkspace = who;
outStr = regexpi(namesWorkspace, 'nameOfVariable');
ind = ~cellfun('isempty',outStr);
vars = namesWorkspace(ind);
outStr = regexpi(namesWorkspace, 'BB');
ind = ~cellfun('isempty',outStr);
vars = namesWorkspace(ind)

result:

vars = 
    'BB1UN'
    'BB1UR'

Now i want plot(BB1UN) and plot(BB1UR) How i do it?

i try this but its not work: plot(vars(1,1)) ; plot(vars(1,2))

BB1UN- Its vector in my workspace

BB1UR- Its vector in my workspace

Answer 1

[A. Sawas]

plot(eval(vars{1})); % 'BB1UN'
plot(eval(vars{2})); % 'BB1UR'

[madhan ravi]

Why beginners should learn to avoid eval?

[A. Sawas]

What I really started to hate in this community? ... when "expert" people use the word "beginners" when they don't like the solutions.

I am sure there are cases when using eval is not a bad thing, otherwise it shall be removed from Matlab.

[Stephen23]

"... otherwise it shall be removed from Matlab."

eval is not the problem: the problem is how beginners use it when other ways of writing code are simpler, neater, more efficient, less buggy, and easier to debug.

This topic has been discussed many times before:

https://www.mathworks.com/matlabcentral/answers/364851-assignin-and-eval-functions

https://www.mathworks.com/matlabcentral/answers/352237-is-there-the-more-elegant-way-to-do-this

"What I really started to hate in this community? ... when "expert" people use the word "beginners" when they don't like the solutions."

Interestingly those slow, complex, obfuscated, buggy and hard-to-debug "solutions" are discussed in some detail in the MATLAB documentation:

https://www.mathworks.com/help/matlab/matlab_prog/string-evaluation.html

and on the official TMW blogs:

https://blogs.mathworks.com/loren/2005/12/28/evading-eval/

https://blogs.mathworks.com/loren/2006/01/04/more-in-eval/

https://blogs.mathworks.com/videos/2010/03/08/top-10-matlab-code-practices-that-make-me-cry/

and in many threads on this forum, where many explanations (based on experimental data and an understanding of how MATLAB actually works) have been provided on why this approach to code design forces users into writing slow, complex, obfuscated, and buggy code that is hard to debug. Based on many threads on this forum, the use of those slow, complex, buggy "solutions" does seem to be more correlated with beginners.