# Changes

,  00:30, 23 October 2019
Line 1: Line 1:
This is a list of frequently asked questions (FAQ) for GNU Octave users.

This is a list of frequently asked questions (FAQ) for GNU Octave users.
−
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes. If you have general questions about GNU Octave, or need help for something that is not covered by the Octave manual or the FAQ, please use the [https://mailman.cae.wisc.edu/listinfo/help-octave help@octave.org mailing list].
+
−
This FAQ is intended to supplement, not replace, the GNU Octave manual. Before posting a question to the [https://mailman.cae.wisc.edu/listinfo/help-octave help@octave.org mailing list], you should first check to see if the topic is covered in the manual.
+
=Where do I get additional help?=
+

+
If you can't find an answer to your question in this FAQ, wiki, or in the [http://www.octave.org/doc/interpreter manual] ([http://www.octave.org/octave.pdf PDF]) you can:
+

+
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]
+
* Contact our user community using our [https://lists.gnu.org/mailman/listinfo/help-octave help@octave.org mailing list] (feel free to subscribe to this mailing list)
+
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]
+

+
<div class="tocinline">__TOC__</div>

=General=

=General=
Line 9: Line 17:
==What is Octave?==

==What is Octave?==
−
GNU Octave is a high-level interactive language, primarily intended for numerical computations, that is mostly compatible with Matlab.
+
[https://www.gnu.org/software/octave/ GNU Octave] is a high-level interpreted language, primarily intended for numerical computations. It provides capabilities for the numerical solution of linear and nonlinear problems, and for performing other numerical experiments.  It also provides extensive graphics capabilities for data visualization and manipulation.  GNU Octave is normally used through its interactive interface ([https://en.wikipedia.org/wiki/Command-line_interface CLI] and [https://en.wikipedia.org/wiki/Graphical_user_interface GUI]), but it can also be used to write non-interactive programs.

+
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.
GNU Octave can do arithmetic for real, complex or integer-valued scalars and matrices, solve sets of nonlinear algebraic equations, integrate functions over finite and infinite intervals, and integrate systems of ordinary differential and differential-algebraic equations.
−
GNU Octave uses the GNU readline library to handle reading and editing input. By default, the line editing commands are similar to the cursor movement commands used by GNU Emacs, and a vi-style line editing interface is also available. At the end of each session, the command history is saved, so that commands entered during previous sessions are not lost.
+
The GNU Octave distribution includes a [http://www.octave.org/octave.pdf 1000+ page Texinfo manual].  Access to the complete text of the manual is available via the <code>doc</code> command at the GNU Octave prompt.
−
The GNU Octave distribution includes a 650+ page Texinfo manual. Access to the complete text of the manual is available via the doc command at the GNU Octave prompt.
+
==What is Octave Forge?==
−
==What is Octave-Forge?==
+
[https://octave.sourceforge.io/ Octave Forge] is a collection of [[packages]] for GNU Octave, something similar to the Matlab toolboxes. When talking about the two projects at the same time, GNU Octave is usually referred to as Octave core (or just "core"). Octave Forge also serves as a test bed for code that may eventually end up in the core, and distributes binaries for systems with a lack of developers tools (mainly Windows).
[http://octave.sourceforge.net/ Octave-Forge] is a collection of packages for GNU Octave, something similar to the Matlab toolboxes. When talking about the two projects at the same time, GNU Octave is usually referred to as Octave core (or just ''core''). [http://octave.sourceforge.net/ Octave-Forge] also serves as a test bed for code that may eventually end up in the core, and distributes binaries for systems with a lack of developers tools (mainly Windows).

==Who uses Octave?==

==Who uses Octave?==
−
Lots of people. It seems that universities use it for research and teaching, companies of all sizes, for development, individuals. This question comes often on Octave mailing lists, see [[Who Uses Octave?]] for a few answers
+
Lots of people. Universities use it for research and teaching, companies of all sizes for development, and individuals for whatever private purpose. See [[Who Uses Octave?]] for a few answers.

==Who develops Octave?==

==Who develops Octave?==
−
Discussions about writing the software that would eventually become Octave started in about 1988 with James B. Rawlings and John W. Eaton at the University of Texas. John W. Eaton was the original author of Octave, starting full-time development in February 1992. He is still the primary maintainer. The community of users/developers has in addition contributed some code and fuels the discussion on the mailing lists help@octave.org (user forum), maintainers@octave.org (development issues).
+
Discussions about writing the software that would eventually become Octave started in about 1988 with James B. Rawlings and [http://jweaton.org/ John W. Eaton] at the University of Texas. John W. Eaton is the original author of Octave, starting full-time development in February 1992. He is still the primary maintainer. The community of users and developers has in addition contributed some code and fuels the discussion on the mailing lists [https://lists.gnu.org/mailman/listinfo/help-octave help@octave.org] (user forum), [https://lists.gnu.org/mailman/listinfo/octave-maintainers maintainers@octave.org] (development issues).

==Why "Octave"?==

==Why "Octave"?==
−
Octave's name has nothing to do with music. It's named after [http://en.wikipedia.org/wiki/Octave_Levenspiel Octave Levenspiel], a former professor of John who was famous for his ability to do quick back-of-the-envelope calculations. You can hear John pronounce the name "Octave" a few times [http://videolectures.net/mloss08_eaton_oct/ in this video]. We hope that GNU Octave will help perform computations with the same ease as Dr. Levenspiel.
+
Octave's name has nothing to do with music. It is named after [http://en.wikipedia.org/wiki/Octave_Levenspiel Octave Levenspiel], a former professor of John who was famous for his ability to do quick back-of-the-envelope calculations. You can hear John pronounce the name "Octave" a few times [http://videolectures.net/mloss08_eaton_oct/ in this video]. We hope that GNU Octave will help perform computations with the same ease as Dr. Levenspiel.

−
==Why <em>GNU</em> Octave?==
−

−
The GNU Project was launched in 1984 to develop a complete Unix-like operating system which is free software: the GNU system.
−

−
GNU is a recursive acronym for “GNU's Not Unix”; it is pronounced guh-noo, approximately like canoe.
−

−
The Free Software Foundation (FSF) is the principal organizational sponsor of the GNU Project.
−

−
Octave became GNU Octave in 1997 (beginning with version 2.0.6). This meant agreeing to consider Octave a part of the GNU Project and support the efforts of the FSF. A big part of this effort is to adhere to the [http://www.gnu.org/prep/standards/standards.html GNU coding standards] and to benefit from GNU's infrastructure (e.g. [http://hg.savannah.gnu.org/hgweb/octave/ code hosting] and [http://bugs.octave.org bug tracking]). Additionally, Octave receives [https://my.fsf.org/donate/working-together/octave sponsorship] from the FSF's Working Together fund. However, Octave is not and has never been developed by the FSF.
−

−
−

−
==What version should I use?==
−

−
In general, you will find the latest version on http://www.octave.org/download.html. It is recommended to use the stable version of octave for general use, and the development version if you want the latest features and are willing to tolerate instability.
−

−
A list of user-visible changes since the last release is available in the file NEWS. The file ChangeLog in the source distribution contains a more detailed record of changes made since the last release.
−

−
==On what platforms does Octave run?==
−

−
Octave runs on various Unices—at least Linux and Solaris, Mac OS X, Windows and anything you can compile it on. Binary distributions exist at least for Debian, SUSE, Fedora and RedHat Linuxes (Intel and AMD CPUs, at least), for Mac OS X and Windows' 98, 2000, XP, Vista, and 7.
−

−
Two and three dimensional plotting is fully supported using gnuplot and an experimental OpenGL backend.
−

−
The underlying numerical solvers are currently standard Fortran ones like LAPACK, LINPACK, ODEPACK, the BLAS, etc., packaged in a library of C++ classes. If possible, the Fortran subroutines are compiled with the system's Fortran compiler, and called directly from the C++ functions. If that's not possible, you can still compile Octave if you have the free Fortran to C translator f2c.
−
Octave is also free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 3, as published by the Free Software Foundation, or at your option any later version.
+
==Why "GNU" Octave?==
−
==Why are the developers planning to replace Gnuplot with an OpenGL backend?==
+
The [https://www.gnu.org/ GNU Project] was launched in 1984 to develop a complete Unix-like operating system which is free software: the GNU system.  GNU is a recursive acronym for "GNU's Not Unix"; it is pronounced [https://www.gnu.org/gnu/pronunciation.en.html g'noo].
−
The development of Octave is committed to being both compatible with Matlab and adding additional features. Toward those ends, the development community has chosen to introduce a native OpenGL backend that supports Matlab handle graphics and its uicontrols. Starting with the 3.8 release, Octave now uses OpenGL graphics by default with FLTK widgets. A Qt OpenGL toolkit is also [https://github.com/goffioul/QtHandles under development].
+
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organizational sponsor of the GNU Project.
−
There are no plans to remove the gnuplot backend. While a better backend may some day become the new default plotter, the gnuplot backend will still be available as long as our users find it useful.
+
Octave became GNU Octave in 1997 (beginning with [[Release History|version 2.0.6]]).  This meant agreeing to consider Octave a part of the GNU Project and support the efforts of the FSF.  A big part of this effort is to adhere to the [https://www.gnu.org/prep/standards/standards.html GNU coding standards] and to benefit from GNU's infrastructure (e.g. [https://hg.savannah.gnu.org/hgweb/octave/ code hosting] and [http://bugs.octave.org bug tracking]).  Additionally, Octave receives [https://my.fsf.org/donate/working-together/octave sponsorship] from the FSF's Working Together fund.  However, Octave is not and has never been developed by the FSF.

==How can I cite Octave?==

==How can I cite Octave?==
−
Pointing to http://www.octave.org is good, because that gives people a direct way to find out more. If citation of a URL is allowed by the publisher you can use this entry (update year and version accordingly!):
+
Octave is free software and does not legally bind you to cite it. However, we have invested a lot of time and effort in creating GNU Octave, and we would appreciate if you would cite if you used.  To cite GNU Octave in publications use:
−
<nowiki>@MISC{octave:2014,
+
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).
author = {{Octave community}},
+
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.
keywords = {Octave,Software},
+
URL https://www.gnu.org/software/octave/doc/v{{Release}}/
title = {{GNU Octave 3.8.1}},
−
url = {www.gnu.org/software/octave/},
−
year = {2014}
−
}</nowiki>
−
if you also want to point to a traditional reference, then you can cite the Octave manual:
+
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:
−
<nowiki>@BOOK{eaton:2009,
+
@manual{,
author    = {John W. Eaton and David Bateman and S\oren Hauberg},
+
title    = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},
title    = {{GNU Octave} version 3.0.1 manual: a high-level interactive language for numerical computations},
+
author    = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},
publisher = {CreateSpace Independent Publishing Platform},
+
year      = <span>{</span>{{Release Year}}},
year      = {2009},
+
url      = {https://www.gnu.org/software/octave/doc/v{{Release}}/},
note      = {{ISBN} 1441413006},
+
}
url      = {http://www.gnu.org/software/octave/doc/interpreter},
−
}</nowiki>
+
Run {{manual|citation}} at the Octave prompt for details on how to best cite the Octave version you are running.  Certain Octave packages also have recommended citations in which case use <code>citation package_name</code>.
−
If you want to acknowledge Octave instead of citing it, you can use text such as this:
+
Note that there are two reasons for citing the software used.  One is giving recognition to the work done by others which we already addressed.  The other is giving details on the system used so that experiments can be replicated.  For this, you should cite the version of Octave and all packages used (you can get this information using the <code>ver</code> command), as well as any details of your setup as part of your Methods.  In addition, you should make your source available.  See [http://software.ac.uk/so-exactly-what-software-did-you-use How to cite and describe software] for more details and an in depth discussion.
−
<blockquote>
+
==What documentation exists for Octave?==
The data has been numerically analyzed with the free software package GNU Octave.
−
</blockquote>
−

−
or
−

−
<blockquote>
−
This work made use of the free software package GNU Octave, and the authors are grateful for the support of the Octave development community.
−
</blockquote>
−

−
==When will feature X be released or implemented?==
−
When it's ready, sooner if you help. Send us patches if you can. We like patches. If you can't, some developers may be convinced to work on your specific problem for some money.
−

−
==How can I get involved in Octave development?==
−

−
Be around. Be social. Participate in the [https://mailman.cae.wisc.edu/listinfo/help-octave help] and [https://mailman.cae.wisc.edu/listinfo/octave-maintainers maintainers] mailing lists. Find things about Octave you don't like, and start thinking about how to fix them. Many people who now contribute to Octave first spent several years helping in the mailing list before they started to delve into the code. A good way to learn Octave is to understand the problems other people are having with it, so being helpful in the mailing lists not only helps Octave as a whole, but it also prepares you to be a better Octave contributor.
−
If you feel ready to dive right into the code, read [[Hacking | here]] and [http://www.gnu.org/software/octave/get-involved.html here] for guidance. One of the best ways for understanding how Octave works is to [[Debugging Octave|run it in a debugger]].
+
Besides this wiki, the GNU Octave distribution includes a [http://www.octave.org/doc/interpreter 1000+ page Texinfo manual] ([http://www.octave.org/octave.pdf PDF]). Access to the complete text of the manual is available via the {{manual|doc}} command at the GNU Octave prompt.  If you have problems using this manual, or find that some topic is not adequately explained, indexed, or cross-referenced, please report it on http://bugs.octave.org.
−
We also need help with this wiki and the [http://www.gnu.org/software/octave/doc/interpreter/ manual]. These are also important tasks. The documentation is easier to patch, so you can discuss improvements to it and submit patches. Or just edit this wiki!
+
==How can I report a bug in Octave?==
−
Accurate bug reporting is also very useful. Find and report [http://www.gnu.org/software/octave/bugs.html bugs], making an attempt to diagnose them. Eventually, you will also know how to fix them. If you want to help with bug reports or patches, subscribe to [https://savannah.gnu.org/mail/?group=octave the bug tracker mailing list]. You'll get updates on all bug activity, and you can jump in when you see something you can help with.
+

−
Look at our [[Projects]] and [[Summer of Code Project Ideas]] if you need specific inspiration for coding tasks that we would like to get done. See also the list of [[short projects]].

=Licensing issues=

=Licensing issues=
Line 121: Line 79:
==If I write code using Octave do I have to release it under the GPL?==

==If I write code using Octave do I have to release it under the GPL?==
−
The answer depends on precisely how the code is written and how it works.
+
The answer depends on precisely how the code is written and how it works:
−
Code written entirely in the scripting language of Octave (interpreted code in .m files) may be released under the terms of whatever license you choose.
+
* Code written '''entirely in the scripting language of Octave''' (interpreted code in .m files) may be released under the terms of whatever license you choose.
−
Code written using Octave's native plug-in interface (also known as a .oct file) necessarily links with Octave internals and is considered a derivative work of Octave and therefore must be released under terms that are compatible with the GPL.
+
* Code written using [https://www.gnu.org/software/octave/doc/interpreter/Oct_002dFiles.html Octave's native code interface] (also known as a .oct file) necessarily links with Octave internals and is considered a derivative work of Octave.  Therefore it must be released under terms that are compatible with the [https://www.gnu.org/licenses/gpl.html GPL].
−
Code written using Octave's implementation of the Matlab MEX interface may be released under the terms of whatever license you choose, provided that the following conditions are met:
+
* Code written using [https://www.gnu.org/software/octave/doc/interpreter/Mex_002dFiles.html Octave's implementation of the Matlab MEX interface] may be released under the terms of whatever license you choose, provided that the following conditions are met:
−
# The plugin should not use any bindings that are specific to Octave. In other words, the MEX file must use the MEX interface only, and not also call on other Octave internals. It should be possible in principle to use the MEX file with other programs that implement the MEX interface (e.g., Matlab).
+
:# The MEX file may not use any bindings that are specific to Octave, '''it has to use the MEX interface only'''.  In other words, it should be possible in principle to use the MEX file with other programs that implement the MEX interface (e.g., Matlab).  For example including an Octave header file or calling an Octave function within the MEX file, that is not related with Octave's implementation of the MEX interface make the MEX file a derivative work of Octave and has therefore to be released under terms that are compatible with the [https://www.gnu.org/licenses/gpl.html GPL].
# The MEX file should not be distributed together with Octave in such a way that they effectively create a single work. For example, you should not distribute the MEX file and Octave together in a single package such that Octave automatically loads and runs the MEX file when it starts up. There are other possible ways that you might effectively create a single work; this is just one example.
+
:# The MEX file may not be distributed together with Octave in such a way that they effectively create a single work. For example, you should not distribute the MEX file and Octave together in a single package such that Octave automatically loads and runs the MEX file when it starts up. There are other possible ways to effectively create a single work; this is just one example.
−
A program that embeds the Octave interpreter (e.g., by calling the "octave_main" function), or that calls functions from Octave's libraries (e.g., liboctinterp, liboctave, or libcruft) is considered a derivative work of Octave and therefore must be released under terms that are compatible with the GPL.
+
* Code that '''embeds the Octave interpreter''' (e.g., by calling the <code>octave_main</code> function), or that calls functions from Octave's libraries (e.g., liboctinterp, liboctave, or libcruft) is considered a derivative work of Octave and therefore must be released under terms that are compatible with the GPL.
−
==Since the MEX interface allows plugins to be distributed under terms that are incompatible with the GPL, does this mean that you are encouraging people to write non-free software for Octave?==
+
==Will you change the license of the Octave libraries for me?==
−
No. The original reason for implementing the MEX interface for Octave was to allow Octave to run free software that uses MEX files (the particular goal was to run SundialsTB in Octave). The intent was to liberate that software from Matlab and increase the amount of free software available to Octave users, not to enable people to write proprietary code for Octave. For the good of the community, we strongly encourage users of Octave to release the code they write for Octave under terms that are compatible with the GPL.
+
'''No.''' Instead of asking us to change the licensing terms for Octave, we recommend that you release your program under terms that are compatible with the GPL.  This way the free software community can benefit from your work the same as you have benefited from the work of all the people who have contributed to Octave.
−
==I wrote a program that links with Octave libraries and I don't want to release it under the terms of the GPL. Will you change the license of the Octave libraries for me?==
+
==Should I favor the MEX interface to avoid the GPL?==
−
No. Instead of asking us to change the licensing terms for Octave, we recommend that you release your program under terms that are compatible with the GPL so that the free software community can benefit from your work the same as you have benefited from the work of all the people who have contributed to Octave.
+
'''No.''' The original reason for implementing the [https://www.gnu.org/software/octave/doc/interpreter/Mex_002dFiles.html MEX interface] for Octave was to allow Octave to run free software that uses MEX files (the particular goal was to run [https://computation.llnl.gov/projects/sundials/release-history#sundialsTB sundialsTB] in Octave). The intent was to liberate that software from Matlab and increase the amount of free software available to Octave users, not to enable people to write proprietary code for Octave. For the good of the community, we strongly encourage users of Octave to release the code they write for Octave under terms that are compatible with the [https://www.gnu.org/licenses/gpl.html GPL].
−
==Why can't I use code from File Exchange in Octave? It's released under a BSD license!==
+
==Why can't I use code from File Exchange in Octave?==
−
When one downloads code from File Exchange and use it on non Mathworks software (such as Octave), they are violating the Matlab central [http://www.mathworks.co.uk/matlabcentral/termsofuse.html Terms of Use]. While the [http://en.wikipedia.org/wiki/BSD_licenses BSD licenses] does allow one to use such code in Octave, it also allows others to further impose restrictions which Mathworks does through the MATLAB Central Terms of Use of their site:
+
−
{{quote|text=Content submitted to File Exchange may only be used with MathWorks products.|sign=Matlab central|source=[http://www.mathworks.co.uk/matlabcentral/termsofuse.html#content Terms of Use 2iii]}}
+
{{Quote|text=Content submitted to File Exchange may only be used with MathWorks products. | |§ 2(a)(iii) [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]}}
−
It should suffice -- although interpretations of this vary -- to contact the author directly and have them send you the code personally, or download the code from the author's own website, if available.
+
That does not apply to GNU Octave, therefore the usage is in general prohibited.  It should suffice although interpretations of this vary to contact the author directly to send you the code personally (maybe released under a free license), or download the code from the author's own website, if available. [[Asking_for_package_to_be_released_under_GPL:_examples|Some examples of letters/email sent to authors for that purpose]].
−
If you need that code or think that the code is useful, please write the authors asking them to release under a free license. Some examples of letters/email sent to authors can be found in the page [[Asking_for_package_to_be_released_under_GPL:_examples|Asking for package to be released under GPL: examples]].
+
=Installation=
−
Feel free to remix and reuse, just make sure you use your name!
+
==How can I install Octave on Windows?==
−
=What's new in Octave=
+
:''See: [[Octave for Microsoft Windows]]''
==What's new in version series 3.6.N and 3.7.N of Octave==
−
Several new features have been added to the 3.6.N series. The full details are in the NEWS file, but in brief 3.6.N series brings:
+
==How can I install Octave on macOS?==
−
* Perl compatible regular expressions
+
:''See: [[Octave for macOS]]''
* A profiler has been added.
−
* Broadcasting enabled for all built-in binary element-wise operators.
−
* The statistical distribution functions have been overhauled.
−
−
* Performance of all m-file string functions has been improved.
−
* The qhull geometry functions have been revamped.
−
* Date/time functions have been updated.
−
* Matlab compatible preference functions have been added.
−
* Various handle graphics functions have been introduced.
−
* The parfor keyword is now recognized.
−
==Features added in version series 3.4.N and 3.5.N of Octave==
+
==How can I install Octave on GNU/Linux?==
Here are some features that have been around since 3.4.N
−
* Many improvements to native OpenGL plotting
+
:''See: [[Octave for GNU/Linux]]''
* ARPACK now distributed with Octave
−
* Indexing optimisations
−
* FTP object using libcurl
−
* Better consistency with ismatrix, issquare, and issymetric
−
* Function handles aware of overloaded functions
−
* More efficient matrix division by making a single LAPACK call
−
* Other optimisations in matrix operations
−
* bsxfun optimised for basic arithmetic functions
−
* Matlab-style ignoring of output arguments using {{Codeline|~}}
−
* Many optimisations of the accumarray function
−
* Sparse matrix indexing has been rewritten for speed
−
* Configuration pseudo-variables like page_screen_output accept a  "local" option argument to limit their scope to function scope
−
* The pkg command now accepts a -forge option to pull packages directly from Octave-forge
−
−
* Octave now uses gnulib for better cross-platform compatibility
−
==Features added in version series 3.2.N and 3.3.N of Octave==
+
==How can I install Octave on Android / what is this Octave app in the Google Play store?==
Here are some features that have been around since 3.2.N
−
* integer types
+
* fixed point arithmetic
−
* sparse matrices
−
* linear programming code based on GLPK
−
* 64-bit compilation support
−
* gzipped files and stream and consequently support of Matlab v7 files
−
* better support for both msvc and mingw
−
* a fully compatible MEX interface
−
* many many other minor features and compatibility changes
−
* an experimental OpenGL graphics toolkit to replace gnuplot
−
* object orient programming
−
−
* imwrite and imread (based on the GraphicsMagick library)
−
* Lazy transpose <br/> Special treatment in the parser of things like "a' * b", where the transpose is never explicitly formed but a flag is rather passed to the underlying LAPACK code.
−
* Single precision type
−
* Improved array indexing <br/> The underlying code used for indexing of arrays has been completely rewritten and so the indexing of arrays is now significantly faster.
−
==Features available since 2.1.N==
+
==How can I install Octave on platform X?==
Here are some older features that have been around since 2.1.N:
−
* NDArrays
+
Octave currently runs on [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], and [[Octave for Microsoft Windows|Windows]].  It should be possible to make Octave work on other systems as well.  If you are interested in porting Octave to other systems, please contact the maintainers development mailing list [https://lists.gnu.org/mailman/listinfo/octave-maintainers maintainers@octave.org].
* cells
−
==Coming in a future release==
+
==What Octave version should I use?==
See [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS on the development branch]
−
=What documentation exists for Octave?=
+
For general use, it is recommended to use the latest stable version of Octave (currently {{Release}}), available from http://www.octave.org/download.html.  For development and bleeding-edge features one can obtain the development source code from the Mercurial repository https://hg.savannah.gnu.org/hgweb/octave/graph/.
−
Besides the current wiki, there are other important sources of documentation and help for Octave.
+
The used version of Octave is available via the {{manual|ver}} command and a list of user-visible changes since the last release is available via the {{manual|news}} command at the GNU Octave prompt.
−
==What documentation exists for Octave?==
+
==On what platforms does Octave run?==
−
The Octave distribution includes a 650+ page manual that is also distributed under the terms of the GNU GPL. It is available on the web at http://www.gnu.org/software/octave/doc/interpreter/ and you will also find there instructions on how to order a paper version.
+
Octave runs on any platform you can compile it on.  Binary distributions exist for [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], and [[Octave for Microsoft Windows|Windows]].  To work fully functional, Octave requires the used platform to support the underlying numerical libraries like [https://en.wikipedia.org/wiki/Basic_Linear_Algebra_Subprograms BLAS], [https://en.wikipedia.org/wiki/LAPACK LAPACK], [http://www.suitesparse.com SuiteSparse], etc., and for plotting [https://www.opengl.org/ OpenGL] or [http://www.gnuplot.info/ gnuplot].
−
The complete text of the Octave manual is also available using the GNU Info system via the GNU Emacs, info, or xinfo programs, or by using the {{Codeline|doc}} command to start the GNU info browser directly from the Octave prompt.
+
==How can I obtain Octave's source code?==
−
If you have problems using this documentation, or find that some topic is not adequately explained, indexed, or cross-referenced, please report it on http://bugs.octave.org.
+
The latest version of the Octave source code (and older versions) is available from:
−
+
+
* https://ftp.gnu.org/gnu/octave/
−
If you can't find an answer to your question, the help@octave.org mailing list is available for questions related to using, installing, and porting Octave that are not adequately answered by the Octave manual or by this document.
+
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.
−
==User community==
+
==How can I build Octave from the source code?==
−
To subscribe to the list, go to http://www.octave.org/archive.html and follow the link to the subscription page for the list.
+
To use Octave it is usually not required to build it from it's source code.  Binary distributions exist for [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], and [[Octave for Microsoft Windows|Windows]].
−
Please do not send requests to be added or removed from the mailing list, or other administrative trivia to the list itself.
+
If you have reasons to build Octave from the source code, see [[Building]] for more information.
−
An archive of old postings to the help-octave mailing list is maintained on http://www.octave.org/archive.html.
+
==What do I need to build Octave from the source code?==
−
You will also find some user advice and code spread over the web. Good starting points are the Octave Wiki http://wiki.octave.org and Octave-Forge http://octave.sourceforge.net
+
For a list of build dependencies see [[Building]].
−
We also have [http://webchat.freenode.net?channels=octave&uio=d4 an IRC chat room], <code>#octave</code> in Freenode.
+
==Do I need GCC to build Octave from the source code?==
−
==I think I have found a bug in Octave.==
+
No. The development is done primarily with [https://gcc.gnu.org/ GCC], so you may hit some incompatibilities.  Octave is intended to be portable to any standard conforming compiler (for example [https://clang.llvm.org/ clang] is know to work as well).  If you have difficulties that you think are bugs, please report them to the [http://bugs.octave.org bug tracker], or ask for help on the [https://lists.gnu.org/mailman/listinfo/help-octave help@octave.org mailing list].
−
“I think I have found a bug in Octave, but I'm not sure. How do I know, and who should I tell?
+
=What's new in Octave?=
−
First, see the section [http://www.octave.org/bugs.html on bugs and bug reports in the Octave manual]. When you report a bug, make sure to describe the type of computer you are using, the version of the operating system it is running, and the version of Octave that you are using. Also provide enough code and configuration details of your operating system so that the Octave maintainers can duplicate your bug.
+
Each new Octave release introduces many new features. A complete list of user visible changes can be seen by running <code>news</code> at the Octave prompt.  The following changes are a distilled list of the major changes:
−
=How can I obtain Octave?=
+
==What's new in the next version of Octave?==
−
==Source code==
+
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.
−
Source code is available on the Octave development site, where you are sure to get the latest version.
+
==What's new in version series 4.0.X of Octave==
−
+
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].
* ftp://ftp.octave.org/pub/octave/
−
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy, or from the Octave website.
+
* First official release of the GUI.
+
* Release of official windows binaries.
+
* Experimental support for [[classdef]].
+
* OpenGL graphics with Qt widgets.
+
* Several functions for reading, writing, and recording of audio.
−
==Pre-compiled binary packages==
+
==What's new in version series 3.8.X of Octave==
−
The Octave project does not distribute binary packages, but other projects do. For an up-to-date listing of packagers, see:
+
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].
−
+
* Experimental GUI interface.
* [[Build From Source]]
+
* OpenGL graphics with fltk widgets.
+
* Support for nested functions.
+
* Support for java packages in Octave core.
+
* Reading and writing of image files vastly extended.
−
As of today, Octave binaries are available at least on Debian, Ubuntu, RedHat, Suse and Fedora GNU/Linux, Mac OS X, Windows versions 98, 2000, XP, Vista, 7 and 8.
+
==What's new in version series 3.6.X of Octave==
−
==How do I get a copy of Octave for (some other platform)?==
+
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].
−
Octave currently runs on Unix-like systems, Mac OS X, and Windows. It should be possible to make Octave work on other systems as well. If you are interested in porting Octave to other systems, please contact [mailto:maintainers@octave.org the maintainers' mailing list]
+
* Perl compatible regular expressions
.
+
* A profiler has been added.
==How can I install Octave on Android? What is this Octave app in the Google Play store?==
+
* Broadcasting enabled for all built-in binary element-wise operators.
+
* Performance of all m-file string functions has been improved.
−
+
==What's new in version series 3.4.X of Octave==
−
=Installation issues and problems=
+
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].
−
Octave 3.4 requires approximately 1.3 GB of disk storage to unpack and compile from source (considerably less if you don't compile with debugging symbols). Once installed, Octave requires approximately 355 MB of disk space (again, considerably less if you don't compile with debugging symbols, approximately 50 MB).
+
* Many improvements to native OpenGL plotting
+
* ARPACK now distributed with Octave
+
* Indexing optimizations
+
* FTP objects
+
* Function handles aware of overloaded functions
+
* bsxfun optimized for basic arithmetic functions
+
* Matlab-style ignoring of output arguments using {{Codeline|~}}
+
* Many optimizations of the accumarray function
+
* Sparse matrix indexing has been rewritten for speed
+
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge
−
Check out the page [[Installation]] for more detailed information about installing Octave.
+
==What's new in version series 3.2.X of Octave==
−
==What else do I need?==
+
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].
−
To compile Octave, you will need a recent version of GNU Make. You will also need GCC 4.3 or later, although GCC 4.4 or later is recommended.
+
* Single precision type

+
* Experimental OpenGL graphics toolkit to replace gnuplot
'''You must have GNU Make to compile octave'''. Octave's Makefiles use features of GNU Make that are not present in other versions of make. GNU Make is very portable and easy to install.
+
* Object orient programming via @class named directories
+
* 64-bit compilation support
+
* gzipped files and stream and consequently support of Matlab v7 files
+
* a fully compatible MEX interface
+
* imwrite and imread (based on the GraphicsMagick library)
+
* Lazy transpose: Special treatment in the parser of things like "a' * b", where the transpose is never explicitly formed but a flag is rather passed to the underlying LAPACK code.
−
==Can I compile Octave with another C++ compiler?==
+
==Older releases==
−
Yes, but development is done primarily with GCC, so you may hit some incompatibilities. Octave is intended to be portable to any standard conforming compiler. If you have difficulties that you think are bugs, please report them to the http://bugs.octave.org bug tracker, or ask for help on the [mailto:help@octave.org mailing list].
+
For full details on older releases, see:
−
== How do I install ''all'' Octave packages? ==
+
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series
Do not do it! Really, there is no reason to do this. Octave Forge has many packages for different needs but it's unlikely that you need all of them. The common misconception is that the more packages one installs, the more complete and powerful its octave installation will be. However, in the same way one would ''never'' install all perl modules, ruby gems or python packages (because it simply makes no sense), one should not install all octave packages. This isn't desirable and it's not even possible.
+
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series
+
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series
−
Packages should be installed and loaded selectively. Note that some packages are meant to shadow core functions changing the way Octave works, and different packages can have different implementations of a function with the same name, leading to unpredictable results. Others are just broken or crappy and will break your system. What's worse, some of them packages are even loaded automatically at startup so you may be screwing your octave installation without even realizing it.
+
=Packages and Octave Forge=
−
=Coding=
+
==How do I install or load all Octave Forge packages?==
−
==What features are unique to Octave?==
+
Do not do it!  Really, there is no reason to do this.  Octave has many packages for different needs and is unlikely that you need all of them.  You either have a small set of required packages, in which case
+
you know them by name; or you want them all "just because", in which case you don't really need them.
−
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.
+
The common misconception is that the more packages one has installed and loaded, the more complete and powerful its Octave installation will be.  However, in the same way one would never install all perl modules, ruby gems, python packages, and C++ libraries (because it simply makes no sense), one should not install all Octave packages.
−
=== Functions defined on the command-line===
+
Packages should be installed and loaded selectively.  Note that some packages are meant to shadow core functions changing the way Octave works, and that different packages can have different functions with the same name leading to unpredictable results.
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:
−
octave:1> function s = hello_string (to_who)
+
If you really really really want to do load all packages, you can with the following:
> ## Say hello
+
<syntaxhighlight lang="octave">
> if nargin<1, to_who = "World"; end
+
## WARNING: loading all packages is probably not the solution you are looking for.
> s = ["Hello ",\
+
cellfun (@(x) pkg ("load", x.name), pkg ("list"));
>      to_who];
+
</syntaxhighlight>
> endfunction
−
octave:2> hello_string ("Moon")
−
ans = Hello Moon
−
As a natural extension of this, functions can also be defined in script files (m-files whose first non-comment line isn't {{Codeline|function out &#61; foo (...)}})
+
==I have installed a package but still get a "foo undefined" error?==
−
+
You have probably forgotten to load the package.  Use {{Codeline|pkg load package-name}} to load it.  Most packages are no longer loaded automatically to avoid surprises.  See reasoning on related FAQ [[FAQ#How_do_I_install_all_Octave_packages.3F|how do I install all Octave packages]].  If you want a specific package to be loaded by default at startup, consider adding the {{Codeline|pkg load}} command on your {{path|[[.octaverc]]}} file.
−
The pound character, {{Codeline|#}}, may be used to start comments, in addition to {{Codeline|%}}. See the previous example. The major advantage of this is that as {{Codeline|#}} is also a comment character for unix script files, any file that starts with a string like {{Codeline|#! /usr/bin/octave -q}} will be treated as an octave script and be executed by octave.
+
==I cannot install a package. Octave complains about a missing mkoctfile.==

−
===Strings delimited by double quotes "===
−
The double quote, {{Codeline|"}}, may be used to delimit strings, in addition to the single quote {{Codeline|'}}. See the previous example. Also, double-quoted strings include backslash interpretation (like C++, C, and Perl) while single quoted are uninterpreted (like Matlab and Perl).
+
You should normally use your distribution's packages. For Debian and Fedora, Octave package <code>foo</code> will be a deb or rpm called <code>octave-foo</code>, and you should install that instead using <code>apt</code> or <code>yum</code>.
−
===Line continuation by backslash===
+
If you really need to build Octave packages from source to install them, you'll need {{manual|mkoctfile}}. Most distributions split Octave into several packages.  The script {{manual|mkoctfile}} is then part of a separate package:
−
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}}. See the previous example.
+
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]
−
===Informative block closing===
+
* Fedora: {{Codeline|octave-devel}}

−
You may close function, for, while, if, ... blocks with endfunction, endfor, endwhile, ... keywords in addition to using end. As with Matlab, the end (or endfunction) keyword that marks the end of a function defined in a .m file is optional.
−

−
===Coherent syntax===
−

−
Indexing other things than variables is possible, as in:
−

−
octave:1> [3 1 4 1 5 9](3)
−
ans = 4
−
octave:2> cos([0 pi pi/4 7])(3)
−
ans = 0.70711
−

−
In Matlab, it is for example necessary to assign the intermediate result {{Codeline|cos([0 pi pi/4 7])}} to a variable before it can be indexed again.
−

−
===Exclamation mark as not operator===
−

−
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:
−

−
octave:1> if ! strcmp (program_name, "octave"),
−
>  "It's an error"
−
> else
−
>  "It works!"
−
> end
−
ans = It works!
−
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.
−
===Increment and decrement operators===
+
==How do I automatically load a package at Octave startup?==
−
If you like the {{Codeline|++}}, {{Codeline|+&#61;}} etc operators, rejoice! Octave includes the C-like increment and decrement operators {{Codeline|++}} and {{Codeline|--}} in both their prefix and postfix forms, in addition to {{Codeline|+&#61;}}, {{Codeline|-&#61;}}, {{Codeline|*&#61;}}, {{Codeline|/&#61;}}, {{Codeline|^&#61;}},{{Codeline|.+&#61;}},{{Codeline|.-&#61;}},{{Codeline|.*&#61;}}, {{Codeline|./&#61;}}, and {{Codeline|.^&#61;}}.
+
When Octave starts, it runs the file {{Path|~/.octaverc}} (in your user's home directory).  If you want Octave to automatically load a package, simply add a <code>pkg load pkg-name</code> command to it. If the files does not exist, create it.
−
For example, to pre-increment the variable x, you would write {{Codeline|++x}}. This would add one to x and then return the new value of x as the result of the expression. It is exactly the same as the expression {{Codeline|x &#61; x + 1}}.
+
If you do this, remember that other people may not have Octave configured to load packages at startup.  Therefore, if you write code for others, remember that your programs still need to load the packages they require.
−
To post-increment a variable x, you would write {{Codeline|x++}}. This adds one to the variable x, but returns the value that x had prior to incrementing it. For example, if x is equal to 2, the result of the expression x++ is 2, and the new value of x is 3.
+
=Octave usage=

−
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.
−

−
===Unwind-protect===
−

−
In addition to try-catch blocks, Octave supports an alternative form of exception handling modeled after the unwind-protect form of Lisp. The general form of an unwind_protect block looks like this:
−

−
unwind_protect
−
body
−
unwind_protect_cleanup
−
cleanup
−
end_unwind_protect
−

−
Where body and cleanup are both optional and may contain any Octave expressions or commands. The statements in cleanup are guaranteed to be executed regardless of how control exits body.
−

−
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.
−

−
Matlab can be made to do something similar with their {{Codeline|onCleanup}} function that was introduced in 2008a. Octave also has {{Codeline|onCleanup}} since version 3.4.0.
−

−
===Built-in ODE and DAE solvers===
−

−
Octave includes LSODE, DASSL and DASPK for solving systems of stiff ordinary differential and differential-algebraic equations. These functions are built in to the interpreter.
−

−
===Do-Until loop structure===
−

−
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab
−

−
x = 0
−
do
−
x += 1;
−
until (x == 10)
−

−
==How does Octave solve linear systems?==
−

−
In addition to consulting Octave's source for the precise details, you can read the Octave manual for a complete high-level description of the algorithm that Octave uses to decide how to solve a particular linear system, e.g. how the backslash operator {{Codeline|A\x}} will be interpreted. Sections [http://www.gnu.org/software/octave/doc/interpreter/Techniques-Used-for-Linear-Algebra.html#Techniques-Used-for-Linear-Algebra Techniques Used for Linear Algebra] and [http://www.gnu.org/software/octave/doc/interpreter/Sparse-Linear-Algebra.html Linear Algebra on Sparse Matrices] from the manual describe this procedure.
−

−
=How do I...?=

==How do I execute an Octave script?==

==How do I execute an Octave script?==
−
First of all, make sure you understand [http://www.gnu.org/software/octave/doc/interpreter/Script-Files.html the difference between script files and function files]. If you want to execute a function defined in a file, just call the function like any other Octave function: <code>foo(arg1, arg2);</code>
+
First of all, make sure you understand [http://www.octave.org/doc/interpreter/Script-Files.html the difference between script files and function files]. If you want to execute a function defined in a file, just call the function like any other Octave function: <code>foo(arg1, arg2);</code>
−
To execute a script from within Octave, just type its name without the .m extension. Thus, if you have a script called <code>foo.m</code>, just type <code>foo</code> from within Octave to execute it. You have to make sure that the script is in your current path. Type <code>path</code> in Octave to see what this path is, and type <code>pwd</code> to print the working directory (where you're currently standing). The current working directory is referred to as "." in the <code>path</code>.
+
To execute a script from within Octave, just type its name without the <code>.m</code> extension. Thus, if you have a script called <code>foo.m</code>, just type <code>foo</code> from within the Octave command prompt to execute it. You have to make sure that the script is in your current working directory or in Octave's load path. Type {{manual|pwd}} to get the current working directory or type {{manual|path}} to see which paths belong to Octave's load path. The current working directory is referred to as "." in the output of {{manual|path}}.
−
If the script name has characters that are not valid for an Octave identifier, or if you do not want to use addpath to add the script's location to the current path, you can use the <code>run</code> function instead:
+
If the script name has characters that are not valid for an Octave identifier, or if you do not want to use {{manual|addpath}} to add the script's location to the current path, you can use the {{manual|run}} function instead:
−
octave> run("Script Name With Spaces.m")
+
<syntaxhighlight lang="octave">
octave> run("/opt/local/foo.m")
+
run ("Script Name With Spaces.m")
+
run ("/opt/local/foo.m")
+
</syntaxhighlight>
−
An alternative is to run the script from outside Octave by calling Octave from your operating system shell. Unlike calling the script from inside Octave, this also allows you to pass arguments from the shell into the script, which the script can access using the <code>argv</code> command:
+
An alternative is to run the script from outside Octave by calling Octave from your operating system shell. Unlike calling the script from inside Octave, this also allows you to pass arguments from the shell into the script, which the script can access using the {{manual|argv}} command:

$octave the-script.m arg1 arg2$ octave the-script.m arg1 arg2
Line 428: Line 298:
If you call the script from the shell and it's plotting, please note [[#When I try plotting from a script, why am I not seeing anything?|how to plot when running a script from the shell]].

If you call the script from the shell and it's plotting, please note [[#When I try plotting from a script, why am I not seeing anything?|how to plot when running a script from the shell]].
−
==do xxxx?==
+
==How do I close a figure?==
−
You are probably looking for the function ''lookfor''. This function searches the help text of all functions for a specific string and returns a list of functions. Note that by default it will only search the first line of the help text (check ''help lookfor'' at the octave prompt for more). The following example helps to find the function to calculate correlation coefficient in a matrix:
+
To close the current figure type {{manual|close}} in the Octave command prompt.
−
octave> lookfor correlation
+
==How do I set the number of displayed decimals?==
corr2              Returns the correlation coefficient between I and J.
−
cor                Compute correlation.
−
corrcoef            Compute correlation.
−
spearman            Compute Spearman's rank correlation coefficient RHO for each of the variables sp
−
autocor            Return the autocorrelations from lag 0 to H of vector X.
−
Also, there's a high chance that the function name has a suggestive name, and so you can try auto-completion to get some hints. For the previous example, typing ''corr'' at the octave promp followed by pressing [Tab] twice would suggest the following:
+
You can control the number of displayed decimals using the {{manual|format}} command:
−
octave> corr
+
<syntaxhighlight lang="octave">
corr2    corrcoef
+
>> format long
+
>> pi
+
pi = 3.14159265358979
+
>> format short
+
>> pi
+
pi = 3.1416
+
</syntaxhighlight>
−
==How do I erase a figure?==
+
==How do I call an Octave function from C++?==
−
closeplot();
+
closefig(number)
−
==How do I set the number of displayed decimals?==
+
==How do I change color/line definition in gnuplot postscript?==

−
octave:1> format long
−
octave:2> pi
−
pi = 3.14159265358979
−
octave:3> format short
−
octave:4> pi
−
pi = 3.1416
−

−
==How do I call an octave function from C++?==
−
*Here is an untested code snippet for calling rand([9000,1]), modified from a post by HerberFarnsworth? to help-octave on 2003-05-01:
+
Here is a awk script to get a rainbow color map

−
#include <octave/oct.h>
−
...
−
ColumnVector NumRands(2);
−
NumRands(0) = 9000;
−
NumRands(1) = 1;
−
octave_value_list f_arg, f_ret;
−
f_arg(0) = octave_value(NumRands);
−
f_ret = feval("rand",f_arg,1);
−
Matrix unis(f_ret(0).matrix_value());
−

−
==How do I change colour/line definition in gnuplot postscript?==
−
Here is a awk script to get a rainbow colour map

#!/bin/awk -f

#!/bin/awk -f
Line 511: Line 359:
==How do I tell if a file exists?==

==How do I tell if a file exists?==
−
Look at functions like exist, file_in_path.. and the other functions that their descriptions point to.
+
One can use the function {{manual|exist}} to tell if a regular file, say <code>foo.txt</code> exist in Octave's load path, or the current directory:
+
<syntaxhighlight lang="octave">
+
>> exist ("foo.txt", "file")  # 2, if file exists, 0 otherwise
+
ans = 2
+
</syntaxhighlight>
−
==How do I create a plot without a window popping up (ie, a plot to a file)?==
+
==How do I create a plot without a window popping up (plot to a file directly)?==
−
'''This only works with gnuplot as graphics_toolkit, NOT with fltk. See [https://savannah.gnu.org/bugs/?33180 Bug#33180]'''
+
<syntaxhighlight lang="octave">
+
figure (1, "visible", "off");
+
plot (sin (1:100));
+
print -deps "/tmp/sin.eps"
+
</syntaxhighlight>
−
figure(1, "visible", "off");
+
One can set that behavior as default:
plot(sin(1:100));
−
print -deps "/tmp/sin.eps"
−
One can set that behaviour as default:
+
<syntaxhighlight lang="octave">
+
set (0, "defaultfigurevisible", "off");
+
</syntaxhighlight>
−
set(0, 'defaultfigurevisible', 'off');
+
==How do I increase Octave's precision?==
−
== How do I make Octave use more precision? ==
+
Octave's default numerical type is [https://en.wikipedia.org/wiki/IEEE_754 IEEE 754] binary64 , a.k.a. "double" or "hardware floats".  This type has a precision of 53 bits or about 16 decimal digits. It is supported by each modern computer hardware, so it is really '''fast'''.  This type is assumed throughout for Octave's calculations.  If more precision was required, one can obtain a "few bits more" by using integer types, e.g. {{manual|uint64}}, but in general one cannot expect more precision from any '''fast''' numerical software.  Just to visualize "how big" those numerical limits are, consider the following table:
−
Octave's default numerical type is IEEE 754 doubles, a.k.a. hardware floats. This type has 52 bits of precision or about 16 decimal digits. It's implemented in your computer's hardware, in your CPU, so it's '''fast'''. This type is assumed throughout for Octave's calculations.
+
{| class="wikitable"
+
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.
+
|-
+
| <code>intmax ("uint64")</code>
+
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code>
+
| <code>2^64-1</code>
+
|-
+
| <code>intmax ("int64")</code>
+
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code>
+
| <code>2^63-1</code>
+
|-
+
| <code>flintmax ("double")</code>
+
| style="text-align: right;" | <code>9,007,199,254,740,992</code>
+
| <code>2^53</code>
+
|-
+
| <code>flintmax ("single")</code>
+
| style="text-align: right;" | <code>16,777,216</code>
+
| <code>2^24</code>
+
|}
−
You can use a few other built-in types. The int64 type will have 63 bits of precision. One bit is used for the sign, but if you don't want to lose that bit, uint64 can be used instead. These types, however, cannot represent numbers as large as the default double type, and can only represent integers. Furthermore, there is no way to represent integer literals, so if you do
+
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:
−
<syntaxhighlight lang="Octave">uint64(18446744073709551610);</syntaxhighlight>
+
<syntaxhighlight lang="Octave">
+
>> uint64 (2^53 + 1)
+
ans = 9007199254740992
+
>> uint64 (2^53) + 1
+
ans = 9007199254740993
+
</syntaxhighlight>
−
the literal "18446744073709551610" first gets converted to a double precision type, so <code>uint64</code>'s additional precision is lost. Instead, initialise the <code>uint64</code> with smaller numbers and perform a computation to get the larger number you want. E.g.,
+
Notice the difference, in the first line the addition within the brackets is performed using double precision, therefore the result gets "truncated" to the maximum possible value without a warning. The third line uses throughout uint64 precision.
−
<syntaxhighlight lang="Octave">uint64(999999999999999) * 10000</syntaxhighlight>
+
Consider carefully if your problem really needs more precision.  Often if you're running out of precision the problem lies fundamentally in your methods being [https://en.wikipedia.org/wiki/Numerical_stability numerically unstable], thus more precision will not help you here.
−
would produce value 9999999999999990000, which is close to the maximum possible value for the uint64 type, but can't be at the moment input directly, doing uint64(9999999999999990000), due to the mentioned error of rounding.
+
If you absolutely must have more precision, you're at present better off using a [https://en.wikipedia.org/wiki/Computer_algebra_system CAS] instead of Octave.  However, CAS or symbolic computations must be implemented '''in software''' which makes it much slower than hardware floats.  An example of such a CAS is [http://www.sagemath.org/ Sage] or have a look at Octave's [[Symbolic package]].
−
Alternatively, one may use arbitrary precision arithmetic, which has as much precision as is practical to hold in your computer's memory. The ''symbolic'' package, when it works, has a vpa() function for arbitrary precision arithmetic. Note that arbitrary precision arithmetic must be implemented '''in software''' which makes it much slower than hardware floats.
+
==How do I run a Matlab P-file in Octave?==
−
At present, however, the symbolic package is almost useless, since even when you get it to compile and not crash, it cannot handle any array type, which hardly helps for an array-oriented language like Octave. If this limitation is not important to you, attempt to use the symbolic package. If you would like to get this fixed, [http://octave.1599824.n4.nabble.com/Internal-Precision-Symbolic-tp4645257p4645594.html Jordi Gutiérrez Hermoso has volunteered] to fix the package for 5000 USD, which can be obtained from a kickstarter campaign.
+
You can't. Matlab P-files (files with a <code>.p</code> file extension), also known as P-code, are [https://en.wikipedia.org/wiki/Obfuscation_%28software%29 obfuscated] files than cannot be run outside of Matlab itself. The original source Matlab m-files that were used to generate these P-files should be used in Octave instead.
−
Consider carefully if your problem really needs more precision. Often if you're running out of precision the problem lies fundamentally in your methods being [http://en.wikipedia.org/wiki/Numerical_stability numerically unstable], so more precision will not help you here. If you absolutely must use arbitrary-precision arithmetic, you're at present better off using a CAS instead of Octave. An example of such a CAS is [http://sagemath.org Sage].
+
There are no plans to support running P-files produced by Matlab in Octave.
+

+
==How does Octave solve linear systems?==
+

+
In addition to consulting Octave's source for the precise details, you can read the Octave manual for a complete high-level description of the algorithm that Octave uses to decide how to solve a particular linear system, e.g. how the backslash operator <code>A \ x</code> will be interpreted.  Sections [http://www.octave.org/doc/interpreter/Techniques-Used-for-Linear-Algebra.html Techniques Used for Linear Algebra] and [http://www.octave.org/doc/interpreter/Sparse-Linear-Algebra.html Linear Algebra on Sparse Matrices] from the manual describe this procedure.
+

+
==How do I do X?==
+

+
You are probably looking for the function {{manual|lookfor}}.  This function searches the help text of all functions for a specific string and returns a list of functions.  Note that by default it will only search the first line of the help text (check <code>help lookfor</code> at the octave prompt for more). The following example helps to find the function to calculate correlation coefficient in a matrix:
+

+
>> lookfor correlation
+
corr                Compute matrix of correlation coefficients.
+
corrcoef            Compute a matrix of correlation coefficients.
+
spearman            Compute Spearman's rank correlation coefficient RHO.
+

+
Also, there's a high chance that the function name has a suggestive name, and so you can try auto-completion to get some hints. For the previous example, typing <code>corr</code> at the octave prompt followed by pressing the {{key press|Tab}}-Key twice would suggest the following:
+

+
>> corr
+
corr    corrcoef

=Common problems=

=Common problems=
−
==I am running a script that should produce output during execution but I don't see anything until it has finished==
+
==I do not see any output of my script until it has finished?==
−
By default Octave is set to pass its screen output through a pager (usually the default pager is "less") which allows
+
By default Octave is set to pass its screen output through a [https://en.wikipedia.org/wiki/Terminal_pager pager] (usually the default pager is "less") which allows things such as navigating through the output with arrow keys or searching for text or regular expressions within the output. The pager only displays the output after it's finished receiving it, so when it is active you'll not be able to see anything until your script has terminated. To change this behavior temporarily or permanently you may want to use one of the options described [http://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].
things such as navigating through the output with arrow keys or searching for text or regular expressions within the output.
−
The pager only displays the output after it's finished receiving it, so when it is active you'll not be able to see anything until your script has terminated. To change this behavior temporarily or permanently you may want to use one of the options described [http://www.gnu.org/software/octave/doc/interpreter/Paging-Screen-Output.html here].

==When I try plotting from a script, why am I not seeing anything?==

==When I try plotting from a script, why am I not seeing anything?==
−
If you are running an Octave script that includes a plotting command, the script and Octave may terminate immediately. So the plot window does show up, but immediately closes when Octave finishes execution. Alternatively, if using fltk, the plot window needs a readline loop to show up (the time when Octave is sitting around doing nothing waiting for interactive input).
+
If you are running an Octave script that includes a plotting command, the script and Octave may terminate immediately. So the plot window does show up, but immediately closes when Octave finishes execution. Alternatively, if using fltk, the plot window needs a readline loop to show up (the time when Octave is sitting around doing nothing waiting for interactive input).

−
A common solution is to put a {{Codeline|pause}} command at the end of your script.
−
==How do I get sound input or output in Windows?==
+
A common solution is to put a {{manual|pause}} command at the end of your script.
Sound I/O is badly broken on anything that isn't using Linux's Open Sound System. Nowadays, this usually doesn't even include Linux, since OSS is frequently considered "legacy". All of the audio functions in Octave are badly in need of a rewrite so that they actually work.
−
==I cannot install a package. Octave complains about a missing mkoctfile.==
+
==How do I get sound input or output in Windows?==
−
You should normally use your distribution's packages. For Debian and Fedora, Octave package '''foo''' will be a deb or rpm called '''octave-foo''', and you should install that instead using apt or yum.
+
Sound input from a sound card and output to a sound card is fully supported since Octave 4.0.0 for all platforms.  If you have problems with the [http://www.octave.org/doc/interpreter/Audio-Processing.html audio I/O functions] using Octave 4.0.0 or a newer version, please report them on the [http://bugs.octave.org bug tracker].
−
If you really need to build Octave packages from source to install them, you'll need mkoctfile. Most distributions split Octave into several packages. The script mkoctfile is then part of a separate package:
+
==I have problem X using the latest Octave version==
−
+
−
* Fedora: {{Codeline|octave-devel}}
+
* The latest stable version is {{Release}}.  Be aware that you may still have an older version due to whatever distribution method you are using.  To get a newer stable version for your system see for example [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]]).
−
== I'm having problem XXX using the latest Octave version ==
+
* If you refer to the latest Mercurial revision, please specify the [https://www.mercurial-scm.org/wiki/ChangeSetID changeset ID] not the revision number, e.g. the output of <code>hg summary</code> or <code>hg id</code>.  Changeset IDs are globally unique across all repos.
−
Please be more specific. What is the latest version, according to you? If you mean the latest released version, be aware that you may still have an older version due to whatever distribution method you're using. There may be a newer version available that you're not aware of due to the distribution method you're using to get Octave, and in most cases, there is a way to get a newer version via your distribution method (see other wiki pages for [[Octave_for_GNU/Linux|GNU/Linux]], [[Octave_for_MacOS_X|Mac OSX]], and [[Octave_for_Windows|Windows]]).
+
If your problem truly persists with the "latest version", then please [http://bugs.octave.org/ report a bug] or ask for help at[https://lists.gnu.org/mailman/listinfo/help-octave help@octave.org].  Otherwise, don't be surprised if volunteers are less inclined to help you with a problem that only exists in an older version of Octave and is already fixed in a newer version.
−
If you mean the latest Mercurial revision, please specify which one that is. "Latest tip" is not informative, because from the time you wrote "latest tip" to the time someone reads that message, "latest tip" might have changed meaning. Also, you might be standing on a different commit than what "hg tip" says. The tip may be on a different branch, or you might have updated to a different revision different from what "hg tip" says.
+
==Why is Octave's floating-point computation wrong?==
−
Instead, report the output of "hg summary" or "hg id". Also please use hashes instead or in addition to revision numbers. Revision numbers are just a convenience and only make sense in your local repo, and might not coincide with what someone sees on their own repo. Hashes are globally unique across all repos.
+
Floating-point arithmetic is an approximation '''in binary''' to arithmetic on real or complex numbers.  Just like you cannot represent 1/3 exactly in decimal arithmetic (0.333333... is only a rough approximation to 1/3), you cannot represent some fractions like $1/10$ exactly in base 2.  In binary, the representation to one tenth is $0.0\overline{0011}_b$ where the bar indicates that it repeats infinitely (like how $1/6 = 0.1\overline{6}_d$ in decimal).  Because this infinite repetition cannot be represented exactly with a finite number of digits, rounding errors occur for values that appear to be exact in decimal but are in fact approximations in binary, such as for example how 0.3 - 0.2 - 0.1 is not equal to zero.
−
If your problem truly persists with the latest version, as indicated [http://www.gnu.org/software/octave/download.html here], then by all means report a bug or ask for help, but don't be surprised if volunteers are less inclined to help you with a problem that only exists in an older version of Octave.
+
In addition, some advanced operations are computed by approximation and are not guaranteed to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma].  Their results are system-dependent.
−
== Why is this floating point computation wrong? ==
+
This isn't an Octave bug.  It happens with any program that uses [https://en.wikipedia.org/wiki/IEEE_754 IEEE 754 floating-point arithmetic].  To be fair, IEEE 754 also specifies decimal floating-point arithmetic, which has never seen wide adoption.  The reason why Octave and other programs using IEEE 754 binary floating-point numbers is that they are ''fast'', because they are implemented in hardware or system libraries.  Unless you are using very exotic hardware, Octave will use your computer's processor for basic floating-point arithmetic.
−
Floating point arithmetic is an approximation '''in binary''' to arithmetic on real or complex numbers. Just like you cannot represent 1/3 exactly in decimal arithmetic (0.333333 is only a rough approximation to 1/3), you cannot represent some fractions like $1/10$ exactly in base 2. In binary, the representation to one tenth is $0.0\overline{0011}_b$ where the bar indicates that it repeats infinitely (like how $1/6 = 0.1\overline{6}_d$ in decimal). Because this infinite repetition cannot be represented exactly with a finite number of digits, rounding errors occur for values that appear to be exact in decimal but are in fact approximations in binary, such as for example how 0.3 - 0.2 - 0.1 is not equal to zero.
+
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computatons with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floatin-point arithmetic.
−
This isn't an Octave bug. It happens with any program that uses [http://en.wikipedia.org/wiki/IEEE_754 IEEE 754 floating point arithmetic]. The reason why Octave and other programs use IEEE 754 floats is that they are ''fast'', because they are implemented in hardware. Unless you are using very exotic hardware, Octave will use your computer's processor for floating point arithmetic.
+
To learn more about floating-point arithmetic, consult the [https://en.wikipedia.org/wiki/Floating-point_arithmetic Wikipedia article] or the classical reference by David Goldberg [http://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html What Every Computer Scientist Should Know About Floating-Point Arithmetic].
−
Like death and taxes, rounding errors are a fact of life. You cannot avoid them. You can only move a rounding error from one part of a computation to another, or you can use more precision and delay the rounding error. One way to delay the rounding error is to use arbitrary precision arithmetic, which is inevitably slower as it has to be implemented in software instead of hardware. You may use the vpa function from the symbolic package for this purpose.
+
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==
−
To learn more about floating point arithmetic, consult [http://en.wikipedia.org/wiki/Floating_point_arithmetic its Wikipedia article] or the classical reference [http://floating-point-gui.de/ What Every Computer Scientist Should Know About Floating Point Arithmetic].
+
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}
−
== I have installed a package but still get a "foo undefined" error ==
+
Users with this kind of problem should try to install/update their Intel OpenGL drivers for Windows or consider installing Mesa drivers from http://qt-project.org/wiki/Cross-compiling-Mesa-for-Windows .
−
You have probably forgotten to load the package. Use {{Codeline|pkg load package-name}} to load it. Most packages are no longer loaded automatically to avoid surprises. See reasoning on related FAQ [[FAQ#How_do_I_install_all_Octave_packages.3F|how do I install all Octave packages]]. If you want a specific package to be loaded by default at startup, consider adding the {{Codeline|pkg load}} command on your {{path|.octaverc}} file.
+
−
== Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU ==
+
==Plot hangs and makes the GUI unresponsive==
−
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}
+
If the Qt graphics toolkit is used and "plot" is used for the first time, the fontconfig scanner searches the font directory to build a font cache. This can take up to 3min on slow CPUs. See {{bug|45458}}
−
Users with this kind of problem should try to install/update their Intel OpenGL drivers for Windows or consider installing Mesa drivers from http://qt-project.org/wiki/Cross-compiling-Mesa-for-Windows
+
==Error message about invalid call to script or invalid use of script in index expression==
−
+
If Octave shows an error message about {{Codeline|invalid call to script .../close.m}} or {{Codeline|invalid use of of script .../close.m in index expression}}, it means that you have created a script called close.m that is overriding the built-in Octave function {{Codeline|close}}. Octave functions and scripts share the samem global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function.
−
=Porting programs from Matlab to Octave=
+
=Differences between Octave and Matlab=

<blockquote>

<blockquote>
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?
+
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?

</blockquote>

</blockquote>
Line 616: Line 508:
<blockquote>

<blockquote>
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?
+
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?

</blockquote>

</blockquote>
−
which is not quite the same thing. There are still a number of differences between Octave and Matlab, however in general differences between the two are considered as bugs. Octave might consider that the bug is in Matlab and do nothing about it, but generally functionality is almost identical. If you find an important functional difference between Octave behavior and Matlab, then you should send a description of this difference (with code illustrating the difference, if possible) to http://bugs.octave.org.
+
which is not quite the same thing. There are still a number of differences between Octave and Matlab, however in general differences between the two are considered as bugs. Octave might consider that the bug is in Matlab and do nothing about it, but generally functionality is almost identical. If you find an important functional difference between Octave behavior and Matlab, then you should send a description of this difference (with code illustrating the difference, if possible) to http://bugs.octave.org.
+

+
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.
−
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users. As both Octave and Matlab are under constant development the information in this section is subject to change at anytime.
+
As both Octave and Matlab are under constant development, the information in this section is subject to change.

You should also look at the pages http://octave.sourceforge.net/packages.php and http://octave.sourceforge.net/docs.html that have a function reference that is up to date. You can use this function reference to see the number of octave functions that are available and their Matlab compatibility.

You should also look at the pages http://octave.sourceforge.net/packages.php and http://octave.sourceforge.net/docs.html that have a function reference that is up to date. You can use this function reference to see the number of octave functions that are available and their Matlab compatibility.
−
==How is Octave different from Matlab?==
+
==Nested Functions==
−
The major differences between Octave 3.4.N and Matlab R2010b are:
+
Octave has limited support for nested functions since version 3.8.0. That is
−
===Nested Functions===
+
<syntaxhighlight lang="Matlab">
Octave has limited support for nested functions. That is
+
function y = foo (x)
+
y = bar(x)
+
function y = bar (x)
+
y = ...;
+
end
+
end
+
</syntaxhighlight>
−
function y = foo (x)
+
is equivalent to
y = bar(x)
−
function y = bar (x)
−
y = ...;
−
end
−
end
−
is equivalent to
+
<syntaxhighlight lang="Octave">
+
function y = foo (x)
+
y = bar(x)
+
endfunction
−
function y = foo (x)
+
function y = bar (x)
y = bar(x)
+
y = ...;
end
+
endfunction
function y = bar (x)
+
</syntaxhighlight>
y = ...;
−
end
−
The main difference with Matlab is a matter of scope. While nested functions have access to the parent function's scope in Matlab, no such thing is available in Octave, due to how Octave essentially “un-nests” nested functions.
+
The main difference with Matlab is a matter of scope. While nested functions have access to the parent function's scope in Matlab, no such thing is available in Octave, due to how Octave essentially “un-nests” nested functions.

The authors of Octave consider the nested function scoping rules of Matlab to be more problems than they are worth as they introduce difficult to find bugs as inadvertently modifying a variable in a nested function that is also used in the parent is particularly easy for those not attentive to detail.

The authors of Octave consider the nested function scoping rules of Matlab to be more problems than they are worth as they introduce difficult to find bugs as inadvertently modifying a variable in a nested function that is also used in the parent is particularly easy for those not attentive to detail.
−
===Differences in core syntax===
+
==Differences in core syntax==

There are a few core Matlab syntaxes that are not accepted by Octave, these being

There are a few core Matlab syntaxes that are not accepted by Octave, these being
−
* Some limitations on the use of function handles. The major difference is related to nested function scoping rules (as above) and their use with function handles.
+
* Some limitations on the use of function handles. The major difference is related to nested function scoping rules (as above) and their use with function handles.

* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.

* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.
−
* Matlab classdef object oriented programming is not yet supported, though work is underway in a branch of the development tree.
+
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.
−
===Differences in core functions===
+
==Differences in core functions==
−
A large number of the Matlab core functions (ie those that are in the core and not a toolbox) are implemented, and certainly all of the commonly used ones. There are a few functions that aren't implemented, usually to do with specific missing Octave functionality (GUI, DLL, Java, ActiveX, DDE, web, and serial functions). Some of the core functions have limitations that aren't in the Matlab version. For example the sprandn function can not force a particular condition number for the matrix like Matlab can.
+
A large number of the Matlab core functions (i.e. those that are in the core and not a toolbox) are implemented, and certainly all of the commonly used ones. There are a few functions that aren't implemented, usually to do with specific missing Octave functionality (GUI, DLL, Java, ActiveX, DDE, web, and serial functions). Some of the core functions have limitations that aren't in the Matlab version. For example the {{manual|sprandn}} function can not force a particular condition number for the matrix like Matlab can.  Another example is that testing and the runtests function work differently in Matlab and Octave.
−
===Just-In-Time compiler===
+
==Just-In-Time compiler==
−
Matlab includes a "Just-In-Time" compiler. This compiler allows the acceleration of for-loops in Matlab to almost native performance with certain restrictions. The JIT must know the return type of all functions called in the loops and so you can't include user functions in the loop of JIT optimized loops. Octave doesn't have a JIT and so to some might seem slower than Matlab. For this reason you must vectorize your code as much as possible. The MathWorks themselves have a good document discussing vectorization at http://www.mathworks.com/support/tech-notes/1100/1109.html.
+
Matlab includes a "Just-In-Time" compiler. This compiler allows the acceleration of for-loops in Matlab to almost native performance with certain restrictions. The JIT must know the return type of all functions called in the loops and so you can't include user functions in the loop of JIT optimized loops. Octave has a [[JIT|not fully functional JIT compiler]]. For this reason you must [[Performance#Vectorization|vectorize your code]] as much as possible. The MathWorks themselves have a good document discussing vectorization at http://www.mathworks.com/support/tech-notes/1100/1109.html.
−
===Compiler===
+
==Compiler==
−
On a related point, there is no Octave compiler, and so you can't convert your Octave code into a binary for additional speed or distribution. There have been several aborted attempts at creating an Octave compiler. Should the JIT compiler above ever be implemented, an Octave compiler should be more feasible.
+
On a related point, there is no Octave compiler, and so you can't convert your Octave code into a binary for additional speed or distribution.
−
===Graphic handles===
+
==Graphic handles==
−
Up to Octave 2.9.9 there was no support for graphic handles in Octave itself. In the 3.2.N versions of Octave and beyond the support for graphics handles is converging towards full compatibility. The patch function is currently limited to 2-D patches, due to an underlying limitation in gnuplot, but the experimental OpenGL backend is starting to see an implementation of 3-D patches.
+
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].
−
===GUI functions ===
+
==GUI functions==
−
There are no Matlab compatible GUI functions yetThis might be an issue if you intend to exchange Octave code with Matlab users. There are a number of bindings from Octave to {{Forge|tcl-octave|Tcl/Tk}}, [http://octaviz.sourceforge.net/index.php? VTK] and {{Forge|zenity}} for example, that can be used for a GUI, but these are not Matlab compatible. Work on a Matlab compatible GUI is in an alpha stage in the QtHandles project, which may form part of a future release of Octave.
+
The support for [http://www.octave.org/doc/interpreter/GUI-Development.html Matlab compatible GUI functions] was added in Octave version 3.6.0 and is converging towards full compatibilityIf you notice any incompatibilities, please [http://bugs.octave.org report a bug].
−
+
−
Octave itself includes no Simulink support. Typically the simulink models lag research and are less flexible, so shouldn't really be used in a research environment. However, some Matlab users that try to use Octave complain about this lack.
+
Octave itself includes no Simulink support. Typically the simulink models lag research and are less flexible, so shouldn't really be used in a research environment. However, some Matlab users that try to use Octave complain about this lack.
−
===MEX-Files===
+
==MEX-Files==
−
Octave includes an API to the Matlab MEX interface. However, as MEX is an API to the internals of Matlab and the internals of Octave differ from Matlab, there is necessarily a manipulation of the data to convert from a MEX interface to the Octave equivalent. This is notable for all complex matrices, where Matlab stores complex arrays as real and imaginary parts, whereas Octave respects the C99/C++ standards of co-locating the real/imag parts in memory. Also due to the way Matlab allows access to the arrays passed through a pointer, the MEX interface might require copies of arrays (even non complex ones).
+
Octave includes an [http://www.octave.org/doc/interpreter/Mex_002dFiles.html API to the Matlab MEX interface]. However, as MEX is an API to the internals of Matlab and the internals of Octave differ from Matlab, there is necessarily a manipulation of the data to convert from a MEX interface to the Octave equivalent. This is notable for all complex matrices, where Matlab stores complex arrays as real and imaginary parts, whereas Octave respects the C99/C++ standards of co-locating the real/imag parts in memory. Also due to the way Matlab allows access to the arrays passed through a pointer, the MEX interface might require copies of arrays (even non complex ones).
−
+
−
Block comments denoted by {{Codeline|#{}} and {{Codeline|#&#125;}markers (or {{Codeline|%{}} and {{Codeline|%&#125;}}) are supported by Octave with some limitations. The major limitation is that block comments are not supported within [] or {}.
+
Block comments denoted by <code>#{</code> and <code>#}</code> markers (or <code>%{</code> and <code>%}</code>) are supported by Octave with some limitations. The major limitation is that block comments are not supported within [] or {}.
−
===Mat-File format===
+
==Mat-File format==
−
There are some differences in the mat v5 file format accepted by Octave. Matlab recently introduced the "-V7.3" save option which is an HDF5 format which is particularly useful for 64-bit platforms where the standard Matlab format can not correctly save variables. Octave accepts HDF5 files, but is not yet compatible with the "-v7.3" versions produced by Matlab.
+
There are some differences in the mat v5 file format accepted by Octave. Matlab recently introduced the "-V7.3" save option which is an HDF5 format which is particularly useful for 64-bit platforms where the standard Matlab format can not correctly save variables. Octave accepts HDF5 files, but is not yet compatible with the "-v7.3" versions produced by Matlab.

Although Octave can load inline function handles saved by Matlab, it can not yet save them.

Although Octave can load inline function handles saved by Matlab, it can not yet save them.
−
Finally, Some multi-byte Unicode characters aren't yet treated in mat-files.
+
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.
−
===Profiler===
+
==Profiler==
−
Thanks to Daniel Kraft's 2011 Google Summer of Code project, Octave has a profiler since version 3.6.0. However, at the moment it only produces text output and has its own makeshift interface for hierarchical profiling.
+
Thanks to Daniel Kraft's 2011 Google Summer of Code project, [http://www.octave.org/doc/interpreter/Profiling.html Octave has a profiler] since version 3.6.0.
−
===Toolboxes===
+
==Toolboxes==
−
Octave is a community project and so the toolboxes that exist are donated by those interested in them through [[Octave Forge]]. These might be lacking in certain functionality relative to the Matlab toolboxes, and might not exactly duplicate the Matlab functionality or interface.
+
Octave is a community project and so the toolboxes that exist are donated by those interested in them through [[Octave Forge]]. These might be lacking in certain functionality relative to the Matlab toolboxes, and might not exactly duplicate the Matlab functionality or interface.
−
===Short-circuit {{Codeline|&}} and {{Codeline|&#124;}} operators===
+
==Short-circuit <code>&</code> and <code>|</code> operators==
−
The {{Codeline|&}} and {{Codeline|&#124;}} operators in Matlab short-circuit when included in a condition (e.g. an {{Codeline|if}} or {{Codeline|while}} statement) and not otherwise. In Octave only the {{Codeline|&&}} and {{Codeline|&#124;&#124;}} short circuit. Note that this means that
+
The <code>&</code> and <code>|</code> operators in Matlab short-circuit when included in a condition (e.g. an {{Codeline|if}} or {{Codeline|while}} statement) and not otherwise. In Octave only the <code>&&</code> and <code>||</code> short circuit. Note that this means that
−
if (a | b)
+
<syntaxhighlight lang="Octave">
...
+
if (a | b)
end
+
...
+
end
+
</syntaxhighlight>

and

and
−
t = a | b;
+
<syntaxhighlight lang="Octave">
if t
+
t = a | b;
...
+
if (t)
end
+
...
+
end
+
</syntaxhighlight>
+

+
have different semantics in Matlab.  This is really a Matlab bug, but there is too much code out there that relies on this behavior to change it.  Prefer the <code>&&</code> and <code>||</code> operators in {{Codeline|if}} statements if possible.
−
have different semantics in Matlab. This is really a Matlab bug, but there is too much code out there that relies on this behaviour to change it. Prefer the {{Codeline|&#124;&#124;}} and {{Codeline|&&}} operators in {{Codeline|if}} statements if possible. If you need to use code written for Matlab that depends on this buggy behaviour, you can enable it since Octave 3.4.0 with the following command:
+
Note that the difference with Matlab is also significant when either argument is a function with side effects or if the first argument is a scalar and the second argument is an empty matrix. For example, note the difference between
−
+
<syntaxhighlight lang="Octave">
+
t = 1 | [];          ## results in [], so...
+
if (t) 1, end        ## in if ([]), this is false.
+
</syntaxhighlight>
−
Note that the difference with Matlab is also significant when either argument is a function with side effects or if the first argument is a scalar and the second argument is an empty matrix. For example, note the difference between
+
and
−
t = 1 | [];          ## results in [], so...
+
<syntaxhighlight lang="Octave">
if (t) 1, end       ## in if ([]), this is false.
+
if (1 | []) 1, end   ## short circuits so condition is true.
+
</syntaxhighlight>
−
and
+
In the latter case, Octave displays since version 4.0.0 a warning:
−
if (1 | []) 1, end   ## short circuits so condition is true.
+
warning: Matlab-style short-circuit operation performed for operator |

Another case that is documented in the Matlab manuals is that

Another case that is documented in the Matlab manuals is that
−
t = [1, 1] | [1, 2, 3];          ## error
+
<syntaxhighlight lang="Matlab">
if ([1, 1] | [1, 2, 3]) 1, end  ## OK
+
t = [1, 1] | [1, 2, 3];          ## error
+
if ([1, 1] | [1, 2, 3]) 1, end  ## OK
+
</syntaxhighlight>
−
Also Matlab requires the operands of {{Codeline|&&}} and {{Codeline|&#124;&#124;}} to be scalar values but Octave does not (it just applies the rule that for an operand to be considered true, every element of the object must be nonzero or logically true).
+
Also Matlab requires the operands of <code>&&</code> and <code>||</code> to be scalar values but Octave does not (it just applies the rule that for an operand to be considered true, every element of the object must be nonzero or logically true).

Finally, note the inconsistence of thinking of the condition of an {{Codeline|if}} statement as being equivalent to {{Codeline|all(X(:))}} when {{Codeline|X}} is a matrix. This is true for all cases EXCEPT empty matrices:

Finally, note the inconsistence of thinking of the condition of an {{Codeline|if}} statement as being equivalent to {{Codeline|all(X(:))}} when {{Codeline|X}} is a matrix. This is true for all cases EXCEPT empty matrices:
−
if ([0, 1]) == if (all ([0, 1]))  ==>  i.e., condition is false.
+
<syntaxhighlight lang="Matlab">
if ([1, 1]) == if (all ([1, 1]))  ==>  i.e., condition is true.
+
if ([0, 1]) == if (all ([0, 1]))  ==>  i.e., condition is false.
+
if ([1, 1]) == if (all ([1, 1]))  ==>  i.e., condition is true.
+
</syntaxhighlight>

However,

However,
−
if ([])
+
<syntaxhighlight lang="Matlab">
+
if ([])
+
</syntaxhighlight>

is not the same as

is not the same as
−
if (all ([]))
+
<syntaxhighlight lang="Matlab">
+
if (all ([]))
+
</syntaxhighlight>
−
because, despite the name, the {{Codeline|all}} is really returning true if none of the elements of the matrix are zero, and since there are no elements, well, none of them are zero. This is an example of [http://en.wikipedia.org/wiki/Vacuous_truth vacuous truth]. But, somewhere along the line, someone decided that {{Codeline|if ([])}} should be false. Mathworks probably thought it just looks wrong to have {{Codeline|[]}} be true in this context even if you can use logical gymnastics to convince yourself that "all" the elements of an empty matrix are nonzero. Octave however duplicates this behavior for {{Codeline|if}} statements containing empty matrices.
+
because, despite the name, the {{manual|all}} is really returning true if none of the elements of the matrix are zero, and since there are no elements, well, none of them are zero. This is an example of [https://en.wikipedia.org/wiki/Vacuous_truth vacuous truth]. But, somewhere along the line, someone decided that {{Codeline|if ([])}} should be false. The Mathworks probably thought it just looks wrong to have {{Codeline|[]}} be true in this context even if you can use logical gymnastics to convince yourself that "all" the elements of an empty matrix are nonzero. Octave however duplicates this behavior for {{Codeline|if}} statements containing empty matrices.
−
===Solvers for singular, under- and over-determined matrices===
+
==Solvers for singular, under- and over-determined matrices==
−
Matlab's solvers as used by the operators mldivide (\) and mrdivide (/), use a different approach than Octave's in the case of singular, under-, or over-determined matrices. In the case of a singular matrix, Matlab returns the result given by the LU decomposition, even though the underlying solver has flagged the result as erroneous. Octave has made the choice of falling back to a minimum norm solution of matrices that have been flagged as singular which arguably is a better result for these cases.
+
Matlab's solvers as used by the operators {{manual|mldivide}} <code>\</code> and {{manual|mrdivide}} <code>/</code>, use a different approach than Octave's in the case of singular, under-, or over-determined matrices. In the case of a singular matrix, Matlab returns the result given by the LU decomposition, even though the underlying solver has flagged the result as erroneous. Octave has made the choice of falling back to a minimum norm solution of matrices that have been flagged as singular which arguably is a better result for these cases.

In the case of under- or over-determined matrices, Octave continues to use a minimum norm solution, whereas Matlab uses an approach that is equivalent to

In the case of under- or over-determined matrices, Octave continues to use a minimum norm solution, whereas Matlab uses an approach that is equivalent to
−
function x = mldivide (A, b)
+
<syntaxhighlight lang="Octave">
m = rows(A);
+
function x = mldivide (A, b)
[Q, R, E] = qr(A);
+
m = rows (A);
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]
+
[Q, R, E] = qr (A);
end
+
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]
+
end
+
</syntaxhighlight>

While this approach is certainly faster and uses less memory than Octave's minimum norm approach, this approach seems to be inferior in other ways.

While this approach is certainly faster and uses less memory than Octave's minimum norm approach, this approach seems to be inferior in other ways.
−
A numerical question arises: how big can the null space component become, relative to the minimum-norm solution? Can it be nicely bounded, or can it be arbitrarily big? Consider this example:
+
A numerical question arises: how big can the null space component become, relative to the minimum-norm solution? Can it be nicely bounded, or can it be arbitrarily big? Consider this example:
−
m = 10;
+
<syntaxhighlight lang="Octave">
n = 10000;
+
m = 10;
A = ones(m, n) + 1e-6 * randn(m,n);
+
n = 10000;
b = ones(m, 1) + 1e-6 * randn(m,1);
+
A = ones (m, n) + 1e-6 * randn (m, n);
norm(A \ b)
+
b = ones (m, 1) + 1e-6 * randn (m, 1);
+
norm (A \ b)
+
</syntaxhighlight>
−
while Octave's minimum-norm values are around 3e-2, Matlab's results are 50-times larger. For another issue, try this code:
+
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:
−
m = 5;
+
<syntaxhighlight lang="Octave">
n = 100;
+
m = 5;
j = floor(m * rand(1, n)) + 1;
+
n = 100;
b = ones(m, 1);
+
j = floor (m * rand (1, n)) + 1;
A = zeros(m, n);
+
b = ones (m, 1);
A(sub2ind(size(A),j,1:n)) = 1;
+
A = zeros (m, n);
x = A \ b;
+
A(sub2ind(size(A),j,1:n)) = 1;
[dummy,p] = sort(rand(1,n));
+
x = A \ b;
y = A(:,p)\b;
+
[~,p] = sort (rand (1, n));
norm(x(p)-y)
+
y = A(:,p) \ b;
+
norm (x(p) - y)
+
</syntaxhighlight>
−
It shows that unlike in Octave, mldivide in Matlab is not invariant with respect to column permutations. If there are multiple columns of the same norm, permuting columns of the matrix gets you different result than permuting the solution vector. This will surprise many users.
+
It shows that unlike in Octave, {{manual|mldivide}} in Matlab is not invariant with respect to column permutations. If there are multiple columns of the same norm, permuting columns of the matrix gets you different result than permuting the solution vector. This will surprise many users.
−
Since the mldivide (\) and mrdivide (/) operators are often part of a more complex expression, where there is no room to react to warnings or flags, it should prefer intelligence (robustness) to speed, and so the Octave developers are firmly of the opinion that Octave's approach for singular, under- and over-determined matrices is a better choice than Matlab's.
+
Since the {{manual|mldivide}} <code>\</code> and {{manual|mrdivide}} <code>/</code> operators are often part of a more complex expression, where there is no room to react to warnings or flags, it should prefer intelligence (robustness) to speed, and so the Octave developers are firmly of the opinion that Octave's approach for singular, under- and over-determined matrices is a better choice than Matlab's.
−
===Octave extensions===
+
==Octave extensions==
−
The extensions in Octave over Matlab syntax are very useful, but might cause issues when sharing with Matlab users. A list of the major extensions that should be avoided to be compatible with Matlab are:
+
The extensions in Octave over MATLAB syntax are very useful, but might cause issues when sharing with Matlab users. A list of the major extensions that should be avoided to be compatible with Matlab are:
−
Comments in octave can be marked with {{Codeline|#}}. This allows POSIX systems to have the first line as {{Codeline|#! octave -q}} and mark the script itself executable. Matlab doesn't have this feature due to the absence of comments starting with {{Codeline|#}}".
+
Comments in Octave can be marked with {{Codeline|#}}. This allows POSIX systems to have the first line as {{Codeline|#! octave -q}} and mark the script itself executable. MATLAB doesn't have this feature due to the absence of comments starting with {{Codeline|#}}".
−
Code blocks like if, for, while, etc can be terminated with block specific terminations like endif. Matlab doesn't have this and all blocks must be terminated with end.
+
Code blocks like if, for, while, etc can be terminated with block specific terminations like endif. MATLAB doesn't have this and all blocks must be terminated with end.
−
Octave has a lisp-like {{Codeline|unwind_protect}} block that allows blocks of code that terminate in an error to ensure that the variables that are touched are restored. You can do something similar with try/catch combined with {{Codeline|rethrow (lasterror ())}} in Matlab, however rethrow and lasterror are only available in Octave 2.9.10 and later. Matlab 2008a also introduced {{Codeline|OnCleanUp}} that is similar to {{Codeline|unwind_protect}}, except that the object created by this function has to be explicitly cleared in order for the cleanup code to run.
+
Octave has a lisp-like {{Codeline|unwind_protect}} block that allows blocks of code that terminate in an error to ensure that the variables that are touched are restored. You can do something similar with try/catch combined with {{Codeline|rethrow (lasterror ())}} in Matlab, however rethrow and lasterror are only available in Octave 2.9.10 and later. MATLAB 2008a also introduced {{Codeline|OnCleanUp}} that is similar to {{Codeline|unwind_protect}}, except that the object created by this function has to be explicitly cleared in order for the cleanup code to run.
−
Note that using try/catch combined with {{Codeline|rethrow (lasterror ())}} can not guarantee that global variables will be correctly reset, as it won't catch user interrupts with Ctrl-C. For example
+
Note that using try/catch combined with {{Codeline|rethrow (lasterror ())}} cannot guarantee that global variables will be correctly reset, as it won't catch user interrupts with Ctrl-C. For example
−
global a
+
<syntaxhighlight lang="Matlab">
a = 1;
+
global a
try
+
a = 1;
_a = a;
+
try
a = 2
+
_a = a;
while true
+
a = 2
end
+
while true
catch
+
end
fprintf ('caught interrupt\n');
+
catch
a = _a;
+
fprintf ('caught interrupt\n');
rethrow (lasterror());
+
a = _a;
end
+
rethrow (lasterror());
+
end
+
</syntaxhighlight>

compared to

compared to
−
global a
+
<syntaxhighlight lang="Octave">
a = 1;
+
global a
unwind_protect
+
a = 1;
_a = a;
+
unwind_protect
a = 2
+
_a = a;
while true
+
a = 2
end
+
while true
unwind_protect_cleanup
+
end
fprintf ('caught interrupt\n');
+
unwind_protect_cleanup
a = _a;
+
fprintf ('caught interrupt\n');
end
+
a = _a;
+
end
+
</syntaxhighlight>
−
Typing Ctrl-C in the first case returns the user directly to the prompt, and the variable ''a'' is not reset to the saved value. In the second case the variable ''a'' is reset correctly. Therefore Matlab gives no safe way of temporarily changing global variables.
+
Typing Ctrl-C in the first case returns the user directly to the prompt, and the variable <code>a</code> is not reset to the saved value. In the second case the variable <code>a</code> is reset correctly. Therefore Matlab gives no safe way of temporarily changing global variables.

Indexing can be applied to all objects in Octave and not just variables. Therefore {{Codeline|sin(x)(1:10)}} for example is perfectly valid in Octave but not Matlab. To do the same in Matlab you must do {{Codeline|y &#61; sin(x); y &#61; y([1:10]);}}

Indexing can be applied to all objects in Octave and not just variables. Therefore {{Codeline|sin(x)(1:10)}} for example is perfectly valid in Octave but not Matlab. To do the same in Matlab you must do {{Codeline|y &#61; sin(x); y &#61; y([1:10]);}}
−
Octave has the operators {{Codeline|++}}, {{Codeline|–-}}, {{Codeline|-&#61;}}, {{Codeline|+&#61;}}, {{Codeline|*&#61;}}, etc. As Matlab doesn't, if you are sharing code these should be avoided.
+
Octave has the operators {{Codeline|++}}, {{Codeline|–-}}, {{Codeline|-&#61;}}, {{Codeline|+&#61;}}, {{Codeline|*&#61;}}, etc. As MATLAB doesn't, if you are sharing code these should be avoided.
+

+
Character strings in Octave can be denoted with double or single quotes. There is a subtle difference between the two in that escaped characters like {{Codeline|\n}} (newline), {{Codeline|\t}} (tab), etc are interpreted in double quoted strings but not single quoted strings. This difference is important on Windows platforms where the {{Codeline|\}} character is used in path names, and so single quoted strings should be used in paths. MATLAB doesn't have double quoted strings and so they should be avoided if the code will be transferred to a MATLAB user.
+

+
==What features are unique to Octave?==
+

+
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.
+

+
=== Functions defined on the command-line===
+
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:
+

+
<syntaxhighlight lang="Octave">
+
>> function s = hello_string (to_who)
+
> ## Say hello
+
> if nargin<1, to_who = "World"; end
+
> s = ["Hello ",\
+
>      to_who];
+
> endfunction
+
>> hello_string ("Moon")
+
ans = Hello Moon
+
</syntaxhighlight>
+

+
As a natural extension of this, functions can also be defined in script files (m-files whose first non-comment line isn't {{Codeline|function out &#61; foo (...)}})
+

+
Note: MATLAB R2016b added the ability to [http://www.mathworks.com/help/matlab/matlab_prog/local-functions-in-scripts.html define functions in script files].
−
Character strings in Octave can be denoted with double or single quotes. There is a subtle difference between the two in that escaped characters like {{Codeline|\n}} (newline), {{Codeline|\t}} (tab), etc are interpreted in double quoted strings but not single quoted strings. This difference is important on Windows platforms where the {{Codeline|\}} character is used in path names, and so single quoted strings should be used in paths. Matlab doesn't have double quoted strings and so they should be avoided if the code will be transferred to a Matlab user.
+
−
=GUI=
+
The pound character, {{Codeline|#}}, may be used to start comments, in addition to {{Codeline|%}}. See the previous example. The major advantage of this is that as {{Codeline|#}} is also a comment character for unix script files, any file that starts with a string like {{Codeline|#! /usr/bin/octave -q}} will be treated as an octave script and be executed by octave.
This is a small section but it's probably one of the most frequent questions.
+

+
===Strings delimited by double quotes "===
+

+
In 2016, Matlab introduced String Arrays, that are initialized by using double quoted strings, and are not implemented in Octave yet.  In Octave double-quoted strings include backslash interpretation (like C++, C, and Perl) while single quoted are uninterpreted (like Matlab and Perl).
+

+
===Line continuation by backslash===
+

+
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.
+

+
===Informative block closing===
+

+
You may close function, for, while, if, ... blocks with endfunction, endfor, endwhile, ... keywords in addition to using end. As with Matlab, the end (or endfunction) keyword that marks the end of a function defined in a .m file is optional.
+

+
===Coherent syntax===
+

+
Indexing other things than variables is possible, as in:
+

+
<syntaxhighlight lang="Octave">
+
>> [3 1 4 1 5 9](3)
+
ans = 4
+
>> cos([0 pi pi/4 7])(3)
+
ans = 0.70711
+
</syntaxhighlight>
+

+
In Matlab, it is for example necessary to assign the intermediate result {{Codeline|cos([0 pi pi/4 7])}} to a variable before it can be indexed again.
+

+
===Exclamation mark as not operator===
+

+
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:
+

+
<syntaxhighlight lang="Octave">
+
>> if ! strcmp (program_name, "octave"),
+
>  "It's an error"
+
> else
+
>  "It works!"
+
> end
+
ans = It works!
+
</syntaxhighlight>
+

+
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.
+

+
===Increment and decrement operators===
+

+
If you like the {{Codeline|++}}, {{Codeline|+&#61;}} etc operators, rejoice! Octave includes the C-like increment and decrement operators {{Codeline|++}} and {{Codeline|--}} in both their prefix and postfix forms, in addition to {{Codeline|+&#61;}}, {{Codeline|-&#61;}}, {{Codeline|*&#61;}}, {{Codeline|/&#61;}}, {{Codeline|^&#61;}},{{Codeline|.+&#61;}},{{Codeline|.-&#61;}},{{Codeline|.*&#61;}}, {{Codeline|./&#61;}} and {{Codeline|.^&#61;}}.
+

+
For example, to pre-increment the variable x, you would write {{Codeline|++x}}. This would add one to x and then return the new value of x as the result of the expression. It is exactly the same as the expression {{Codeline|x &#61; x + 1}}.
+

+
To post-increment a variable x, you would write {{Codeline|x++}}. This adds one to the variable x, but returns the value that x had prior to incrementing it. For example, if x is equal to 2, the result of the expression x++ is 2, and the new value of x is 3.
+

+
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.
+

+
===Unwind-protect===
+

+
In addition to try-catch blocks, Octave supports an alternative form of exception handling modeled after the unwind-protect form of Lisp. The general form of an unwind_protect block looks like this:
+

+
<syntaxhighlight lang="Octave">
+
unwind_protect
+
body
+
unwind_protect_cleanup
+
cleanup
+
end_unwind_protect
+
</syntaxhighlight>
+

+
Where body and cleanup are both optional and may contain any Octave expressions or commands. The statements in cleanup are guaranteed to be executed regardless of how control exits body.
+

+
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.
+

+
Matlab can be made to do something similar with their {{manaul|onCleanup}} function that was introduced in 2008a. Octave also has {{manual|onCleanup}} since version 3.4.0.
+

+
===Built-in ODE and DAE solvers===
+

+
Octave includes LSODE, DASSL and DASPK for solving systems of stiff ordinary differential and differential-algebraic equations. These functions are built in to the interpreter.
+

+
===Do-Until loop structure===
+

+
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:
+

+
<syntaxhighlight lang="Octave">
+
x = 0
+
do
+
x += 1;
+
until (x == 10)
+
</syntaxhighlight>
+

+
+

+
+

+
<syntaxhighlight lang="Octave">
+
f = (1:0.1:2);
+
# put angular frequencies on the first dimension to prepare broadcasting
+
omega = 2 * pi * f(:);
+
# time is already on the second dimension (row vector)
+
t = 0:0.02:2;
+
# the resulting s will be a 2-dimensional array
+
s = sin(omega .* t);
+
# which can be displayed as
+
pcolor(t, f, s)
+
xlabel("t (s)")
+
ylabel("f (Hz)")
+
</syntaxhighlight>
+

+
Note: [https://www.mathworks.com/help/matlab/matlab_prog/compatible-array-sizes-for-basic-operations.html Automatic expansion of dimensions] was added to MATLAB R2016b.
+

+
===Documentation strings===
+

+
Octave allows extensive formatting of the help string of functions using Texinfo. The effect on the online documentation is relatively small, but makes the help string of functions conform to the help of Octave’s own functions. However, the effect on the appearance of printed or online documentation will be greatly improved.
+

+
===Test functions===
+

+
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.
+

+
<syntaxhighlight lang="Octave">
+
function mult = a(val)
+
mult = val.*2;
+
endfunction
+
%!test
+
%! assert (a(3), 6);
+
</syntaxhighlight>
+

+
Such a function can be tested for valid outputs by following code:
+

+
>> test a
+
PASSES 1 out of 1 test
+

+
===Demonstration Functions===
+

+
Example code block can be part of function file in a similar manner as test functions. For example to run {{manual|demo}} for function multinom of package specfun, use:
+

+
demo multinom
+

+
===Powerful assert===
+

+
Function assert have extended input possibilities.
+

+
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=

==Does Octave have a GUI?==

==Does Octave have a GUI?==
Yes! It was released with Octave 3.8.0 (Jan 1st, 2014) but is considered experimental. To start Octave with the GUI, use the {{Codeline|--force-gui}} option.
−
==When will the GUI stop being experimental?==
+
'''Yes!''' It was officially released with Octave 4.0.0.  It was also available since version 3.8.0 as an experimental feature (use the {{Codeline|--force-gui}} option to start Octave).
The plan is for the GUI to be considered stable with version 4.0.
+

+
==Why did you create yet another GUI instead of making one that already exists better?==
+

+
The previously existing GUIs were not part of Octave itself.  The integration within Octave was rather bad, as all of them treated Octave as a foreign black box and used pipes for communication.  This approach is bound to fail with each new version of Octave, as any fix would only be temporary.  For historical reasons and to honor the approaches, a short list of previous GUIs for Octave:
+

+
* '''QtOctave''' was a great, beautiful, and very useful tool which is now abandoned and incompatible with newer versions of Octave.  We are thankful to its developers to make it free software so we could reuse large chunks of it for what is now the Octave GUI.
+

+
* '''Quint''' was a project for an Octave GUI that actually tried to do it right.  Eventually [https://lists.gnu.org/archive/html/octave-maintainers/2011-07/msg00096.html it was merged into the Octave repository] and is no longer a separate project.  Also, many bits from QtOctave were reused in the GUI.
+

+
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.
+

+
* '''GUI Octave''', which was proprietary and is no longer available.
+

+
=Graphics: backends and toolkits=
+

+
==What are the supported graphics backends?==
+

+
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''
+
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit
+

+
==How do I change my graphics toolkit?==
+

+
There are three commands to deal with graphics toolkits:
+

+
{| class="wikitable"
+
| <code>available_graphics_toolkits</code>
+
| lists all available graphics toolkits
+
|-
+
| <code>graphics_toolkit</code>
+
| displays the currently used graphics toolkit
+
|-
+
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code>
+
| sets the graphics toolkit to either of [https://www.qt.io/ qt], [http://www.fltk.org/ fltk], or [http://www.gnuplot.info/ gnuplot], if available
+
|}
+

+
==Why did you replace gnuplot with an OpenGL backend?==
+

+
The development of Octave is committed to being both compatible with Matlab and adding additional features.  Toward those ends, the developers decided to introduce a native OpenGL backend that supports Matlab handle graphics and its uicontrols.  Starting with the 3.8 release, Octave uses OpenGL graphics by default (with [http://www.fltk.org/ FLTK widgets] in Octave 3.8 and [https://www.qt.io/ Qt widgets] in Octave 4.0 and later).
+

+
==Are there any plans to remove the gnuplot backend?==
+

+
'''No.''' There are no plans to remove the gnuplot backend.  It will be available as long as our users find it useful.
+

+
==How can I implement a new graphics backend/toolkit?==
+

+
This is one of those times where the best documentation is to read the existing code.  We have three different toolkits in Octave now, so there are some examples to draw from.
+

+
=Development=
+

+
==When will feature X be released or implemented?==
+

+
When it's ready, sooner [http://www.octave.org/get-involved.html if you help].  You can [https://savannah.gnu.org/patch/?group=octave send us patches] if you can implement feature X yourself.  If you can't, some [http://www.octave.org/commercial-support.html developers may be convinced to work on your specific problem for some money].
+

+
==How can I get involved in Octave development?==
+

+
Be around.  Be social.  Participate in our mailing lists [https://lists.gnu.org/mailman/listinfo/help-octave help@octave.org] and [https://lists.gnu.org/mailman/listinfo/octave-maintainers maintainers@octave.org].  Find things about Octave you don't like, and start thinking about how to fix them.  Many people who now contribute to Octave first spent several years helping in the mailing list before they started to delve into the code.  A good way to learn Octave is to understand the problems other people are having with it, so being helpful in the mailing lists not only helps Octave as a whole, but it also prepares you to be a better Octave contributor.
+

+
If you feel ready to dive right into the code, read the [[Developers]] wiki page or [http://www.octave.org/get-involved.html start here].  But do not send an email to the mailing lists listing your skills and offering to help.  We won't just suggest things for you to do.  We lack volunteers and we do need your help, but because of that, we also lack the time to provide good guidance and mentoring.  If there is a specific short-term project you would like to work on, say so, and just do it.  Then ask for help or advice when you're doing it.  It is a lot more important that you do something that you're actually interested on than something we suggested because it only matches your skills.
−
==Why are you working on yet another GUI instead of making one that already exists better?==
+
We also need help with this wiki and the [http://www.octave.org/doc/interpreter/ manual].  These are also important tasks. The documentation is easy to patch, and the help text for individual functions even more so.  Editing this wiki is even easier.
None of the GUIs for Octave that have been developed thus far are part of Octave and there is a reason for it. All of them fail at a very important point, integration with Octave. They treat Octave as a foreign black box using pipes for communication, an approach that is bound to fail with each new version. Any fix made to make them work with new Octave versions would only be temporary. This included QtOctave (now abandoned and incompatible with newer versions of Octave), Xoctave (which is proprietary and commercial) and GUI Octave (which is proprietary).
−
QtOctave was great and very useful tool. It looked beautiful and we are thankful to its developers for working on such a nice tool plus making it libre. However, it would ''never'' be stable.
+
Accurate bug reporting is also very useful. Find and report [http://bugs.octave.org/ bugs], making an attempt to diagnose them.  Eventually, you will also know how to fix them. If you want to help with bug reports or patches, subscribe to the [https://lists.gnu.org/mailman/listinfo/octave-bug-tracker bug tracker mailing list].  You'll get updates on all bug activity, and you can jump in when you see
+
something you can help with.
−
Quint was a project for an Octave GUI that actually tried to do it right. Eventually it was merged into the Octave repository and is no longer a separate project. Also, many bits from QtOctave were reused in the GUI.
+
Look at our [[projects]], [[short projects]], and [[Summer of Code Project Ideas]] if you need specific inspiration for coding tasks that we would like to get done.
1,556

edits