Editing User:Edu159
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 17: | Line 17: | ||
== C: Contact == | == C: Contact == | ||
'''* Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave. ''We really want unique nicks. You might want to bold it.''''' | |||
nick: edu159 | nick: edu159 | ||
'''* Which time zone do you live in? Will that change over GSoC duration? ''Perhaps DST adjustment or a relocation. Note that both UTC and GMT are not aware of daylight saving time! Please state UTC+x or -x.''''' | |||
Time zone: UTC+0. It won't change during GSoC. | Time zone: UTC+0. It won't change during GSoC. | ||
'''* Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers? ''Example: I usually code around 9.00 to 18.00 and could also try to start earlier (~7.00) for few days ;-)''''' | |||
I can code from 7:00-13:00 in May, June and first half of July from Monday to Thursday. On Fridays, Saturdays and Sundays I have almost the whole day free for coding. In the second half of July and August I have no timeframe restrictions. | I can code from 7:00-13:00 in May, June and first half of July from Monday to Thursday. On Fridays, Saturdays and Sundays I have almost the whole day free for coding. In the second half of July and August I have no timeframe restrictions. | ||
Line 37: | Line 37: | ||
I have only that kind of experience while doing some personal projects with a friend of mine, so I have not experience with such a large project and free software community. | I have only that kind of experience while doing some personal projects with a friend of mine, so I have not experience with such a large project and free software community. | ||
* '''Please describe the biggest project you have written code for and what you learned by doing so. Also describe your role in that project over time.''' | * '''Please describe the biggest project you have written code for and what you learned by doing so. Also describe your role in that project over time.''' | ||
I have dealt with projects with around 2.5-3k lines of code, not more. I don't have a extraordinary successful story about a project I have been in although I have been in lots of small ones. I worked the last year while in college with a friend on a website for informal job seeking done in PHP+MySQL (around 3K lines of PHP code). We even sent the idea to Ycombinator to get funding. Unfortunately we were not selected and the idea was not | I have dealt with projects with around 2.5-3k lines of code, not more. I don't have a extraordinary successful story about a project I have been in although I have been in lots of small ones. I worked the last year while in college with a friend on a website for informal job seeking done in PHP+MySQL (around 3K lines of PHP code). We even sent the idea to Ycombinator to get funding. Unfortunately we were not selected and the idea was not at good as we thought. I learned a lot with that project, particularly combining both college and a project at the same time, working regularly and establishing deadlines. | ||
* '''Please state the commits and patches you already contributed to Octave. ''This question (one of the most important parts by the way) is the only part of your application our wiki admins will edit for you even after the application deadline. Code sometimes speaks louder than many words do.''''' | * '''Please state the commits and patches you already contributed to Octave. ''This question (one of the most important parts by the way) is the only part of your application our wiki admins will edit for you even after the application deadline. Code sometimes speaks louder than many words do.''''' | ||
*Contributions to Octave: | *Contributions to Octave: | ||
** Patch submitted for bug [http://savannah.gnu.org/bugs/?41839 #41839] | ** Patch submitted for bug [http://savannah.gnu.org/bugs/?41839 #41839] (m-file) | ||
** Patch submitted for bug [http://savannah.gnu.org/bugs/?41796 #41796] | ** Patch submitted for bug [http://savannah.gnu.org/bugs/?41796 #41796] (c++) | ||
== F: Feeling fine == | == F: Feeling fine == | ||
Line 77: | Line 75: | ||
I like programming on Linux. | I like programming on Linux. | ||
* '''If you have access to more than one, please state them and the conditions under which you are granted this access.''' | * '''If you have access to more than one, please state them and the conditions under which you are granted this access.''' | ||
I | I have windows (native) and mac virtualized. | ||
* '''Please estimate an average time per day you will be able to ''(if separated)'' access''' | * '''Please estimate an average time per day you will be able to ''(if separated)'' access''' | ||
** an internet connection --> ~18 hours a day | ** an internet connection --> ~18 hours a day | ||
Line 97: | Line 95: | ||
== Y: Your task == | == Y: Your task == | ||
My intention is upgrading some functions related with sparse matrices so they become compliant with Matlab and implement others that are not present in Octave right now. Next | |||
The functions are '''ichol''', '''ilu''', '''sprand''', '''sprandn''', '''sprandsym''', '''minres''' and '''lsqr'''. | |||
* Approach: | |||
**'''ilu:''' That function has a big chunk of options and the last year was almost implemented by Kai Torben as his GSOC project. He interfaced Octave with ITSOL/ZITSOL libraries but in the end there were some issues with that approach. | |||
1) ILUTP algorithm did not work for him | |||
2) He had to patch the library to get things work! | |||
3) modified versions of algorithms ("milu" option) were not implemented in the libraries | |||
4) That "ugly" scenario lead to finally not being able to include ITSOL as a dependency with Octave. Bottom line, the integration of the function with the development repository could not be achieved. | |||
* 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.'' | |||
[[Category: Summer of Code]] | |||
Under construction.... | |||