emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Neil Jerram <neil@ossau.homelinux.net>
To: emacs-orgmode@gnu.org
Subject: Re: babel, matlab export plot to png fails
Date: Tue, 15 Aug 2017 11:12:40 +0200	[thread overview]
Message-ID: <5678702d-9fdc-74ff-443c-fa979185ffca@ossau.homelinux.net> (raw)
In-Reply-To: <87shgveujl.fsf@mat.ucm.es>

On 13/08/17 10:33, Uwe Brauer wrote:
> Hi
>
> I would like to execute some matlab code in org file (using GNU emacs 26
> and the git version of org mode) and save the result of the plot command
> in a png file, so I tried
>
> #+begin_src matlab :session :exports both :file testplot.png
> t=[0:0.1:1];
> y=sin(t);
> plot(t,y)
> print -dpng  testplot.png
> #+end_src
>
> And also
> #+begin_src matlab :results output latex :exports results  :file testplot.png
> t=[0:0.1:1];
> y=sin(t);
> plot(t,y)
> print -dpng  testplot.png
> #+end_src
>
> But the resulting png files are corrupt. I presume also the matlab
> commands are included in the png file which is not correct. But I don't
> know who to achieve that just the last command is saved in a png file.

I guess the problem is that the Matlab line "print -dpng testplot.png" 
is correctly writing the plot to testplot.png, as you want, but then 
org-mode is overwriting that file because of the ":file testplot.png".  
I would try deleting ":file testplot.png".

The meaning of ":results output" may be a bit language-dependent - I 
don't know org-mode well enough to be sure about that yet - but in 
general I would expect it to consist of the standard output of those 
commands.  So, for example, if you type "print -dpng testplot.png" and 
Matlab responds with "Generated 'testplot.png'", I would expect 
":results output" to contain "Generated 'testplot.png'", not the PNG data.

Regards - Neil

  parent reply	other threads:[~2017-08-15  9:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13  8:33 babel, matlab export plot to png fails Uwe Brauer
2017-08-13 14:30 ` John Kitchin
2017-08-16 12:26   ` Uwe Brauer
2017-08-15  9:12 ` Neil Jerram [this message]
2017-08-16 12:28   ` Uwe Brauer
2017-08-16 17:25   ` Berry, Charles
2017-08-16 17:41     ` Eric S Fraga
2017-08-16 17:48       ` Berry, Charles
2017-08-16 18:19         ` Eric S Fraga
2017-08-16 18:29           ` Berry, Charles
2017-08-16 21:52     ` Uwe Brauer
     [not found] <35e27070f72a4368bdf61b972ddef4c6@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-08-15 17:21 ` Eric S Fraga
2017-08-16 12:33   ` Uwe Brauer
2017-08-16 17:10     ` Eric S Fraga
2017-08-17 15:09       ` Uwe Brauer
     [not found]   ` <53741190f80c4e229a9c7f55cf46f1e6@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-08-16 13:07     ` Eric S Fraga
2017-08-16 14:23       ` Adonay Felipe Nogueira

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=5678702d-9fdc-74ff-443c-fa979185ffca@ossau.homelinux.net \
    --to=neil@ossau.homelinux.net \
    --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).