diff options
Diffstat (limited to 'Master/texmf-dist/doc/latex/pgfplots/pgfplots.reference.3dplots.tex')
| -rw-r--r-- | Master/texmf-dist/doc/latex/pgfplots/pgfplots.reference.3dplots.tex | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/latex/pgfplots/pgfplots.reference.3dplots.tex b/Master/texmf-dist/doc/latex/pgfplots/pgfplots.reference.3dplots.tex index b1a41674b22..b06207ff078 100644 --- a/Master/texmf-dist/doc/latex/pgfplots/pgfplots.reference.3dplots.tex +++ b/Master/texmf-dist/doc/latex/pgfplots/pgfplots.reference.3dplots.tex @@ -903,6 +903,8 @@ As mentioned, you can use any of the \PGFPlots\ input methods as long as it yiel All this invocation of |gnuplot|, including input/output file management is transparent to the user. It only requires two things: first of all, it requires matrix data as input\footnote{Note that \texttt{contour gnuplot} processes the input stream only once. Consequently, the temporary file will contain only information which was available before the first point has been seen. The example above works because it contains |empty line|s as end-of-scanline markers. If you do not provide such markers, you may need to provide two of the three options \texttt{mesh/rows}, \texttt{mesh/cols}, or \texttt{mesh/num points}.}. Second, it requires you to enable system calls. Consider the documentation for \verbpdfref{plot gnuplot} for how to enable system calls. + Note that the $z$ coordinate of the data which is communicated to |gnuplot| is the current value of |point meta|. This allows to generate contours on two columns only and has more freedom. See also the |contour external/output point meta| key. + There are several fine-tuning parameters of the input/output file management, and it is even possible to invoke different programs than |gnuplot| (even |matlab|). These details are discussed at the end of this section, see below at page~\pageref{key:pgfplots:contour:gnuplot}. \end{plottype} @@ -1198,6 +1200,18 @@ save 'exporteddata.dat' data -ASCII A template to generate system calls for the external program. Inside of \meta{system call}, you may use |\script| as placeholder for the filename which contains the result of |contour external/script|. \end{pgfplotskey} + \begin{pgfplotskey}{contour external/output point meta=\marg{point meta read from result of external tool} (initially empty)} + Allows to customize the |point meta| configuration which is applied to the result of the external tool. + + In |contour external|, the value of |point meta| is used to generate the \emph{input} $z$ coordinate for the external tool. + + As soon as the external tool computed contour lines, its output is read and interpreted as contour lines -- and the value of |output point meta| determines the value of |point meta| which will be used to visualize the result. + + An empty value means to use the $z$ coordinate returned by the external tool. + + Any other value is interpreted as a valid choice of |point meta|. + \end{pgfplotskey} + \begin{stylekey}{/pgfplots/contour gnuplot} \label{key:pgfplots:contour:gnuplot} The initial configuration is |