7
edits
User:Ben zen: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
'''Don't mind the state of the page, I'm assembling it (just getting it started, I'll fill in some more details soon.)''' (I'll also remove all the markup as it suggests, once I make sure it's in a worthy state!) | '''Don't mind the state of the page, I'm assembling it (just getting it started, I'll fill in some more details soon.)''' (I'll also remove all the markup as it suggests, once I make sure it's in a worthy state!) | ||
= Public application | = GSoC 2012 Public application = | ||
== A: An introduction == | == A: An introduction == | ||
| Line 35: | Line 34: | ||
== F: Feeling fine == | == F: Feeling fine == | ||
I'm quite used to IRC/mailing lists and wiki/Mediawiki/etc. I'm not as up to speed on source code management as I've not worked on a large project before, but I think I can catch on fairly quickly. I've used make and gcc before; having worked mostly in Java I've not needed them too regularly, so I'll need to learn some more, but again, I don't think that will take much. | I'm quite used to IRC/mailing lists and wiki/Mediawiki/etc. (Apparently not Mediawiki so much, but I know my way around it for the most part.) I'm not as up to speed on source code management as I've not worked on a large project before, but I think I can catch on fairly quickly. I've used make and gcc before; having worked mostly in Java I've not needed them too regularly, so I'll need to learn some more, but again, I don't think that will take much. | ||
* 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.'' | * 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.'' | ||
| Line 48: | Line 47: | ||
** If so, when and where? How far have you been involved already? | ** If so, when and where? How far have you been involved already? | ||
** If not, where would you expect or advise us to do advertising? | ** 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? | * What was the first question concerning Octave you could not find an answer to rather quickly? | ||
I first heard about Octave waaay back in High School, when I was looking for something a little more powerful than my calculator to do a lot of matrix problems, and didn't want to buy an expensive software package. I've not been involved in the project before now, partially because I didn't feel I had anything to contribute until now. I've seen Octave mentioned in places like ##math on Freenode (was #math until recently), so I think there's some effective advertising already happening. As for quick answers, it took me a moment to determine where the application page data was actually hiding (as I wave around my ignorance of the more subtle features of the MediaWiki system) since the [[Student_Application_Template_2012|student application]] included a call to the template, nothing more. On the other hand, I learned something about MediaWiki in the thirty seconds it took me to figure out the solution! | I first heard about Octave waaay back in High School, when I was looking for something a little more powerful than my calculator to do a lot of matrix problems, and didn't want to buy an expensive software package. I've not been involved in the project before now, partially because I didn't feel I had anything to contribute until now. I've seen Octave mentioned in places like ##math on Freenode (was #math until recently), so I think there's some effective advertising already happening. As for quick answers, it took me a moment to determine where the application page data was actually hiding (as I wave around my ignorance of the more subtle features of the MediaWiki system) since the [[Student_Application_Template_2012|student application]] included a call to the template, nothing more. On the other hand, I learned something about MediaWiki in the thirty seconds it took me to figure out the solution! | ||
| Line 67: | Line 66: | ||
== Y: Your task == | == Y: Your task == | ||
* Did you select a task from our list of proposals and ideas? | |||
** 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 provide a rough estimated timeline for your work on the task. | |||
I've decided to pursue the Least-Squares Spectral Analysis ([[GSoC_Project_Ideas#Least-squares_spectral_analysis|here]] on the project ideas page) task for Octave-Forge. I don't think there's really a single part of it I can focus on; it'll mostly be a process of first reading up on the method, examining the C and R implementation, and bringing it into the fold. | I've decided to pursue the Least-Squares Spectral Analysis ([[GSoC_Project_Ideas#Least-squares_spectral_analysis|here]] on the project ideas page) task for Octave-Forge. I don't think there's really a single part of it I can focus on; it'll mostly be a process of first reading up on the method, examining the C and R implementation, and bringing it into the fold. | ||
| Line 73: | Line 76: | ||
The largest initial point is going to be comprehending the C/R code; after that, probably most of my work will be in writing a safe package — the actual implementation shouldn't be very long, but let's call it a milestone too; the rest is making sure that the code will catch any errors in what data is fed into it. | The largest initial point is going to be comprehending the C/R code; after that, probably most of my work will be in writing a safe package — the actual implementation shouldn't be very long, but let's call it a milestone too; the rest is making sure that the code will catch any errors in what data is fed into it. | ||
<!--[[Category:Summer of Code 2012]]--> | <!--[[Category:Summer of Code 2012]]--> | ||