MATLAB: Dir problem

dirdirectory

I try to find files with the function DIR. Unfortunately I get many more then the ordinary 'dos' of windows DIR function gets.

This is the query:

dir('abc_1.*')

I do not only get: abc_1.avi, abc_1.mat, abc_1.bck but also: abc_10.avi, abc_11.mat, abc_1000.bck

Is there any way to avoid this?

Thanks,

Jeroen

Best Answer

Hi! Thanks for looking into it. Apparently the problem is solved in version 12a. I work with version Matlab 7.10.0 (R2010a)

A student of mine (Marije) found the answer though. here is the problem and the solution:

>> ls
.                       Untitled2 - Copy (5).m  Untitled20.m            
..                      Untitled2 - Copy.m      Untitled200.m           
Untitled2 - Copy (4).m  Untitled2.m             
>> dir('Untitled2.*')
Untitled2 - Copy (4).m  Untitled2.m             
Untitled2 - Copy (5).m  Untitled20.m            
Untitled2 - Copy.m      Untitled200.m           
>> dir('Untitled20.*')
Untitled20.m   Untitled200.m

But This is the answer!! The '.' is the problem and '..' is the solution

>> dir('Untitled2..*')
Untitled2.m

Jeroen

Related Solutions

MATLAB: Issues of Sensitive in ‘dir’ function

d     = dir('*.m');
match = strcmpi({d.name}, 'abc.m');  % [EDITED] strcmp*i*
Name  = d(match).name;

Another implementation: FEX: FileRealCase. This adjusts the upper/lower case of the path also.

MATLAB: How to use “run command” within a function which saves all variables inside base workspace

No. run is defined as executing a script, and scripts always have access to the current workspace and affect the current workspace (though in some very recent MATLAB versions there are starting to be some ways in which scripts do not have full access to private information.)

You could create a wrapper function that looked in its parent function and copied all of the parent's variables into the current workspace, and then ran the script, and then looked at all remaining variables and compared them to the parent's copies of the variables in order to determine which had changed, and then write the changed versions to the base workspace. This would be somewhat troublesome, but I guess there might be some use for it.

If you did not want the script to have access to any of the current workspace's variables while it ran, then you could

evalin('base', 'run(''script.m'')')

Best Answer

Related Solutions

MATLAB: Issues of Sensitive in ‘dir’ function

MATLAB: How to use “run command” within a function which saves all variables inside base workspace

Related Question