1,847
edits
(→Configuration and Installation: Strip finished items for clarity.) |
(→Numerical: Acknowledge {{patch|8172}}.) |
||
(10 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) | ||
*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. | *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. See {{patch|8172}} for a previous attempt. | |||
*Make functions like gamma() return the right IEEE Inf or NaN values for extreme args or other undefined cases. | *Make functions like gamma() return the right IEEE Inf or NaN values for extreme args or other undefined cases. | ||
Line 345: | Line 351: | ||
=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 <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 390: | Line 388: | ||
=Programming= | =Programming= | ||
*Better error messages for missing operators? | *Better error messages for missing operators? | ||
Line 420: | 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 446: | 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 480: | 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]. |