Projects: Difference between revisions

Jump to navigation Jump to search
621 bytes removed ,  9 April 2019
→‎Missing functions: link to category
(→‎Numerical: eig functionality added in GSoC 2016)
(→‎Missing functions: link to category)
(12 intermediate revisions by 6 users not shown)
Line 1: Line 1:
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 [http://www.gnu.org/software/octave/doc/interpreter/Contributing-Guidelines.html#Contributing-Guidelines Contributing Guidelines chapter] in the [http://www.gnu.org/software/octave/doc/interpreter/ Octave manual].
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.
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.
Line 75: Line 75:
== Matlab-compatible ODE solvers in core-Octave ==
== Matlab-compatible ODE solvers in core-Octave ==


* Adapt "odeset" and "odeget" from the odepkg package so that the list of supported options is more Matlab-compatible, in the sense that all option names that are supported by Matlab should be available. On the other hand, Matlab returns an error if an option which is not in the list of known options is passed to "odeset", but we would rather make this a warning in order to allow for special extensions, for example for symplectic integrators.
* <strike> Adapt "odeset" and "odeget" from the odepkg package so that the list of supported options is more Matlab-compatible, in the sense that all option names that are supported by Matlab should be available. On the other hand, Matlab returns an error if an option which is not in the list of known options is passed to "odeset", but we would rather make this a warning in order to allow for special extensions, for example for symplectic integrators. </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> 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>
* Build Matlab compatible versions of "ode15s" and "ode15i". jwe has prototype implementations [https://savannah.gnu.org/patch/index.php?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> 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".


Line 94: 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).
**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).
**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).
== Implement a Qt widget for manipulating plots ==
Octave has had for some time a native OpenGL plotter. The plotter requires some user interaction for manipulating the plots, and it's been using fltk for quite some time. We want to replace this with Qt, so it fits better with the overall GUI look-and-feel and is easier to extend in the future.
[https://github.com/goffioul/QtHandles QtHandles] is a current work in progress integrating the octave OpenGL renderer plus good support for GUI elements (uicontrol, uimenu, uitoolbar...). This project may initially consists of integrating the existing QtHandles code base into Octave. Then if time permits, further improvements can be made to QtHandles.


== Create a better (G)UI for the profiler ==
== Create a better (G)UI for the profiler ==
Line 177: Line 171:
   if (expr) 'this is a string' end
   if (expr) 'this is a string' end


is parsed as IF expr STRING END. ''(see [https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2014-March/039554.html this] post on the mailing list)''
is parsed as IF expr STRING END. ''(see [https://lists.gnu.org/archive/html/octave-maintainers/2014-03/msg00087.html this] post on the mailing list)''


*Clean up functions in input.cc that handle user input (there currently seems to be some unnecessary duplication of code and it seems overly complex).
*Clean up functions in input.cc that handle user input (there currently seems to be some unnecessary duplication of code and it seems overly complex).
Line 231: Line 225:


*Too much time is spent allocating and freeing memory. What can be done to improve performance?
*Too much time is spent allocating and freeing memory. What can be done to improve performance?
  Use move constructors rather than copy constructors for things like dim_vectors which are repeatedly created just to initialize Array or Matrix objects.


*Error output from Fortran code is ugly. Something should be done to make it look better.
*Error output from Fortran code is ugly. Something should be done to make it look better.
Line 294: Line 290:


* On 'imagesc' plots, report the matrix values also based on the mouse position, updating on mouse moving.
* On 'imagesc' plots, report the matrix values also based on the mouse position, updating on mouse moving.
* Create a "getframe" function that receives a  a graphics handle and returns a 3D matrix from the graphics window associated with that handle.


* Add map-creating capabilities similar to the Matlab [http://www.mathworks.com/help/map/functionlist.html Mapping toolbox] for inclusion in the Octave Forge [https://sourceforge.net/p/octave/mapping mapping package].
* Add map-creating capabilities similar to the Matlab [http://www.mathworks.com/help/map/functionlist.html Mapping toolbox] for inclusion in the Octave Forge [https://sourceforge.net/p/octave/mapping mapping package].
Line 351: Line 345:
=Configuration and Installation=
=Configuration and Installation=


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


*Makefile changes:
*Makefile changes:
Line 360: Line 354:
*Create a docs-only distribution?
*Create a docs-only distribution?


*Better binary packaging and distribution, especially on Windows.
*<strike> Better binary packaging and distribution, especially on Windows. </strike>  Now done by MXE


*Octave Emacs mode needs maintenance.
*<strike> Octave Emacs mode needs maintenance. </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> 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=


*Document new features.
*<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.
*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.


*The docs should mention something about efficiency and that using array operations is almost always a good idea for speed.
*<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.
*Doxygen documentation for the C++ classes.
Line 380: Line 374:
*Make `help -i' try to find a whole word match first.
*Make `help -i' try to find a whole word match first.


*Clean up help stuff.
*<strike> Clean up help stuff. </strike>


*Demo files.
*Demo files.
Line 413: Line 407:
=Programming=
=Programming=


*Add support for listeners (addlistener, dellistener, etc) on the C++ side.
*<strike> Add support for listeners (addlistener, dellistener, etc) on the C++ side. </strike>


*C++ namespace for Octave library functions.
*<strike> C++ namespace for Octave library functions. </strike>


*Better error messages for missing operators?
*Better error messages for missing operators?
Line 473: Line 467:
** ScipyCentral, http://scipy-central.org/ has all the features we need and is also free software.  
** ScipyCentral, http://scipy-central.org/ has all the features we need and is also free software.  


*Move [http://octave.sourceforge.net/ Octave-Forge] to [http://savannah.gnu.org/projects/octave/ Savannah] so everything is hosted in the same place.
*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]
*For ideas, see the [http://openoffice.apache.org/orientation/intro-marketing.html Apache Open Office Introduction to Marketing]
Line 554: Line 548:
=Bugs=
=Bugs=


There is always bugs to fix. The [http://savannah.gnu.org/bugs/?group=octave bug tracker] is a good place to find tasks needing a hand. See also [[Short projects#Bugs]].
There are always bugs to fix. The [https://savannah.gnu.org/bugs/?group=octave bug tracker] is a good place to find tasks needing a hand. See also [[Short projects#Bugs]].


= Matlab compatibility =
= Matlab compatibility =
Line 564: Line 558:
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].
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]], and [[Statistics package|Statistics]] packages.
Lists are also kept for [[:Category:Missing functions|several 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]]!
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]]!
281

edits

Navigation menu