1,072
edits
(→GUI/IDE: Overhaul.) |
m (Add reference to Pairwise Summation) |
||
(7 intermediate revisions by 2 users not shown) | |||
Line 10: | Line 10: | ||
*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 334: | Line 338: | ||
=Configuration and Installation= | =Configuration and Installation= | ||
*Makefile changes: | *Makefile changes: | ||
Line 343: | Line 345: | ||
*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 396: | Line 386: | ||
=Programming= | =Programming= | ||
*Better error messages for missing operators? | *Better error messages for missing operators? | ||
Line 426: | Line 412: | ||
*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 452: | Line 438: | ||
=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 design a user or a | |||
* Help prepare and deliver presentations about Octave at colleges and universities. | * Help prepare and deliver presentations about Octave at colleges and universities. | ||
** [https://indico.cern.ch/event/626097/contributions/2902420/attachments/1615292/2566811/2018-03-12-octave.pdf Octave talk] at [[OctConf 2018]]. | |||
** "What is Octave?" [[File:Slides_octconf_gdf_jgh.pdf]] ([http://inversethought.com/hg/what-is-octave/ source]). | |||
* [ | |||
== Improve Windows binary packaging == | == Improve Windows binary packaging == | ||
Line 486: | Line 456: | ||
'''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]. |
edits