{"id":476,"date":"2017-05-15T19:43:08","date_gmt":"2017-05-16T03:43:08","guid":{"rendered":"http:\/\/wonghoi.humgar.com\/blog\/?page_id=476"},"modified":"2017-05-15T19:43:08","modified_gmt":"2017-05-16T03:43:08","slug":"matlab-the-know-it-cold-list","status":"publish","type":"page","link":"https:\/\/wonghoi.humgar.com\/blog\/matlab-the-know-it-cold-list\/","title":{"rendered":"MATLAB: The “know it cold” list"},"content":{"rendered":"
Very often, the MATLAB documentation is enough\u00a0for anybody with a vague idea of what they want to dig their way to the right concepts\/features to solve their problem. Nonetheless, there are few handy tools or quirks that\u00a0are “either you know it or you don’t”.<\/p>\n
Most of the tips in the following list are essential to avoid super-clumsy maneuvers. I’ve seen enough people that developed messy workarounds just because they didn’t know these:<\/p>\n
\n
addpath( genpath() ): now you can organize your code by folder and add it in one shot!\u00a0Preach it! \naddpath(…, ‘-end’):\u00a0gives the new paths lower priority to avoid shadowing existing functions<\/li>\n
userpath(‘reset’): fixes it when\u00a0you see MATLAB starting in “C:\\Windows\\System32”.\u00a0\n<\/li>\n
verLessThan(): deal with backward compatibility issues<\/li>\n
struct2table(ver()) instead of plain ver(), which gives you a nasty array of structs \nstruct2table(dir()) instead of plain dir(), which gives you a nasty array of structs<\/p>\n<\/li>\n
spotting implicit run-length encoding<\/li>\n
spotting implicit uses of diff()\/cumsum(). \ndiff() is easy to come up with, but we often missed cumsum().<\/li>\n
comma separated list from dereferencing multiple cells (e..g C{:}) or multiple array-of-structs.<\/li>\n
[varargout{1:nargout}] = f(…)<\/li>\n
relay varargin by varargin{:}<\/li>\n
use\u00a0exist(…, ‘var’) to define simple optional arguments instead of counting argument numbers (nargin). <\/li>\n<\/ul>\n
I’ll expand the list as I recall more concepts. Keep checking this page for updates. Feel free to suggest more in the comments section<\/p>\n