From: Paul Stansell <paulstansell@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: using gnuplot's "splot" and "every" commands on org-mode table data
Date: Mon, 23 Sep 2013 14:54:37 +0000 (UTC) [thread overview]
Message-ID: <loom.20130923T165236-625@post.gmane.org> (raw)
In-Reply-To: 87k3ncxeqt.fsf@gmail.com
Hi Eric,
There appears to be a slight bug in the way gnuplot handles blocked
data with missing entries.
An example is provided in the org script at then end of this note.
In the code block gnuplot_1 the use of ':missing "?"' seems to cause
the exported data file to lack the blanks lines that are essential
for the plot. The plot from this code block is incorrect.
In gnuplot_2 ':missing' is not used, but instead 'set datafile missing
"?"' is set explicitly in the gnuplot code block. The plot from this
code block is correct.
Surely gnuplot_1 should produce exactly the same plot as gnuplot_2.
Kind regards,
Paul
Exported data file does not include blank lines.
#+name: gnuplot_1
#+begin_src gnuplot :var d=block_data_missing :missing "?" :results silent
set ticslevel 0
splot d index 0 u 1:2:3 w lp pt 6 ps 5, d index 1 u 1:2:3 w lp pt 6 ps 5
#+end_src
Exported data file includes blank lines.
#+name: gnuplot_2
#+begin_src gnuplot :var d=block_data_missing :results silent
set datafile missing "?"
set ticslevel 0
splot d index 0 u 1:2:3 w lp pt 6 ps 5, d index 1 u 1:2:3 w lp pt 6 ps 5
#+end_src
#+name: block_data_missing
| 1 | 1 | 2 |
| 1 | 2 | 5 |
| 1 | 3 | 10 |
| | | |
| 2 | 1 | 5 |
| 2 | 2 | 10 |
| 2 | 3 | 13 |
| | | |
| 3 | 1 | 10 |
| 3 | 2 | ? |
| 3 | 3 | 18 |
| | | |
| | | |
| 1 | 1 | 12 |
| 1 | 2 | 15 |
| 1 | 3 | 20 |
| | | |
| 2 | 1 | 15 |
| 2 | 2 | 18 |
| 2 | 3 | 23 |
| | | |
| 3 | 1 | ? |
| 3 | 2 | 23 |
| 3 | 3 | 28 |
next prev parent reply other threads:[~2013-09-23 14:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 14:39 using gnuplot's "splot" and "every" commands on org-mode table data Paul Stansell
2013-05-03 16:09 ` Eric Schulte
2013-05-06 18:57 ` Achim Gratz
2013-05-09 12:54 ` Eric S Fraga
2013-05-09 20:23 ` Achim Gratz
2013-05-09 20:42 ` Eric S Fraga
2013-05-11 10:39 ` Achim Gratz
2013-05-11 12:20 ` Rick Frankel
2013-05-21 12:36 ` Eric S Fraga
2013-05-07 17:14 ` Paul Stansell
2013-05-07 18:25 ` Eric Schulte
2013-05-07 18:39 ` Paul Stansell
2013-05-08 12:46 ` Eric Schulte
2013-05-08 15:48 ` Paul Stansell
2013-05-13 21:43 ` Eric Schulte
2013-05-17 15:00 ` Eric Schulte
2013-05-17 20:18 ` Paul Stansell
2013-05-17 20:39 ` Eric Schulte
2013-05-17 21:33 ` Paul Stansell
2013-08-30 17:16 ` Paul Stansell
2013-08-30 19:13 ` Achim Gratz
2013-05-07 18:19 ` Paul Stansell
2013-05-08 12:41 ` Eric Schulte
2013-05-08 16:00 ` Paul Stansell
2013-05-12 18:55 ` Achim Gratz
2013-05-13 21:38 ` Eric Schulte
2013-05-14 7:06 ` Achim Gratz
2014-03-25 18:42 ` Achim Gratz
2013-05-11 10:51 ` Achim Gratz
2013-09-23 14:54 ` Paul Stansell [this message]
2013-09-23 23:32 ` Eric Schulte
2013-09-24 12:05 ` Paul Stansell
2013-09-25 18:21 ` Eric Schulte
2013-09-25 20:01 ` Paul Stansell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20130923T165236-625@post.gmane.org \
--to=paulstansell@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).