From mboxrd@z Thu Jan 1 00:00:00 1970 From: JBash Subject: Re: org-plot questions Date: Wed, 22 Oct 2008 13:39:59 -0400 Message-ID: <407c66ac0810221039m6a8015b9x1d2b76c8960e06d2@mail.gmail.com> References: <407c66ac0810220727qd861245p47bbece859899da9@mail.gmail.com> <874p34r6bm.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1525270021==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kshgj-0005zr-Bw for emacs-orgmode@gnu.org; Wed, 22 Oct 2008 13:40:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kshgi-0005zf-4E for emacs-orgmode@gnu.org; Wed, 22 Oct 2008 13:40:05 -0400 Received: from [199.232.76.173] (port=42065 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kshgh-0005zV-UR for emacs-orgmode@gnu.org; Wed, 22 Oct 2008 13:40:03 -0400 Received: from yw-out-1718.google.com ([74.125.46.153]:6299) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Kshgg-00069f-JT for emacs-orgmode@gnu.org; Wed, 22 Oct 2008 13:40:03 -0400 Received: by yw-out-1718.google.com with SMTP id 9so592107ywk.66 for ; Wed, 22 Oct 2008 10:40:00 -0700 (PDT) In-Reply-To: <874p34r6bm.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: emacs-orgmode@gnu.org --===============1525270021== Content-Type: multipart/alternative; boundary="----=_Part_33747_11708305.1224697199992" ------=_Part_33747_11708305.1224697199992 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks, Eric! It's a great tool... I like how it, within org, makes it easy to keep the data organized an yet easily accessible. Another quick org-plot question... I found that to turn on the grid, I use: #+PLOT: set:grid So, to set an axis label, I tried #+PLOT: set:xlabel("Frequency") and #+PLOT: set:xlabel "Frequency" and a few other things, but didn't hit on the right combination. What's the correct syntax? --snip-- > > Notice that you are missing an hline in your table after the headers. > Sorry, I should have seen that. > > > When I try to use the deps option, I either get an error or an undesired > result. For example, if I include > > a "deps:3,4", I get a "Wrong type argument" error. If I enclose the 3,4 > in single quotes (eg. deps:'3,4'), > > > Currently no there is not. In the current setup all of the plot lines > adjacent to a table are collected and used to generate a single plot for > the table. I does seem like a good idea to allow multiple plots from a > single table. Two ideas that come to mind are... > > 1) keep all of the plot lines adjacent with the table, but number them > into any number of different plots. For example the following would > specify plots 1 and 2 for a table > > #+PLOT1: title:"the first plot" > #+PLOT1: ind:1 with:points > #+PLOT2: title:"the second plot on the same table" > #+PLOT2: ind:2 deps:(3 4) with:lines > | Frequency | Amplitude | Phase | Delta | Peak | > |-----------+-----------+-------+-------+------| > | 0.9 | 9 | 6 | 5 | 198 | > | 1.0 | 10 | 9 | 7 | 212 | > | 1.1 | 11 | 8 | 3 | 144 | > | 9.9 | 19 | 12 | 9 | 235 | > | 10.0 | 18 | 7 | 12 | 222 | > | 10.1 | 22 | 14 | 4 | 187 | > | 19.9 | 14 | 11 | 6 | 220 | > | 20.0 | 20 | 15 | 14 | 213 | > | 20.1 | 18 | 16 | 11 | 201 | > > 2) the only other mechanism which occurs to me is to somehow label the > table with a unique ID, and then allow the plot lines to be located > This feature (multiple plots from a single table) would be a very nice addition, with either approach. > > > Thanks for the bug reports and ideas -- Eric > You're welcome, and thanks for your help. Jerry ------=_Part_33747_11708305.1224697199992 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks, Eric!

It's a great tool... I like how it, within org, makes it easy to keep the data organized an yet easily accessible.

Another quick org-plot question...

I found that to turn on the grid, I use:
#+PLOT: set:grid

So, to set an axis label, I tried
#+PLOT: set:xlabel("Frequency")
and
#+PLOT: set:xlabel "Frequency"
and a few other things, but didn't hit on the right combination.  What's the correct syntax?

--snip--

Notice that you are missing an hline in your table after the headers.

Sorry, I should have seen that.

> When I try to use the deps option, I either get an error or an undesired result.  For example, if I include
> a "deps:3,4", I get a "Wrong type argument" error.  If I enclose the 3,4 in single quotes (eg. deps:'3,4'),


Currently no there is not.  In the current setup all of the plot lines
adjacent to a table are collected and used to generate a single plot for
the table.  I does seem like a good idea to allow multiple plots from a
single table.  Two ideas that come to mind are...

1) keep all of the plot lines adjacent with the table, but number them
  into any number of different plots.  For example the following would
  specify plots 1 and 2 for a table

#+PLOT1: title:"the first plot"
#+PLOT1: ind:1 with:points
#+PLOT2: title:"the second plot on the same table"
#+PLOT2: ind:2 deps:(3 4) with:lines
| Frequency | Amplitude | Phase | Delta | Peak |
|-----------+-----------+-------+-------+------|
|       0.9 |         9 |     6 |     5 |  198 |
|       1.0 |        10 |     9 |     7 |  212 |
|       1.1 |        11 |     8 |     3 |  144 |
|       9.9 |        19 |    12 |     9 |  235 |
|      10.0 |        18 |     7 |    12 |  222 |
|      10.1 |        22 |    14 |     4 |  187 |
|      19.9 |        14 |    11 |     6 |  220 |
|      20.0 |        20 |    15 |    14 |  213 |
|      20.1 |        18 |    16 |    11 |  201 |

2) the only other mechanism which occurs to me is to somehow label the
  table with a unique ID, and then allow the plot lines to be located

This feature (multiple plots from a single table) would be a very nice addition, with either approach.


Thanks for the bug reports and ideas -- Eric

You're welcome, and thanks for your help.

Jerry


------=_Part_33747_11708305.1224697199992-- --===============1525270021== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============1525270021==--