Editing User:Yefllower

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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 52: Line 52:




* Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?
* 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 prefer to code in nights, (UTC+0)from 11:00 to 17:00.  
I prefer to code in nights, (UTC+0)from 11:00 to 17:00.  
If no acm training or other meetings, I can start from afternoon like (UTC+0)7:00. (this happens three to four times a week)
If no acm training or other meetings, I can start from afternoon like (UTC+0)7:00. (this happens three to four times a week)
Line 59: Line 59:


* Please describe your experience with C++, Octave or Matlab m-scripts, OpenGL and Qt.
* Please describe your experience with C++, Octave or Matlab m-scripts, OpenGL and Qt.
I have programming C++ since high school, more than five years till now.
I've tried Octave and Matlab, but not often use them. Usually I use mathematica instead.
I've never used Qt or OpenGL. OpenGL was once in my plan until I'm too busy to learn it.
* Please describe your experience with other programming languages.
* Please describe your experience with other programming languages.
I can write a bit Python and Java, can read programs in these language.
* Please describe your experience with being in a development team. ''Do you have experience working with open source or free projects?''
 
 
* Please describe your experience with being in a development team.
No such experience.
 
 
* 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.
Not big one, just an AI for a chess like game called fish. and a simple rewritten version of C++ STL list and map.
* 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.''
Until then I have no habit of saving codes of different versions.
 
 
* Please state the commits and patches you already contributed to Octave.  
Not yet.


== F: Feeling fine ==
== F: Feeling fine ==
* Please describe (in short) your experience with the following tools:
* 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 and mailing lists
** IRC and mailing lists
First time to use, getting  familiar.
** Mercurial or other source code management systems
** Mercurial or other source code management systems
I used github for my course design last year.
** Mediawiki or other wiki software
** Mediawiki or other wiki software
Have never used.
** make, gcc, gdb or other development tools
 
* 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 :-)''


** make, gcc, gdb or other development tools
== O: Only out of interest ==
Not familiar with gdb, knowing well others.
* Did you ever hear about Octave before?
** If so, when and where? How far have you been involved already?
** If not, where would you expect or advise us to do advertising?
* 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 ==
Line 107: Line 88:
** a computer with your progressing work on
** a computer with your progressing work on


All the time I have access to my laptop with a sometime slow connection.
All the time I have access to my laptop. But I might not have free time.




Line 115: Line 96:
== 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.
If I know it is useful I would love to hear all of it. It can get me familiar with things I've never touched. But before hear it and think about it, I cannot know whether it is useful. Maybe the best way is to welcome all the criticism.
* How autonomous are you when developing? ''If you answer both subquestions with "Yes, definitely", we are a tad confused. ;-)''
 
 
* How autonomous are you when developing?
** Do you like to discuss changes intensively and not start coding until you know what you want to do?
** Do you like to discuss changes intensively and not start coding until you know what you want to do?
** 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?
** 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?
I do want to answer both with "Yes". When facing a tough task, I prefer thinking deep before I start, at least the possible structure of my work. But to details or ideas I'm not sure engough, I prefer writing it and testing it first as a small piece to start with.


== Y: Your task ==
== Y: Your task ==
* Did you select a task from our list of proposals and ideas?
* Did you select a task from our list of proposals and ideas?
Yes.
** 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.''
The Numerical part.
** 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.''
 
** 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.
I especially want to focus on the implement of improving logm, sqrtm, funm[http://wiki.octave.org/GSoC_Project_Ideas#Improve_logm.2C_sqrtm.2C_funm]. Maybe I can start with expm as an easy one.
 
or some of following ones within my ability to learn, as all of them have already papers and books on them.
 
Generalized eigenvalue problem, and Various sparse matrix improvements.
 
Implement solver for initial-boundary value problems for parabolic-elliptic PDEs in 1D.
 
Implement solver for 1D nonlinear boundary value problems.
 
 
* Please provide a rough estimated timeline for your work on the task.
A rough timeline:
 
April: Get the structure of my task to do.
 
May: Read the papers about the algorithms I need and get started with a few small programs to test.
 
June: Implementation of expm(or other easy functions I chose)
 
July: Complete other remaining functions.
 
August: Testing and maintaining , and end of the GSoC.
 
[[Category: Summer of Code]]
[[Category: Summer of Code]]
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)