https://wiki.octave.org/wiki/api.php?action=feedcontributions&user=Batterylow&feedformat=atomOctave - User contributions [en]2024-03-29T15:49:21ZUser contributionsMediaWiki 1.39.2https://wiki.octave.org/wiki/index.php?title=User:Batterylow&diff=11899User:Batterylow2019-04-11T17:33:24Z<p>Batterylow: </p>
<hr />
<div> Hey there, I am [https://me-ydv-5.github.io Sahil], a senior year undergraduate student pursuing Bachelors in Computer Science and Engineering at IIT Mandi, India. I was a GSoC, 2018 student at GNU Octave for the project Octave Code Sharing. See more at: [https://me-ydv-5.github.io/gsoc2018 Octave Code Sharing]</div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=Template:Student_application_template_public&diff=11898Template:Student application template public2019-04-11T17:31:34Z<p>Batterylow: Revert changes.</p>
<hr />
<div>= Public application template =<br />
This part should be answered in public on your '''[[Special:MyPage|user page]]'''. Please '''copy''' its source ('''edit''' tab) and then fill. '''DO NOT MAKE CHANGES TO THIS PAGE!''' Delete any examples and annotations (''this markup'') afterwards. Same for questions that do not apply to your situation.<br />
<br />
== A: An introduction ==<br />
* Please describe yourself in three sentences, one of them regarding your current studies.<br />
** Which languages do you speak?<br />
** What's your overall background? ''The general field you work in or are studying, e.g. computer science, physics, artificial intelligence, control theory...''<br />
*Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?<br />
**Please also describe your previous experience with the GSoC, if any. ''Includes any community-bonding, mentor experience or application, not necessarily accepted. We use this subquestion to identify which students are unfamiliar with how the program goes, providing further support. It has no negative impact on your rating!''<br />
* Why are you choosing Octave?<br />
<br />
== C: Contact ==<br />
* 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.''<br />
* 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.''<br />
* Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers? <br />
** ''Example: I usually code around 9.00 to 18.00 and could also try to start earlier (~7.00) for few days ;-)''<br />
<br />
== E: Coding experience ==<br />
This part is one of the more important ones in your application. You are allowed to be as verbose as you want, as long as you stay on topic ;-)<br />
* Please describe your experience with C++, Octave or Matlab m-scripts, OpenGL and Qt.<br />
* Please describe your experience with other programming languages.<br />
* Please describe your experience with being in a development team. ''Do you have experience working with open source or free projects?''<br />
* 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.<br />
* 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.''<br />
<br />
== F: Feeling fine ==<br />
* 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 won't necessarily need all of them while working with us.''<br />
** IRC and mailing lists <br />
** Mercurial or other source code management systems<br />
** Mediawiki or other wiki software<br />
** make, gcc, gdb or other development tools<br />
<br />
* 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 :-)''<br />
<br />
== O: Only out of interest ==<br />
* Did you ever hear about Octave before? <br />
** If so, when and where? How far have you been involved already?<br />
** If not, where would you expect or advise us to do advertising?<br />
* 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, …''<br />
<br />
== P: Prerequisites ==<br />
* Please state the operating system you work with.<br />
* Please estimate an average time per day you will be able to access<br />
** an internet connection<br />
** a computer<br />
** a computer with your progressing work on<br />
<br />
* Please describe the degree to which you can install new software on computers you have access to.<br />
<br />
== S: Self-assessment ==<br />
* Please describe how useful criticism looks from your point of view as committing student.<br />
* How autonomous are you when developing:<br />
** Do you like to discuss changes intensively and not start coding until you know what you want to do?<br />
** 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?<br />
<br />
== Y: Your task ==<br />
* Did you select a task from our list of proposals and ideas?<br />
** 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.''<br />
* 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.''<br />
[[Category: Summer of Code]]</div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=User:Batterylow&diff=11266User:Batterylow2018-12-10T18:26:24Z<p>Batterylow: Removed lines of code</p>
<hr />
<div> Hey there, I am [https://me-ydv-5.github.io Sahil], a senior (junior) year undergraduate student pursuing Bachelors in Computer Science and Engineering at IIT Mandi, India. I was a GSoC, 2018 student at GNU Octave for the project Octave Code Sharing.</div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=File:Exam.png&diff=11128File:Exam.png2018-06-18T06:00:05Z<p>Batterylow: Batterylow uploaded a new version of File:Exam.png</p>
<hr />
<div></div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=File:Exam.png&diff=11125File:Exam.png2018-06-17T18:26:11Z<p>Batterylow: Batterylow uploaded a new version of File:Exam.png</p>
<hr />
<div></div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=File:Exam.png&diff=11122File:Exam.png2018-06-17T18:17:07Z<p>Batterylow: Batterylow uploaded a new version of File:Exam.png</p>
<hr />
<div></div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=File:Exam.png&diff=11121File:Exam.png2018-06-17T18:14:27Z<p>Batterylow: </p>
<hr />
<div></div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=User:Batterylow&diff=11082User:Batterylow2018-05-01T17:46:26Z<p>Batterylow: /* A: An introduction */</p>
<hr />
<div> I am [https://me-ydv-5.github.io Sahil Yadav], a third (junior) year undergraduate student persuing Bachelors in Computer Science and Engineering at IIT Mandi, India. I've been selected as a GSoC, 2018 student at GNU Octave for the project Octave Code Sharing.<br />
<br />
The following is the list with decreasing changes of exact lines:<br />
1. '''[https://savannah.gnu.org/bugs/?52647#comment11 52647 - erase function]'''<br />
2. '''i) [https://savannah.gnu.org/bugs/?52756#comment2 52756 - XOR function in C++]''' '''ii) [https://savannah.gnu.org/bugs/?52756#comment1 52756 - mkoctfile version]'''<br />
3. '''[https://savannah.gnu.org/bugs/?52798#comment1 52798 - set property in graphics]'''<br />
4. '''[https://savannah.gnu.org/bugs/?52802#comment1 52802 - Variable Editor Size]'''<br />
5. '''[https://savannah.gnu.org/bugs/?52787#comment2 52787 - Chop function behavior]'''<br />
6. '''[https://savannah.gnu.org/bugs/?53198#comment1 53198 - nnz for diagonal matrices]'''<br />
7. '''[https://savannah.gnu.org/bugs/?52720#comment3 52720 - FLTK 'R' button]'''<br />
8. '''[https://savannah.gnu.org/bugs/?53176#comment0 53176 - Placeholder instead of variable]'''<br />
<br />
I'll keep updating this page timely. Thanks!</div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=User:Batterylow&diff=11081User:Batterylow2018-05-01T17:46:02Z<p>Batterylow: Removed GSoC proposal.</p>
<hr />
<div>== A: An introduction ==<br />
* Please describe yourself in three sentences, one of them regarding your current studies. <br />
<br />
I am [https://me-ydv-5.github.io Sahil Yadav], a third (junior) year undergraduate student persuing Bachelors in Computer Science and Engineering at IIT Mandi, India. I've been selected as a GSoC, 2018 student at GNU Octave for the project Octave Code Sharing.<br />
<br />
The following is the list with decreasing changes of exact lines:<br />
1. '''[https://savannah.gnu.org/bugs/?52647#comment11 52647 - erase function]'''<br />
2. '''i) [https://savannah.gnu.org/bugs/?52756#comment2 52756 - XOR function in C++]''' '''ii) [https://savannah.gnu.org/bugs/?52756#comment1 52756 - mkoctfile version]'''<br />
3. '''[https://savannah.gnu.org/bugs/?52798#comment1 52798 - set property in graphics]'''<br />
4. '''[https://savannah.gnu.org/bugs/?52802#comment1 52802 - Variable Editor Size]'''<br />
5. '''[https://savannah.gnu.org/bugs/?52787#comment2 52787 - Chop function behavior]'''<br />
6. '''[https://savannah.gnu.org/bugs/?53198#comment1 53198 - nnz for diagonal matrices]'''<br />
7. '''[https://savannah.gnu.org/bugs/?52720#comment3 52720 - FLTK 'R' button]'''<br />
8. '''[https://savannah.gnu.org/bugs/?53176#comment0 53176 - Placeholder instead of variable]'''<br />
<br />
I'll keep updating this page timely. Thanks!</div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=User:Batterylow&diff=11067User:Batterylow2018-04-18T15:56:19Z<p>Batterylow: Added link for timeline</p>
<hr />
<div>== A: An introduction ==<br />
* Please describe yourself in three sentences, one of them regarding your current studies. <br />
<br />
I am Sahil Yadav, a third (junior) year undergraduate student persuing Bachelors in Computer Science and Engineering at IIT Mandi, India. I am particularly interested in Computer Networks and algorithms and have worked on projects in varied areas of Computer Science such as Pattern Recognition, System Administration, Web and Database Development.<br />
<br />
** Which languages do you speak?<br />
<br />
I speak Hindi and English.<br />
<br />
** What's your overall background? <br />
<br />
I am a Computer Science student looking forward for a career in Cloud Computing or Computer Networks.<br />
<br />
* Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?<br />
<br />
Since a free code can be used by anybody and everybody, it's a great honor to see our code used by so many people. GSoC, for sure provides a way to plunge oneself into the world of Free and Open Source Software by offering us the prestige and fame that comes with it. Moreover, as stated on the website itself, it surely does increase the [https://google.github.io/gsocguides/student/why-should-i-apply.html weight] of one's resume.<br />
<br />
** Please also describe your previous experience with the GSoC, if any. <br />
<br />
I haven't tried GSoC before.<br />
<br />
* Why are you choosing Octave?<br />
<br />
I came to know about Octave while doing an online machine learning course. After that, it has also helped me with [https://github.com/me-ydv-5/patternAssignment my own] assignments in Pattern Recognition. Hence, I had used it before trying my luck in GSoC and so felt that it would be great if I can be a part of the octave community.<br />
<br />
== C: Contact ==<br />
* Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave. <br />
<br />
I am always available as '''batterylow''' on freenode IRC and as '''Sahil''' on mailing lists. <br />
<br />
* Which time zone do you live in? Will that change over GSoC duration? <br />
<br />
I live in UTC+05:30. No, it won't be changing over the GSoC duration.<br />
<br />
* Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers? <br />
<br />
I would be most available between 13:30 and 19:30 on weekdays and between 03:30 and 08:30 on weekends. <br />
<br />
== E: Coding experience ==<br />
<br />
* Please describe your experience with C++, Octave or Matlab m-scripts, OpenGL and Qt.<br />
<br />
I started programming in my freshmen year of college. I am most familiar with C++ with quite a few self implemented Algorithms and Data Structures codes. I solve puzzle problems in C++. I also have a good hand in Octave/Matlab m-scripts and have an introductory understanding of Qt C++ classes, procedures etc. <br />
<br />
* Please describe your experience with other programming languages.<br />
<br />
I also program in C, Python. As for the web development, I can efficiently build stuff using HTML, CSS, JavaScript and LAMP stack. I have familiarity with microcontrollers as well.<br />
<br />
* Please describe your experience with being in a development team.<br />
<br />
Though I haven't been in an free software development prior to this, I have assisted and led team work in college projects. <br />
<br />
* 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.<br />
I made a web portal for a [https://github.com/me-ydv-5/school-db school management system]. Structured and coded the back end in MySQL and used server side scripting in PHP. I also developed the front end using HTML, CSS , JavaScript and [https://getmdl.io/ Google MDL] components.<br />
<br />
* Please state the commits and patches you already contributed to Octave.<br />
<br />
I have worked on a variety of bugs in Octave. The following is the list with decreasing changes of exact lines:<br />
1. '''[https://savannah.gnu.org/bugs/?52647#comment11 52647 - erase function]'''<br />
2. '''i) [https://savannah.gnu.org/bugs/?52756#comment2 52756 - XOR function in C++]''' '''ii) [https://savannah.gnu.org/bugs/?52756#comment1 52756 - mkoctfile version]'''<br />
3. '''[https://savannah.gnu.org/bugs/?52798#comment1 52798 - set property in graphics]'''<br />
4. '''[https://savannah.gnu.org/bugs/?52802#comment1 52802 - Variable Editor Size]'''<br />
5. '''[https://savannah.gnu.org/bugs/?52787#comment2 52787 - Chop function behavior]'''<br />
6. '''[https://savannah.gnu.org/bugs/?53198#comment1 53198 - nnz for diagonal matrices]'''<br />
7. '''[https://savannah.gnu.org/bugs/?52720#comment3 52720 - FLTK 'R' button]'''<br />
8. '''[https://savannah.gnu.org/bugs/?53176#comment0 53176 - Placeholder instead of variable]'''<br />
<br />
== F: Feeling fine ==<br />
* Please describe (in short) your experience with the following tools: <br />
<br />
** IRC and mailing lists <br />
<br />
I am always available on IRC as '''batterylow''' and fine with interactions on it. I am comfortable with mailing lists as well but tend to use IRC channel more for communication and random musings. <br />
<br />
** Mercurial or other source code management systems<br />
<br />
I am fully comfortable with Mercurial (and TortoiseHg) as well as Git. <br />
<br />
** Mediawiki or other wiki software<br />
<br />
I am comfortable with MediaWiki. I randomly [https://wiki.octave.org/Special:Contributions/Batterylow refine] [https://wiki.octave.org/wiki/index.php?title=Sci_cosim&type=revision&diff=10629&oldid=10382 stuff] on Octave's wiki.<br />
<br />
** make, gcc, gdb or other development tools<br />
<br />
I am quite comfortable with make (including VPATH builds, etc.), gcc and gdb.<br />
<br />
* What will make you actively stay in our community after this GSoC is over? <br />
<br />
Quite a handful of bugs / new implementations which can help me earn ''@octave/developer/batterylow'' cloak on IRC would be sufficient. If I don't get selected in GSoC, I would still be active on IRC channel to help any others with general problems in installation and usage of the software.<br />
<br />
== O: Only out of interest ==<br />
* Did you ever hear about Octave before? <br />
<br />
Yes, I did.<br />
<br />
** If so, when and where? How far have you been involved already?<br />
<br />
I used it in an online machine learning course as well as my own Pattern Recognition assignments.<br />
<br />
** If not, where would you expect or advise us to do advertising?<br />
<br />
Since, piracy is always discouraged and there are a number of free software advocates all around, I don't think octave is lagging behind in any way. Moreover, generally the professors at universities discourage piracy, so yeah, the students do get to use it in their courses.<br />
<br />
* What was the first question concerning Octave you could not find an answer to rather quickly? <br />
<br />
I don't remember something as such.<br />
<br />
== P: Prerequisites ==<br />
* Please state the operating system you work with.<br />
<br />
I work mostly on Linux (Ubuntu 16.04) and sometimes Windows.<br />
<br />
* Please estimate an average time per day you will be able to access<br />
** an internet connection<br />
24 hours a day.<br />
** a computer<br />
24 hours a day.<br />
** a computer with your progressing work on<br />
24 hours a day.<br />
* Please describe the degree to which you can install new software on computers you have access to.<br />
I have admin privilages on my computers.<br />
<br />
== S: Self-assessment ==<br />
* Please describe how useful criticism looks from your point of view as committing student.<br />
I take criticisms positively and try to look at the problem from the other person's point of view ( I've been reading Dale Carnegie's book these days). I actively hear suggestions from subordinates as well. <br />
<br />
* How autonomous are you when developing:<br />
I am able to take independent decisions when building something though sometimes I do need valuable advice/suggestions. I give utmost important to the one who suggests something to me, because he/she must have put some time on my work and he/she would also not feel insignificant.<br />
<br />
** Do you like to discuss changes intensively and not start coding until you know what you want to do?<br />
<br />
Yes, it saves a lot of time and useless directions if I discuss the things before-hand and then try to code it.<br />
<br />
** 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?<br />
<br />
Yes, I am in complete agreement with the notion of proof of concept for large scale projects. Though small projects (200-300 lines of code) are generally preferred to be on-the-go.<br />
<br />
== Y: Your task ==<br />
* Did you select a task from our list of proposals and ideas?<br />
<br />
Yes, I did.<br />
<br />
** 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. <br />
<br />
I chose [https://wiki.octave.org/Summer_of_Code_Project_Ideas#Octave_code_sharing Octave Code Sharing] as my GSoC project.<br />
<br />
* Please provide a rough estimated timeline for your work on the task.<br />
<br />
My timeline for the project is as follows: [https://docs.google.com/document/d/1InJhgZQkW61a42qPwiIWjYz7xPo4Gk9fKhsdrd3G_7M/edit?usp=sharing Click Here] for Google Doc link.<br />
<br />
<br />
<br />
[[Category: Summer of Code]]</div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=User:Batterylow&diff=10860User:Batterylow2018-03-21T19:36:12Z<p>Batterylow: First addition to the page, GSoC application.</p>
<hr />
<div>== A: An introduction ==<br />
* Please describe yourself in three sentences, one of them regarding your current studies. <br />
<br />
I am Sahil Yadav, a third (junior) year undergraduate student persuing Bachelors in Computer Science and Engineering at IIT Mandi, India. I am particularly interested in Computer Networks and algorithms and have worked on projects in varied areas of Computer Science such as Pattern Recognition, System Administration, Web and Database Development.<br />
<br />
** Which languages do you speak?<br />
<br />
I speak Hindi and English.<br />
<br />
** What's your overall background? <br />
<br />
I am a Computer Science student looking forward for a career in Cloud Computing or Computer Networks.<br />
<br />
* Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?<br />
<br />
Since a free code can be used by anybody and everybody, it's a great honor to see our code used by so many people. GSoC, for sure provides a way to plunge oneself into the world of Free and Open Source Software by offering us the prestige and fame that comes with it. Moreover, as stated on the website itself, it surely does increase the [https://google.github.io/gsocguides/student/why-should-i-apply.html weight] of one's resume.<br />
<br />
** Please also describe your previous experience with the GSoC, if any. <br />
<br />
I haven't tried GSoC before.<br />
<br />
* Why are you choosing Octave?<br />
<br />
I came to know about Octave while doing an online machine learning course. After that, it has also helped me with [https://github.com/me-ydv-5/patternAssignment my own] assignments in Pattern Recognition. Hence, I had used it before trying my luck in GSoC and so felt that it would be great if I can be a part of the octave community.<br />
<br />
== C: Contact ==<br />
* Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave. <br />
<br />
I am always available as '''batterylow''' on freenode IRC and as '''Sahil''' on mailing lists. <br />
<br />
* Which time zone do you live in? Will that change over GSoC duration? <br />
<br />
I live in UTC+05:30. No, it won't be changing over the GSoC duration.<br />
<br />
* Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers? <br />
<br />
I would be most available between 13:30 and 19:30 on weekdays and between 03:30 and 08:30 on weekends. <br />
<br />
== E: Coding experience ==<br />
<br />
* Please describe your experience with C++, Octave or Matlab m-scripts, OpenGL and Qt.<br />
<br />
I started programming in my freshmen year of college. I am most familiar with C++ with quite a few self implemented Algorithms and Data Structures codes. I solve puzzle problems in C++. I also have a good hand in Octave/Matlab m-scripts and have an introductory understanding of Qt C++ classes, procedures etc. <br />
<br />
* Please describe your experience with other programming languages.<br />
<br />
I also program in C, Python. As for the web development, I can efficiently build stuff using HTML, CSS, JavaScript and LAMP stack. I have familiarity with microcontrollers as well.<br />
<br />
* Please describe your experience with being in a development team.<br />
<br />
Though I haven't been in an free software development prior to this, I have assisted and led team work in college projects. <br />
<br />
* 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.<br />
I made a web portal for a [https://github.com/me-ydv-5/school-db school management system]. Structured and coded the back end in MySQL and used server side scripting in PHP. I also developed the front end using HTML, CSS , JavaScript and [https://getmdl.io/ Google MDL] components.<br />
<br />
* Please state the commits and patches you already contributed to Octave.<br />
<br />
I have worked on a variety of bugs in Octave. The following is the list with decreasing changes of exact lines:<br />
1. '''[https://savannah.gnu.org/bugs/?52647#comment11 52647 - erase function]'''<br />
2. '''i) [https://savannah.gnu.org/bugs/?52756#comment2 52756 - XOR function in C++]''' '''ii) [https://savannah.gnu.org/bugs/?52756#comment1 52756 - mkoctfile version]'''<br />
3. '''[https://savannah.gnu.org/bugs/?52798#comment1 52798 - set property in graphics]'''<br />
4. '''[https://savannah.gnu.org/bugs/?52802#comment1 52802 - Variable Editor Size]'''<br />
5. '''[https://savannah.gnu.org/bugs/?52787#comment2 52787 - Chop function behavior]'''<br />
6. '''[https://savannah.gnu.org/bugs/?53198#comment1 53198 - nnz for diagonal matrices]'''<br />
7. '''[https://savannah.gnu.org/bugs/?52720#comment3 52720 - FLTK 'R' button]'''<br />
8. '''[https://savannah.gnu.org/bugs/?53176#comment0 53176 - Placeholder instead of variable]'''<br />
<br />
== F: Feeling fine ==<br />
* Please describe (in short) your experience with the following tools: <br />
<br />
** IRC and mailing lists <br />
<br />
I am always available on IRC as '''batterylow''' and fine with interactions on it. I am comfortable with mailing lists as well but tend to use IRC channel more for communication and random musings. <br />
<br />
** Mercurial or other source code management systems<br />
<br />
I am fully comfortable with Mercurial (and TortoiseHg) as well as Git. <br />
<br />
** Mediawiki or other wiki software<br />
<br />
I am comfortable with MediaWiki. I randomly [https://wiki.octave.org/Special:Contributions/Batterylow refine] [https://wiki.octave.org/wiki/index.php?title=Sci_cosim&type=revision&diff=10629&oldid=10382 stuff] on Octave's wiki.<br />
<br />
** make, gcc, gdb or other development tools<br />
<br />
I am quite comfortable with make (including VPATH builds, etc.), gcc and gdb.<br />
<br />
* What will make you actively stay in our community after this GSoC is over? <br />
<br />
Quite a handful of bugs / new implementations which can help me earn ''@octave/developer/batterylow'' cloak on IRC would be sufficient. If I don't get selected in GSoC, I would still be active on IRC channel to help any others with general problems in installation and usage of the software.<br />
<br />
== O: Only out of interest ==<br />
* Did you ever hear about Octave before? <br />
<br />
Yes, I did.<br />
<br />
** If so, when and where? How far have you been involved already?<br />
<br />
I used it in an online machine learning course as well as my own Pattern Recognition assignments.<br />
<br />
** If not, where would you expect or advise us to do advertising?<br />
<br />
Since, piracy is always discouraged and there are a number of free software advocates all around, I don't think octave is lagging behind in any way. Moreover, generally the professors at universities discourage piracy, so yeah, the students do get to use it in their courses.<br />
<br />
* What was the first question concerning Octave you could not find an answer to rather quickly? <br />
<br />
I don't remember something as such.<br />
<br />
== P: Prerequisites ==<br />
* Please state the operating system you work with.<br />
<br />
I work mostly on Linux (Ubuntu 16.04) and sometimes Windows.<br />
<br />
* Please estimate an average time per day you will be able to access<br />
** an internet connection<br />
24 hours a day.<br />
** a computer<br />
24 hours a day.<br />
** a computer with your progressing work on<br />
24 hours a day.<br />
* Please describe the degree to which you can install new software on computers you have access to.<br />
I have admin privilages on my computers.<br />
<br />
== S: Self-assessment ==<br />
* Please describe how useful criticism looks from your point of view as committing student.<br />
I take criticisms positively and try to look at the problem from the other person's point of view ( I've been reading Dale Carnegie's book these days). I actively hear suggestions from subordinates as well. <br />
<br />
* How autonomous are you when developing:<br />
I am able to take independent decisions when building something though sometimes I do need valuable advice/suggestions. I give utmost important to the one who suggests something to me, because he/she must have put some time on my work and he/she would also not feel insignificant.<br />
<br />
** Do you like to discuss changes intensively and not start coding until you know what you want to do?<br />
<br />
Yes, it saves a lot of time and useless directions if I discuss the things before-hand and then try to code it.<br />
<br />
** 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?<br />
<br />
Yes, I am in complete agreement with the notion of proof of concept for large scale projects. Though small projects (200-300 lines of code) are generally preferred to be on-the-go.<br />
<br />
== Y: Your task ==<br />
* Did you select a task from our list of proposals and ideas?<br />
<br />
Yes, I did.<br />
<br />
** 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. <br />
<br />
I chose [https://wiki.octave.org/Summer_of_Code_Project_Ideas#GUI_Variable_Editor_and_Property_Inspector GUI Property Inspector] as my GSoC project.<br />
<br />
* Please provide a rough estimated timeline for your work on the task.<br />
<br />
1.) Setting up the basic window and its invocation through the interpreter.<br />
2.) Implementing the boolean valued properties and multi valued properties.<br />
3.) Implementing the callbacks, `userdata` and tooltips for documentation, other tests documentation, etc.<br />
A concrete timeline is in the private Google Doc proposal. I would be posting the weekly updates on my progress [http://batterylow.me here].<br />
<br />
<br />
<br />
[[Category: Summer of Code]]</div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=Template:Student_application_template_private&diff=10636Template:Student application template private2018-01-31T15:25:45Z<p>Batterylow: Reverted the changes and added caution about not editing the page</p>
<hr />
<div>= Private application template =<br />
This part is only meant to be included in your application at Google Melange. Nobody needs to see your contact details in public! <br />
You only need to '''copy''' the template from this page and '''NOT CHANGE THE PAGE ITSELF'''. Do '''NOT''' change this page.<br />
<br />
== A: An introduction ==<br />
* Please give an idea of the timeframe you plan to be<br />
** working on your project<br />
** able to join our IRC channel<br />
* Do you have other commitments for the summer period? Do you plan to take any vacations?<br />
** If yes, when and for how long?<br />
* Please describe your written English.<br />
<br />
== C: Contact ==<br />
* Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave.<br />
* Please state the email address you check most regularly.<br />
* Which time zone ''(UTC+-x)'' and country do you live in? ''Will that change over SoC duration (DST changes perhaps)?''<br />
* Are there instant messenger networks you regularly visit? Would you like your mentor to contact you there?<br />
* Please decide if you would like us to have further non-public contact information of you and share them here. ''This is meant as absolutely last resort (total absence from internet or computer havoc for instance). It might, for instance, be a phone number with international code. It will only be shared with the mentor in case of absolute emergency and '''never''' be published!''<br />
<br />
== S: Self-assessment ==<br />
* Do you give constructive advice? Do you receive advice ? <br />
* Are you good at sorting useful criticisms from useless ones?<br />
<br />
== Y: Your task ==<br />
* Why did you choose your particular task? What do you expect to gain from working on it?<br />
<br />
[[Category:Applicants]]</div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=Summer_of_Code_-_Getting_Started&diff=10620Summer of Code - Getting Started2018-01-13T13:26:05Z<p>Batterylow: extra whitespace was not letting the hyperlink refer to the project mentioned</p>
<hr />
<div>The following is distilled from the [[Projects]] page for the benefit of potential [https://summerofcode.withgoogle.com Google] and [http://sophia.estec.esa.int/socis ESA] Summer of Code (SoC) students. Although students are welcome to attempt any of the projects in that page or any of their own choosing, here we offer some suggestions on what good student projects might be.<br />
<br />
You can also take a look at last years [[Summer of Code]] projects for inspiration.<br />
<br />
= Steps Toward a Successful Application =<br />
<br />
== Help Us Get To Know You == <br />
*: If you aren't communicating with us before the application is due, your application will not be accepted.<br />
*:* '''Join the [https://lists.gnu.org/mailman/listinfo/octave-maintainers maintainers mailing list]''' or read the archives and see what topics we discuss and how the developers interact with each other.<br />
*:* '''Hang out in our [https://webchat.freenode.net/?channels=#octave IRC channel]'''. Ask questions, answer questions from users, show us that you are motivated, and well-prepared. There will be more applicants than we can effectively mentor, so do ask for feedback on your public application to increase the strength of your proposal!<br />
* '''Do not wait for us to tell you what to do'''<br />
*: You should be doing something that interests you, and should not need us to tell you what to do. Similarly, you shouldn't ask us what to do either.<br />
*:* When you email the list and mentors, do not write it to say on what project you're interested. Be specific about your questions and clear on the email subject. For example, do not write an email with the subject "GSoC student interested in the ND images projects". Such email is likely be ignored. Instead, show you are already working on the topic, and email "Problem implementing morphological operators with bitpacked ND images".<br />
*:* It is good to ask advice on how to solve something you can't but you must show some work done. Remember, we are mentors and not your boss. Read [http://www.catb.org/esr/faqs/smart-questions.html How to ask questions the smart way]:<br />
*:*: <blockquote cite="http://www.catb.org/esr/faqs/smart-questions.html">''Prepare your question. Think it through. Hasty-sounding questions get hasty answers, or none at all. The more you do to demonstrate that having put thought and effort into solving your problem before seeking help, the more likely you are to actually get help.''</blockquote><br />
*:* It can be difficult at the beginning to think on something to do. This is nature of free and open source software development. You will need to break the mental barrier that prevents you from thinking on what can be done. Once you do that, you will have no lack of ideas for what to do next.<br />
*:* Use Octave. Eventually you will come accross somethings that does not work the way you like. Fix that. Or you will come accross a missing function. Implement it. It may be a difficult problem (they usually are) but while solving that problem you may find other missing functions (). Implemenent and contribute those to Octave.<br />
*:* Take a look at the [[Short projects]] for something that may be simple to start with.<br />
== Find Something That Interests You == <br />
*: It's '''critical''' that you '''find a project that excites you'''. You'll be spending most of the summer working on it (we expect you to treat the SoC as a full-time job).<br />
*: Don't just tell us how interested you are, show us that you're willing and able to '''contribute''' to Octave. You can do that by [https://savannah.gnu.org/bugs/?group=octave fixing a few bugs] or [http://savannah.gnu.org/patch/?group=octave submitting patches] well before the deadline, in addition to regularly interacting with Octave maintainers and users on the mailing list and IRC. Our experience shows us that successful SoC students demonstrate their interest early and often.<br />
== Prepare Your Proposal With Us ==<br />
*: By working with us to prepare your proposal, you'll be getting to know us and showing us how you approach problems. The best place for this is your Wiki user page and the [https://webchat.freenode.net/?channels=#octave IRC channel].<br />
== Complete Your Application ==<br />
*: Fill out our '''''public''''' application template.<br />
*:* This is best done by '''[[Special:CreateAccount|creating an account at this wiki]]''', and copying the '''[[Template:Student_application_template_public|template]]''' from its page.<br />
*:* You really only need to copy and answer the '''''public''''' part there, there is no need to showcase everything else to everybody reading your user page!<br />
*: Fill out our '''''private''''' application template.<br />
*:* This is best done by copying the '''[[Template:Student_application_template_private|template]]''' from its page and '''adding the required information to your application at Google (melange)''' or at '''ESA'''.<br><br />
*:* Only the organization admin and the possible mentors will see this data. You can still edit it after submitting until the deadline!<br />
<br />
== Things You'll be Expected to Know or Quickly Learn On Your Own ==<br />
<br />
Octave is mostly written in C++ and its own scripting language that is mostly compatible with Matlab. There are bits and pieces of Fortran, Perl, C, awk, and Unix shell scripts here and there. In addition to being familiar with C++ and Octave's scripting language, successful applicants will be familiar with or able to quickly learn about Octave's infrastructure. You can't spend the whole summer learning how to build Octave or prepare a changeset and still successfully complete your project.<br />
<br />
* '''The Build System'''<br />
*: [http://en.wikipedia.org/wiki/GNU_build_system The GNU build system] is used to build Octave.<br />
*: While you generally don't need to understand too much unless you actually want to change how Octave is built, you should be able to understand enough to get a general idea of how to build Octave.<br />
*: If you've ever done a {{Codeline|configure && make && make install}} series of commands, you have already used the GNU build system.<br />
*: '''You must demonstrate that you are able to build the development version of Octave from sources before the application deadline.''' You will be able to find instructions how to it on this wiki, and the manual. Linux is arguably the easiest system to work on.<br />
*:* [[Building]]<br />
*:* [https://www.gnu.org/software/octave/doc/interpreter/Installation.html Octave Manual on Installing Octave]<br />
* '''The Version Control System'''<br />
*: We use [http://mercurial.selenic.com/ Mercurial] (abbreviated hg).<br />
*: Mercurial is the [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control system] (DVCS) we use for managing our source code. You should have some basic understanding of how a DVCS works, but hg is pretty easy to pick up, especially if you already know a VCS like git or svn.<br />
* '''The Procedure for Contributing Changesets'''<br />
*: You will be expected to follow the same procedures as other contributors and core developers.<br />
*: You will be helping current and future Octave developers by using our standard style for changes, commit messages, and so on. You should also read the same [https://www.gnu.org/software/octave/doc/interpreter/Contributing-Guidelines.html contribution] [http://hg.savannah.gnu.org/hgweb/octave/file/tip/etc/HACKING guidelines] we have for everyone.<br />
*: [[Hg_instructions_for_mentors#Mercurial_Tips_for_SoC_students | This page]] describes the procedures students are expected to use to publicly display their progress in a public mercurial repo during their work.<br />
* '''The Maintainers Mailing List'''<br />
*: We primarily use [https://lists.gnu.org/mailman/listinfo/octave-maintainers mailing lists] for communication among developers.<br />
*: The mailing list is used most often for discussions about non-trivial changes to Octave, or for setting the direction of development.<br />
*: You should follow basic mailing list etiquette. For us, this mostly means "do not [https://en.wikipedia.org/wiki/Posting_style#Top-posting top post]".<br />
* '''The IRC Channel'''<br />
*: We also have [http://webchat.freenode.net?channels=octave the #octave IRC channel in Freenode].<br />
*: You should be familiar with the IRC channel. It's very helpful for new contributors (you) to get immediate feedback on ideas and code.<br />
*: Unless your primary mentor has a strong preference for some other method of communication, the IRC channel will likely be your primary means of communicating with your mentor and Octave developers.<br />
* '''The Octave Forge Project'''<br />
*: [http://octave.sf.net Octave-Forge] is a collection of contributed packages that enhance the capabilities of core Octave. They are somewhat analogous to Matlab's toolboxes.<br />
* '''Related Skills'''<br />
*: In addition, you probably should know '''some''' mathematics, engineering, experimental science, or something of the sort.<br />
*: If so, you probably have already been exposed to the kinds of problems that Octave is used for.<br />
<br />
== Criteria by which applications are judged ==<br />
<br />
These might vary somewhat depending on the mentors and coordinators for a particular Summer of Code, but typically the main factors considered would be:<br />
<br />
* '''Applicant has demonstrated an ability to make substantial modifications to Octave'''<br />
*: The most important thing is that you've contributed some interesting code samples to judge you by. It's OK during the application period to ask for help on how to format these code samples, which normally are Mercurial patches.<br />
<br />
* '''Applicant shows understanding of topic'''<br />
*: Your application should make it clear that you're reasonably well versed in the subject area and won't need all summer just to read up on it.<br />
<br />
* '''Applicant shows understanding of and interest in Octave development'''<br />
*: The best evidence for this is previous contributions and interactions.<br />
<br />
* '''Well thought out, adequately detailed, realistic project plan'''<br />
*: "I'm good at this, so trust me" isn't enough. You should describe which algorithms you'll use and how you'll integrate with existing Octave code. You should also prepare a full timeline and goals for the midterm and final evaluations.<br />
<br />
= Suggested projects =<br />
<br />
The following projects are broadly grouped by category and probable skills required to tackle each. Remember to check [[Projects]] for more ideas if none of these suit you, and your own ideas are always welcome.<br />
<br />
{{Note|these are suggested projects but you are welcome to propose your own projects provided you find an Octave mentor}}<br />
<br />
== Summary table ==<br />
<br />
{| class="wikitable sortable" style="text-align: center; width:99%"<br />
|-<br />
!Title<br />
!Mentor<br />
!co-Mentors<br />
!Class<br />
!New?<br />
!Difficulty<br />
!Last active<br />
|-<br />
! <br />!! !! !! !! !! !!<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Make_specfuns_special_again | Make specfuns special again]] || Marco Caliari || Colin Macdonald || Numerical || No || Medium || [https://gsocspecfun.blogspot.de/ GSoC 2017]<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#ode15s_:_Matlab_Compatible_DAE_solver | ode15{i,s} : Matlab Compatible DAE solvers]] || Carlo de Falco || Francesco Faccio, Marco Caliari, Jacopo Corno, Sebastian Schöps || Numerical || No || Medium || GSoC 2016<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Improve_logm.2C_sqrtm.2C_funm | Improve logm, sqrtm, funm]] || Jordi Gutiérrez Hermoso || Marco Caliari, Mudit Sharma || Numerical || [https://github.com/RickOne16/matrix No] || Hard || Independent devs 2016<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Improve_iterative_methods_for_sparse_linear_systems | Improve iterative methods for sparse linear systems]] || Marco Caliari || Carlo de Falco || Numerical || No || Hard || SOCIS 2016<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Neural Networks package: Convolutional Neural Networks | Neural Networks package: Convolutional Neural Networks]] || [[User:Francesco Faccio|Francesco Faccio]] || Ankit || Octave Forge || No || Hard || [https://gsocnnet.blogspot.de/ GSoC 2017]<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#EPA_hydrology_software_suite | EPA hydrology software suite]] || [[User:KaKiLa| KaKiLa]] || ? || Octave Forge || Yes || Medium || Never<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#FullSWOF overland flow simulator | FullSWOF overland flow simulator]] || [[User:KaKiLa| KaKiLa]] || ? || Octave Forge || Yes || Medium || Never<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#TISEAN_package | TISEAN: Nonlinear Time Series Analysis]] || [[User:KaKiLa|KaKiLa]] || ? || Octave Forge || [[TISEAN_package | No]] || Medium || GSoC 2015<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Octave_Package_management | Octave Package management]] || Sebastian Schöps || [[User:KaKiLa|KaKiLa]], Carnë Draug, Carlo de Falco || Infrastructure || Yes || Medium || Never<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Symbolic_package | Symbolic package]] || Colin B. Macdonald || Mike Miller, Abhinav Tripathi || Octave Forge || [https://github.com/cbm755/octsympy Octsympy] || Medium || GSoC 2016<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Interval_package | Interval package]] || [[User:oheim|Oliver Heimlich]] || [[User:Siko1056|Kai T. Ohlhus]] || Octave Forge, Numerical || No || Medium || [https://gsocinterval.blogspot.de/ GSoC 2017]<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Using_Python_within_Octave | Pytave project]] || Mike Miller || Colin B. Macdonald, Abhinav Tripathi || Infrastructure || No || Medium || some in GSoC 2016<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Jupyter_Integration | Jupyter integration]] || Mike Miller || Colin B. Macdonald || Infrastructure || Yes || Medium || Never<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Chebfun_in_Octave | Chebfun in Octave]] || Colin B. Macdonald || [[User:KaKiLa|KaKiLa]], needs core-Octave mentor/comentor || Infrastructure, Numerical || Yes || Hard || Never<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#Octave_code_sharing | Octave code sharing]] || [[User:Siko1056|Kai T. Ohlhus]] || ? || Infrastructure || Yes || Medium || Never<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#GUI Variable Editor and Property Inspector | GUI Property Inspector]] || ? || || GUI || Yes || Medium || Never<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#SPQR Interface | Write API to SPQR Library]] || ? || || Infrastructure || Yes || Medium || Never<br />
|-<br />
| [[Summer_of_Code_Project_Ideas#PolarAxes and Plotting Improvements | PolarAxes and Plotting Improvements ]] || ? || Rik || Graphics || Yes || Medium || Never<br />
|}<br />
<br />
== Numerical ==<br />
<br />
These projects involve implementing certain mathematical functions, primarily in core Octave.<br />
<br />
=== Make specfuns special again ===<br />
<br />
Traditionally, problem solving environments like Octave provide simple interfaces to numerical linear algebra, special function evaluation, root finding, and other tools. Special functions (such as Bessel functions, exponential integrals, LambertW, etc) are expected by users to "just work". But many of Octave's special functions could be improved to improve their numerical accuracy. Generally a user might expect these to be accurate to full 15 digits. Software testing is important to Octave; this project would improve the tests of many special functions, in particular by comparing the output with slow-but-accurate symbolic computations.<br />
<br />
State: some bugs include [https://savannah.gnu.org/bugs/?48307 #48307] (sinc), [https://savannah.gnu.org/bugs/?47738 #47738] (expint), [https://savannah.gnu.org/bugs/?47800 #47800] (gammainc), [https://savannah.gnu.org/bugs/?48036 #48036] (gammaincinv) [https://savannah.gnu.org/bugs/index.php?48316 #48316] (besselj) ''TODO: add others?'' The unmaintained specfun pkg had some poor implementations (e.g., divergence for large x, see [https://github.com/cbm755/octsympy/issues/416].). See also the Symbolic functions in `@double`: these probably should have native double implementations.<br />
<br />
* '''Required skills'''<br />
: Octave m-file programming, some familiarity with Approximation Theory (a branch of mathematics).<br />
* '''Difficulty'''<br />
: Medium (mathematics needed, but on the other hand, perhaps little or no C++).<br />
* '''Potential mentors'''<br />
: Marco Caliari, Colin Macdonald, others?<br />
<br />
How to get started: pick a special function, see if it has tests: contribute a patch that adds more tests, e.g., comparing its values to symbolic computations or other highly accurate solutions<br />
<br />
=== ode15{i,s} : Matlab Compatible DAE solvers ===<br />
<br />
An initial implementation of a Matlab compatible ode15{i,s} solver,<br />
based on [http://computation.llnl.gov/projects/sundials SUNDIALS], <br />
was done by Francesco Faccio during<br />
GSOC 2016.<br />
The blog describing the work is [http://gsoc2016ode15s.blogspot.it/ here].<br />
The resulting code has been pushed into the main Octave repository in the development branch and<br />
consists mainly of the following three files<br />
[http://hg.savannah.gnu.org/hgweb/octave/file/4890b1c4a6bd/libinterp/dldfcn/__ode15__.cc __ode15__.cc],<br />
[http://hg.savannah.gnu.org/hgweb/octave/file/4890b1c4a6bd/scripts/ode/ode15i.m ode15i.m] and<br />
[http://hg.savannah.gnu.org/hgweb/octave/file/4890b1c4a6bd/scripts/ode/ode15s.m ode15s.m].<br />
The list of outsanding tracker tickets concerning this implementation can be found <br />
[https://savannah.gnu.org/search/?Search=Search&words=ode15&type_of_search=bugs&only_group_id=1925&exact=1&max_rows=25#options here]<br />
<br />
Possible useful improvements that could be done in a new project include:<br />
<br />
* Implement a better funtion for selecting consistent initial conditions compatible with Matlab's decic.m. The algorithm to use is described [http://faculty.smu.edu/shampine/cic.pdf here]<br />
<br />
* make ode15{i,s} with datatypes other than double<br />
<br />
* improve interpolation at intermediate time steps.<br />
<br />
* general code profiling and optimization <br />
<br />
Other tasks, not strictly connected to ode15{i,s} but closely related that could be added <br />
to a possible project plan would be improving documentation and tests in odepkg and removing <br />
overlaps with the documentation in core Octave.<br />
<br />
<br />
* '''Required skills'''<br />
: C++; C; familiarity with numerical methods for DAEs; Basic knowledge of makefiles and/or autotools.<br />
* '''Difficulty'''<br />
: Medium.<br />
* '''Potential mentors'''<br />
: Francesco Faccio, Carlo de Falco, Marco Caliari, Jacopo Corno, Sebastian Schöps<br />
<br />
=== Improve logm, sqrtm, funm ===<br />
<br />
The goal here is to implement some missing Matlab functions related to matrix functions like the [http://en.wikipedia.org/wiki/Matrix_exponential matrix exponential]. There is [http://octave.1599824.n4.nabble.com/matrix-functions-td3137935.html a general discussion] of the problem. A good starting point for available algorithms and open-source implementations is Higham and Deadman's [http://eprints.ma.man.ac.uk/2102/01/covered/MIMS_ep2014_8.pdf "A Catalogue of Software for Matrix Functions"].<br />
<br />
* '''Required skills'''<br />
: Read and Write both C++ and Octave code, find and read research papers, research experience in numerical analysis, familiarity with analysis of algorithms.<br />
* '''Difficulty'''<br />
: Difficult.<br />
* '''Potential mentors'''<br />
: Jordi Gutiérrez Hermoso<br />
<br />
=== Improve iterative methods for sparse linear systems ===<br />
<br />
GNU Octave currently has the following Krylov subspace methods for sparse linear systems: pcg (spd matrices) and pcr (Hermitian matrices), bicg,<br />
bicgstab, cgs, gmres, and qmr (general matrices). The description of some of them (pcr, qmr) and their error messages are not aligned. Moreover, they have similar blocks of code (input check for instance) which can be written once and for all in common functions. The first step in this project could be a revision and a synchronization of the codes, starting from the project [http://planet.octave.org/#tag:blogger.com,1999:blog-1297699247151766814.post-8054019978706480250 SOCIS2016], whose latest patch, still to be included, is [https://savannah.gnu.org/patch/?9108 here].<br />
<br />
In Matlab, some additional methods are available: minres and symmlq (symmetric matrices), bicgstabl (general matrices), lsqr (least<br />
squares). The second step in this project could be the implementation of some of these missing functions.<br />
<br />
The reference book is available [www-users.cs.umn.edu/~saad/IterMethBook_2ndEd.pdf here]<br />
<br />
* '''Required skills'''<br />
: numerical linear algebra, m-file programming.<br />
* '''Difficulty'''<br />
: Maybe hard the mathematical part, medium the programming part.<br />
* '''Mentor'''<br />
:<br />
<br />
=== Chebfun in Octave ===<br />
<br />
[https://chebfun.org Chebfun] is a mathematics and software project for "numerical computing with functions". Basically it approximates functions to machine precision accuracy (10<sup>-15</sup>) using piecewise Chebyshev polynomial interpolants. Operations on those functions (arithmetic, derivatives, root-finding, etc) are then overloaded and return new interpolating polynomials, which are themselves proxies for the actual solution.<br />
<br />
Chebfun makes extensive use of classdef classes, and is one of the largest Free Software projects to do so. Unfortunately it currently only works in Matlab. This project seeks to (1) improve Octave's classdef support and (2) tweak Chebfun to work under Octave, for example, removing undocumented classdef features. The final goal is to have at least basic Chebfun features working on Octave. An additional goal would be making "pkg install chebfun.zip" work in Octave.<br />
<br />
This project is important for both technical reasons (to improve Octave's classdef support) and ethical reasons (to allow Chebfun to run without proprietary software).<br />
<br />
* '''Required skills'''<br />
: Octave m-file programming, C++, some familiarity with Approximation Theory (a branch of mathematics).<br />
* '''Difficulty'''<br />
: Medium to Hard (probably requires a deep dive into how Octave supports OO).<br />
* '''Potential mentors'''<br />
: Colin B. Macdonald, [[User:KaKiLa|KaKiLa]], Mike Miller (?), Carnë Draug (?), someone from Chebfun team (?).<br />
<br />
How to get started: learn about Chebfun, browse Octave's bug list for classdef-related bugs, play with other classdef projects (Pytave, https://github.com/cbm755/octsympy/issues/545)<br />
<br />
== Adding functionality to Forge packages ==<br />
<br />
=== Neural Networks package: Convolutional Neural Networks ===<br />
Convolutional Neural Networks (CNNs) have recently become the state-of-the-art for image recognition and are widely used for solving classification and regression problems and for [https://github.com/tensorflow/tensorflow/blob/master/tensorflow/examples/tutorials/deepdream/deepdream.ipynb image generation]. The goal of the project is to implement a [https://it.mathworks.com/help/nnet/convolutional-neural-networks.html Matlab compatible] CNN toolbox using Google's library [https://www.tensorflow.org/ TensorFlow], which has a Python and C++ interface. As execution environment for the training function, the user will be able to choose between single/multiple CPUs and GPUs.<br />
* '''Required skills'''<br />
: C, C++, Python, m-file scripting, familiarity with Machine Learning algorithms, basic knowledge of Makefiles, experience with parallel computing and distributed systems.<br />
* '''Difficulty'''<br />
: Difficult.<br />
* '''Mentors'''<br />
: [[User:Francesco Faccio|Francesco Faccio]], Ankit<br />
<br />
=== EPA hydrology software suite ===<br />
Create native interfaces to the EPA software suites.<br />
<br />
Starting points<br />
* [https://forja.cica.es/projects/epanet-octave/ epanet-octave].<br />
* [https://github.com/OpenWaterAnalytics/ Open Water Analytics]<br />
<br />
* '''SWMM'''<br />
** [https://www.epa.gov/water-research/storm-water-management-model-swmm Official page]<br />
** Check work done in [https://github.com/water-systems/MatSWMM MatSWMM] [http://digital.csic.es/bitstream/10261/132982/1/MatSWMM.pdf article]<br />
<br />
* '''EPANET'''<br />
** [https://www.epa.gov/water-research/epanet Official page]<br />
<br />
* '''Required skills'''<br />
: m-file scripting, C, C++, API knowledge, file I/O, classdef (optional). <br />
<br />
* '''Difficulty'''<br />
: easy/medium<br />
<br />
* '''Mentor'''<br />
: [[User:KaKiLa|KaKiLa]]<br />
<br />
=== FullSWOF overland flow simulator ===<br />
Create scripting tools for (optional: native interfaces).<br />
<br />
Starting points<br />
* [http://www.univ-orleans.fr/mapmo/soft/FullSWOF/ The FullSWOF Project].<br />
* [https://arxiv.org/abs/1204.3210 FullSWOF: A software for overland flow simulation]<br />
* [https://bitbucket.org/binello7/fswof2d Initial work on Bitbucket]<br />
<br />
* '''Required skills'''<br />
: m-file scripting, C, C++, API knowledge, file I/O, classdef (optional). <br />
<br />
* '''Difficulty'''<br />
: easy/medium<br />
<br />
* '''Mentor'''<br />
: [[User:KaKiLa|KaKiLa]]<br />
<br />
=== TISEAN package ===<br />
<br />
[http://www.mpipks-dresden.mpg.de/~tisean/Tisean_3.0.1/index.html TISEAN] is a suite of code for nonlinear time series analysis. It has been [http://wiki.octave.org/TISEAN_package partially re-implemented] as libre software. The objective is to integrate TISEAN as an Octave Forge package, as was done for the Control package.<br />
[[TISEAN_package | A lot has been completed]] but [[TISEAN_package:Procedure | there is still work left to do]].<br />
<br />
There are missing functions to do computations on spike trains, to simulate autoregresive models, to create specialized plots, etc. Do check [[TISEAN_package:Procedure#Table_of_functions|the progress of the project]] to see if you are interested.<br />
<br />
* [http://octave.sourceforge.net/tisean/overview.html Package help at source forge.] <br />
* [https://sourceforge.net/p/octave/tisean/ci/default/tree/ Package repository at source forge.] <br />
<br />
* '''Required skills'''<br />
: m-file scripting, C, C++, and FORTRAN API knowledge. <br />
* '''Difficulty'''<br />
: easy/medium<br />
* '''Mentor'''<br />
: [[User:KaKiLa|KaKiLa]]<br />
<br />
=== Symbolic package ===<br />
<br />
Octave's [https://github.com/cbm755/octsympy Symbolic package] handles symbolic computing and other CAS tools. The main component of Symbolic is a pure m-file class "@sym" which uses the Python package [https://www.sympy.org SymPy] to do (most of) the actual computations. The package aims to expose the full functionality of SymPy while also providing a high-level of compatibility with the Matlab Symbolic Math Toolbox. The Symbolic package requires communication between Octave and Python. Recently, a GSoC2016 project successfully re-implemented this communication using the new [https://bitbucket.org/mtmiller/pytave Pytave tool].<br />
<br />
This project proposes to go further: instead of using Pytave only for the communication layer, we'll use it throughout the Symbolic project. For example, we might make "@sym" a subclass of "@pyobject". We also could stop using the "python_cmd" interface and use Pytave directly from methods. The main goal was already mentioned: to expose the *full functionality* of SymPy. For example, we would allow OO-style method calls such as "f.diff(x)" instead of "diff(f, x)".<br />
<br />
* '''Required skills'''<br />
: OO-programming with m-files, Python, and possibly C/C++ for improving Pytave (if needed).<br />
* '''Difficulty'''<br />
: easy/medium<br />
* '''Mentors and/or other team members'''<br />
: Colin B. Macdonald, Mike Miller, Abhinav Tripathi<br />
<br />
=== Interval package ===<br />
<br />
The [[Interval_package|interval package]] provides several arithmetic functions with accurate and guaranteed error bounds. Its development started in the end of 2014 and there is some fundamental functionality left to be implemented. See the [https://octave.sourceforge.io/interval/overview.html list of functions], basically any missing numeric Octave function could be implemented as an interval extension in the package. Potential projects:<br />
* Implement missing algorithms (as m-files)-difficulty and whether knowledge in interval analysis is required depends on the particular function. Of course, you may use papers which present such algorithms.<br />
* Improve existing algorithms (support more options for plotting, support more options for optimizers, increase accuracy, …)<br />
* Integrate functions from VERSOFT [http://uivtx.cs.cas.cz/~rohn/matlab/] in the package (some work has already been done and current progress is tracked in [[Interval_package#VERSOFT]]). This basically involves conversion of the documentation into Texinfo format, use [[Contribution_guidelines#Coding_style|Octave coding guidelines]] and to make sure that any called functions are available in the interval package. VERSOFT is originally based on INTLAB [http://www.ti3.tu-harburg.de/rump/intlab/], a proprietary Octave/Matlab package. Some functions may be missing. Also, the interval package doesn't support complex numbers, so it might not be possible to migrate some functions.<br />
* List more interesting use cases of interval arithmetic in the package's manual [https://octave.sourceforge.io/interval/package_doc/Examples.html]<br />
<br />
* '''Required skills'''<br />
: m-file scripting, basic knowledge of computer arithmetics (especially floating-point computations), interval analysis (depending on the functions to implement).<br />
* '''Difficulty'''<br />
: Medium.<br />
* '''Mentor and co-mentor'''<br />
: [[User:oheim|Oliver Heimlich]], [[User:Siko1056|Kai T. Ohlhus]]<br />
<br />
== Infrastructure ==<br />
<br />
=== Jupyter Integration ===<br />
<br />
[http://jupyter.org Jupyter Notebook] is a web-based worksheet interface for computing. There is a [https://github.com/Calysto/octave_kernel Octave kernel for Jupyter]. This project seeks to improve that kernel to make Octave a first-class experience within the Jupyter Notebook.<br />
<br />
* '''Mentors'''<br />
: Colin B. Macdonald, Mike Miller, others?<br />
<br />
<br />
=== Using Python within Octave ===<br />
<br />
[https://bitbucket.org/mtmiller/pytave Pytave] allows one to call Python functions and interact with Python objects from within Octave .m file code and from the Octave command line interface. Ideally, Pytave will not be a separate project, but rather a core feature of Octave. This project aims to improve Pytave with the goal of merging the code into the core Octave code base. <br />
<br />
Based on a previous summer project related to Pytave, this work will consist of fast-paced collaborative software development based on tackling the [https://bitbucket.org/mtmiller/pytave/issues?status=new&status=open pytave issue list]. You would also be expected to participate in software design decisions and discussion, as well as improve documentation, doctests and unit tests. As an example of the sorts of decision decisions being made, note that Octave indexes from 1 whereas Python typically indexes from 0; in which cases is it appropriate to make this transparent to the user?<br />
<br />
* '''Mentors'''<br />
: Mike Miller, Colin B. Macdonald, Abhinav Tripathi, others?<br />
<br />
<br />
=== Octave Package management ===<br />
<br />
Octave management of installed packages is performed by a single function, {{codeline|pkg}}, which does pretty much everything. This function has a few limitations which are hard to implement with the current codebase, and will most likely require a full rewrite.<br />
<br />
The planned improvements are:<br />
<br />
* install from URLs<br />
* install and update from repositories (hg and git)<br />
* automatic handling of dependencies<br />
* easily load, update or check specific package versions<br />
* management of tests and demos in C++ sources of packages<br />
* more flexibility on dependencies, e.g., dependent on specific Octave build options or being dependent in one of multiple packages<br />
* support for multiple version packages<br />
* support for multiple Octave installs<br />
* support for system-wide and user installed packages<br />
<br />
The main objective of this project is to make {{codeline|pkg}} more user friendly and to make it a tool to foster third party participation in Octave.<br />
{{codeline|pkg}} needs to be more flexible and intelligent when dealing with packages, different verisons and different sources, as well as options on how to build and install the package.<br />
There are also advance features of pkg that are useful for testing packages. However, the current {{codeline|pkg}} also performs some maintenance functions which it probably should not.<br />
Instead a package for developers should be created with such tools.<br />
<br />
To do this enhacenment effectively, a refactoring of the current {{codeline|pkg}} code will be needed.<br />
[https://bitbucket.org/carandraug/octave/commits/branch/pkg This job was started once], but due to diverging and growing specifications, it stalled. <br />
In this project we will focus on the most needed features, keeping the requirements to a minimum. <br />
<br />
Many of these problems have been solved in other languages. Familiarity with how other languages handle this problem will be useful to come up with elegant solutions. In some cases, there are standards to follow. For example, there are specifications published by freedesktop.org about where files should go ([http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html base directory spec]) and Windows seems to have its own standards. See bugs {{bug|36477}} and {{bug|40444}} for more details.<br />
<br />
In addition, package names may start to collide very easily. One horrible way to workaround this by is choosing increasingly complex package names that give no hint on the package purpose. A much better is option is providing an Authority category like Perl 6 does. Nested packages is also an easy way to provide packages for specialized subjects (think {{codeline|image::morphology}}). A new {{codeline|pkg}} would think all this things now, or allow their implementation at a later time. Read the [[OEP:pkg|unfinished plan]] for more details.<br />
<br />
* '''Minimum requirements'''<br />
: Ability to read and write Octave code, experience with Octave packages, and understanding of the basics of autotools. The most important skill is software design.<br />
* '''Difficulty'''<br />
: Easy to Medium.<br />
* '''Mentor'''<br />
: [[User:KaKiLa|KaKiLa]], Carnë Draug, Carlo de Falco, Sebastian Schöps<br />
<br />
=== Command line suggestion feature ===<br />
<br />
Currently Octave has no mechanism for suggesting corrections to typographic errors on the command line. An autocomplete/suggestion function is provided (using the double-TAB shortcut), but recent discussions have indicated a desire for a more proactive measure to catch user error. Potential applicants are referred to bug {{bug|46881}} regarding the usage of grey vs. gray. <br />
<br />
Suggested improvements are:<br />
* provide one or more suggested corrections to the user when a command line entry produces an error.<br />
* recognition and suggested correction for apparent syntax errors<br />
* function suggestion(s) when a 'close' match is found (close remains to be defined)<br />
* multiple suggestions if more than one option seems likely, along with a user-friendly method of selecting the appropriate choice.<br />
* user selectable option to disable and/or customize the suggestion behavior<br />
* correct operation, or graceful degradation, whether Octave is run in GUI or command-line mode. <br />
<br />
As mentioned in the bug {{bug|46881}} discussion, this project has little-to-no relation to m-code compatibility. As such, emulation of the behavior of other software is not required, nor even necessarily desired. Octave is free to implement as simple or complex a solution to this feature request as is necessary to provide the best experience to the user. There may be tools, features, or code from other license-compatible projects that can be of use here, and the applicant would be encouraged to identify and leverage such resources as appropriate. <br />
<br />
* '''Minimum requirements'''<br />
: TBD<br />
* '''Difficulty'''<br />
: Easy to Medium.<br />
* '''Mentor'''<br />
: Undetermined<br />
<br />
<br />
=== Octave code sharing ===<br />
<br />
Recently, on the [[OctConf_2017]] a [https://rawgit.com/siko1056/Octconf2017/master/octconf2017-publish-ohlhus-slides.pdf talk] about uploading [https://www.gnu.org/software/octave/doc/interpreter/XREFpublish.html published Octave code] to a MediaWiki (like this one) as an easy way to share code was given. With the talk, a [https://github.com/siko1056/OctConf2017 repository] containing example code for the MediaWiki upload is given. This might continue the idea of an unfinished [[Agora]] code sharing website, but one is not restricted to fully stay with the proposed approach. Another, but more ambitious idea is for example [http://central.scipy.org/ Scipy Central] - a website for Scipy code sharing. Their [https://github.com/scipy/SciPyCentral Code] is released under a BSD license.<br />
<br />
* '''Minimum requirements'''<br />
: Ability to read and write Octave code, some familiarity with C++ ([https://curl.haxx.se libcurl]), web development (GET/POST/FORM data, cookies), and [https://www.mediawiki.org/wiki/MediaWiki MediaWiki].<br />
* '''Difficulty'''<br />
: Medium.<br />
* '''Mentor'''<br />
: [[User:Siko1056|Kai T. Ohlhus]]<br />
<br />
=== SPQR Interface ===<br />
<br />
Octave implements QR factorization for sparse matrices, but it does so with an older library. This has caused fundamental issues, including segfaults as recorded here (https://savannah.gnu.org/bugs/?func=detailitem&item_id=51950). The goal of this project is to program an interface to the API for the SQPR library (http://faculty.cse.tamu.edu/davis/suitesparse.html). This is the same library that Matlab uses for this purpose.<br />
<br />
* '''Minimum requirements'''<br />
: Ability to read and write C++ code.<br />
* '''Difficulty'''<br />
: Medium.<br />
* '''Mentor'''<br />
: <br />
<br />
== Image Analysis ==<br />
<br />
=== Improvements to N-dimensional image processing ===<br />
<br />
The image package has partial functionality for N-dimensional images. These images exist for example in medical imaging where slices from scans are assembled to form anatomical 3D images. If taken over time and at different laser wavelengths or light filters, they can also result in 5D images. Albeit less common, images with even more dimensions also exist. However, their existence is irrelevant since most of the image processing operations are mathematical operations which are independent of the number of dimensions.<br />
<br />
As part of GSoC 2013, the core functions for image IO, {{codeline|imwrite}} and {{codeline|imread}}, were extended to better support this type of images. Likewise, many functions in the image package, mostly morphology operators, were expanded to deal with this type of image. Since then, many other functions have been improved, sometimes completely rewritten, to abstract from the number of dimensions. In a certain way, supporting ND images is also related to choosing good algorithms since such large images tend to be quite large.<br />
<br />
This project will continue on the previous work, and be mentored by the previous GSoC student and current image package maintainer. Planning the project requires selection of functions lacking ND support and identifying their dependencies. For example, supporting {{codeline|imclose}} and {{codeline|imopen}} was better implemented by supporting {{codeline|imerode}} and {{codeline|imdilate}} which then propagated ND support to all of its dependencies. These dependencies need to be discovered first since often they are not being used yet, and may even be missing function. This project can also be about implementing functions that have [http://wiki.octave.org/Image_package#Missing_functions not yet been implemented]. Also note that while some functions in the image package will accept ND images as input, they are actually not correctly implemented and will give incorrect results.<br />
<br />
* '''Required skills'''<br />
: m-file scripting, and a fair amount of C++ since a lot of image analysis cannot be vectorized. Familiarity with common CS algorithms and willingness to read literature describing new algorithms will be useful. <br />
* '''Difficulty'''<br />
: Difficult.<br />
* '''Potential mentor'''<br />
: Carnë Draug<br />
<br />
=== Improve Octave's image IO ===<br />
<br />
There are a lot of image formats. To handle this, Octave uses [http://www.graphicsmagick.org/ GraphicsMagic] (GM), a library capable of handling [http://www.graphicsmagick.org/formats.html a lot of them] in a single C++ interface. However, GraphicsMagick still has its limitations. The most important are:<br />
<br />
* GM has build option {{codeline|quantum}} which defines the bitdepth to use when reading an image. Building GM with high quantum means that images of smaller bitdepth will take a lot more memory when reading, but building it too low will make it impossible to read images of higher bitdepth. It also means that the image needs to always be rescaled to the correct range.<br />
* GM supports unsigned integers only thus incorrectly reading files such as TIFF with floating point data<br />
* GM hides away details of the image such as whether the image file is indexed. This makes it hard to access the real data stored on file.<br />
<br />
This project would implement better image IO for scientific file formats while leaving GM handle the others. Since TIFF is the de facto standard for scientific images, this should be done first. Among the targets for the project are:<br />
<br />
* implement the Tiff class which is a wrap around libtiff, using classdef. To avoid creating too many private __oct functions, this project could also create a C++ interface to declare new Octave classdef functions.<br />
* improve imread, imwrite, and imfinfo for tiff files using the newly created Tiff class<br />
* port the bioformats into Octave and prepare a package for it<br />
* investigate other image IO libraries<br />
* clean up and finish the dicom package to include into Octave core<br />
* prepare a matlab compatible implementation of the FITS package for inclusion in Octave core<br />
<br />
* '''Required skills'''<br />
: Knowledge of C++ and C since most libraries are written in those languages.<br />
* '''Difficulty'''<br />
: Medium.<br />
* '''Potential mentor'''<br />
: Carnë Draug<br />
<br />
== GUI ==<br />
<br />
=== GUI Variable Editor and Property Inspector ===<br />
<br />
Octave has a preliminary implementation of a Variable Editor: a spreadsheet-like tool for quickly editing and visualizing variables. The initial phase of the project will be learning how the implementation was done, and then finishing off the remaining action items listed in the Bug Tracker (principally a reasonable display of cell arrays and a concise display of strings).<br />
<br />
With the knowledge gained, the second part of the project will be to implement a Property Inspector. This is a spreadsheet like interface to the many, many graphics properties that exist and are different on a per-object basis. The goal would be not only the concise-display of the existing properties, but a reasonable user interface to change them. As examples, boolean properties should be able to be toggled with a double-click; Radio properties should have a drop-down list of only the supported options; Other properties that can be modified should have the constraints built-in (for example, Linewidth must be a scalar, while Position must be a 1x4 vector). It would also be important to have easy access to the documentation of a property. <br />
<br />
* '''Minimum requirements'''<br />
: Ability to read and write C++ code. Experience with Qt toolkit and GUI programming is optional, but desirable.<br />
* '''Difficulty'''<br />
: Medium.<br />
* '''Mentor'''<br />
: <br />
<br />
== Graphics ==<br />
<br />
=== PolarAxes and Plotting Improvements ===<br />
<br />
Octave currently provides supports for polar axes by using a Cartesian 2-D axes and adding a significant number of properties and callback listerners to get things to work. What is needed is a first class implementation of a "polaraxes" object in C++. This will require creating a new fundamental graphics object type, and programming in C++/OpenGL to render the object. When "polaraxes" exist as an object type then m-files will be written to access them including polaraxes.m, polarplot.m, rticks.m, rticklabels.m, thetaticks, thetaticklabels.m, rlim.m, thetalim.m<br />
<br />
* '''Minimum requirements'''<br />
: Ability to read and write C++ code. Ability to read and write Octave code. Experience with OpenGL programming is optional.<br />
* '''Difficulty'''<br />
: Medium.<br />
* '''Mentor'''<br />
: Rik <br />
<br />
<noinclude><br />
[[Category:Summer of Code]]<br />
[[Category:Project Ideas]]<br />
</noinclude></div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=Short_projects&diff=10581Short projects2017-12-24T17:42:02Z<p>Batterylow: /* Miscellaneous */</p>
<hr />
<div>This is a list of small projects, the type that could be done in a couple of hours, maybe even minutes (no promises, we should all know about how estimates for software development work). This is probably the best place for users who want to start helping with Octave development (please, see also Octave coding guidelines). Please submit a fix to the [https://savannah.gnu.org/bugs/?func=additem&group=octave bug tracker] (not to the mailing list) and add a link to the item in question. Use the [https://savannah.gnu.org/patch/?func=additem&group=octave patch tracker] for submissions unrelated to an existing bug.<br />
<br />
The list is meant to be dynamic -- please add, remove, and comment on it. And since the things are likely to be of short duration, don't ask if is there is anyone already working on it. Projects of long duration should be added to the [[Projects]] page instead.<br />
<br />
Most of the small and easy bugs are caught and fixed quickly by the Octave developers. The best way to catch an easy one is then to [https://lists.gnu.org/mailman/listinfo/octave-bug-tracker subscribe to the bug tracker] (note that this has a lot of activity so you'll probably prefer to receive a digest).<br />
<br />
{{warning| do not simply add a patch/file to the bug or patch tracker. Always leave a comment at the same time, even if it just a simple "I prepared a change that should fix it". If there is no comment, it's hard to notice that a patch was added since there will be no notice on the discussion about it.}}<br />
<br />
== Bugs==<br />
<br />
Please help with the triage of [https://savannah.gnu.org/bugs/?group=octave existing bugs] to populate the list of easy bugs below. You may find it useful to review the [http://wiki.octave.org/wiki/index.php?title=Short_projects&action=history history] of this short projects page, to give you an idea of past successful short projects. <br />
* {{bug|41674}} - image package: temporary arrays in imresize are doubles<br />
* {{patch|8368}} - imremap - Change to imremap to reduce memory footprint<br />
* {{patch|8369}} - imresize - Change to imresize to reduce memory footprint<br />
<br />
==== Code submitted, requires changeset & verification ====<br />
Sometimes a standalone file or a diff file is submitted; Octave maintainers prefer a changeset though; preparing a changeset will expedite bug fixing.<br />
<br />
* {{bug|33935}} - demo function humps is not defined<br />
<br />
== Missing functions ==<br />
<br />
* there is a list of missing functions for the [[image package|image]], [[mapping package|mapping]], [[Optimization package|optimization]], and [[Signal package|signal]] packages.<br />
** It would help to group the several missing functions in the [[image package]], as per [http://www.mathworks.com/help/images/functionlist.html] (similar to what was done in the [[signal package]] wiki page); please keep the original alphabetical list intact.<br />
* openfig/savefig functions<br />
** These should be particularly easy additions as they are really just a wrapper on top of hgload/hgsave.<br />
<br />
== Function Compatibility ==<br />
A number of functions are implemented, but may have known incompatibilities or only partially handled option sets, etc.<br />
* integral - currently cannot handle all optional inputs, see see {{bug|42037}}<br />
<br />
== BIST tests ==<br />
<br />
Write Built-In Self Tests (BIST) for a function. This improve's Octave's regression testing and ensures that we don't break anything when we add new features. Tests are written in the Octave m-file language and usually take less than 10 minutes to code for a single instance.<br />
<br />
* [[Add_BIST_tests_for_octave_functions_written_in_C%2B%2B| BIST for C++ functions]]<br />
<br />
* [[BIST_for_m-files| BIST for m-files]]. See also [[Projects#Tests]].<br />
<br />
== Miscellaneous ==<br />
<br />
* C++ cleanup of packages after the switch to exceptions (late 2015).See [[Invert if/else/error]].<br />
<br />
* Use "units.h" from [http://www.gnu.org/software/units/ GNU units] in [http://octave.sourceforge.net/miscellaneous/function/units.html function units] (from the Octave-Forge [http://octave.sourceforge.net/miscellaneous/ miscellaneous package]) rather than making a system call and parsing its output (and having to handle multiple versions of it). This change will make it much more robust. It likely will alleviate the requirement of having [http://www.gnu.org/software/units/ GNU units] installed in the system separately by the user. This requires knowledge of C (units is written on C) and C++ to write its Octave interface. It can be very easy if the units.h truly allows to be used as library or maybe impossible if it does not. This has not been investigated yet.<br />
<br />
* Use non-empty identifiers in all warnings and errors issued by Octave; see {{bug|39439}}, {{bug|39434}}. You may tackle as many or as few IDs as you have time for. As it is a widespread issue, finding occurrences in the source code should give you valuable knowledge about the way Octave files are organized. <br />
** When raising errors and warnings try to use the ids that are documented in the functions [http://octave.sourceforge.net/octave/function/warning_ids.html warning_ids] and [http://octave.sourceforge.net/octave/function/error_ids.html error_ids]. If you really need a new id (please, first read the ones already there!), please add it to those functions as well. If you see other ids used in core that are not given by the functions mentioned above, please, report or submit patch for them, in addition to the patch to the calling functions as well. <br />
<br />
* extend sub2ind and ind2sub: {{bug|41796}}<br />
<br />
[[Category:Development]]<br />
[[Category:Project Ideas]]<br />
<br />
== Feature requests ==<br />
* {{bug|41844}} - GUI Debug Menu could offer "Stop If..."<br />
* {{bug|41530}} - Editor debug mode could show a dbup/dbdown GUI component<br />
* {{bug|41470}} - offer editor preference "highlight current word"<br />
* {{bug|40211}} - More compact output for structs and cell arrays<br />
* {{bug|32088}} - Feature request: -ALL option for WHICH<br />
* {{bug|47464}} - audioformats: a new function to get information on supported audio formats<br />
* {{bug|47239}} - calling system without shell</div>Batterylowhttps://wiki.octave.org/wiki/index.php?title=Invert_if/else/error&diff=10580Invert if/else/error2017-12-24T17:33:20Z<p>Batterylow: </p>
<hr />
<div>== Introduction ==<br />
<br />
The C++ error handling mechanism in core Octave has been changed to use exceptions. Previously, calling error() in C++ would always return execution to the calling function. This made it necessary to explicitly use the else keyword to control program flow. With exceptions, the C++ code may now be written in a manner that closely resembles Octave's own m-file language.<br />
<br />
The principal work for this topic is to convert if/else statements that have an error() call in the else branch to a new format. The goal is to move the error() call to be after the if statement, eliminate the else branch, and decrease the indent of the remaining code. This requires reversing the conditional test in the if. For a single condition, the condition should be reversed rather than just adding the negation operator '!' to the start of the conditional. For a test with multiple conditions, use DeMorgan's Law ([https://en.wikipedia.org/wiki/Demorgans_law Demorgan's Law]). In brief, you will need to negate each individual conditional and then change all && to || or vice versa.<br />
<br />
==== Example 1 : Single Conditional (rows() from data.cc) ====<br />
{|<br />
!Before !! After<br />
|-<br />
|<pre><br />
bool do_set (const octave_value& v)<br />
{<br />
if (v.is_scalar_type () && v.is_real_type ())<br />
{<br />
double new_val = v.double_value ();<br />
<br />
if (new_val != current_val)<br />
{<br />
current_val = new_val;<br />
return true;<br />
}<br />
}<br />
else<br />
error ("set: invalid value for double property \"%s\"",<br />
get_name ().c_str ());<br />
return false;<br />
}<br />
</pre><br />
|<pre><br />
bool do_set (const octave_value& v)<br />
{<br />
if (! v.is_scalar_type () || ! v.is_real_type ())<br />
error ("set: invalid value for double property \"%s\"",<br />
get_name ().c_str ());<br />
<br />
double new_val = v.double_value ();<br />
<br />
if (new_val != current_val)<br />
{<br />
current_val = new_val;<br />
return true;<br />
}<br />
<br />
return false;<br />
}<br />
</pre><br />
|}<br />
<br />
== Detailed Instructions ==<br />
<br />
The list of files which contain an instance of else followed by error() is shown in the Files section of this page. The actual instances, including line numbers, are shown in the Instances section. To avoid duplication, sign up for a particular file by editing the Files section of this wiki page and replacing '???' with your name. When you have edited a file you should verify that everything is okay by executing<br />
<br />
<pre><br />
make all<br />
./run-octave<br />
test FILENAME<br />
</pre><br />
<br />
When that passes, upload your patch to the patch tracker https://savannah.gnu.org/patch/?group=octave. If you can, e-mail the Octave Maintainer's list at octave-maintainers@gnu.org and let us know that there is something to review. Also, add the wiki tags <pre><strike> ... </strike></pre> to the Files section to cross the file off the list. In addition, increment the number of files that were fixed by +1.<br />
<br />
== Files ==<br />
<br />
As of now, all the files have been corrected in Octave core source. Contributors are, however, welcomed to make changes as described above in Octave's packages.</div>Batterylow