[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problem saving multiplot to a file

From: Ronald Kumon
Subject: Re: problem saving multiplot to a file
Date: Thu, 12 Jun 2003 13:20:07 -0400 (EDT)

On Thu, 12 Jun 2003, Manojit Roy wrote:

> The way I solve this problem is by creating a load file "load.m", at the
> beginning of which is your gset commands, followed by plot commands and
> ended with "gset nomulti" (the last command is to get a readable
> postscript file). Each time when I need to refresh the plot, I quit
> octave, restart it, and execute "load". This complicated method may have
> to do with deleting intermediate tmp files (command "purge_tmp_files" does
> not do a good job). I am sure there are better ways, maybe someone can
> help.

Hmm... I often use multiplot and don't seem to have this problem.
However,  I typically put all my plotting commands in a script (say,

# plotgraph.m
gset term postscript
gset output ""
[graphing commands]
gset nomultiplot
gset term x11 (to return to screen output)

I then edit and run the script until I get what I want.  However, for
complicated graphs, I usually try to get roughly what I want on the screen
first, and only output to Postscript when I need to settle on the final
layout.  I also find it helpful to use a Postscript viewer with a "watch
file" option (e.g., gv, ggv).  That way every time I run the script, the
changes will be automatically updated in the viewer.  Occasionally the
viewer will get confused, and I have to manually reload, but it works most
of the time.

I find I only need to use "purge_tmp_files" when I am generating many,
many graphs (100s) in one session.

Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]