User:Avbm: Difference between revisions

Jump to navigation Jump to search
675 bytes added ,  30 November 2013
no edit summary
No edit summary
 
(3 intermediate revisions by one other user 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 30: Line 30:
== O: Only out of interest ==
== O: Only out of interest ==
I guess I have covered most of the topics above. My two main gripes with octave are:
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 weiner filter
*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)
*Octave is much slower than Matlab especially for non-vectorized code (which have many loops)


Line 48: Line 48:
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.
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 2013 Applicants]]
 
[[Category:2013]]
[[Category:Applicants]]
501

edits

Navigation menu