Difference between revisions of "User:Carandraug"

From Octave
Jump to navigation Jump to search
(add list of things I would like to see on the image package soon)
 
(42 intermediate revisions by 2 users not shown)
Line 1: Line 1:
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.
+
I got involved with Octave on the Winter of 2010, at the end of my first year as PhD student. My project involved using a Matlab piece of code written by a collaborator but I refused to use it, I wanted free software. So I convinced the collaborators to release it under GPL and ported it to Octave (released as [https://github.com/af-lab/frapinator frapinator], but I really should go back and write it properly).
  
== Octave to do list ==
+
Since then, I have contributed to Octave many times, became maintainer of the Octave Forge project and its image package. While I have no formal education in programming or computer science, it was the freedom of Octave and its community that allowed me to learn so much.
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 <nowiki>~~~~</nowiki>
 
  
=== wiki to do list ===
+
=== Roadmap ===
  
=== octave code to write ===
+
The following are missing targets that would be nice to have on future releases of the image package
* make unimplemented check for packages as well
 
* implement {{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?</pre>
 
* replacement for [http://www.mmorph.com/ 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)
 
** 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 ===
+
* add ellipse properties to {{codeline|regionprops}} (see bug {{bug|44100}}) ([http://hg.code.sf.net/p/octave/image/rev/7cf22a478792 done])
* find copyright holder of gcvsplf.f after death of Herman Woltring
+
* speed up {{codeline|regionprops}} for large images with many small objects (probably work around for loop with labeled == labelid)
* finish iptcheckinput
+
* support passing {{codeline|bwconncomp}} output to {{codeline|regionprops}} (and then fix {{codeline|bwpropfilt}} to use that instead of a labeled image)
* get an octave-forge logo (falar com o Duarte)
+
* ND support on {{codeline|imfilter}}
* finish zenity package once inputParser is finished
+
* check if {{codeline|normxcorr2}} is Matlab compatible and investigate making use of {{codeline|fftconvn}} since it's likely to receive large input
** for scale see https://savannah.gnu.org/bugs/?33330
+
* investigate implementing the missing deconvolution functions (see patch {{patch|8571}})
* get hough transform function in image package compatible
+
* anything else that is done or submitted before the above are done
* look into [[http://siptoolbox.sourceforge.net/ SIP]] and [[http://sivp.sourceforge.net/ sivp]]
 
* from Perl
 
** File::Temp
 
** check for revision numbers
 
** Getopt::Long
 
* port ReadImageJROI
 
* make better normxcorr2: [[http://www.idiom.com/~zilla/Papers/nvisionInterface/nip.html 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
 

Latest revision as of 21:50, 31 August 2018

I got involved with Octave on the Winter of 2010, at the end of my first year as PhD student. My project involved using a Matlab piece of code written by a collaborator but I refused to use it, I wanted free software. So I convinced the collaborators to release it under GPL and ported it to Octave (released as frapinator, but I really should go back and write it properly).

Since then, I have contributed to Octave many times, became maintainer of the Octave Forge project and its image package. While I have no formal education in programming or computer science, it was the freedom of Octave and its community that allowed me to learn so much.

Roadmap[edit]

The following are missing targets that would be nice to have on future releases of the image package

  • add ellipse properties to regionprops (see bug #44100) (done)
  • speed up regionprops for large images with many small objects (probably work around for loop with labeled == labelid)
  • support passing bwconncomp output to regionprops (and then fix bwpropfilt to use that instead of a labeled image)
  • ND support on imfilter
  • check if normxcorr2 is Matlab compatible and investigate making use of fftconvn since it's likely to receive large input
  • investigate implementing the missing deconvolution functions (see patch #8571)
  • anything else that is done or submitted before the above are done