Rank: 1604 based on 80 downloads (last 30 days) and 5 files submitted
photo

Alan Robinson

E-mail
Company/University
UC San Diego

Personal Profile:

http://cogsci.ucsd.edu/~aerobins


 

Watch this Author's files

 

Files Posted by Alan Robinson View all
Updated   File Tags Downloads
(last 30 days)
Comments Rating
07 Jan 2014 Process named Arguments Easily add optional, named arguments to your functions, like this: f('var_name', value). Author: Alan Robinson named arguments, optional arguments, function calls, utility, calling argument proc..., namevalue pairs 7 3
  • 4.0
4.0 | 1 rating
17 Dec 2012 DispA(ll) Enhanced disp that can take any number of arguments Author: Alan Robinson strings, display, disp, text, string manipulation, utilities 7 2
17 Dec 2012 ASCII ProgresBar (included elapsed/estimated time) Prints a graphical progress bar to the console showing percent complete + elapsed and remaining time Author: Alan Robinson progressbar, ascii 5 0
28 Mar 2012 Screenshot Set Window Titlebar Set current figure's titlebar text to something more informative than "Figure N". Author: Alan Robinson figure, gui 2 0
04 Aug 2010 Screenshot set errorbar width and thickness Set an error bar's width and thickness. Author: Alan Robinson errorbar, errorbar_tick 59 0
  • 5.0
5.0 | 2 ratings
Comments and Ratings by Alan Robinson View all
Updated File Comments Rating
08 Jan 2014 easyparse Easy-to-use interface for parsing function inputs in the form of parameter-value pairs. Author: Jared

Much easier than Matlab's inputparser. I do something similar with my procArgs function, except I get the list of allowed variables by requiring that they already be created in the calling function, which is arguably easier still.

28 Mar 2012 process_varargin utility to make setting and changing default values in a script easier Author: christie harper

Makes it easy to support optional, named arguments.

Could use with a better code example.

I prefer my procArgs method (also on file exchange) for setting the default values, but clearly it comes down to taste.

28 Mar 2012 process_varargin utility to make setting and changing default values in a script easier Author: christie harper

04 Aug 2010 DispA(ll) Enhanced disp that can take any number of arguments Author: Alan Robinson

I guess it depends on how much you like printf strings. I find them easy to write, but error prone to edit after the fact.

23 Nov 2009 A manual code for image THRESHOLDING (or) Color to binary image conversion This file convert any image into a binary format Author: Rama Chandra Rao Naradasu

This code does what img(img > threshold) = 0, would do, more or less, but with a lot of loops. I think it should be removed.

Comments and Ratings on Alan Robinson's Files View all
Updated File Comment by Comments Rating
29 Jul 2014 set errorbar width and thickness Set an error bar's width and thickness. Author: Alan Robinson Christoph

11 Mar 2014 set errorbar width and thickness Set an error bar's width and thickness. Author: Alan Robinson Vincent

04 Aug 2010 DispA(ll) Enhanced disp that can take any number of arguments Author: Alan Robinson Alan Robinson

I guess it depends on how much you like printf strings. I find them easy to write, but error prone to edit after the fact.

21 Feb 2010 DispA(ll) Enhanced disp that can take any number of arguments Author: Alan Robinson Oleg Komarov

Don't see why I should be tired of:
>> fprintf('the brightness is %.3f cd/m2 \n',32.098)
the brightness is 32.098 cd/m2

21 Nov 2009 Process named Arguments Easily add optional, named arguments to your functions, like this: f('var_name', value). Author: Alan Robinson Jan Simon

If the EXIST test would be omitted, procArgs could even *create* variables in the caller. But this would be dangerous and would confuse the JIT compiler: "assignin('caller', 'RANK', 1)" collides with the Matlab toolbox function 'rank' (at least in Matlab 6.5 and 7.7). Therefore I appreciate that you've included (and updated) the EXIST test.
You are right: debugging is not impossible. ASSIGNIN and EVALIN can obfuscate a program and predicting the effects can be really hard. But to be honest: one can write obfuscated source even without ASSIGNIN! procArgs with some good comments can be much better than a hard coding without comments.
Rating: H1 line, help, example, version number, name of author: exsiting. Function works, is useful and usable. I personally prefer hardcoded access of variables and this might be a question of taste.

Contact us