From: Dan Davison <email@example.com>
To: Sami Airaksinen <firstname.lastname@example.org>
Cc: emacs org-mode mailing list <email@example.com>
Subject: Re: Suggestion to org-R mode
Date: Tue, 07 Jul 2009 23:22:05 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <1245919961.7505.23.camel@leviathan> (Sami Airaksinen's message of "Thu, 25 Jun 2009 11:52:41 +0300")
Sami Airaksinen <email@example.com> writes:
> But to the point: I have "tons" of tables that have different things, so
> that I can keep organized my data (one table with +60 columns is pretty
> clumsy to me). And to produce something meaningful stats I would like to
> combine these tables (I know that putting them to one big table would
> solve my problem).
> So my idea was,
> #+R: intables:"table1","table2",... Rnames:"tab1","tab2",...
> #+R: intables:(table1 tab1)(table2 tab2)...
> or something more generic.
> The goal is that afterwards I could manipulate them as will with raw R,
> #+RR: res <- tab1$varX + tab2$varY #example.
I'd prefer not to add the ability to reference multiple tables to org-R,
as I'm planning for it to be replaced by org-babel[fn:1], which I'm
working on together with Eric Schulte. It's still in development, but
you can already do this in org-babel -- here's a simple example in which
two org tables are referenced:
| 1 | 2 | 3 |
| 4 | 5 | 6 |
| 4 | 5 | 6 |
| 7 | 8 | 9 |
#+begin_src R :var tab1=table1 :var tab2=table2
tab1 + tab2
| 5 | 7 | 9 |
| 11 | 13 | 15 |
There's still work to be done, but if you do want to try it, after
downloading/cloning the code from github use the following lines to load
(add-to-list 'load-path "/path/to/org-babel/lisp")
> I would love to do this myself, but unfortunately my lisp and R skills
> are at best amateurish.
> Best Regards,
> Sami Airaksinen
> Astronomy Department, Physical Sciences
> Oulu University
parent reply other threads:[~2009-07-08 3:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1245919961.7505.23.camel@leviathan>]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).