emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Including multiple plots resulting from a loop of R code in LaTeX
Date: Sun, 26 Aug 2012 22:15:41 -0500	[thread overview]
Message-ID: <CA+M2ft9e4VKNsaHb9=aVxSWmOAaR3f2WFPUta3Rb1xGZQKTceQ@mail.gmail.com> (raw)
In-Reply-To: <87wr0p4l0h.fsf@gmx.com>

On Thu, Aug 23, 2012 at 11:43 AM, Eric Schulte <eric.schulte@gmx.com> wrote:
> John Hendy <jw.hendy@gmail.com> writes:
>> I'm conducting some neural network analysis, and the results are
>> highly dependent on the random seed set prior to creating the model. I
>> loop through seeds 1-500, storing the predicted values in one data
>> frame and a table of mean sum of squared errors in another table.
>> Then, I use ggplot to create only the 10 or so plots with the lowest
>> error. The loop is something like this:
>> ----------
>> for(i in 1:10) {
>> filename <- paste("neuralnet-","-seed-",as.character(mse[i,1]),".pdf", sep="")
>> pdf(filename, width=12, height=8)
>> [ggplot code]
>> dev.off()
>> ----------
>> What I want to know is how to include the resultant files in LaTeX
>> export. Since my model runs and then sorts by error, I don't know
>> which seeds produce the best files beforehand, so I'd have to look at
>> the error table and manually insert the plot names by hand. Changing
>> results means changing file names by hand again.
>> Any suggestions for things like this where the output of a babel block
>> is not a single file?
> Have you tried using header arguments like the following.
> :results output raw :exports results
> and then printing the file names (including the Org-mode link syntax) to
> STDOUT from within your R code block.

Disregard the previous. I found that I should be using cat(paste(...))
instead of print(), since that removes the [1] from each line.

| cat(paste("[[../plots/",filename,"]]",sep=""), sep="\n\n")

still gives me output in orgmode of filenames with no new lines in
between so my plots are being printed 4-up on a page (2 wide, 2 tall)
instead of only 1 wide and 2 tall. If I manually enter new lines in
between the output file names, they behave as they should. How do I
get org to accept the extra newlines I'm trying to add? Executing in
the R session itself behaves as expected and does space the lines.


> If I understand correctly that should result in the behavior you're
> after.
> Best,
>> Thanks,
>> John
> --
> Eric Schulte
> http://cs.unm.edu/~eschulte

  parent reply	other threads:[~2012-08-27  3:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 17:41 Including multiple plots resulting from a loop of R code in LaTeX John Hendy
2012-08-23 16:43 ` Eric Schulte
2012-08-27  2:58   ` John Hendy
2012-08-27  3:15   ` John Hendy [this message]
2012-08-27  3:24     ` John Hendy
2012-08-27 20:16       ` John Hendy
2012-08-27 20:40         ` Nick Dokos
2012-08-27 21:40           ` John Hendy
2012-08-27 20:50         ` Eric Schulte
2012-08-27 21:37           ` John Hendy

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:

  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='CA+M2ft9e4VKNsaHb9=aVxSWmOAaR3f2WFPUta3Rb1xGZQKTceQ@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric.schulte@gmx.com \


* 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).