The World’s Largest Online Community for Developers
I have a program in Octave that has a loop - running a function with various parameters, not something that I can turn into matrices. At the beginning of each iteration I print the current parameters using
The first times I ran it I had a brazillion warnings, and then I also got these prints. Now that I cleaned them up, I no longer see them. My guess is that they're stuck in a buffer, and I'll see them when the program ends or the buffer fills.
Is there any way to force a flush of the print buffer so that I can see my prints?
Use fflush(stdout) and/or fflush(stderr) to flush the buffer from disp().
As mentioned by moastab,
fflush(stdout) works for Octave.
In MATLAB, use
drawnow('update') to flush the output.
drawnow function will be familiar to those who control the redrawing of graphical objects in MATLAB, but it applies to the stdout stderr buffers as well. The
'update' option is not required, but limits the flushing to non-graphical queues. This detail is merely implied in the drawnow() documentation; I have verified it to work on fprintf calls in a loop.
Octave: You can turn off buffering of output by calling
This will disable pagination such that all output is sent directly to the screen.
Put the following commands at the beginning of your section or your code:
If I understand your question correctly, you can use diary function to dump all session output to a text file.
diary on will start recording, and
diary off will stop.
diary filename will use filename instead of default "diary".
It is build -in function in both Octave and MATLAB. For more details see
Also you can increase Octave buffer size. On Windows you can do it in Octave Properties dialog from upper left corner menu.
drawnow will cause graphs to update, I'm not sure if it works on the
stdout pipe as well.
You might also convert your
disp(...) statements to
fprintf(stderr, ...), I think
stderr is handled differently from
stdout on Octave.
From here and elsewhere, there are at least 5 methods to get immediate output, in Octave.
Use one of the following:
%--------------------------- % Turn OFF output buffering %--------------------------- more off % command & NOT shown in output PAGER = "less" % built-in var - shown in output page_screen_output = 0 % built-in var - shown in output page_output_immediately = 1 % built-in var - shown in output fflush(stdout) % Need to call after each "output" line