Skip to main content

Matlab, nested functions, and variables

I rejoiced that MATLAB lets you have locally declared functions. Ahh, where are Python's namespaces? All hail Python. Fie promiscuous MATLAB! poor shadow, false pretender.. ahem..

Ok, so I go and nest a function and load some data from a file and Boom! MATLAB cries Uncle, with some wimpy excuse that it can't load variables into a static workspace. I ask you, is that grown up behavior?

So I have to do this round about thing: Suppose I have a mat file segmenting.mat with 6 variables called segment, dive_trials, dive_segment, trials, interaction, and capture. I have to load them into an explicit variable (thisisbogus) and then I have them as structure fields. Ewww.

thisisbogus = load('segmenting')

thisisbogus =

segment: [43x2 double]
dive_trials: [2 3 4 5 7 8 9 10 12 16 19 20 26 29 32 38 39 41 43]
dive_segment: [19x2 double]
trials: [1x38 double]
interaction: [43x1 double]
capture: [43x1 double]

I didn't want to type the bazillion lines of code to assign each field back to a variable, so I automated it

thisisbogus = load('segmenting')
bog = fieldnames(thisisbogus)
for n=1:length(bog),
disp([bog{n} ' = getfield(thisisbogus,bog{' num2str(n) '});'])

which prints

segment = getfield(thisisbogus,bog{1});
dive_trials = getfield(thisisbogus,bog{2});
dive_segment = getfield(thisisbogus,bog{3});
trials = getfield(thisisbogus,bog{4});
interaction = getfield(thisisbogus,bog{5});
capture = getfield(thisisbogus,bog{6});

Which can be pasted into the MATLAB function.

I get this nagging feeling that MathWorks is getting sloppy, I wonder why. This makes me upset, just like Microsoft Word's half-baked implementation of a cross-referencing system.

Then why don't I just go use Python and Latex then, you say? I do, I do, but JEB prefers Word files, and my co-authors use MATLAB and Word...


  1. FYI, you don't have to copy and paste that output to do your reassignment. You can execute the commands directly in your loop if you just change the "disp" to an "eval".

  2. Unfortunately, no. The evals will require MATLAB to generate variables on the fly, which it can not do in nested functions (aka static workspaces)

  3. Good point. How about an "evalin('caller',..." then? I got it to work as follows:

    function output=nestTest()
    function []=nest()
    for i = 0:25


    >> nestTest()
    ans =
    a: 0
    b: 1
    c: 2 ...


Post a Comment

Popular posts from this blog

Python: Multiprocessing: passing multiple arguments to a function

Write a wrapper function to unpack the arguments before calling the real function. Lambda won't work, for some strange un-Pythonic reason.

import multiprocessing as mp def myfun(a,b): print a + b def mf_wrap(args): return myfun(*args) p = mp.Pool(4) fl = [(a,b) for a in range(3) for b in range(2)] #mf_wrap = lambda args: myfun(*args) -> this sucker, though more pythonic and compact, won't work, fl)

Flowing text in inkscape (Poster making)

You can flow text into arbitrary shapes in inkscape. (From a hint here).

You simply create a text box, type your text into it, create a frame with some drawing tool, select both the text box and the frame (click and shift) and then go to text->flow into frame.


The omnipresent anonymous asked:
Trying to enter sentence so that text forms the number three...any ideas?
The solution:
Type '3' using the text toolConvert to path using object->pathSize as necessaryRemove fillUngroupType in actual text in new text boxSelect the text and the '3' pathFlow the text

Drawing circles using matplotlib

Use the pylab.Circle command

import pylab #Imports matplotlib and a host of other useful modules cir1 = pylab.Circle((0,0), radius=0.75, fc='y') #Creates a patch that looks like a circle (fc= face color) cir2 = pylab.Circle((.5,.5), radius=0.25, alpha =.2, fc='b') #Repeat (alpha=.2 means make it very translucent) ax = pylab.axes(aspect=1) #Creates empty axes (aspect=1 means scale things so that circles look like circles) ax.add_patch(cir1) #Grab the current axes, add the patch to it ax.add_patch(cir2) #Repeat