From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Out of Order Evaluation
Date: Fri, 21 Mar 2014 09:01:14 +0100 [thread overview]
Message-ID: <87ha6sc75h.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: loom.20140321T020453-841@post.gmane.org
Charles Berry <ccberry@ucsd.edu> writes:
> Andreas Leha <andreas.leha <at> med.uni-goettingen.de> writes:
>
>>
>> Hi Michael,
>>
>> Michael Weylandt <michael.weylandt <at> gmail.com> writes:
>>
>> > Hi,
>> >
>> > I want to put a summary of my analysis at the beginning of a document
>> > using results calculated at the end of the document. Is this possible?
>
> [snip]
>
>> >
>> > Is this possible in a single pass?
>
>
> Not quite. The method suggested by Andreas computes the result twice. If
> there is any randomness in the results (as in the example) you will get a
> different answer in the summary than when the block is later evaluated.
>
Well, you could enter the ':cache yes' world here. Although, for me,
that produced more problems than it solved (since there is no tracking
of dependencies among code blocks in :session mode).
My typical workflow now is something 'less literate': My typical
project Org file will look like this:
--8<---------------cut here---------------start------------->8---
* Execution
This is full of #+call: lines. By (my own) convention, this subtree has
to be evaluated before exporting the next subsection.
* Report
This is the report / presentation.
* Analysis
This contains all the code block to be called from the Execution
subtree.
(Plus usually quite a lot of code blocks from dead ends of the
project...)
--8<---------------cut here---------------end--------------->8---
This solves your problem (and is along the lines Charles suggests as
well), but requires more work than just export the document and is,
thus, less literate.
Regards,
Andreas
>> > I've played with #+NAME and
>> > <<block()>> but haven't gotten the out-of-order evaluation quite
>> > right.
>
> You can use
>
> #+results: the-mean
>
> before
>
> #+NAME: the-mean
> #+begin_src R
> mean(x)
> #+end_src
>
> which is after 'theanalysis' block.
>
> And if the format is not pleasing add a filter that reformats the result.
>
>
>> >
>> > Michael
>> >
>>
>> How about something along:
>>
>> --8<---------------cut here---------------start------------->8---
>> #+TITLE: Test
>> #+AUTHOR: Michael Weylandt
>> #+PROPERTY: header-args:R :session *__R__* :exports both
>>
>> * Summary
>> The mean result was src_R[:exports results :var
> analysisresults=theanalysis()]{mean(unlist(analysisresults))}
>>
>> * Analysis,
>> We do some complicated calculations:
>>
>> #+name: theanalysis
>> #+BEGIN_SRC R
>> x <- rnorm(5)
>> #+END_SRC
>> --8<---------------cut here---------------end--------------->8---
>
>
> It might be better to mark all the blocks in the doc ':eval never'
> and ':exports code' or ':exports none' and put blocks before the first
> headline that do all the calcs from noweb references, and put the #+results
> lines (if you need them) wherever you want them in the doc. Like so:
>
>
>
> #+TITLE: Test
> #+AUTHOR: Michael Weylandt
> #+PROPERTY: header-args:R :session *__R__* :exports both
>
>
> #+NAME: master
> #+BEGIN_SRC R :noweb yes :results silent :exports results
> <<theanalysis>>
> #+END_SRC
>
> * Summary
>
>
> The mean result was src_R[:exports results]{mean(x)}
>
> * Analysis,
> We do some complicated calculations:
>
> #+name: theanalysis
> #+BEGIN_SRC R :eval never :exports code
> x <- rnorm(5)
> #+END_SRC
>
>
> IMO, needing ':exports results' for inline src blocks is a bug not a
> feature.
>
> HTH,
>
> Chuck
next prev parent reply other threads:[~2014-03-21 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 22:02 Out of Order Evaluation Michael Weylandt
2014-03-20 22:13 ` Andreas Leha
2014-03-21 1:34 ` Charles Berry
2014-03-21 8:01 ` Andreas Leha [this message]
2014-03-21 8:15 ` Andreas Leha
2014-03-21 18:51 ` Michael Weylandt
2014-03-24 2:06 ` Eric Schulte
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=87ha6sc75h.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).