Difference between revisions of "User:Carandraug"

From Octave
Jump to navigation Jump to search
m (→‎octave-forge to do: done new release of time and financial)
Line 15: Line 15:
 
* port omero toolbox
 
* port omero toolbox
 
* use post_install to move oct into private directory?
 
* use post_install to move oct into private directory?
 +
* import to octave from octave-forge
 +
** cmpermute (image)
 +
** cmunique (image)
 +
** condeig (linear-algebra)
 +
** ellipj (specfun)
 +
** ellipke (specfun)
 +
** erfcinv (specfun)
 +
** exifread <-- readexif (image)
 +
** expint (specfun)
 +
** fminsearch (optim)
 +
** funm (linear-algebra)
 +
** gsvd (linear-algebra)
 +
** inputdlg (java)
 +
** listdlg (java)
 +
** publish (miscellaneous)
 +
** resample (signal)
  
 
=== octave-forge to do ===
 
=== octave-forge to do ===

Revision as of 09:42, 21 April 2012

Somehow I got involved with GNU octave even though I don't actually need it for work anymore. I used it for 6 months during my PhD to write the FRAPINATOR.

Octave to do list

You can add stuff to my todo list (I may however move it back to your todo list on your userpage). Don't forget to sign each item with ~~~~

wiki to do list

octave code to write

  • implement Template:Codeline:@inputParser/StructExpand property on general package
  • implement strel object for image package
  • implement nlinfit as wrapper to leasqr once inputParser is finished
  • make test and demo deal with tests and demos in .cc packages
I don't like the first option. It's ugly and further pollutes the user namespace. And even if we have some Makefile that copies the .cc file at pkg install time, users won't know they have to make the call to test and demo differently. I guess demo and test functions would have to be modifed for that. I say just place the demos and tests on the .cc file. Later we can change pkg to copy the .cc file, and then change demo and test to look for those files if the function is .oct file. Tests are mainly used in development so users won't need them. Demos... well in the case of ellipj, it has not been working for a very long time so my guess is that people haven't been using it that much. What do you think?
  • replacement for morphology toolbox
  • port omero toolbox
  • use post_install to move oct into private directory?
  • import to octave from octave-forge
    • cmpermute (image)
    • cmunique (image)
    • condeig (linear-algebra)
    • ellipj (specfun)
    • ellipke (specfun)
    • erfcinv (specfun)
    • exifread <-- readexif (image)
    • expint (specfun)
    • fminsearch (optim)
    • funm (linear-algebra)
    • gsvd (linear-algebra)
    • inputdlg (java)
    • listdlg (java)
    • publish (miscellaneous)
    • resample (signal)

octave-forge to do

  • find copyright holder of gcvsplf.f after death of Herman Woltring
  • fix imhist
  • finish iptcheckinput
  • get an octave-forge logo (falar com o Duarte)
  • finish zenity package once inputParser is finished
  • get hough transform function in image package compatible
  • look into [SIP] and [sivp]
  • from Perl
    • File::Temp
    • check for revision numbers
    • Getopt::Long
  • port ReadImageJROI
  • make better normxcorr2: [Jordi metioned this paper] and
  • fix warnings on C++ code of xml functions moved to IO package
  • new release of optim 1.1.0
    • move test scripts into function test blocks
    • move example scripts into demo blocks
  • turn __bwdist into bwdist (image package)

other octave related todo

  • update gtksourceview octave lang file
  • make gtksourceview highlight octave help text as texinfo
  • make gtksourceview highlight test and demo as octave and not comment
  • finish GeSHi octave lang