Editing User:Carandraug

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
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).
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.


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.
== 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 <nowiki>~~~~</nowiki>


=== Roadmap ===
=== wiki to do list ===


The following are missing targets that would be nice to have on future releases of the image package
=== octave code to write ===
* 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) but should probably be implemented in C++ using [http://www.graphicsmagick.org/Magick++/Image.html GraphicsMagick]
** expint (specfun)
** fminsearch (optim)
** funm (linear-algebra)
** gsvd (linear-algebra)
** inputdlg (java)
** listdlg (java)
** publish (miscellaneous)
** resample (signal)


* add ellipse properties to {{codeline|regionprops}} (see bug {{bug|44100}})  ([http://hg.code.sf.net/p/octave/image/rev/7cf22a478792 done])
=== octave-forge to do ===
* speed up {{codeline|regionprops}} for large images with many small objects (probably work around for loop with labeled == labelid)
* find copyright holder of gcvsplf.f after death of Herman Woltring
* support passing {{codeline|bwconncomp}} output to {{codeline|regionprops}} (and then fix {{codeline|bwpropfilt}} to use that instead of a labeled image)
* finish iptcheckinput
* ND support on {{codeline|imfilter}}
* get an octave-forge logo (falar com o Duarte)
* check if {{codeline|normxcorr2}} is Matlab compatible and investigate making use of {{codeline|fftconvn}} since it's likely to receive large input
* finish zenity package once inputParser is finished
* investigate implementing the missing deconvolution functions (see patch {{patch|8571}})
** for scale see https://savannah.gnu.org/bugs/?33330
* anything else that is done or submitted before the above are done
* get hough transform function in image package compatible
* 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
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Templates used on this page:

Retrieved from "https://wiki.octave.org/User:Carandraug"