From: Graham Smith <myotisone@gmail.com>
To: Emacs-orgmode@gnu.org
Subject: Re: Org babel R Help
Date: Sun, 21 Mar 2010 09:53:41 +0000 [thread overview]
Message-ID: <2c75873c1003210253q491d221bib59d195a8c9e4e41@mail.gmail.com> (raw)
In-Reply-To: <20100321221848.100245krd2ozqirc@www.studentmail.otago.ac.nz>
Joseph/Dan
>>> 2) Width/Height exports for R graphics output. Do they work?
>>>
>>> I've tried a lot of combinations of :width and :height as exports, and
>>> they don't seem to work at all. I've tried small numbers (1-10), large
>>> numbers (100-2000) and numbers prefixed by "cm" with no luck.
>>
>> Hmm, I'm not seeing a problem here. It works for me with both png and
>> pdf output. E.g.
>>
>> #+begin_src R :file z.pdf :width 20 :height 40 :exports both
>> plot(1:10)
>> #+end_src
>
>> What image format (i.e. R graphics device) are you using? Can you post
>> an example block that is not working? The values for :width and :height
>> will be passed straight on to the graphics device, so their meaning
>> depends on which graphics device is being used in R.
>
> I'm trying the code you posted with the latest org-mode from ubuntu and
> getting nothing in my results if I use png. If I use pdf, I get a really
> tiny chart which is incomprehensible. Width and height seem to work
> randomly, as using 20:40 work with pdf (although tiny), but 100,100 do not
> work at all.
>
> It only works correctly if I use the #+attr_latex: width=Xcm and omit the
> width and height.
Based on what is happening here with me on Ubuntu 9.10, R 2.10 and orgmode 6.34.
The ":file z.pdf :width 20 :height 40 :exports both" is affecting
the size of the graphic that R produces. If you open x.pdf directly
you will find that it changes size as expected.
BUT regardless of the size of the z.pdf, Latex defaults to a fixed,
and tiny, standard size. Unless you give an explicit latex command
#+attr_latex: width=Xcm
> Using babel. For some reason my R graphics embedded within my pdf's don't
> seem to be as "nice" as viewing them from within R, i.e. slightly fuzzy
> edges. It's like the antialiasing has failed or something. The text labels
> on the axes are definitely not up to latex standard.
Are you just viewing them or printing them. I find with Ubuntu that
the default viewer seems to arbitrarily change between programs and
the quality of graphics on the screen varies, but the quality of
printed output stays the same. Try opening the final PDF in an
alternative viewer and see if things still appear the same.
Graham
next prev parent reply other threads:[~2010-03-21 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 8:01 Org babel R Help Joseph Cole
2010-03-19 14:30 ` Dan Davison
[not found] ` <5084fc611003210151x41850afcg36b275679ae76acb@mail.gmail.com>
2010-03-21 9:18 ` Joseph Cole
2010-03-21 9:53 ` Graham Smith [this message]
2010-03-21 14:19 ` Dan Davison
2010-03-21 17:45 ` Graham Smith
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=2c75873c1003210253q491d221bib59d195a8c9e4e41@mail.gmail.com \
--to=myotisone@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).