# Editing Projects

Jump to navigation
Jump to search

**Warning:** You are not logged in. Your IP address will be publicly visible if you make any edits. If you **log in** or **create an account**, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision | Your text | ||

Line 1: | Line 1: | ||

− | The list below summarizes features or bug fixes we would like to see in Octave. | + | 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 octave-maintainers@octave.org know. We might have information that could help you. You should also read the [[Contribution guidelines |Contributing Guidelines]]. |

− | + | 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 octave-maintainers@octave.org before you start working on some large project. | |

− | + | Summer of Code students, please also see [[SoC Project Ideas]]. | |

− | + | ||

+ | If you're looking for small project, something more suited to start getting involved with Octave development or to fill a boring evening, see [[short projects]] | ||

=Numerical= | =Numerical= | ||

− | |||

− | |||

*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. | |

− | |||

− | |||

− | |||

− | *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 | ||

*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 34: | Line 29: | ||

*Evaluate harmonics and cross-correlations of unevenly sampled and nonstationary time series, as in http://www.jstatsoft.org/v11/i02 (which has C code with interface to R). (This is now partly implemented in the [http://octave.sourceforge.net/lssa/index.html lssa] package.) | *Evaluate harmonics and cross-correlations of unevenly sampled and nonstationary time series, as in http://www.jstatsoft.org/v11/i02 (which has C code with interface to R). (This is now partly implemented in the [http://octave.sourceforge.net/lssa/index.html lssa] package.) | ||

− | + | == General purpose Finite Element library == | |

Octave-Forge already has a set of packages for discretizing Partial Differential operators by Finite Elements and/or Finite Volumes, | Octave-Forge already has a set of packages for discretizing Partial Differential operators by Finite Elements and/or Finite Volumes, | ||

Line 44: | Line 39: | ||

* create new functions specifically suited for Octave | * create new functions specifically suited for Octave | ||

* improve the efficiency of the code | * improve the efficiency of the code | ||

− | The main goal for the fem-fenics package is ultimately to be merged with the FEnics project itself, so that it can remain in-sync with the main library development. | + | The main goal for the fem-fenics package is ultimately to be merged with the FEnics project itself, so that it can remain in-sync with the main library development. |

== Implement solver for initial-boundary value problems for parabolic-elliptic PDEs in 1D == | == Implement solver for initial-boundary value problems for parabolic-elliptic PDEs in 1D == | ||

Line 56: | Line 51: | ||

Details on the methods to be implemented can be found in [http://dx.doi.org/10.1145/502800.502801 this paper] on bvp4c and [http://www.jnaiam.net/new/uploads/files/014dde86eef73328e7ab674d1a32aa9c.pdf this paper] on bvp5c. Further details are available in [http://books.google.it/books/about/Nonlinear_two_point_boundary_value_probl.html?id=s_pQAAAAMAAJ&redir_esc=y this book]. | Details on the methods to be implemented can be found in [http://dx.doi.org/10.1145/502800.502801 this paper] on bvp4c and [http://www.jnaiam.net/new/uploads/files/014dde86eef73328e7ab674d1a32aa9c.pdf this paper] on bvp5c. Further details are available in [http://books.google.it/books/about/Nonlinear_two_point_boundary_value_probl.html?id=s_pQAAAAMAAJ&redir_esc=y this book]. | ||

− | + | == Geometric integrators for Hamiltonian Systems == | |

[http://openlibrary.org/books/OL9056139M/Geometric_Numerical_Integration Geometric (AKA Symplectic) integrators] are useful for | [http://openlibrary.org/books/OL9056139M/Geometric_Numerical_Integration Geometric (AKA Symplectic) integrators] are useful for | ||

Line 77: | Line 72: | ||

* SHAKE, see [http://en.wikipedia.org/wiki/Constraint_algorithm here] or [http://dx.doi.org/10.1016/0021-9991(77)90098-5 here] | * SHAKE, see [http://en.wikipedia.org/wiki/Constraint_algorithm here] or [http://dx.doi.org/10.1016/0021-9991(77)90098-5 here] | ||

* RATTLE, see [http://dx.doi.org/10.1016/0021-9991(83)90014-1 here] or [http://dx.doi.org/10.1002/jcc.540161003 here] | * RATTLE, see [http://dx.doi.org/10.1016/0021-9991(83)90014-1 here] or [http://dx.doi.org/10.1002/jcc.540161003 here] | ||

− | |||

== Matlab-compatible ODE solvers in core-Octave == | == Matlab-compatible ODE solvers in core-Octave == | ||

Line 84: | Line 78: | ||

* <strike> Adapt the interface of "ode45" in odepkg to be completely Matlab compatible, fix its code and documentation style and move it to Octave-core. </strike> | * <strike> Adapt the interface of "ode45" in odepkg to be completely Matlab compatible, fix its code and documentation style and move it to Octave-core. </strike> | ||

* <strike> Build Matlab compatible versions of "ode15s" and "ode15i". jwe has prototype implementations [https://savannah.gnu.org/patch/?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. </strike> | * <strike> Build Matlab compatible versions of "ode15s" and "ode15i". jwe has prototype implementations [https://savannah.gnu.org/patch/?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. </strike> | ||

− | |||

− | |||

− | |||

− | |||

− | |||

− | |||

* Implement Matlab compatible versions of "deval". | * Implement Matlab compatible versions of "deval". | ||

− | |||

− | |||

== High Precision Arithmetic Computation == | == High Precision Arithmetic Computation == | ||

Line 102: | Line 88: | ||

=GUI/IDE= | =GUI/IDE= | ||

+ | :''See also: [[Summer of Code Project Ideas#GUI]]'' | ||

*Søren Hauberg has suggested that we need C++ code that can: | *Søren Hauberg has suggested that we need C++ code that can: | ||

**Determine if a line of code could be fully parsed, i.e. it would return true for "plot (x, y);", but false for "while (true)". | **Determine if a line of code could be fully parsed, i.e. it would return true for "plot (x, y);", but false for "while (true)". | ||

Line 107: | Line 94: | ||

**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. | * 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 ([[Control package]])== | ||

Line 124: | Line 103: | ||

The paper by [http://arxiv.org/abs/cs.MS/0604006 Bateman & Adler] is good reading for understanding the sparse matrix implementation. | The paper by [http://arxiv.org/abs/cs.MS/0604006 Bateman & Adler] is good reading for understanding the sparse matrix implementation. | ||

+ | |||

+ | *Improve QR factorization functions, using idea based on CSPARSE cs_dmsol.m | ||

+ | |||

+ | *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 | ||

*Improve Matlab compatibility for {{manual|sprandsym}}. | *Improve Matlab compatibility for {{manual|sprandsym}}. | ||

Line 133: | Line 116: | ||

**minres | **minres | ||

**symmlq | **symmlq | ||

− | |||

− | |||

− | |||

− | |||

− | |||

− | |||

− | |||

− | |||

=Strings= | =Strings= | ||

Line 369: | Line 344: | ||

*<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= | + | =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. | ||

+ | |||

+ | *[[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 | ||

=Tests= | =Tests= | ||

Line 376: | Line 362: | ||

**Tests for various functions. Would be nice to have a test file corresponding to every function (see below) | **Tests for various functions. Would be nice to have a test file corresponding to every function (see below) | ||

**Tests for element by element operators: + - .* ./ .\ .^ | & < <= == >= > != ! | **Tests for element by element operators: + - .* ./ .\ .^ | & < <= == >= > != ! | ||

− | |||

**Tests for boolean operators: && || | **Tests for boolean operators: && || | ||

**Tests for other operators: * / \ ' .' | **Tests for other operators: * / \ ' .' | ||

Line 424: | Line 409: | ||

*Reduce the amount of datatypes in liboctave. | *Reduce the amount of datatypes in liboctave. | ||

− | |||

− | |||

− | |||

− | |||

− | |||

=Miscellaneous= | =Miscellaneous= | ||

Line 462: | Line 442: | ||

* Help design a user or a [https://www.openoffice.org/marketing/ooocon2006/presentations/wednesday_c10.pdf developer survey] | * Help design a user or a [https://www.openoffice.org/marketing/ooocon2006/presentations/wednesday_c10.pdf developer survey] | ||

− | * Help prepare and deliver presentations | + | * 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 472: | Line 452: | ||

'''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 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]. | '''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]. | ||

Line 482: | Line 460: | ||

=Performance= | =Performance= | ||

− | * A profiler for Octave would be a very useful tool. And now we have one! But it really needs a better interface. | + | *A profiler for Octave would be a very useful tool. And now we have one! But it really needs a better interface. |

− | * Having {{Codeline|parfor}} functioning would speed code development and execution now that multicore architectures are widespread. See [http://octave.1599824.n4.nabble.com/Parfor-td4630575.html here] and [http://stackoverflow.com/questions/24970519/how-to-use-parallel-for-loop-in-octave-or-scilab here]. Existing code from the [[Parallel package | parallel]] and [http://octave.sourceforge.net/mpi/index.html mpi] packages could perhaps be adapted for this | + | *Having {{Codeline|parfor}} functioning would speed code development and execution now that multicore architectures are widespread. See [http://octave.1599824.n4.nabble.com/Parfor-td4630575.html here] and [http://stackoverflow.com/questions/24970519/how-to-use-parallel-for-loop-in-octave-or-scilab here]. Existing code from the [[Parallel package | parallel]] and [http://octave.sourceforge.net/mpi/index.html mpi] packages could perhaps be adapted for this. |

− | |||

=Packaging= | =Packaging= |