Ashh87

Joined 1 August 2013
293 bytes added ,  1 August 2013
no edit summary
No edit summary
No edit summary
Line 40: Line 40:
== S: Self-assessment ==
== S: Self-assessment ==
* Please describe how useful criticism looks from your point of view as committing student.#
* Please describe how useful criticism looks from your point of view as committing student.#
  Criticism is very useful, it helps catch bugs and improve the quality of the software. Even simple code style advice is good, keeping new code in line with the existing code.
Criticism is very useful, it helps catch bugs and improve the quality of the software. Even simple code style advice is good, keeping new code in line with the existing code.
* How autonomous are you when developing?
* How autonomous are you when developing?
I am reasonably autonomous when developing. Most of my previous contributions to open source projects have been developed without guidance and then submitted. Feedback has been received and acted upon and the process repeated. I tend to think about the task and come up with a solution on paper and then start to code it up. With a mentor, I can see that this process may well be improved by running ideas past them first to avoid going down dead ends.
I am reasonably autonomous when developing. Most of my previous contributions to open source projects have been developed without guidance and then submitted. Feedback has been received and acted upon and the process repeated. I tend to think about the task and come up with a solution on paper and then start to code it up. With a mentor, I can see that this process may well be improved by running ideas past them first to avoid going down dead ends.
Line 46: Line 46:


== Y: Your task ==
== Y: Your task ==
* Did you select a task from our list of proposals and ideas?
I have chosen the "Incomplete sparse factorizations ichol, ilu"  task - http://wiki.octave.org/Summer_of_Code_Project_Ideas#Incomplete_sparse_factorizations_ichol.2C_ilu
** 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.''
 
** 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?
* 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.''
* 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 would like to take a week or two to familiarise myself with the existing Octave sparse matrix code and related theory, discussing with the mentor where new C++ code should be put in the source tree. Then I would spend a several weeks understanding the algorithm (using books and the existing code previously posted for guidance) to be implemented and how it needs to be modified to use Octaves sparse representation. Finally, I would then start to implement the required code.
Personal commitments include a week long trip to a conference in September and continuing work on my PhD thesis.
4

edits