Question

I have some programs written in Matlab that I need to run several times for some reasons (debugging, testing with different input, etc…)

But, there are a lot’s of graphs that are plotted by the programs and its various functions such that everytime I run the program, I have to wait for all the graphs to be displayed, which is very annoying and time consuming (especially when you are working with a small laptop).
After the program is executed, I close them with a close all.

So my question is:

Is there a way to disable all plots/figures/graphs in Matlab? either in the options, or by executing a certain code like disable plot and enable plot to ensure that no figures are being displayed.

I know that I can just browse the code and comment the plotting part, but I don’t want to forget to uncomment.

Answer 1

Try some combination of the two commands:

set(gcf,'Visible','off')              % turns current figure "off"
set(0,'DefaultFigureVisible','off');  % all subsequent figures "off"

The second one, if you put it near the beginning of your program, might do the trick for you. Of course, it is still creating the plots, which might be undesirable for computation time and/or RAM issues.

This is a classic reason to avoid Matlab when one can. It fosters bad programming design. To solve this problem correctly, you should create something that lets you “flip a switch” at the highest level of your program and control whether plots show or do not show. Perhaps it even has gradations of the show/don’t show option so you can select different types of plots that do/do not show depending on what diagnostics you are running.

Ideally, you’d want this “flip a switch” creation to be a class that has access to visibility and plot functions of other objects. But because interactive object-orientation is so cumbersome in Matlab, it’s often not worth the effort to develop such a solution, and most people don’t think about this design aspect from the outset of their project.

Matlab would encourage someone to solve this by making flag variables like “isPlotVisible” or something, and creating functions that always accept such flags. I agree this is a bad design.