feedgnuplot/guide/guide.org

145 lines
4.8 KiB
Org Mode
Raw Normal View History

2021-02-21 05:06:10 +08:00
* Guide
2021-02-21 04:00:45 +08:00
2021-02-21 05:06:10 +08:00
This is an overview of the capabilities of =feedgnuplot= and a set of example
recipes. The [[https://github.com/dkogan/feedgnuplot/][documentation]] provides a complete reference. The capabilities of
gnuplot itself are demonstrated at [[http://www.gnuplot.info/demo/][its demo page]].
2021-02-21 04:00:45 +08:00
2021-02-21 05:35:05 +08:00
* Tutorial
2021-02-21 04:00:45 +08:00
First, a trivial plot: let's plot a sinusoid
#+BEGIN_SRC sh :results file link :exports both
2021-02-21 05:06:10 +08:00
seq 100 | \
2021-02-21 05:42:36 +08:00
perl -nE 'say sin($_/5.)' | \
feedgnuplot
2021-02-21 04:00:45 +08:00
#+END_SRC
#+RESULTS:
[[file:guide-1.svg]]
2021-02-21 05:06:10 +08:00
This was a trivial plot, and was trivially-easy to make: we gave the tool one
column of data with no specific instructions, and we got a plot.
2021-02-21 05:35:05 +08:00
Here each point we plotted was 2-dimensional (has an =x= value an a =y= value),
but we passed in only one number for each point. This is what is expected
without =--domain=, so =feedgnuplot= filled in sequential integers (0, 1, 2,
...) for the =x= coordinate. Without =--domain= and without =--dataid=, each line
of input is interpreted as =y0 y1 y2...=. So we can plot a sin and a cos
together:
2021-02-21 05:06:10 +08:00
#+BEGIN_SRC sh :results file link :exports both
seq 100 | \
2021-02-21 05:42:36 +08:00
perl -nE '$th = $_/100.*2.*3.14159; $s=sin($th); $c=cos($th); say "$c $s"' | \
feedgnuplot
2021-02-21 05:06:10 +08:00
#+END_SRC
#+RESULTS:
[[file:guide-2.svg]]
2021-02-21 05:35:05 +08:00
Note that, the lines may have different numbers of points. To plot the cosine
from every line, but a sine from every 5th line:
2021-02-21 05:06:10 +08:00
#+BEGIN_SRC sh :results file link :exports both
seq 100 | \
2021-02-21 05:42:36 +08:00
perl -nE '$th = $_/100.*2.*3.14159; $s=sin($th); $c=cos($th);
if($.%5) { say "$c"; }
else { say "$c $s"; }' | \
feedgnuplot
2021-02-21 05:06:10 +08:00
#+END_SRC
#+RESULTS:
[[file:guide-3.svg]]
2021-02-21 05:35:05 +08:00
If we pass in two columns and =--domain=, =feedgnuplot= will use one for the =x=,
and the other for the =y=. With =--domain= and without =--dataid=, each line of
2021-02-21 05:06:10 +08:00
input is interpreted as =x y0 y1 y2...=. Let's plot =sin(theta)= vs.
=cos(theta)=, i.e. a circle:
#+BEGIN_SRC sh :results file link :exports both
seq 100 | \
2021-02-21 05:42:36 +08:00
perl -nE '$th = $_/100.*2.*3.14159; $s=sin($th); $c=cos($th); say "$c $s"' | \
feedgnuplot --domain
2021-02-21 05:06:10 +08:00
#+END_SRC
#+RESULTS:
[[file:guide-4.svg]]
Hmmm. We asked for a circle, but this looks more like an ellipse. Why? Because
2021-02-21 05:35:05 +08:00
gnuplot is autoscaling the =x= and =y= axes independently to fill the plot window.
2021-02-21 05:06:10 +08:00
We can scale the axes /together/ by passing =--square=, and we get a circle:
#+BEGIN_SRC sh :results file link :exports both
seq 100 | \
2021-02-21 05:42:36 +08:00
perl -nE '$th = $_/100.*2.*3.14159; $s=sin($th); $c=cos($th); say "$c $s"' | \
feedgnuplot --domain --square
2021-02-21 05:06:10 +08:00
#+END_SRC
#+RESULTS:
[[file:guide-5.svg]]
Again, we can have multiple =y= in each line, and each line may have a different
number of =y=. Let's plot a circle /and/ an ellipse, sampled more coarsely:
#+BEGIN_SRC sh :results file link :exports both
seq 100 | \
2021-02-21 05:42:36 +08:00
perl -nE '$th = $_/100.*2.*3.14159; $s=sin($th); $c=cos($th);
if($.%5) { say "$c $s"; }
else { $s2 = $s/2;
say "$c $s $s2"; }' | \
feedgnuplot --domain --square
2021-02-21 05:06:10 +08:00
#+END_SRC
#+RESULTS:
[[file:guide-6.svg]]
2021-02-21 05:35:05 +08:00
We just plotted something where each point is represented by 2 values: =x= and
=y=. When making 2D plots, this is the most common situation, but others are
possible. What if we want to color-code our points using another column of data?
We feed in the new column, and we tell =feedgnuplot= that we now have /3/ values
per point (the tuple size), and we tell =gnuplot= how we want this plot to be
2021-02-21 05:42:36 +08:00
made. Color-coding by the angle, in degrees:
2021-02-21 05:35:05 +08:00
#+BEGIN_SRC sh :results file link :exports both
seq 100 | \
2021-02-21 05:42:36 +08:00
perl -nE '$thdeg = $_/100.*360.;
$th = $_/100.*2.*3.14159;
$s=sin($th); $c=cos($th);
say "$c $s $thdeg";' | \
feedgnuplot --domain --square \
--tuplesizeall 3 \
--styleall 'with points palette'
2021-02-21 05:35:05 +08:00
#+END_SRC
#+RESULTS:
[[file:guide-7.svg]]
Here we said that /all/ the datasets have 3 values per point. And that /all/ the
datasets should be plotted with that particular style. The styles are strings
that are passed on to =gnuplot= verbatim. So the full power of =gnuplot= is
available, and there's nothing =feedgnuplot=-specific to learn. =gnuplot= has
plenty of documentation about styling details.
The above =--styleall= argument may be identically replaced with a shorthand:
2021-02-21 05:42:36 +08:00
#+BEGIN_EXAMPLE
--with 'points palette'
#+END_EXAMPLE
2021-02-21 05:35:05 +08:00
The styles and tuple sizes can be different for each dataset. For instance, to
2021-02-21 05:42:36 +08:00
apply the colors only to the circle (dataset 0), leaving the ellipse (dataset 1)
with the default tuple size and style:
2021-02-21 05:35:05 +08:00
#+BEGIN_SRC sh :results file link :exports both
seq 100 | \
2021-02-21 05:42:36 +08:00
perl -nE '$thdeg = $_/100.*360.;
$th = $_/100.*2.*3.14159;
$s=sin($th); $c=cos($th);
if($.%5) { say "$c $s $thdeg" }
else { $s2 = $s/2;
say "$c $s $thdeg $s2"; }' | \
feedgnuplot --domain --square \
--tuplesize 0 3 \
--style 0 'with points palette'
2021-02-21 05:35:05 +08:00
#+END_SRC
#+RESULTS:
2021-02-21 05:42:36 +08:00
[[file:guide-8.svg]]