Mithil

← Older edit

User:Mithil (edit)

Revision as of 07:41, 3 April 2017

1,329 bytes added , 3 April 2017

→‎A: An introduction

Mithil

45

edits

@@ Line 19: / Line 19: @@
 *** This is my first GSoC experience.
 * Why are you choosing Octave?
-**I opted for Octave because it overlaps with my interest areas. I have excellent Computer Science and Mathematical background which inclines me towards Octave. Also, I have worked on Octave for a while, it'd be a great opportunity to contribute and give it back to Open Source Community.
+**I opted for Octave because it overlaps with my area of interest. I have excellent Computer Science and Mathematical background which is the primary reason to opt Octave. Moreover, I have worked on Octave for a while. Hence it'd be a great opportunity to contribute to the Open Source Community.
 == C: Contact ==
@@ Line 72: / Line 72: @@
 ** Yes, I have heard of Octave before.
 ** If so, when and where? How far have you been involved already?
-*** Last summer during my research intern at Purdue University, Professor Ananth Gramma advised me to have a look on "Octave-Networks Toolbox". After that, I used it for my Machine learning course by Andrew NG.
+*** I have extensively used Octave over the past year, beginning with my Summer Research Intern at Purdue University, followed by assignments in Andrew NG's Machine Learning Course.
 * What was the first question concerning Octave you could not find an answer to rather quickly? ''Of course, ore 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, …''
-** I couldn't find "Building guidelines" for Octave. It'd be great to put the contents of "HACKING" file to a webpage.
+** I had a hard time to find "Building guidelines" for Octave. It'd be great to put the contents of "HACKING" file to a web page.
 == P: Prerequisites ==
@@ Line 111: / Line 111: @@
 * 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"). If possible, include two or three milestones you expect.''
 [[Category: Summer of Code]]
-** I would update the timeline after working out the finer details with mentors.
+**Community Bonding Period ( 4th May - 30th May)
+***1st Week: Understanding the code base and reading about the research work going on in the relevant area.
+***2nd Week: Discussing possible areas of improvement with the mentors. Getting an abstract idea about the implementation.
+***3rd Week: Proposing new functions which could be included, study about them and constantly review ideas with mentors.
+***4th Week: Fixating on the proposed upgrades and schedule.
+**Phase I ( 1st June - 30th June)
+***1st Week: Profile the present code of expm, sqrtm and logm. Implement efficient algorithms as m script functions (if any).
+***2nd Week: Change possible functions to equivalent C++ functions.
+***3rd Week: Review the work done and consult mentors for suggestions.
+***4th Week: Work on suggestions and then wind up the Phase I. Start preparing for the Phase II.
+**Phase II ( 1st July - 28th July)
+***1st Week: Confer about the new functions which could be added and then implement them.
+***2nd Week: Profile the code to identify weak sections and then improvise accordingly.
+***3rd Week: Review Phase II.
+***4th Week: Work on suggestions and look back through Phase I and Phase II.
+**Phase III ( 29th July - 29th August)
+***1st Week: Complete pending work ( if any ).
+***2nd Week: Identify bugs and documenting the project.
+***3rd Week: Get feedback and finalize the Submission.
+***4th Week: Wait for Evaluation :)