From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: using a table from one org-file as a variable in a code block in another org-file
Date: Mon, 26 Nov 2012 19:50:36 -0500 [thread overview]
Message-ID: <CAJ51ETpda_JDtR7qs1b_+WunBV9R5yXZMO-BbmX--=M13PgRTQ@mail.gmail.com> (raw)
In-Reply-To: <87lido46el.fsf@gmail.com>
That is pretty awesome! Thanks!
John
-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Mon, Nov 26, 2012 at 12:32 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> Hi everyone,
>>
>> I have been using tables as variables for codeblocks on an org-file, e.g.
>> #+tblname: class-data
>> | user | oxide | xc |
>> | jkitchin | TiO2 | LDA|
>> ...
>>
>> #+BEGIN_SRC python :var data=class-data
>> from pylab import *
>> import numpy as np
>>
>> vol = [x[1] if x[1] != '' else np.nan for x in data]
>> B = [x[2] if x[2] != '' else np.nan for x in data ]
>>
>> scatter(vol, B)
>> xlabel('Volume ($\AA^3$)')
>> ylabel('Bulk modulus (GPa)')
>> title('All polymorphs of all oxides for all functionals')
>> show()
>> #+END_SRC
>>
>> This is a fantastic feature, since I can have some code that is
>> expensive to run create the table, but then have analysis code that is
>> quick, since it only reads the table.
>>
>> But, sometimes the tables are defined in other org-files. Is there a
>> way to specify a table from another org-file in the variable header?
>>
>> Something like this would be pretty handy:
>>
>> :var ./org-file.org::class-data
>>
>> Especially if I could click on it, and have it open the other org-file
>> with point at the table!
>>
>> Any thoughts? Thanks,
>>
>
> Hi John,
>
> This feature does exist, and your guess at the syntax is almost correct.
> To reference a variable named foo1 in a file named foo.org you would use
> the following syntax, ":var data=foo.org:foo1".
>
> See the attached foo.org and bar.org files for an example (in order to
> work they must be in the same directory).
>
> I'll make a note to mention this functionality in the documentation.
>
> Best,
>
>
>
>>
>> John
>>
>> -----------------------------------
>> John Kitchin
>> Associate Professor
>> Doherty Hall A207F
>> Department of Chemical Engineering
>> Carnegie Mellon University
>> Pittsburgh, PA 15213
>> 412-268-7803
>> http://kitchingroup.cheme.cmu.edu
>>
>
> --
> Eric Schulte
> http://cs.unm.edu/~eschulte
>
prev parent reply other threads:[~2012-11-27 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 16:47 using a table from one org-file as a variable in a code block in another org-file John Kitchin
2012-11-26 17:32 ` Eric Schulte
2012-11-27 0:50 ` John Kitchin [this message]
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='CAJ51ETpda_JDtR7qs1b_+WunBV9R5yXZMO-BbmX--=M13PgRTQ@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/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).