Difference between revisions of "User:Avbm"

From Octave
Jump to navigation Jump to search
 
(13 intermediate revisions by 2 users not shown)
Line 11: Line 11:
  
 
===Matlab/Octave===
 
===Matlab/Octave===
I have used Matlab for various college projects for the last 5 years. I began using Octave as a Matlab replacement about 2 years ago. The main uses have been for simulation and image processing. I am know most of the similarities and differences between Matlab and Octave.  
+
I have used Matlab for various college projects for the last 5 years. I began using Octave as a Matlab replacement about 2 years ago. The main uses have been for simulation and image processing. I know most of the similarities and differences between Matlab and Octave.
  
 
===Python===
 
===Python===
Line 17: Line 17:
  
 
===Other===
 
===Other===
Other than the above three  I have used somebasic javascript & HTML. I am quite familiar with the Mediawiki framework am one of the site maintainers for the [[wiki.cyanogenmod.org | Cyanogenmod wiki]]. I have used the CGal library for a graphics project. I have breifly dabbled with QT when we were experimenting with various frontend/interface for an embedded project which transmitted data on the serial port. I primarily used Labview for my master's Thesis.
+
Other than the above three  I have used some basic javascript & HTML. I am quite familiar with the Mediawiki framework and am one of the site maintainers for the [http://wiki.cyanogenmod.org Cyanogenmod wiki]. I have used the CGal library for a graphics project. I have briefly dabbled with QT when we were experimenting with various frontend/interface for an embedded project which transmitted data on the serial port. I primarily used Labview for my Master's Thesis.
 +
 
 +
I am a bit familiar with mercurial(thanks to Jordi) and have submitted a couple of minor patches which fix Texinfo5 compatibility issues in Octave.
  
I am a bit familiar with mercurial(thanks to Jordi) and have submitted a couple of minor patches which fix Texinfo5 compatibility issues.
 
 
== F: Feeling fine ==
 
== F: Feeling fine ==
* Please describe (in short) your experience with the following tools: ''We only use this question to determine where you need guidance, not for rating!  We by no means expect you to be familiar with all of these and you'll won't necessarily need them while working with us.''
+
*IRC/mailing lists: familiar with using IRC.(IRC name: white) I have also used (subscribed and posted)the octave-maintainers list
** IRC and mailing lists
+
*Mercurial: new to using mercurial but I have the hang of it(thanks to Jordi)
** Mercurial or other source code management systems
+
*Mediawiki: quite familiar with mediawiki including (slightly) advanced features such as templates
** Mediawiki or other wiki software
+
*Average working knowledge of make and gcc. Haven't used gdb much.
** make, gcc, gdb or other development tools
+
*I work much better in a group (of 2/3 than individually) and prefer to have regular (constructive) feedback. Since both of those are inherently a part of OSS I should be quite happy to continue contributing to Octave after GSoC during most of my free time.
* What will make you actively stay in our community after this GSoC is over? ''You can also tell us after applications close and we'll happily try to fulfill :-)''
 
  
 
== O: Only out of interest ==
 
== O: Only out of interest ==
* Did you ever hear about Octave before?
+
I guess I have covered most of the topics above. My two main gripes with octave are:
** If so, when and where? How far have you been involved already?
+
*Not all of the image processing built-in functions are not supported including some of the more commonly used ones like the wiener filter
** If not, where would you expect or advise us to do advertising?
+
*Octave is much slower than Matlab especially for non-vectorized code (which have many loops)
* What was the first question concerning Octave you could not find an answer to rather quickly? ''Of course more than one question can be stated. We try to improve based on this each year! Includes learning how to use it, code, website, GSoC application, …''
 
  
 
== P: Prerequisites ==
 
== P: Prerequisites ==
* Please state the operating system you work with.
+
My primary OS is linux (Arch linux distro if that matters). I also have access to Windows 7 professional.
** If you have access to more than one, please state them and the conditions under which you are granted this access.
+
I should have access to the internet 24x7 unless I am on the road/travelling (which is a remote possibility). I have two computers (laptop + Desktop) and have complete access to them 24x7.
* Please estimate an average time per day you will be able to ''(if separated)'' access
 
** an internet connection
 
** a computer
 
** a computer with your progressing work on
 
* Please describe the degree up to which you can install new software on computers you have access to.
 
  
 
== S: Self-assessment ==
 
== S: Self-assessment ==
* Please describe how useful criticism looks from your point of view as committing student.
+
*I am quite capable of working alone for extended periods but I prefer working in small groups and periodic review/criticism. Also working alone(in a void) for a long time tends to get boring.
* How autonomous are you when developing? ''If you answer both subquestions with "Yes, definitely", we are a tad confused. ;-)''
+
*I prefer to have a sort of holistic view of the work ahead but prefer to write code iteratively/incrementally with small improvements and testing between each step. I usually jot down my algorithm and functional blocks on paper before I start writing the code. Also usually I tend to prefer simple working algorithms(even if they have poor performance) initially and to replace them, at a later time, with more complicated but efficient ones.
** Do you like to discuss changes intensively and not start coding until you know what you want to do?
+
*I don't mind throwing out chunks of my work if it doesn't fit with the overall project. I have worked in a student run lab for 5 years and we did on occasion have to chuck out weeks worth of work but what I learnt from it was that the effort is never wasted and that dumped code tends to find applications elsewhere later.
** Do you like to code a proof of concept to 'see how it turns out', modifying that and taking the risk of having work thrown away if it doesn't match what the project or original proponent had in mind?
 
  
 
== Y: Your task ==
 
== Y: Your task ==
* Did you select a task from our list of proposals and ideas?
+
I am interested in two tasks:
** If yes, what task did you choose? Please describe what part of it you especially want to focus on if you can already provide this information. ''Please also wiki-link the page for your elaborated proposal here.''
+
*Expand the built-in image processing functions to support more/most of those already there in matlab.
** If you apply for a task you have added yourself instead, please describe this task, its scope and people you already talked to concerning it. What field of tasks did you miss on the list?
+
*Work on JIT compilation and expand it to work with matrices/other data types than scalars.
* Please provide a rough estimated timeline for your work on the task. ''This should include the GSoC midterms and personal commitments like exams or vacation ("non-coding time"). Optionally include two or three milestones you expect.''
+
I am quite sure that I will have enough time for only <b>one</b> of the two and am leaning more towards JIT since that will be more useful in general.
 +
 
 +
My planned schedule is:
 +
*May 28 - June 16: Get acquainted with llvm and familiarize myself with Octave's Abstract Syntax Tree(AST) and Single Static Assignment(SSA) property of intermediate representation(IR). Also seperate the various parts of the code into smaller functional blocks and start on llvm 3.2 compatibility.(Some work has already been done on 3.2 compatibility)
 +
*June 17 - July 29: Make the current JITC code compatible with llvm 3.2 and work on making an llvm IR for a matrix.
 +
*July 30 - August 30: Convert an octave Matrix IR to llvm IR and work on getting everything together.
 +
*Sept 1 - Sept 14: Clean up the code, iron out the creases and work on final report.
  
  
<!--[[Category:Summer of Code 2012]]-->
+
[[Category:2013]]
 +
[[Category:Applicants]]

Latest revision as of 02:56, 30 November 2013

Amod Mulay's Application[edit]

A: An introduction[edit]

I am a graduate student at Stony Brook University. I have a master's in Mechanical Engineering and am pursuing a second one in Computer Engineering and my primary research interest is robotics. I speak English, Hindi and Marathi. Quite honestly I wanted to contribute to a FOSS project for some time. I chose Octave because a lot of the work I do requires Matlab and Octave is the one open source alternative which is most compatible with Matlab. Participating in GSoC has the added bonus of getting paid for your work ;).

C: Contact[edit]

I usually use the nick "white" on IRC and other public forums. I live in the EST timezone(UTC-5) and will be here all of summer. I am usually more comfortable working at night but don't mind being active during the day(since most of the contributors are more active on IRC during work hours).

E: Coding experience[edit]

C/C++[edit]

C/C++ was the first programming language I learnt. Have been using it on and off for various projects for a little more than 6 years. I am fairly comfortable with C/C++ code and am familiar(not an expert/advanced user) with the GNU build system however I don't have any experience working with a large code base.

Matlab/Octave[edit]

I have used Matlab for various college projects for the last 5 years. I began using Octave as a Matlab replacement about 2 years ago. The main uses have been for simulation and image processing. I know most of the similarities and differences between Matlab and Octave.

Python[edit]

I learnt python just for fun a few years ago. The only project that I have done using python is for my Computer Networks class. Other than that, I ported a few of my old college projects to python for practice but that's about it. I do like the language and would classify myself as an average user.

Other[edit]

Other than the above three I have used some basic javascript & HTML. I am quite familiar with the Mediawiki framework and am one of the site maintainers for the Cyanogenmod wiki. I have used the CGal library for a graphics project. I have briefly dabbled with QT when we were experimenting with various frontend/interface for an embedded project which transmitted data on the serial port. I primarily used Labview for my Master's Thesis.

I am a bit familiar with mercurial(thanks to Jordi) and have submitted a couple of minor patches which fix Texinfo5 compatibility issues in Octave.

F: Feeling fine[edit]

  • IRC/mailing lists: familiar with using IRC.(IRC name: white) I have also used (subscribed and posted)the octave-maintainers list
  • Mercurial: new to using mercurial but I have the hang of it(thanks to Jordi)
  • Mediawiki: quite familiar with mediawiki including (slightly) advanced features such as templates
  • Average working knowledge of make and gcc. Haven't used gdb much.
  • I work much better in a group (of 2/3 than individually) and prefer to have regular (constructive) feedback. Since both of those are inherently a part of OSS I should be quite happy to continue contributing to Octave after GSoC during most of my free time.

O: Only out of interest[edit]

I guess I have covered most of the topics above. My two main gripes with octave are:

  • Not all of the image processing built-in functions are not supported including some of the more commonly used ones like the wiener filter
  • Octave is much slower than Matlab especially for non-vectorized code (which have many loops)

P: Prerequisites[edit]

My primary OS is linux (Arch linux distro if that matters). I also have access to Windows 7 professional. I should have access to the internet 24x7 unless I am on the road/travelling (which is a remote possibility). I have two computers (laptop + Desktop) and have complete access to them 24x7.

S: Self-assessment[edit]

  • I am quite capable of working alone for extended periods but I prefer working in small groups and periodic review/criticism. Also working alone(in a void) for a long time tends to get boring.
  • I prefer to have a sort of holistic view of the work ahead but prefer to write code iteratively/incrementally with small improvements and testing between each step. I usually jot down my algorithm and functional blocks on paper before I start writing the code. Also usually I tend to prefer simple working algorithms(even if they have poor performance) initially and to replace them, at a later time, with more complicated but efficient ones.
  • I don't mind throwing out chunks of my work if it doesn't fit with the overall project. I have worked in a student run lab for 5 years and we did on occasion have to chuck out weeks worth of work but what I learnt from it was that the effort is never wasted and that dumped code tends to find applications elsewhere later.

Y: Your task[edit]

I am interested in two tasks:

  • Expand the built-in image processing functions to support more/most of those already there in matlab.
  • Work on JIT compilation and expand it to work with matrices/other data types than scalars.

I am quite sure that I will have enough time for only one of the two and am leaning more towards JIT since that will be more useful in general.

My planned schedule is:

  • May 28 - June 16: Get acquainted with llvm and familiarize myself with Octave's Abstract Syntax Tree(AST) and Single Static Assignment(SSA) property of intermediate representation(IR). Also seperate the various parts of the code into smaller functional blocks and start on llvm 3.2 compatibility.(Some work has already been done on 3.2 compatibility)
  • June 17 - July 29: Make the current JITC code compatible with llvm 3.2 and work on making an llvm IR for a matrix.
  • July 30 - August 30: Convert an octave Matrix IR to llvm IR and work on getting everything together.
  • Sept 1 - Sept 14: Clean up the code, iron out the creases and work on final report.