Projects: Difference between revisions

Jump to navigation Jump to search

Projects (edit)

Revision as of 17:55, 19 September 2019

2,433 bytes removed ,  19 September 2019
m
Add reference to Pairwise Summation
(→‎Sparse Matrices: Update some items.)
m (Add reference to Pairwise Summation)
(8 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 93: Line 97:
**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).
**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).
* 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 profiler ==
 
During GSoC 2011, Daniel Kraft successfully implemented a profiler for Octave. It needs a better interface and a way to generate reports. This may be done with Qt, but not necessarily, and HTML reports might also be good.


== Sisotool. Create a graphical design tool for tuning closed loop control system (control pkg) ==
== Sisotool. Create a graphical design tool for tuning closed loop control system ([[Control package]])==


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 338:


=Configuration and Installation=
=Configuration and Installation=
*<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 346: Line 345:


*Create a docs-only distribution?
*Create a docs-only distribution?
*<strike> Better binary packaging and distribution, especially on Windows. </strike>  Now done by MXE
*<strike> Octave Emacs mode needs maintenance. </strike>


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


*<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.
*Make index entries more consistent to improve behavior of <code>help -i</code>.


*Make index entries more consistent to improve behavior of `help -i'.
*Make <code>help -i</code> try to find a whole word match first.


*Make `help -i' try to find a whole word match first.
*Add more demo files.
 
*<strike> Clean up help stuff. </strike>
 
*Demo files.
 
*Document C++ sources, to make it easier for newcomers to get into writing code.


*Flesh out this wiki
*Flesh out this wiki
Line 399: Line 386:


=Programming=
=Programming=
*<strike> Add support for listeners (addlistener, dellistener, etc) on the C++ side. </strike>
*<strike> C++ namespace for Octave library functions. </strike>


*Better error messages for missing operators?
*Better error messages for missing operators?
Line 429: 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 [[Project liboctave 4.2]]
*Reduce the amount of datatypes in liboctave.


=Miscellaneous=
=Miscellaneous=
Line 455: Line 438:
=Marketing and Community=
=Marketing and Community=


*Make the website prettier. Maybe a new design, maybe a more "corporate" design (if we're heading down the "paid support for Octave" path.
* Make the Octave website/[[Project Infrastructure]] easier to maintain.


** FusionForge's "Submit a Snippet" and "Create A Package" would seem to be directly usable for Agora's "Post a Snippet" and "Share your Code", respectively: https://alioth.debian.org/snippet/.  It is FLOSS.
* Make it easier for newcomers to contribute.
** ScipyCentral, http://scipy-central.org/ has all the features we need and is also free software.  


*Move [https://octave.sourceforge.io/ Octave-Forge] to [https://savannah.gnu.org/projects/octave/ Savannah] so everything is hosted in the same place.
* For marketing ideas, see the [https://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]
* Help design a user or a [https://www.openoffice.org/marketing/ooocon2006/presentations/wednesday_c10.pdf developer survey]
 
* Help design a user or a developer survey [http://www.openoffice.org/marketing/ooocon2006/presentations/wednesday_c10.pdf]


* 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]].
== Finish the Agora website ==
** "What is Octave?" [[File:Slides_octconf_gdf_jgh.pdf]] ([http://inversethought.com/hg/what-is-octave/ source]).
 
In 2009, the Mathworks decided to restrict the terms of use Matlab Central, a place dedicated to Matlab collaboration. The Mathworks forbade copyleft licenses and using the "free" code found in Matlab central on anything other than Mathworks products (e.g. forbidding from using it on Octave, even if the authors of the code wanted to allow this). Thus Octave users have no place to centrally, quickly, and conveniently share Octave code. See the [[FAQ#Why_can.27t_I_use_code_from_File_Exchange_in_Octave.3F_It.27s_released_under_a_BSD_license.21|FAQ]] for more details.
 
In response to this, a website started to form, [http://agora.octave.org/ Agora Octave].
 
This should be relatively easy webdev in Python using [http://en.wikipedia.org/wiki/Django_%28web_framework%29 Django].
 
Things to be considered when working on this:
 
* [http://octave-forge.blogspot.ie/2012/08/octconf2012-agora-and-pkg.html discussion of Agora during OctConf2012]
* [http://scipy-central.org/ Scipy Central] - a website with the same objective as Agora for Scipy. Their [https://github.com/scipy/SciPyCentral Code] is released under a BSD license. Might be useful to reuse some parts.
 
Most of the basic functionality of Agora is already in, but there are many ways in which it could be improved, such as implementing comment threads, giving it an email interface, or a ReSTful API which could be used from Octave for package management. See also [[Agora]]. Talk to [[User:JordiGH|Jordi]]


== Improve Windows binary packaging ==
== Improve Windows binary packaging ==
Line 489: 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 Mac OS X binary packaging ==
== Improve macOS 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]?).
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].
Rik
1,072

edits

Retrieved from "https://wiki.octave.org/Special:MobileDiff/12111...12264"

Navigation menu