The list below summarizes features or bug fixes we would like to see in Octave. if you start working steadily on a project, please let email@example.com know. We might have information that could help you. You should also read the [
http://www.gnu.org/software/octave/doc/interpreter/Contributing-Guidelines.html#Contributing-Guidelines Contributing Guidelines chapter] in the [http://www.gnu.org/software/octave/doc/interpreter/ Octave manual].
This list is not exclusive -- there are many other things that might be good projects, but it might instead be something we already have. Also, some of the following items may not actually be considered good ideas now. So please check with firstname.lastname@example.org before you start working on some large project.
*Improve logm, and sqrtm (see this thread: http://octave.1599824.n4.nabble.com/matrix-functions-td3137935.html)
*Improve complex mapper functions. See W. Kahan, ``Branch Cuts for Complex Elementary Functions, or Much Ado About Nothing's Sign Bit (in The State of the Art in Numerical Analysis, eds. Iserles and Powell, Clarendon Press, Oxford, 1987) for explicit trigonometric formulae.
*Add optional arguments to colloc so that it's not restricted to Legendre polynomials.
*Fix eig to also be able to solve the generalized eigenvalue problem, and to solve for eigenvalues and eigenvectors without performing a balancing step first.
*Move rand, eye, xpow, xdiv, etc., functions to the matrix classes.
== Matlab-compatible ODE solvers in core-Octave ==
* Adapt "odeset" and "odeget" from the odepkg package so that the list of supported options is more Matlab-compatible, in the sense that all option names that are supported by Matlab should be available. On the other hand, Matlab returns an error if an option which is not in the list of known options is passed to "odeset", but we would rather make this a warning in order to allow for special extensions, for example for symplectic integrators.* Adapt the interface of "ode45" in odepkg to be completely Matlab compatible, fix its code and documentation style and move it to Octave-core.* Build Matlab compatible versions of "ode15s" and "ode15i". jwe has prototype implementations [https://savannah.gnu.org/patch/
index.php?8102 |here] of these built as wrappers to "dassl" and "daspk". An initial approach could be to just improve these wrappers, but eventually it would be better to have wrappers for "IDA" from the sundials library.
* Implement Matlab compatible versions of "deval".
**Evaluate a line of code and return the output as a string (it would be best if it could provide three strings: output, warnings and errors).
**Query defined variables, i.e. get a list of currently defined variables. Bonus points if it could tell you if anything had changed since the last time you checked the variables (could also be done with signals).
*Make the links in the "Experimental GUI info" dialog box (the one that appears when the button "More Info" is pressed) clickable. They are not clickable in the 3.8.2-2 version (at least not on Windows 7). == Implement a Qt widget for manipulating plots == Octave has had for some time a native OpenGL plotter. The plotter requires some user interaction for manipulating the plots, and it's been using fltk for quite some time. We want to replace this with Qt, so it fits better with the overall GUI look-and-feel and is easier to extend in the future. [https://github.com/goffioul/QtHandles QtHandles] is a current work in progress integrating the octave OpenGL renderer plus good support for GUI elements (uicontrol, uimenu, uitoolbar...). This project may initially consists of integrating the existing QtHandles code base into Octave. Then if time permits, further improvements can be made to QtHandles. == Create a better (G)UI for the profiler == During GSoC 2011, Daniel Kraft successfully implemented a profiler for Octave. It needs a better interface and a way to generate reports. This may be done with Qt, but not necessarily , and HTML reports might also be good.
== Sisotool. Create a graphical design tool for tuning closed loop control system (
control pkg) ==
When tuning a SISO feedback system it is very helpful to be able to grab a pole or a zero and move them by dragging them with the mouse. As they are moving the software must update all the plotted lines. There should be the ability to display various graphs rlocuse, bode, step, impulse etc. and have them all change dynamically as the mouse is moving. The parameters of the compensator must be displayed and updated.
*Improve QR factorization by replacing CXSPARSE code with SPQR code, and make the linear solve return 2-norm solutions for ill-conditioned matrices based on this new code
Implement fourth argument to the sprand and sprandn, and addition arguments to sprandsym that the leading brand implements.
*Sparse logical indexing in idx_vector class so that something like
'a=sprandn(1e6,1e6,1e-6); a(a<1) = 0 ' won't cause a memory overflow.
*Other missing Functions
**<strike>symmmd</strike> (Superseded by symamd)
**<strike>colmmd</strike> (Superseded by colamd)
**<strike>cholinc (or ichol)</strike>
**<strike>luinc (or ilu)</strike>
**<strike>bicg</strike> Moved into octave-core
**<strike>gmres</strike>Moved into octave-core
**qmr (see [https://savannah.gnu.org/patch/?8569 Savannah Patch Tracker])
if (expr) 'this is a string' end
is parsed as IF expr STRING END. ''(see [https://
mailman. cae. wisc.edu/ pipermail/octave-maintainers/2014- March/ 039554.html this] post on the mailing list)''
*Clean up functions in input.cc that handle user input (there currently seems to be some unnecessary duplication of code and it seems overly complex).
*Too much time is spent allocating and freeing memory. What can be done to improve performance?
*Error output from Fortran code is ugly. Something should be done to make it look better.
* On 'imagesc' plots, report the matrix values also based on the mouse position, updating on mouse moving.
* Create a "getframe" function that receives a a graphics handle and returns a 3D matrix from the graphics window associated with that handle.
* Add map-creating capabilities similar to the Matlab [http://www.mathworks.com/help/map/functionlist.html Mapping toolbox] for inclusion in the Octave Forge [https://sourceforge.net/p/octave/mapping mapping package].
=Configuration and Installation=
*Split config.h into a part for Octave-specific configuration things (this part can be installed) and the generic HAVE_X type of configure information that should not be installed.
*Create a docs-only distribution?
Better binary packaging and distribution, especially on Windows. *Octave Emacs mode needs maintenance. *Convert build system to a non-recursive Automake setup. See how Makefile.am files currently include module.mk files in subdirectories, extend this concept to the entire project so there is only one top-level Makefile.am.
=Documentation and On-Line Help=
*Document new features.
*Improve the Texinfo Documentation for the interpreter. It would be useful to have lots more examples, to not have so many forward references, and to not have very many simple lists of functions.
The docs should mention something about efficiency and that using array operations is almost always a good idea for speed.
Doxygen documentation for the C++ classes.
index entries more consistent to improve behavior of `help -i '.
Make `help -i' try to find a whole word match first. *Clean up help stuff. *Demo files . *Document C++ sources, to make it easier for newcomers to get into writing code.
*Flesh out this wiki
*Add support for listeners (addlistener, dellistener, etc) on the C++ side.
*C++ namespace for Octave library functions.
*Better error messages for missing operators?
*Use non-empty identifiers in all warnings and errors issued by Octave, see [[Easy projects#Miscellaneous]].
*Reduce the amount of datatypes in liboctave
[[Project liboctave 4. 2]]
*An interface to gdb. Michael Smolsky <email@example.com> wrote:
*:I was thinking about a tool, which could be very useful for me in my numerical simulation work. It is an interconnection between gdb and octave. We are often managing very large arrays of data in our fortran or c codes, which might be studied with the help of octave at the algorithm development stages. Assume you're coding, say, wave equation. And want to debug the code. It would be great to pick some array from the memory of the code you're developing, fft it and see the image as a log-log plot of the spectral density. I'm facing similar problems now. To avoid high c-development cost, I develop in matlab/octave, and then rewrite into c. It might be so much easier, if I could off-load a c array right from the debugger into octave, study it, and, perhaps, change some [many] values with a convenient matlab/octave syntax, similar to <code>a(:,
50:250)=zeros(100,200)</code>, and then store it back into the memory of my c code.
*Implement gdb extensions for Octave types. Octave has the <code>etc/gdbinit</code> file, which has some basic support for displaying the contents of Octave types. Add more extensions to make it easier to debug octave_values and other Octave types.
=Marketing and Community=
*Make the website
prettier. Maybe a new design, maybe a more "corporate" design (if we're heading down the "paid support for Octave" path.
* FusionForge's "Submit a Snippet" and "Create A Package" would seem to be directly usable for Agora's "Post a Snippet" and "Share your Code", respectively: https://alioth.debian.org/snippet/. It is FLOSS. ** ScipyCentral, http://scipy-central.org/ has all the features we need and is also free software.
Move [ http:// octave. sourceforge. net/ Octave- Forge] to [http://savannah.gnu.org/projects/octave/ Savannah] so everything is hosted in the same place.
*For ideas, see the [http://openoffice.apache.org/orientation/intro-marketing.html Apache Open Office Introduction to Marketing] * Help design a user or a developer survey [ http://www.openoffice.org/marketing/ooocon2006/presentations/wednesday_c10.pdf]
* Help prepare and deliver presentations about Octave at colleges and universities.
== Improve Windows binary packaging ==
'''Skills Required''': Knowledge of GNU build systems, Makefiles, configure files, chasing library dependencies, how to use a compiler. No m-scripting or C++ necessary, beyond understanding [http://david.rothlis.net/c/compilation_model/ the C++ compilation model].
Mac OS X binary packaging ==
We would like to be able to easily generate binary packages for
Mac OS X. Right now, it's difficult and tedious to do so. Most OS X users install Octave using one of the source-based package managers such as Homebrew or MacPorts. Any way to help us build a binary package would be appreciated. Required knowledge is understanding how building binaries in Mac OS X works. Our current approach to building binaries for Windows is to cross-compile from a GNU system using [http://mxe.cc/ MXE], something similar may be possible for OS X ([http://lilypond.org/gub/ GUB]?).
'''Skills Required''': Knowledge of GNU build systems, Makefiles, configure files, chasing library dependencies, how to use a compiler. If you choose to work on GUB, Python will be required. No m-scripting or C++ necessary, beyond understanding [http://david.rothlis.net/c/compilation_model/ the C++ compilation model].
is always bugs to fix. The [ http://savannah.gnu.org/bugs/?group=octave bug tracker] is a good place to find tasks needing a hand. See also [[Short projects#Bugs]].
= Matlab compatibility =
One list is provided on the source for function __unimplemented.m__, subfunction missing_functions; it can be edited in the Octave GUI or browsed at [http://hg.savannah.gnu.org/hgweb/octave/file/default/scripts/help/__unimplemented__.m#l547].
Lists are also kept for
the [[ Image package| Image]], [[Mapping package|Mapping]], [[Optimization package|Optimization]], [[Signal package|Signal]] , and [[Statistics package|Statistics]] packages.
It is also possible to look at existing [[Wikipedia:Free and open-source software|FOSS]] implementations, from FreeMat and Scilab (for more closely compatible languages) to R or Scipy or Julia (for less compatible versions). Obviously, it is NOT OK to look at the Matlab implementation since this is not [[Wikipedia:Free software|free software]]!