User:Carandraug: Difference between revisions

From Octave
Jump to navigation Jump to search
(→‎octave-forge to do: more stuff to do)
(remove GSoC 2013 form)
(28 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.
 
= 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>
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 ===
== wiki to do list ==


=== octave code to write ===
== octave code to write ==
* implement {{Codeline:@inputParser/StructExpand}} property on general package
* make unimplemented check for packages as well
* implement strel object for image package
* rewrite inputParser using classdef
* implement nlinfit as wrapper to leasqr once inputParser is finished
** implement {{Codeline:@inputParser/StructExpand}} property on general package
* implement nlinfit as wrapper to leasqr (using inputParser)
* make test and demo deal with tests and demos in .cc packages
* 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>
: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>
Line 16: Line 19:
* use post_install to move oct into private directory?
* use post_install to move oct into private directory?


=== octave-forge to do ===
== octave-forge to do ==
* find copyright holder of gcvsplf.f after death of Herman Woltring
* finish zenity package
* fix imhist
* fix tiff_tag_reader
* finish iptcheckinput
* get an octave-forge logo (falar com o Duarte)
* finish zenity package once inputParser is finished
** for scale see https://savannah.gnu.org/bugs/?33330
** for scale see https://savannah.gnu.org/bugs/?33330
* get hough transform function in image package compatible
* get hough transform function in image package compatible
Line 31: Line 29:
** Getopt::Long
** Getopt::Long
* port ReadImageJROI
* port ReadImageJROI
* make better normxcorr2: [[http://www.idiom.com/~zilla/Papers/nvisionInterface/nip.html Jordi metioned this paper]] and
* make compatible 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
* fix on optim package
* new release of optim 1.1.0
** move test scripts into function test blocks
** move test scripts into function test blocks
** move example scripts into demo blocks
** move example scripts into demo blocks
* turn __bwdist into bwdist (image package)
* default __spatial_filtering S to zeros of same dimension as DOMAIN
* new release of financial and time packages (if no one complains about removing the time package in 3 days)
* implement im2java2d
* implement imclearborder
* port [https://www.bcube-dresden.de/fiesta/wiki/FIESTA FIESTA]


=== other octave related todo ===
== other octave related todo ==
* update gtksourceview octave lang file
* update gtksourceview octave lang file
* make gtksourceview highlight octave help text as texinfo
* make gtksourceview highlight octave help text as texinfo
* make gtksourceview highlight test and demo as octave and not comment
* make gtksourceview highlight test and demo as octave and not comment
* finish GeSHi octave lang
 
[[Category:2013]]
[[Category:Applicants]]

Revision as of 15:09, 21 March 2014

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.

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

  • make unimplemented check for packages as well
  • rewrite inputParser using classdef
  • implement nlinfit as wrapper to leasqr (using inputParser)
  • 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?

octave-forge to do

  • finish zenity package
  • 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 compatible normxcorr2: [Jordi metioned this paper] and
  • fix on optim package
    • move test scripts into function test blocks
    • move example scripts into demo blocks
  • default __spatial_filtering S to zeros of same dimension as DOMAIN
  • implement im2java2d
  • implement imclearborder
  • port FIESTA

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