1,847
edits
(→Sparse Matrices: Update some items.) |
|||
(11 intermediate revisions by 2 users not shown) | |||
Line 8: | Line 8: | ||
=Numerical= | =Numerical= | ||
* Use C++11 <random> libraries for random number generation. Write link between Octave functions (rand, randi, randn, rande) and C++ API. Implement RandStream objects as Matlab does. | |||
*Improve logm, and sqrtm (see this thread: http://octave.1599824.n4.nabble.com/matrix-functions-td3137935.html) | *Improve logm, and sqrtm (see this thread: http://octave.1599824.n4.nabble.com/matrix-functions-td3137935.html) | ||
*Use pairwise addition in sum() to mitigate against numerical errors without substantial performance penalty (https://en.wikipedia.org/wiki/Pairwise_summation). | |||
*Review implementing algorithm in this 2009 paper (https://epubs.siam.org/doi/pdf/10.1137/080738490) for xsum (sum with extra accuracy). The existing implementation uses a 2005 paper. | |||
*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. | *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. | ||
Line 93: | Line 99: | ||
**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). | **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). | **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). | ||
* | * Create a better (G)UI for the {{manual|profile|profiler}}. This may be done with Qt, but not necessarily. | ||
== Sisotool. Create a graphical design tool for tuning closed loop control system ([[Control package]])== | |||
== Sisotool. Create a graphical design tool for tuning closed loop control system ( | |||
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. | 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. | ||
Recently, some implementation was done during [[Summer_of_Code#GSoC_2018|GSoC 2018]], see https://eriveltongualter.github.io/GSoC2018/final.html for details. | |||
=Sparse Matrices= | =Sparse Matrices= | ||
Line 337: | Line 340: | ||
=Configuration and Installation= | =Configuration and Installation= | ||
*Makefile changes: | *Makefile changes: | ||
Line 346: | Line 347: | ||
*Create a docs-only distribution? | *Create a docs-only distribution? | ||
*<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. | *<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= | =Documentation and On-Line Help= | ||
*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. | *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. | ||
* | *[[Doxygen]] documentation for the C++ classes. | ||
* | *Make index entries more consistent to improve behavior of <code>help -i</code>. | ||
*Make | *Make <code>help -i</code> try to find a whole word match first. | ||
* | *Add more demo files. | ||
*Flesh out this wiki | *Flesh out this wiki | ||
Line 399: | Line 388: | ||
=Programming= | =Programming= | ||
*Better error messages for missing operators? | *Better error messages for missing operators? | ||
Line 429: | Line 414: | ||
*Use non-empty identifiers in all warnings and errors issued by Octave, see [[Easy projects#Miscellaneous]]. | *Use non-empty identifiers in all warnings and errors issued by Octave, see [[Easy projects#Miscellaneous]]. | ||
*Reduce the amount of datatypes in liboctave | *Reduce the amount of datatypes in liboctave. | ||
=Miscellaneous= | =Miscellaneous= | ||
Line 455: | Line 440: | ||
=Marketing and Community= | =Marketing and Community= | ||
*Make the website | * Make the Octave website/[[Project Infrastructure]] easier to maintain. | ||
* Make it easier for newcomers to contribute. | |||
* For marketing ideas, see the [https://openoffice.apache.org/orientation/intro-marketing.html Apache Open Office Introduction to Marketing] | |||
* Help design a user or a [https://www.openoffice.org/marketing/ooocon2006/presentations/wednesday_c10.pdf developer survey] | |||
* [ | * Help prepare and deliver presentations and [[Publications about Octave]] at colleges and universities. | ||
* Create a [[Forum for GNU Octave]]. | |||
== Improve Windows binary packaging == | == Improve Windows binary packaging == | ||
Line 489: | Line 458: | ||
'''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]. | '''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]. | ||
== Improve | == Improve macOS binary packaging == | ||
We would like to be able to easily generate binary packages for | We would like to be able to easily generate binary packages for macOS. 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 macOS 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]. | '''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]. |