https://wiki.octave.org/wiki/api.php?action=feedcontributions&user=Prubhtej+Singh&feedformat=atomOctave - User contributions [en]2020-08-14T20:24:28ZUser contributionsMediaWiki 1.34.1https://wiki.octave.org/wiki/index.php?title=FAQ&diff=13048FAQ2020-06-01T20:49:11Z<p>Prubhtej Singh: /* Should I favor the MEX interface to avoid the GPL? */ Corrected a spelling error in the headline</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc. Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity.<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organization that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to. 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 as well. 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 for the same.<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After Octave upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references. Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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.<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression.<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favour the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S, refer to : [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on MacOS?==<br />
<br />
:''So as to install GNU-Octave for MacOS, refer to : [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:'' So as to install GNU-Octave on GNU/Linux, refer to: [[Octave for GNU/Linux]]''<br />
<br />
==How to install Octave on Android OR What is the Octave app available in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for further information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies, refer to [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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 known to work as well). If you face any 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].<br />
<br />
=What's new in Octave?=<br />
<br />
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.<br />
<br />
* '''What's new in the next version of Octave?'''<br />
** See the [https://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
* '''What was new in Octave Version X.Y.Z?'''<br />
** See [[Release History]].<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
=Differences between Octave and Matlab=<br />
:''See [[Differences between Octave and Matlab]]''.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=Mercurial&diff=12954Mercurial2020-05-10T05:29:42Z<p>Prubhtej Singh: /* Submitting patches */ spelling error</p>
<hr />
<div>[[wikipedia:Mercurial|Mercurial]] (sometimes referred to as {{codeline|hg}})<br />
is the source code management system currently used to develop<br />
Octave.<br />
<br />
== Introduction to Mercurial ==<br />
<br />
An introduction to Mercurial is completely outside the scope of this document.<br />
There are plenty of available documentation on the topic. Some recommendations<br />
are:<br />
<br />
* [http://hginit.com/ Hg Init]<br />
* [https://www.mercurial-scm.org/wiki/Tutorial Mercurial tutorial]<br />
* [https://www.mercurial-scm.org/wiki/QuickStart Mercurial quick start]<br />
<br />
== Contributing to Octave ==<br />
<br />
The preferred method to contribute to Octave is with Mercurial changesets.<br />
Other forms of contributions (e.g., simple diff patches) are<br />
also acceptable, but they slow down the review process.<br />
<br />
If you plan on contributing to Octave:<br />
<br />
* See other [[Contribution guidelines]]<br />
* Always include commit messages in changesets. Please follow the Octave [[commit message guidelines]]<br />
* Follow the style guides for both [[Octave style guide|Octave]] and [[C++ style guide|C++]] languages.<br />
<br />
== Getting the development sources ==<br />
<br />
To clone the Octave repository:<br />
<br />
hg clone http://www.octave.org/hg/octave octave<br />
<br />
Octave packages like image, signal, control, etc. are not parts of Octave<br />
itself, they belong to the Octave Forge. Each package has its own<br />
repository, a list of which can be found<br />
[http://sourceforge.net/p/octave/_list/hg?source=navbar here].<br />
You can clone them in a similar way, for example, to clone the signal package<br />
<br />
hg clone http://hg.code.sf.net/p/octave/signal octave-signal<br />
<br />
== Mercurial configuration ==<br />
<br />
You can use the following to start your hgrc<br />
<br />
{{File||<pre><br />
[ui]<br />
username = Your Name <your@email><br />
<br />
[extensions]<br />
color =<br />
histedit =<br />
pager =<br />
rebase =<br />
strip =<br />
<br />
[pager]<br />
pager = LESS='FSRX' less<br />
attend = help, annotate, cat, diff, export, glog, log, outgoing, incoming<br />
<br />
[diff]<br />
showfunc = True<br />
<br />
[color]<br />
mode = terminfo<br />
<br />
## Custom colors<br />
color.gray = 244<br />
color.orange = 202<br />
color.lightyellow = 191<br />
color.darkorange = 220<br />
color.brightyellow = 226<br />
<br />
status.modified = magenta bold<br />
status.added = green bold<br />
status.removed = red bold<br />
status.deleted = cyan bold<br />
status.unknown = gray bold<br />
status.ignored = gray bold<br />
<br />
## Colours for each label<br />
log.branch = cyan<br />
log.summary = lightyellow<br />
log.description = lightyellow<br />
log.bookmark = green<br />
log.tag = darkorange<br />
log.graph = blue<br />
<br />
## Colors for each phase<br />
changeset.secret = blue bold<br />
changeset.draft = red bold<br />
changeset.public = orange<br />
<br />
desc.here = bold blue_background<br />
<br />
[bookmarks]<br />
track.current = True<br />
<br />
[alias]<br />
glog = log --graph<br />
top = log --graph -l<br />
</pre>}}<br />
<br />
== Submitting patches ==<br />
<br />
When you do not have push permissions to the repository (you cannot add your changes using mercurial itself) and you have a modification to the current GNU Octave code, you have to generate a patch (or changeset) so developers with permissions can include them in the code. The overview of the process is as follows<br />
# Change the code and test that your changes do work (write tests, that's the best!).<br />
# Create the changeset (instructions below). <br />
# Post your patch in the [https://savannah.gnu.org/patch/?group=octave Patch tracker].<br />
<br />
<br />
Patch submissions is done via the [https://savannah.gnu.org/bugs/?group=octave bug]<br />
or [https://savannah.gnu.org/patch/?group=octave patch] trackers. Either<br />
way, you can submit via two different methods: pull requests or attaching<br />
a changeset file.<br />
<br />
=== Pull request ===<br />
<br />
This is the cleaner way. You push your clone to public site, and ask on the<br />
bug tracker to pull a specific changeset from it. It makes special sense if<br />
you plan to send more patches in the future but requires to host the clone<br />
somewhere. Free mercurial repositories are available on [https://bitbucket.org/ bitbucket]<br />
<br />
<br />
=== Creating changesets files with hg ===<br />
==== Simple way ====<br />
* Update to the latest revision. <br />
<pre> hg up </pre><br />
* Make your changes and save them. <br />
* Commit your code. Mercurial will ask you for a commit message, which should follow the [[commit message guidelines]].<br />
<pre> hg ci </pre><br />
* Export the modifications. This creates a file (in the case of the example below, it is called mypatch.patch) that contains a description of the changes that you've made. Someone else can then apply the patch and end up with a repository that looks the same as yours.<br />
<pre> hg export -r tip -o mypatch.patch </pre><br />
* Save the output to a file and upload it to the patch tracker. If your patch file is larger than the upload limit, you can compress it before uploading. Please use a free format!<br />
<br />
== Mercurial Tips for SoC students ==<br />
<br />
This section is meant to provide tips for SOCIS or GSoC students working on new Octave features.<br />
<br />
Students should publish their work as it progresses in a public repository <br />
merging regularly the main savannah repository to facilitate merging back their <br />
code at the end of the project. <br />
<br />
Here are some useful hg commands that can be used to do this.<br />
<br />
=== Getting started ===<br />
<!--[[File:Hg-student-start.png]]--><br />
<ol><br />
<li> Clone the main Octave repository at savannah:<br><br />
<code> hg clone http://www.octave.org/hg/octave </code> </li><br />
<li> Create a new bookmark:<br><br />
<code> hg bookmark student-bookmark-name </code> </li><br />
<li> Make the bookmark visible in the public repo, assuming the public repo is at <code>public.server.org/octave</code><br><br />
<code> hg push --bookmark ssh://student@public.server.org/octave </code> </li><br />
</ol><br />
<br />
=== Staying up-to-date with the main savannah repository ===<br />
<br />
<!-- After working for a while, the public repo should look like the following picture. --><br />
As the students development proceeds,<br />
the savannah repository gets updated, too. <br />
To avoid having the two branches diverging too much, which can<br />
lead to conflicts when the final merge is done, students should<br />
keep their public repo up-to-date with the recent changes, <br />
the following commands can be used for this:<br/><br />
<ol><br />
<!--[[File:Hg-student-flow1.png]] <br/>--><br />
<li> Download new changes from the main line of development <br/><br />
<code> hg pull http://www.octave.org/hg/octave </code> </li><br />
<li> Merge the main line of development into the feature branch <br/><br />
<code> hg up -r student-bookmark-name </code> <br/><br />
<!--[[File:Hg-student-flow2.png]] <br/>--><br />
<code> hg merge @ </code> </li><br />
<li> Apply the change and publish it <br/><br />
<code> hg commit -m "periodic merge of default branch into my branch" </code> <br/><br />
<!--[[File:Hg-student-flow3.png]] <br/>--><br />
<code> hg push ssh://student@public.server.org/octave </code></li><br />
</ol><br />
<br />
=== Preparing for code reviews ===<br />
At the time of the mid-term or final review (or whenever the mentor requires it) students should prepare their code <br />
for review and possibly inclusion into the main development branch. To this end students should:<br />
<ol><br />
<li> prepare a full log of their changes, listing files that have been touched <br />
and including a summary of the purpose of those changes. If students have been following <br />
the [[Commit message guidelines]] the following command will give a good starting point<br> <br />
<code> hg log --style=changelog --no-merges --user student-name </code><br><br />
this message should be edited so that <br />
<ol style="list-style-type: lower-roman;"><br />
<li> each touched file appears only once </li><br />
<li> changes that were backed out should not be mentioned <!--(like changeset "H" in the above example)--> </li><br />
</ol><br />
The main purpose of this log is to make it easy, not only for the main mentor, but also for other developers who<br />
have not been closely following the progress of the project to quickly understand where to look at in the code to evaluate it, but it will also be used as the commit message for the merge changeset, so it should itself comply with the [[Commit message guidelines]].<br />
<li> prepare a merge changeset including all the code that should be submitted for review<br />
<ol style="list-style-type: lower-roman;"><br />
<li> pull from the main repository<br/><br />
<code>hg pull http://www.octave.org/hg/octave</code></li><br />
<li> move to the top of the main line of development and merge in the feature branch<br/><br />
<code>hg up -r @</code><br/><br />
<code>hg merge student-bookmark-name </code><br/></li><br />
<li> create a changeset, export it and send to the mentor for review, remember to use the log created above as a commit message<br/><br />
<code>hg commit </code><br/><br />
<code>hg export @ > mid-term-review.changeset </code><br/><br />
the file mid-term-review.changeset can then be sent to the [mailto:octave-maintainers@octave.org mailing list] or posted<br />
to the [https://savannah.gnu.org/patch/?group=octave patch tracker]</li><br />
</ol> </li><br />
</ol><br />
<br />
== Mercurial Tips for SoC mentors ==<br />
<br />
Will fill in this section after trying out the above procedure at least once with a student and actually pushing his changes to the main repo.<br />
<!---<br />
<code><br />
hg pull http://student.repo.url<br />
</code><br />
<br />
<code><br />
hg pull http://www.octave.org/hg/octave<br />
</code><br />
<br />
<code><br />
hg up -r @<br />
</code><br />
<br />
<code><br />
hg merge student_bookmark<br />
</code><br />
<br />
<code><br />
hg log --style=changelog --user student<br />
</code><br />
--><br />
<br />
==External links==<br />
<br />
* [https://www.mercurial-scm.org/ Official website]<br />
<br />
[[Category:Development]]</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12953FAQ2020-05-08T13:39:21Z<p>Prubhtej Singh: /* Do I need GCC to build Octave from the source code? */ Grammatical errors</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S ,refer to : [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on MacOS?==<br />
<br />
:''So as to install GNU-Octave for MacOS ,refer to : [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:'' So as to install GNU-Octave on GNU/Linux ,refer to: [[Octave for GNU/Linux]]''<br />
<br />
==How to install Octave on Android OR What is the Octave app available in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for further information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies, refer to [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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 known to work as well). If you face any 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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12952FAQ2020-05-08T13:37:53Z<p>Prubhtej Singh: /* What do I need to build Octave from the source code? */</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S ,refer to : [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on MacOS?==<br />
<br />
:''So as to install GNU-Octave for MacOS ,refer to : [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:'' So as to install GNU-Octave on GNU/Linux ,refer to: [[Octave for GNU/Linux]]''<br />
<br />
==How to install Octave on Android OR What is the Octave app available in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for further information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies, refer to [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12951FAQ2020-05-08T13:36:49Z<p>Prubhtej Singh: /* How can I install Octave on Android / what is this Octave app in the Google Play store? */</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S ,refer to : [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on MacOS?==<br />
<br />
:''So as to install GNU-Octave for MacOS ,refer to : [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:'' So as to install GNU-Octave on GNU/Linux ,refer to: [[Octave for GNU/Linux]]''<br />
<br />
==How to install Octave on Android OR What is the Octave app available in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for further information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12950FAQ2020-05-08T13:35:31Z<p>Prubhtej Singh: /* How can I install Octave on GNU/Linux? */</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S ,refer to : [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on MacOS?==<br />
<br />
:''So as to install GNU-Octave for MacOS ,refer to : [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:'' So as to install GNU-Octave on GNU/Linux ,refer to: [[Octave for GNU/Linux]]''<br />
<br />
==How can I install Octave on Android / what is this Octave app in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for more information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12949FAQ2020-05-08T13:34:59Z<p>Prubhtej Singh: /* How can I install Octave on MacOS? */</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S ,refer to : [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on MacOS?==<br />
<br />
:''So as to install GNU-Octave for MacOS ,refer to : [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:'' So as to install GNU-Octave on GNU/Linux ,See: [[Octave for GNU/Linux]]''<br />
<br />
==How can I install Octave on Android / what is this Octave app in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for more information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12948FAQ2020-05-08T13:34:33Z<p>Prubhtej Singh: /* How can I install Octave on Windows? */</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S ,refer to : [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on MacOS?==<br />
<br />
:''So as to install GNU-Octave for MacOS ,See: [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:'' So as to install GNU-Octave on GNU/Linux ,See: [[Octave for GNU/Linux]]''<br />
<br />
==How can I install Octave on Android / what is this Octave app in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for more information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12947FAQ2020-05-08T13:34:05Z<p>Prubhtej Singh: /* How can I install Octave on GNU/Linux? */</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S ,See: [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on MacOS?==<br />
<br />
:''So as to install GNU-Octave for MacOS ,See: [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:'' So as to install GNU-Octave on GNU/Linux ,See: [[Octave for GNU/Linux]]''<br />
<br />
==How can I install Octave on Android / what is this Octave app in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for more information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12946FAQ2020-05-08T13:33:15Z<p>Prubhtej Singh: /* How can I install Octave on macOS? */</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S ,See: [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on MacOS?==<br />
<br />
:''So as to install GNU-Octave for MacOS ,See: [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:''See: [[Octave for GNU/Linux]]''<br />
<br />
==How can I install Octave on Android / what is this Octave app in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for more information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12945FAQ2020-05-08T13:32:25Z<p>Prubhtej Singh: /* How can I install Octave on Windows? */</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for Windows O.S ,See: [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on macOS?==<br />
<br />
:''See: [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:''See: [[Octave for GNU/Linux]]''<br />
<br />
==How can I install Octave on Android / what is this Octave app in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for more information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12944FAQ2020-05-08T13:31:35Z<p>Prubhtej Singh: /* How can I install Octave on Windows? */</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:'' So as to install GNU-Octave for windows O.S. See: [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on macOS?==<br />
<br />
:''See: [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:''See: [[Octave for GNU/Linux]]''<br />
<br />
==How can I install Octave on Android / what is this Octave app in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for more information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12943FAQ2020-05-08T13:30:25Z<p>Prubhtej Singh: /* Should I favor the MEX interface to avoid the GPL? */ Minor correction of grammar</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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 softwares 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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:''See: [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on macOS?==<br />
<br />
:''See: [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:''See: [[Octave for GNU/Linux]]''<br />
<br />
==How can I install Octave on Android / what is this Octave app in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for more information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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.<br />
<br />
Furthermore, Octave adds a few syntactical extensions to Matlab that might cause some issues when exchanging files between Matlab and Octave users.<br />
<br />
As both Octave and Matlab are under constant development, the information in this section is subject to change.<br />
<br />
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.<br />
<br />
==Graphical Curve Fitting Tool==<br />
<br />
Currently, Octave lacks a graphical curve fitting tool such as Matlab's [https://www.mathworks.com/help/curvefit/curvefitting-app.html curvefit] tool. [https://lists.gnu.org/archive/html/help-octave/2015-07/msg00300.html]<br />
<br />
You can use polyfit or the packages [https://octave.sourceforge.io/signal/ signal] or [https://octave.sourceforge.io/optim/ optim] to achieve these task but these are not graphical tools.<br />
<br />
==Nested Functions==<br />
<br />
Octave has limited support for nested functions since version 3.8.0. That is<br />
<br />
<syntaxhighlight lang="Matlab"><br />
function y = foo (x)<br />
y = bar(x)<br />
function y = bar (x)<br />
y = ...;<br />
end<br />
end<br />
</syntaxhighlight><br />
<br />
is equivalent to<br />
<br />
<syntaxhighlight lang="Octave"><br />
function y = foo (x)<br />
y = bar(x)<br />
endfunction<br />
<br />
function y = bar (x)<br />
y = ...;<br />
endfunction<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Differences in core syntax==<br />
<br />
There are a few core Matlab syntaxes that are not accepted by Octave, these being<br />
<br />
* 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.<br />
<br />
* Some limitations of variable argument lists on the LHS of an expression, though the most common types are accepted.<br />
<br />
* Matlab classdef object oriented programming is only partially supported, see [[classdef]] for details.<br />
<br />
==Differences in core functions==<br />
<br />
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.<br />
<br />
==Just-In-Time compiler==<br />
<br />
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.<br />
<br />
==Compiler==<br />
<br />
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.<br />
<br />
==Graphic handles==<br />
<br />
The support for graphics handles is converging towards full compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==GUI functions==<br />
<br />
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 compatibility. If you notice any incompatibilities, please [http://bugs.octave.org report a bug].<br />
<br />
==Simulink==<br />
<br />
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.<br />
<br />
==MEX-Files==<br />
<br />
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).<br />
<br />
==Block comments==<br />
<br />
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 {}.<br />
<br />
==Mat-File format==<br />
<br />
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.<br />
<br />
Although Octave can load inline function handles saved by Matlab, it can not yet save them.<br />
<br />
Finally, some multi-byte Unicode characters aren't yet treated in mat-files.<br />
<br />
==Profiler==<br />
<br />
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.<br />
<br />
==Toolboxes==<br />
<br />
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.<br />
<br />
==Short-circuit <code>&</code> and <code>|</code> operators==<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (a | b)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = a | b;<br />
if (t)<br />
...<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
t = 1 | []; ## results in [], so...<br />
if (t) 1, end ## in if ([]), this is false.<br />
</syntaxhighlight><br />
<br />
and<br />
<br />
<syntaxhighlight lang="Octave"><br />
if (1 | []) 1, end ## short circuits so condition is true.<br />
</syntaxhighlight><br />
<br />
In the latter case, Octave displays since version 4.0.0 a warning:<br />
<br />
warning: Matlab-style short-circuit operation performed for operator |<br />
<br />
Another case that is documented in the Matlab manuals is that<br />
<br />
<syntaxhighlight lang="Matlab"><br />
t = [1, 1] | [1, 2, 3]; ## error<br />
if ([1, 1] | [1, 2, 3]) 1, end ## OK<br />
</syntaxhighlight><br />
<br />
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).<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([0, 1]) == if (all ([0, 1])) ==> i.e., condition is false.<br />
if ([1, 1]) == if (all ([1, 1])) ==> i.e., condition is true.<br />
</syntaxhighlight><br />
<br />
However,<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if ([])<br />
</syntaxhighlight><br />
<br />
is not the same as<br />
<br />
<syntaxhighlight lang="Matlab"><br />
if (all ([]))<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Solvers for singular, under- and over-determined matrices==<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Octave"><br />
function x = mldivide (A, b)<br />
m = rows (A);<br />
[Q, R, E] = qr (A);<br />
x = [A \ b, E(:, 1:m) * (R(:, 1:m) \ (Q' * b))]<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 10;<br />
n = 10000;<br />
A = ones (m, n) + 1e-6 * randn (m, n);<br />
b = ones (m, 1) + 1e-6 * randn (m, 1);<br />
norm (A \ b)<br />
</syntaxhighlight><br />
<br />
while Octave's minimum-norm values are about 3e-2, Matlab's results are 50-times larger. For another issue, try this code:<br />
<br />
<syntaxhighlight lang="Octave"><br />
m = 5;<br />
n = 100;<br />
j = floor (m * rand (1, n)) + 1;<br />
b = ones (m, 1);<br />
A = zeros (m, n);<br />
A(sub2ind(size(A),j,1:n)) = 1;<br />
x = A \ b;<br />
[~,p] = sort (rand (1, n));<br />
y = A(:,p) \ b;<br />
norm (x(p) - y)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
==Octave extensions==<br />
<br />
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:<br />
<br />
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|#}}".<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
<syntaxhighlight lang="Matlab"><br />
global a<br />
a = 1;<br />
try<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
catch<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
rethrow (lasterror());<br />
end<br />
</syntaxhighlight><br />
<br />
compared to<br />
<br />
<syntaxhighlight lang="Octave"><br />
global a<br />
a = 1;<br />
unwind_protect<br />
_a = a;<br />
a = 2<br />
while true<br />
end<br />
unwind_protect_cleanup<br />
fprintf ('caught interrupt\n');<br />
a = _a;<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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]);}}<br />
<br />
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.<br />
<br />
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.<br />
<br />
==What features are unique to Octave?==<br />
<br />
Although most of the Octave language will be familiar to Matlab users, it has some unique features of its own.<br />
<br />
=== Functions defined on the command-line===<br />
Functions can be defined by entering code on the command line, a feature not supported by Matlab. For example, you may type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> function s = hello_string (to_who)<br />
> ## Say hello<br />
> if nargin<1, to_who = "World"; end<br />
> s = ["Hello ",\<br />
> to_who];<br />
> endfunction<br />
>> hello_string ("Moon")<br />
ans = Hello Moon<br />
</syntaxhighlight><br />
<br />
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 (...)}})<br />
<br />
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].<br />
<br />
===Comments with #===<br />
<br />
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.<br />
<br />
===Strings delimited by double quotes "===<br />
<br />
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).<br />
<br />
===Line continuation by backslash===<br />
<br />
Lines can be continued with a backslash, {{Codeline|\}}, in addition to three points {{Codeline|...}} as in Matlab.<br />
<br />
===Informative block closing===<br />
<br />
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.<br />
<br />
===Coherent syntax===<br />
<br />
Indexing other things than variables is possible, as in:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> [3 1 4 1 5 9](3)<br />
ans = 4<br />
>> cos([0 pi pi/4 7])(3)<br />
ans = 0.70711<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Exclamation mark as not operator===<br />
<br />
The exclamation mark {{Codeline|!}} (aka “Bang!”) is a negation operator, just like the tilde {{Codeline|~}}:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> if ! strcmp (program_name, "octave"),<br />
> "It's an error"<br />
> else<br />
> "It works!"<br />
> end<br />
ans = It works!<br />
</syntaxhighlight><br />
<br />
Note however that Matlab uses the {{Codeline|!}} operator for shell escapes, for which Octave requires using the system command.<br />
<br />
===Increment and decrement operators===<br />
<br />
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;}}.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
For matrix and vector arguments, the increment and decrement operators work on each element of the operand.<br />
<br />
===Unwind-protect===<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="Octave"><br />
unwind_protect<br />
body<br />
unwind_protect_cleanup<br />
cleanup<br />
end_unwind_protect<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
The unwind_protect statement is often used to reliably restore the values of global variables that need to be temporarily changed.<br />
<br />
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.<br />
<br />
===Built-in ODE and DAE solvers===<br />
<br />
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.<br />
<br />
===Do-Until loop structure===<br />
<br />
Similar to the do-while loop in C and C++, Octave allows a do-until loop which does not exist in Matlab:<br />
<br />
<syntaxhighlight lang="Octave"><br />
x = 0<br />
do<br />
x += 1;<br />
until (x == 10)<br />
</syntaxhighlight><br />
<br />
===Broadcasting===<br />
<br />
Borrowed from [http://stackoverflow.com/q/26948776/3565696 other languages], [http://www.octave.org/doc/interpreter/Broadcasting.html octave broadcasting] allows easy and readable vectorization.<br />
<br />
<syntaxhighlight lang="Octave"><br />
f = (1:0.1:2);<br />
# put angular frequencies on the first dimension to prepare broadcasting<br />
omega = 2 * pi * f(:);<br />
# time is already on the second dimension (row vector)<br />
t = 0:0.02:2;<br />
# the resulting s will be a 2-dimensional array<br />
s = sin(omega .* t);<br />
# which can be displayed as<br />
pcolor(t, f, s)<br />
xlabel("t (s)")<br />
ylabel("f (Hz)")<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Documentation strings===<br />
<br />
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.<br />
<br />
===Test functions===<br />
<br />
Octave allows to add self-tests to user defined functions. Tests are put after function definition in specially commented block.<br />
<br />
<syntaxhighlight lang="Octave"><br />
function mult = a(val)<br />
mult = val.*2;<br />
endfunction<br />
%!test<br />
%! assert (a(3), 6);<br />
</syntaxhighlight><br />
<br />
Such a function can be tested for valid outputs by following code:<br />
<br />
>> test a<br />
PASSES 1 out of 1 test<br />
<br />
===Demonstration Functions===<br />
<br />
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:<br />
<br />
demo multinom<br />
<br />
===Powerful assert===<br />
<br />
Function assert have extended input possibilities.<br />
<br />
=[https://en.wikipedia.org/wiki/Graphical_user_interface GUI]=<br />
<br />
==Does Octave have a GUI?==<br />
<br />
'''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).<br />
<br />
==Why did you create yet another GUI instead of making one that already exists better?==<br />
<br />
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:<br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
* '''[http://www.xoctave.com/ Xoctave]''', which is proprietary and commercial.<br />
<br />
* '''GUI Octave''', which was proprietary and is no longer available.<br />
<br />
=Graphics: backends and toolkits=<br />
<br />
==What are the supported graphics backends?==<br />
<br />
* [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default) and '''[http://www.fltk.org/ fltk]'''<br />
* [http://www.gnuplot.info/ gnuplot] via the '''gnuplot''' graphics toolkit<br />
<br />
==How do I change my graphics toolkit?==<br />
<br />
There are three commands to deal with graphics toolkits:<br />
<br />
{| class="wikitable"<br />
| <code>available_graphics_toolkits</code><br />
| lists all available graphics toolkits<br />
|-<br />
| <code>graphics_toolkit</code><br />
| displays the currently used graphics toolkit<br />
|-<br />
| <code>graphics_toolkit ("qt/fltk/gnuplot")</code><br />
| 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<br />
|}<br />
<br />
==Why did you replace gnuplot with an OpenGL backend?==<br />
<br />
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).<br />
<br />
==Are there any plans to remove the gnuplot backend?==<br />
<br />
'''No.''' There are no plans to remove the gnuplot backend. It will be available as long as our users find it useful.<br />
<br />
==How can I implement a new graphics backend/toolkit?==<br />
<br />
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.<br />
<br />
=Development=<br />
<br />
==When will feature X be released or implemented?==<br />
<br />
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].<br />
<br />
==How can I get involved in Octave development?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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<br />
something you can help with.<br />
<br />
Look at our [[projects]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.</div>Prubhtej Singhhttps://wiki.octave.org/wiki/index.php?title=FAQ&diff=12942FAQ2020-05-08T13:26:20Z<p>Prubhtej Singh: /* Will you change the license of the Octave libraries for me? */ Minor grammatical error</p>
<hr />
<div>This is a list of frequently asked questions (FAQ) for GNU Octave users.<br />
<br />
We are always looking for new questions (with answers), better answers, or both. Feel free to edit this page with your changes.<br />
<br />
=Where do I get additional help?=<br />
<br />
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:<br />
<br />
* Search for an answer in our [https://lists.gnu.org/archive/html/help-octave/ mailing list archives]<br />
* 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 for the latest updates and discussions)<br />
* Contact our user community using our [https://webchat.freenode.net/?channels=octave IRC chat room <code>#octave</code> in Freenode]<br />
<br />
<div class="tocinline">__TOC__</div><br />
<br />
=General=<br />
<br />
==What is Octave?==<br />
<br />
[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. <br />
The GNU Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
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.<br />
<br />
==What is Octave Forge?==<br />
<br />
[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).<br />
<br />
==Who uses Octave?==<br />
<br />
A huge number of people ranging from students to researchers involved in various fields such as statistics,Machine Learning, data analytics, etc . Universities use it for research and teaching, companies of all sizes for development and individuals for certain private purposes. See [[Who Uses Octave?]] for more clarity .<br />
<br />
==Who develops Octave?==<br />
<br />
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). Since 2011, GNU Octave regularly participates in [[Summer of Code]] events as a mentor organisation. As part of those events, several students contributed to Octave by helping in removal of bugs and development of new features.<br />
<br />
==Why "Octave"?==<br />
<br />
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.<br />
<br />
==Why "GNU" Octave?==<br />
<br />
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].<br />
<br />
The [https://www.fsf.org/ Free Software Foundation (FSF)] is the principal organisation that has sponsored the GNU Project.<br />
<br />
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.<br />
<br />
==How can I cite Octave?==<br />
<br />
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:<br />
<br />
John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring ({{Release Year}}).<br />
GNU Octave version {{Release}} manual: a high-level interactive language for numerical computations.<br />
URL https://www.gnu.org/software/octave/doc/v{{Release}}/<br />
<br />
A [https://en.wikipedia.org/wiki/BibTeX BibTeX] entry for [https://en.wikipedia.org/wiki/LaTeX LaTeX] users is:<br />
<br />
@manual{,<br />
title = {{GNU Octave} version {{Release}} manual: a high-level interactive language for numerical computations},<br />
author = {John W. Eaton and David Bateman and S{\o}ren Hauberg and Rik Wehbring},<br />
year = <span>{</span>{{Release Year}}},<br />
url = {https://www.gnu.org/software/octave/doc/v{{Release}}/},<br />
}<br />
<br />
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>.<br />
<br />
Note that there are two reasons for citing the software used. One is giving recognition to the work done by others which we have already addressed to . 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 as well . 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 for the same .<br />
<br />
==What documentation exists for Octave?==<br />
<br />
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.<br />
<br />
==How can I report a bug in Octave?==<br />
<br />
Please read our website http://www.octave.org/bugs.html.<br />
<br />
<br />
= Common problems =<br />
<br />
== Octave does not start ==<br />
<br />
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information:<br />
<br />
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04'''<br />
* GNU Octave version: e.g. '''Version {{Release}}'''<br />
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html'''<br />
<br />
=== MS Windows ===<br />
<br />
* After upgrade the GUI does not open / shuts down immediately.<br />
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}}<br />
* Missing/conflicting files.<br />
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again.<br />
* Permission errors.<br />
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked.<br />
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions?<br />
<br />
==I do not see any output of my script until it has finished?==<br />
<br />
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 [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual].<br />
<br />
==When I try plotting from a script, why am I not seeing anything?==<br />
<br />
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).<br />
<br />
A common solution is to put a {{manual|pause}} command at the end of your script.<br />
<br />
==How do I get sound input or output in MS Windows?==<br />
<br />
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 [https://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].<br />
<br />
==I have problem X using the latest Octave version==<br />
<br />
Please be more specific about what you mean by "latest version"?<br />
<br />
* 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 the following as in accordance to your Operating system: [[Octave for GNU/Linux|GNU/Linux]], [[Octave for macOS|macOS]], or [[Octave for Microsoft Windows|Windows]].<br />
<br />
* 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.<br />
<br />
If your problem still 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.<br />
<br />
==Why is Octave's floating-point computation wrong?==<br />
<br />
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 <math>1/10</math> exactly in base 2. In binary, the representation to one tenth is <math>0.0\overline{0011}_b</math> where the bar indicates that it repeats infinitely (like how <math>1/6 = 0.1\overline{6}_d</math> 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.<br />
<br />
In addition, some advanced operations are computed by approximation and there is no guarantee for them to be accurate, see [https://en.wikipedia.org/wiki/Rounding#Table-maker.27s_dilemma Table-maker's dilemma] for further references . Their results are system-dependent.<br />
<br />
This isn't a bug that is limited to GNU-Octave & 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.<br />
<br />
Another approach to deal with rounding errors is interval arithmetic with the [[Interval package]] or symbolic computations with the [[Symbolic package]]. These approaches are likely to be slower, since not all operations can be performed on Hardware like pure floating-point arithmetic.<br />
<br />
To learn more about floating-point arithmetic, consult this [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].<br />
<br />
==Missing lines when printing under Windows with OpenGL toolkit and Intel integrated GPU==<br />
<br />
Some windows users with integrated Intel GPUs have reported missing lines when printing with an OpenGL toolkit like FLTK or Qt. {{bug|42534}}<br />
<br />
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 .<br />
<br />
See also https://www.opengl.org/wiki/FAQ#Why_is_my_GL_version_only_1.4_or_lower.3F .<br />
<br />
==Plot hangs and makes the GUI unresponsive==<br />
<br />
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}}<br />
<br />
==Error message about invalid call to script or invalid use of script in index expression==<br />
<br />
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 same global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function as to avoid this error regarding the invalid call to script or invalid use of script in index expression .<br />
<br />
=Licensing issues=<br />
<br />
==If I write code using Octave do I have to release it under the GPL?==<br />
<br />
The answer depends on precisely how the code is written and how it works:<br />
<br />
* 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.<br />
<br />
* 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].<br />
<br />
* 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:<br />
<br />
:# 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].<br />
:# 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.<br />
<br />
* 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.<br />
<br />
==Will you change the license of the Octave libraries for me?==<br />
<br />
'''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 be benefited from your work the same as you were/have benefited from the work of all the people who have contributed to Octave.<br />
<br />
==Should I favor the MEX interface to avoid the GPL?==<br />
<br />
'''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].<br />
<br />
==Why can't I use code from File Exchange in Octave?==<br />
<br />
According to the Matlab Central [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use] (Last updated: 10-Aug-2016), all submitted code is licensed under the [https://en.wikipedia.org/wiki/BSD_licenses BSD license] by default (cf. § 5 [https://www.mathworks.com/matlabcentral/termsofuse.html Terms of Use]), but it is clearly stated that:<br />
<br />
{{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]}}<br />
<br />
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]].<br />
<br />
=Installation=<br />
<br />
==How can I install Octave on Windows?==<br />
<br />
:''See: [[Octave for Microsoft Windows]]''<br />
<br />
==How can I install Octave on macOS?==<br />
<br />
:''See: [[Octave for macOS]]''<br />
<br />
==How can I install Octave on GNU/Linux?==<br />
<br />
:''See: [[Octave for GNU/Linux]]''<br />
<br />
==How can I install Octave on Android / what is this Octave app in the Google Play store?==<br />
<br />
There is an '''unofficial''' Octave app available for Android in the Google Play store. Please see [[Octave for Android]] for more information.<br />
<br />
==How can I install Octave on platform X?==<br />
<br />
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].<br />
<br />
==What Octave version should I use?==<br />
<br />
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/.<br />
<br />
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.<br />
<br />
==On what platforms does Octave run?==<br />
<br />
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].<br />
<br />
==How can I obtain Octave's source code?==<br />
<br />
The latest version of the Octave source code (and older versions) is available from:<br />
<br />
* https://www.octave.org/download.html<br />
* https://ftp.gnu.org/gnu/octave/<br />
<br />
Since Octave is distributed under the terms of the GPL, you can get Octave from a friend who has a copy.<br />
<br />
==How can I build Octave from the source code?==<br />
<br />
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]].<br />
<br />
If you have reasons to build Octave from the source code, see [[Building]] for more information.<br />
<br />
==What do I need to build Octave from the source code?==<br />
<br />
For a list of build dependencies see [[Building]].<br />
<br />
==Do I need GCC to build Octave from the source code?==<br />
<br />
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].<br />
<br />
=What's new in Octave?=<br />
<br />
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:<br />
<br />
==What's new in the next version of Octave?==<br />
<br />
See the [http://hg.savannah.gnu.org/hgweb/octave/file/tip/NEWS NEWS file] on the development branch.<br />
<br />
==What's new in version series 4.0.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-4.0.html NEWS file].<br />
<br />
* First official release of the GUI.<br />
* Release of official windows binaries.<br />
* Experimental support for [[classdef]].<br />
* OpenGL graphics with Qt widgets.<br />
* Several functions for reading, writing, and recording of audio.<br />
<br />
==What's new in version series 3.8.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.8.html NEWS file].<br />
<br />
* Experimental GUI interface.<br />
* OpenGL graphics with fltk widgets.<br />
* Support for nested functions.<br />
* Support for java packages in Octave core.<br />
* Reading and writing of image files vastly extended.<br />
<br />
==What's new in version series 3.6.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.6.html NEWS file].<br />
<br />
* Perl compatible regular expressions<br />
* A profiler has been added.<br />
* Broadcasting enabled for all built-in binary element-wise operators.<br />
* Performance of all m-file string functions has been improved.<br />
<br />
==What's new in version series 3.4.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.4.html NEWS file].<br />
<br />
* Many improvements to native OpenGL plotting<br />
* ARPACK now distributed with Octave<br />
* Indexing optimizations<br />
* FTP objects<br />
* Function handles aware of overloaded functions<br />
* bsxfun optimized for basic arithmetic functions<br />
* Matlab-style ignoring of output arguments using {{Codeline|~}}<br />
* Many optimizations of the accumarray function<br />
* Sparse matrix indexing has been rewritten for speed<br />
* The pkg command now accepts a -forge option to pull packages directly from Octave Forge<br />
<br />
==What's new in version series 3.2.X of Octave==<br />
<br />
See the complete user-visible changes on the [https://www.gnu.org/software/octave/NEWS-3.2.html NEWS file].<br />
<br />
* Single precision type<br />
* Experimental OpenGL graphics toolkit to replace gnuplot<br />
* Object orient programming via @class named directories<br />
* 64-bit compilation support<br />
* gzipped files and stream and consequently support of Matlab v7 files<br />
* a fully compatible MEX interface<br />
* imwrite and imread (based on the GraphicsMagick library)<br />
* 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.<br />
<br />
==Older releases==<br />
<br />
For full details on older releases, see:<br />
<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.1 NEWS.1] for the 1.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.2 NEWS.2] for the 2.X.Y series<br />
* [http://hg.savannah.gnu.org/hgweb/octave/file/83792dd9bcc1/etc/NEWS.3 NEWS.3] for the 3.X.Y series<br />
<br />
=Packages and Octave Forge=<br />
<br />
==How do I install or load all Octave Forge packages?==<br />
<br />
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<br />
you know them by name; or you want them all "just because", in which case you don't really need them.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you really really really want to do load all packages, you can with the following:<br />
<syntaxhighlight lang="octave"><br />
## WARNING: loading all packages is probably not the solution you are looking for.<br />
cellfun (@(x) pkg ("load", x.name), pkg ("list"));<br />
</syntaxhighlight><br />
<br />
==I have installed a package but still get a "foo undefined" error?==<br />
<br />
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.<br />
<br />
==I cannot install a package. Octave complains about a missing mkoctfile.==<br />
<br />
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>.<br />
<br />
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:<br />
<br />
* Debian/Ubuntu: [https://packages.debian.org/stretch/liboctave-dev liboctave-dev]<br />
<br />
* Fedora: {{Codeline|octave-devel}}<br />
<br />
==How do I automatically load a package at Octave startup?==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=Octave usage=<br />
<br />
==How do I execute an Octave script?==<br />
<br />
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><br />
<br />
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}}.<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
run ("Script Name With Spaces.m")<br />
run ("/opt/local/foo.m")<br />
</syntaxhighlight><br />
<br />
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:<br />
<br />
$ octave the-script.m arg1 arg2<br />
<br />
In a Unix environment, if the script has a [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang] (e.g. <code>#!/usr/bin/octave</code>) and executable permissions, you can call it like any other Unix program with arguments:<br />
<br />
$ ./the-script arg1 arg2<br />
<br />
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]].<br />
<br />
==How do I close a figure?== <br />
<br />
To close the current figure type {{manual|close}} in the Octave command prompt.<br />
<br />
==How do I set the number of displayed decimals?==<br />
<br />
You can control the number of displayed decimals using the {{manual|format}} command:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> format long<br />
>> pi<br />
pi = 3.14159265358979<br />
>> format short<br />
>> pi<br />
pi = 3.1416<br />
</syntaxhighlight><br />
<br />
==How do I call an Octave function from C++?==<br />
<br />
Please read the manual https://www.gnu.org/software/octave/doc/interpreter/Calling-Octave-Functions-from-Oct_002dFiles.html.<br />
<br />
==How do I change color/line definition in gnuplot postscript?==<br />
<br />
Here is a awk script to get a rainbow color map<br />
<br />
#!/bin/awk -f<br />
<br />
BEGIN {<br />
split("0 4 6 7 5 3 1 2 8", rainbow, " ");<br />
split("7 3 1 0 2 4 6 5 8", invraim, " ");<br />
}<br />
<br />
$1 ~ /\/LT[0-8]/ {<br />
n = substr($1, 4, 1);<br />
if (n == 0)<br />
lt = "{ PL [] 0.9 0.1 0.1 DL } def";<br />
else if (n == 1)<br />
lt = "{ PL [4 dl 2 dl] 0.1 .75 0.1 DL } def";<br />
else if (n == 2)<br />
lt = "{ PL [2 dl 3 dl] 0.1 0.1 0.9 DL } def";<br />
else if (n == 3)<br />
lt = "{ PL [1 dl 1.5 dl] 0.9 0 0.8 DL } def";<br />
else if (n == 4)<br />
lt = "{ PL [5 dl 2 dl 1 dl 2 dl] 0.1 0.8 0.8 DL } def";<br />
else if (n == 5)<br />
lt = "{ PL [4 dl 3 dl 1 dl 3 dl] 0.9 0.8 0.2 DL } def";<br />
else if (n == 6)<br />
lt = "{ PL [2 dl 2 dl 2 dl 4 dl] 0.5 0.3 0.1 DL } def";<br />
else if (n == 7)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.4 0 DL } def";<br />
else if (n == 8)<br />
lt = "{ PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def";<br />
$0 = sprintf("/LT%d %s", rainbow[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", invraim[n+1], lt);<br />
##$0 = sprintf("/LT%x %s", n, lt);<br />
}<br />
<br />
{ print; }<br />
<br />
==How do I tell if a file exists?==<br />
<br />
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:<br />
<br />
<syntaxhighlight lang="octave"><br />
>> exist ("foo.txt", "file") # 2, if file exists, 0 otherwise<br />
ans = 2<br />
</syntaxhighlight><br />
<br />
==How do I create a plot without a window popping up (plot to a file directly)?==<br />
<br />
<syntaxhighlight lang="octave"><br />
figure (1, "visible", "off");<br />
plot (sin (1:100));<br />
print -deps "/tmp/sin.eps"<br />
</syntaxhighlight><br />
<br />
One can set that behavior as default:<br />
<br />
<syntaxhighlight lang="octave"><br />
set (0, "defaultfigurevisible", "off");<br />
</syntaxhighlight><br />
<br />
==How do I increase Octave's precision?==<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Limits of some of Octave's data types obtained by {{manual|intmax}} and {{manual|flintmax}}.<br />
|-<br />
| <code>intmax ("uint64")</code><br />
| style="text-align: right;" | <code>18,446,744,073,709,551,615</code><br />
| <code>2^64-1</code><br />
|-<br />
| <code>intmax ("int64")</code><br />
| style="text-align: right;" | <code>9,223,372,036,854,775,807</code><br />
| <code>2^63-1</code><br />
|-<br />
| <code>flintmax ("double")</code><br />
| style="text-align: right;" | <code>9,007,199,254,740,992</code><br />
| <code>2^53</code><br />
|-<br />
| <code>flintmax ("single")</code><br />
| style="text-align: right;" | <code>16,777,216</code><br />
| <code>2^24</code><br />
|}<br />
<br />
When working with other types than "double" in Octave, one has to make sure, that the first operand is converted to the desired type:<br />
<br />
<syntaxhighlight lang="Octave"><br />
>> uint64 (2^53 + 1)<br />
ans = 9007199254740992<br />
>> uint64 (2^53) + 1<br />
ans = 9007199254740993<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
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]].<br />
<br />
==How do I run a Matlab P-file in Octave?==<br />
<br />
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 that 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.<br />
<br />
There are no plans to support running P-files produced by Matlab in Octave.<br />
<br />
==How does Octave solve linear systems?==<br />
<br />
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.<br />
<br />
==How do I do X?==<br />
<br />
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:<br />
<br />
>> lookfor correlation<br />
corr Compute matrix of correlation coefficients.<br />
corrcoef Compute a matrix of correlation coefficients.<br />
spearman Compute Spearman's rank correlation coefficient RHO.<br />
<br />
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:<br />
<br />
>> corr<br />
corr corrcoef<br />
<br />
<br />
=Differences between Octave and Matlab=<br />
<br />
People often ask<br />
<br />
<blockquote><br />
I wrote some code for Matlab, and I want to get it running under Octave. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
or alternatively<br />
<br />
<blockquote><br />
I wrote some code in Octave, and want to share it with Matlab users. Is there anything I should watch out for?<br />
</blockquote><br />
<br />
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 s