Jordi Gutiérrez Hermoso | 29 Jan 19:44 2015

Trouble with the mailing lists

If you're having trouble sending email to any  <at> mailing
list, use octave-help <at> or octave-maintainers <at> instead.

We are having trouble with the redirects from maintainers <at>
and help <at> Hopefully this will be fixed soon.

- Jordi G. H.

Mudit Sharma | 29 Jan 13:20 2015

A proposal

Can algorithms be developed for performing lu,qr&cholesky decompositions this SoC?

Ben Abbott | 28 Jan 22:00 2015

Re: Release Ideas

> On Jan 28, 2015, at 3:54 PM, Marius Schamschula <lists <at>> wrote:
> On Jan 28, 2015, at 2:48 PM, Ben Abbott <bpabbott <at>> wrote:
>>> On Jan 28, 2015, at 3:24 PM, John W. Eaton <jwe <at>> wrote:
>>> On 01/28/2015 02:50 PM, John Swensen wrote:
>>>> I know it is a cop-out, but is it really too hard to ask people to go to a terminal and type:
>>> Yeah, I suspect it is.
>>>> ruby -e "$(curl -fsSL"
>>>> and then type:
>>>> brew tap homebrew/science
>>>> brew install gfortran
>>>> brew update && brew upgrade
>>>> brew install gcc
>>>> brew install octave
>>>> I know this is a bit harder, but for a "unsupported" platform it is still quite easy. The only issue is
that for the homebrew recipe that the gui is not the default and you have to run "octave --force-gui"
>>> How long does this process take for someone who is installing everything for the first time?
>>> Even if you scripted this and put a pretty GUI "one-click" installer around it, I suspect most users
would find it annoying that it takes possibly hours to install while the system is quite busy.
>>> Also, if it is this simple to build Octave from homebrew, why do we see so many people complaining about
how hard it is to build Octave for OS X?
>> I think the biggest hurdle for Mac OSX is that Yosemite's clang has broken a some things. Both Fink and
Macports are now able to build 3.8.2 on Yosemite, but those solutions do not work for me using the default
branch. My impression (and not a reliable one) is that I'll need clang 6 before a build can be successful..
>>> Finally, if it is this simple, then why hasn't anyone turned the resulting binaries into a simple
installer?  Is that part difficult?
>> That would be easy, but Octave would end up installed in the directory structure reserved for Homebew,
Macports, or Fink.
> Not necessarily. Years ago when we built the OS X version of CISM_DX, see
<>, we built octave using MacPorts, but installed it
into a custom path.
> Marius

I've done that myself. I even modified it to install as a relocatable bundle ... but it wasn't an easy task. If
we don't make it relocatable, is there a way to enure there isn't a conflict?


Jordi Gutiérrez Hermoso | 28 Jan 17:44 2015

OctConf 2015 survey results

There have been only 14 people so far who have responded about where
would they like OctConf 2015 to happen, but I'm going to close it now:
it's a near perfect tie between UK, Germany, and Austria, with 5, 4,
and 5 votes respectively.

How odd, nobody seems to want to go to Italy?

Anyway, I say we should just go with the UK. We have at least one or
two Octave core developers there, the location is fairly central
between America and Europe, and almost all of us will speak the local

Carnë, Colin, can you really do it?

Germans, Austrians, Italians, do you want to make a case for why we
should go to your countries instead of the UK?

- Jordi G. H.

Carnë Draug | 28 Jan 14:01 2015

shared-mime-info: distinguish x-octave and x-matlab files


currently, shared-mime-info [1] treats x-octave as an alias of x-matlab.
It does this despite using "##" as magic to identify the file as Matlab.
The most obvious problem of this is with text editors picking Matlab as
syntax highlight for Octave code.  My take on the two mime types, is that
having the file written in Octave does not matter, what matters where it
can run.  This means that a file written in Octave that is Matlab compatible
deserves a x-matlab mime.

I submitted them a patch that splits them into two types and added magic
to recognize a shebang line for an octave interpreter [2].  In addition,
it also replaces the common "##" magic with "#" for Octave and "%" for
Matlab.  However this last got rejected since this seems to be too small
of magic for their new standards.  Can anyone suggest new magic that
would help in distinguish between code that is meant to be Octave only
and Matlab compatible?

Another thing I would suggest is to start adding a shebang line to our
Octave files.  This has two advantages, 1) make it easier for such
applications to recognize the file as Octave source, and 2) raise awareness
that it is possible to actually write an Octave program (I think this is a
really nice feature of Octave that it is not given enough attention).



P.S.: to have this fixed in your local machine, create an octave.xml file
in "~/.local/share/mime/packages/" with the magic you want and then run
"update-mime-database ~/.local/share/mime/"

Rik | 28 Jan 03:20 2015

Re: GUI release

On 01/27/2015 04:35 PM, octave-maintainers-request <at> wrote:
Re: Release Ideas
"John W. Eaton" <jwe <at>>
01/27/2015 04:35 PM
Michael Godfrey <michaeldgodfrey <at>>, octave-maintainers <at>
<mailto:octave-maintainers <at>>
<54C801CD.5090705 <at>> <54C821E8.7040309 <at>>
<54C821E8.7040309 <at>>
<54C82EC7.7040200 <at>>
text/plain; charset=utf-8; format=flowed

On 01/27/2015 06:40 PM, Michael Godfrey wrote:

Unless there is something blocking default, why not just make one
release (default already has all the
GUI code).

We deprecated some things in 3.8 that have already been removed from default but not gui-release.  Normally we have one release that still contains the deprecated functions but warns if they are used.  Skipping the gui-release release and going straight to default would break this promise that we normally make.  Not a huge thing, I suppose, but something we should consider if we decide to just release default.


I don't think we want to wait much longer for a GUI release.  The development branch continues to make great strides, but it is rapidly diverging from the gui-release branch.  I would prefer to see us keep the promise about maintaining deprecated code for two releases.

In terms of what to do, there is a checklist of activities for a release on the wiki at  One of the first priorities is figuring out which bugs require fixing before the release and which would only be nice to fix.  In the past we have tried to fix all segmentation faults, all regressions, and any bugs with a severity > 4.  A quick search on Savannah shows that there are 38 bugs marked as crashes.  One thing that becomes apparent is that the GUI has a lot of trouble running and plotting under Mac OS X.  Certainly we will need to have some sort of solution for that OS.

My main concern is the slow down in performance in Octave under the GUI.  As a quick gauge I tried runtests on the corefcn directory.  See below.

--Benchmark Code--
more off
t0 = cputime(); runtests ("libinterp/corefcn"); t1 = cputime(); t1 - t0
--End Code--

hg: 101ce4eaa56c (gui-release)

./run-octave -f
time : 145.40

./run-octave -f --no-gui-libs
time : 80.489

Built with --disable-atomic-refcounts

./run-octave -f
time : 126.40

./run-octave -f --no-gui-libs
time : 71.136
There is about an 80% decrease in performance when running the GUI.  It seems like maybe the update frequency for items in the Variable Browser pane could be slower when Octave is fully engaged making a calculation.

John W. Eaton | 27 Jan 22:23 2015

Release Ideas

It's been a long time since 3.8.0.

What's required for the gui-release branch to be released?  My list 
really only has

   Use Qt widgets for plotting with the GUI

I've been working a little bit on adding buttons and making zooming work 
with the mouse wheel.  I hope to push some changes for those things 
later this week.

Beyond that, I think the GUI is in pretty good shape.  Sure, a lot of 
issues have been reported, but I think it is more than usable at this point.

I'd like to follow that release relatively soon with a release from what 
is now the default branch because it has a lot more bug fixes that 
should probably be in a released version of Octave.

What show-stopping bugs need to be fixed on either branch before we make 
a release?


Carnë Draug | 26 Jan 21:49 2015

database 2.3.1 released

Hi everyone

a new release of the database package [1] is out, version 2.3.1, by Olaf Till.
A summary of important user-visible changes is also available online [2].

This package provides an interface to SQL databases, although currently
only postgresql is supported via libpq.

Enjoy Octave responsibly,


devdoot Ghosh | 26 Jan 16:29 2015

GSOC 2015

I am an engineering student. I have deep knowledge of graphics ,data structures,numerical integration and differential calculus using MATLAB . Will it be necessary to also learn topics in statistics to apply for any project undertaken by your organisation in Gsoc 2015?  
Randy Woodman | 26 Jan 17:08 2015

Octave chops


We're launching a Beta Test on Feb. 16th 2015. and are in need of Octave pros. with large amounts of data to filter.

To get a better idea of what we're doing please go to and see the document page.

If you'd be interested in helping please email me Randy.woodman <at>

Thanks, Randy 

Randy Woodman Vice President
of Marketing/Business Development

P.O. Box 16025
Seattle, WA 98116
917.626.4394 (Mobile)

 "Technology changes are revolutionary, not evolutionary."
Carnë Draug | 25 Jan 15:09 2015

linear-algebra 2.2.1 released

Hi everyone

a new release of the linear-algebra package [1] is out, version 2.2.1, by
Philip Nienhuis.  A summary of important user-visible changes is also
available online [2].

This package provides additional linear algebra code, including general
SVD and matrix functions.

Enjoy Octave responsibly,