emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: R.M.Krug@gmail.com
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Problem with babel and R + lattice
Date: Fri, 9 Mar 2012 08:04:15 -0600	[thread overview]
Message-ID: <CA+M2ft9KXe9Yi-gkL24dWsXQC+Q4qcXjeJxFBKWtjyDqGNp9Cg@mail.gmail.com> (raw)
In-Reply-To: <4F59C257.2060401@gmail.com>

On Fri, Mar 9, 2012 at 2:41 AM, Rainer M Krug <r.m.krug@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/03/12 21:52, John Hendy wrote:
>> Drat. I meant to add that when I run the code exactly as I have it from R directly, it works. I
>> literally copy and paste my org-mode babel block code line by line into a terminal and obtain
>> the proper output via tikz. *That's* the perplexing part. What would be working directly from R
>> and not from Org-mode?
>>
>> For reference, I've generated plenty of stuff just like this via org-mode/babel. Come to think
>> of it, even another lattice plot.
>>
>> Not sure how to pinpoint what's goofy about this specific plot.
>>
>> John
>>
>> On Thu, Mar 8, 2012 at 2:40 PM, John Hendy <jw.hendy@gmail.com> wrote:
>>> I have an R block like so:
>>>
>>> #+begin_src R
>>>
>>> library(lattice) library(tikzDevice)
>>>
>>> =bunch of code=
>>>
>>> barchart(side$name~side$x2,groups=side$type,horiz=T,
>>> xlim=c(0,0.75),col=c("lightblue","yellow"),xlab="Product Performance (2-box)")
>>>
>>> dev.off() tools::texi2dvi("bar-2b.tex",pdf=T)
>>>
>>> #+end_src
>>>
>>> The resultant tex file is empty where the tikz code should be and texi2dvi fails. Any
>>> suggestions? If I change my plot to base graphics with barplot, it works. I'm thinking this
>>> is a lattice/babel issue?
>
> As with ggplot, you have to print your plot (if I remember correctly), i.e:
>
> print(barchart(...))

I stumbled on this, too but hadn't posted back to the list yet. What
got me on the track to the solution was copying my babel block code
into an R source file and trying to do = > source("path/to/file")=
directly from R. That wasn't working either, so I knew it was
something I was doing and not org. I found the R faq which said that
source files don't generate output for everything unless you tell them
to print() :)

Thanks!
John


>
> Cheers,
>
> Rainer
>
>>>
>>>
>>> Thanks for any input, John
>>
>
>
> - --
> Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys.
> (Germany)
>
> Centre of Excellence for Invasion Biology
> Stellenbosch University
> South Africa
>
> Tel :       +33 - (0)9 53 10 27 44
> Cell:       +33 - (0)6 85 62 59 98
> Fax :       +33 - (0)9 58 10 27 44
>
> Fax (D):    +49 - (0)3 21 21 25 22 44
>
> email:      Rainer@krugs.de
>
> Skype:      RMkrug
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk9ZwlcACgkQoYgNqgF2egqMewCfar+JxC9uV9p1O2IYVVYcqyeM
> 7/4AnRLp8gYqSDe/74D9helafqNR5Vgt
> =aDVb
> -----END PGP SIGNATURE-----

      reply	other threads:[~2012-03-09 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08 20:40 Problem with babel and R + lattice John Hendy
2012-03-08 20:52 ` John Hendy
2012-03-09  8:41   ` Rainer M Krug
2012-03-09 14:04     ` John Hendy [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=CA+M2ft9KXe9Yi-gkL24dWsXQC+Q4qcXjeJxFBKWtjyDqGNp9Cg@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=R.M.Krug@gmail.com \
    --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).