Simple Matlab and python script that import colormaps from matplotlib into Matlab.
getPyPlot_cMap returns any colormap implemented in the matplotlib python library. It calls a python script that writes the colormap matrix into a temporary file, i.e. PYTHON (and the matplotlib module) is REQUIRED. However, the advantage is that you get all the colormaps implemented in matplotlib and that you can specify the number of RGB quantization levels, i.e. the number of colors of the colormap.
A list of colormap names is provided in the function help section. getPyPlot_cMap('!GetNames') returns a cellstring containing all available colormap names. See https://matplotlib.org/examples/color/colormaps_reference.html for an illustration of colormaps.
cMapNames = getPyPlot_cMap('!GetNames')
Returns a cellstring containing all available colormap names.
cMap = getPyPlot_cMap(cMapName)
Returns the colormap cMapName with the default of 128 colors. cMap will be a 128x3 matrix.
cMap = getPyPlot_cMap(cMapName, NumberOfColors)
Specify the number of colors, i.e. the number of rows in cMap.
cMap = getPyPlot_cMap(cMapName, NumberOfColors, keepAlphaChannel)
If keepAlphaChannel is not 0 cMap has a 4th column containing the alpha channel.
cMap = getPyPlot_cMap(cMapName, NumberOfColors, keepAlphaChannel, pythonSystemCommand)
Lets you specify the python command (possibly including a path, see below) used to execute the python script.
If you have python installed but Matlab says 'There was an error executing the command... System returned:...' you can try to pass the path to your python installation explicitly as the 4th parameter, e.g.:
cmp = getPyPlot_cMap('Accent', , , '"c:\Program Files\Python37\python.exe"');
Note the double-quotes around the path, which are neccessary because of the containing space character.
Konrad (2020). PyColormap4Matlab (https://github.com/f-k-s/PyColormap4Matlab), GitHub. Retrieved .
Sorry: PYPLOT.CM should be PYPLOT.PY.
Neat concept, I really like the idea of this. Like all good ideas, it is simple at heart but does something fundamentally useful.
Using a temporary data file is innovative, but repeating those system commands and file I/O on every function call is unlikely to be efficient: perhaps PERSISTENT or MEMOIZE could be used here to speed up subsequent calls.
As an aside, note that CubeHelix is not just an array of RGB values but is actually an algorithm which can generate a wide variety of colormaps, for which it has several parameters which the user uses to specify a colormap, independently of the colormap size.
An implementation of the CubeHelix algorithm is actually contained in MatPlotLib's _CM.PY module, but only its default parameters are used when it is imported by CM.PY (which in turn is imported by PYPLOT.CM). This is a shame, because the default values "aren't very good" (according to http://inversed.ru/Blog_2.htm#Cubehelix), which means that users of MatPlotLib (and this FEX submission) are likely put-off by the default CubeHelix colormap, and sadly never have the opportunity to actually experiment with the CubeHelix algorithm itself.
A related discussion on this topic: https://github.com/matplotlib/matplotlib/issues/9895/
A shameless plug of my own FEX: www.mathworks.com/matlabcentral/fileexchange/43700-cubehelix-colormap-generator
Thanks Piercarlo for letting me know!
I added the solution for this issue to the description above.
If the problem occurs to anyone else: pass the path to your python installtion as the 4th argument.
An error is occurring to me:
"Error using getPyPlot_cMap (line 93)
There was an error executing the command python ...(path)\pyplotCMap2txt.py
"python" is not recognized as an internal or external command, or an exe or file batch.
Impossible to find the specified path."
What should I do to fix it?
Added Live Script
Fixed issue when path to python script contain white spaces or special characters.
List of colormap names (when retrieved with !getNames) is now generated by python script instead of hard-coded in Matlab script.
Image added (taken from matplotlib.org)