*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.
**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). == 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])
=Configuration and Installation=
*<strike> 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. </strike> Now config.h and octave-config.h.
*Create a docs-only distribution?
*<strike> Better binary packaging and distribution, especially on Windows. </strike> Now done by MXE
*<strike> Octave Emacs mode needs maintenance. </strike>
*<strike> 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. </strike> Done, except for special dir libgnu which is the only SUBDIRS listed in configure.ac.
=Documentation and On-Line Help=
*<strike> Document new features. </strike>
*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.
<strike> The docs should mention something about efficiency and that using array operations is almost always a good idea for speed. </strike>
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. *<strike> Clean up help stuff. </strike> *Demo files . *Document C++ sources, to make it easier for newcomers to get into writing code.
*Flesh out this wiki
*<strike> Add support for listeners (addlistener, dellistener, etc) on the C++ side. </strike>
*<strike> C++ namespace for Octave library functions. </strike>
*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]]
=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 [https:// octave. sourceforge. io/ Octave- Forge] to [https://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].
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]], [[Splines package|Splines]], 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]]!