1,072
edits
Projects: Difference between revisions
Jump to navigation
Jump to search
m
Add new project
m (Add new project) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 388: | Line 388: | ||
**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: + - .* ./ .\ .^ | & < <= == >= > != ! | ||
*** thorough tests for power operator including corner cases and strange combinations such as complex .^ range. | |||
**Tests for boolean operators: && || | **Tests for boolean operators: && || | ||
**Tests for other operators: * / \ ' .' | **Tests for other operators: * / \ ' .' | ||
| Line 435: | Line 436: | ||
*Reduce the amount of datatypes in liboctave. | *Reduce the amount of datatypes in liboctave. | ||
*Re-implement operators using templates and modern C++. Current system evolved before templates and makes extensive use of macros to define interactions between scalar<->scalar, scalar<->matrix, scalar<->float, etc., etc. | |||
**In liboctave, the directory to work on is liboctave/operators | |||
**In libinterp, the directory to work on is libinterp/operators | |||
**In libinterp, there is also xpow.cc, xdiv.cc in libinterp/corefcn | |||
=Miscellaneous= | =Miscellaneous= | ||
| Line 486: | Line 492: | ||
=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. | ||
* Develop a performance benchmark for Octave (interpreter, load/save, plotting, etc., but not simply tests of underlying libraries such as BLAS or LAPACK). This benchmark could be run periodically to make sure that changes during development do not introduce regressions in performance. | |||
=Packaging= | =Packaging= | ||