Summer of Code - Getting Started: Difference between revisions

← Older edit

Summer of Code - Getting Started (view source)

Revision as of 13:52, 17 March 2025

2,471 bytes added , 17 March

m

update year - edit link this time

Nrjank

164

edits

@@ Line 1: / Line 1: @@
-{{Note|GNU Octave is a [https://summerofcode.withgoogle.com/programs/2023/organizations/gnu-octave mentoring organization for GSoC 2023].}}
+{{Note|GNU Octave is a [https://summerofcode.withgoogle.com/programs/2025/organizations/gnu-octave mentoring organization for GSoC 2025].}}
 Since 2011 the GNU Octave project has successfully mentored:
-* [[Summer of Code | '''37 participants''' 🙂]]
+* [[Summer of Code | '''42 participants''' 🙂]]
-* [[Summer of Code | '''39 projects''' 📝]]
+* [[Summer of Code | '''44 projects''' 📝]]
 in [[Summer of Code]] (SoC) programs by [https://summerofcode.withgoogle.com/ Google] and [https://esa.int/ ESA].
@@ Line 11: / Line 11: @@
 # 😉💬 '''We want to get to know you (before the deadline).  Communicate with us.'''
-#* Join [https://octave.discourse.group/ '''Octave Discourse'''] or [[IRC]]. Using a nickname is fine.
+#* Join [https://octave.discourse.group/ '''Octave Discourse'''] or [[IRC]] for general discussion and to ask questions (Please do not use the bug tracker for general GSOC inquiries unrelated to specific bugs found with Octave.) Using a nickname is fine.
 #* Show us that you're motivated to work on Octave 💻.  There is no need to present an overwhelming CV 🏆; evidence of involvement with Octave is more important.
 #* '''<span style="color:darkblue;">If you never talked to us, we will likely reject your proposal</span>''', even it looks good 🚮
@@ Line 27: / Line 27: @@
 #* Try to show us as early as possible a draft of your proposal 📑
 #* If we see your proposal for the first time after the application deadline, it might easily contain some paragraphs not fully clear to us.  Ongoing interaction will give us more confidence that you are capable of working on your project 🙂👍
+#* Here’s a sample proposal outline that you can use as a reference when drafting your own application. [https://docs.google.com/document/d/1kGtT9_f0FrXdCKwyKEWwOV6R-AU90bkd/edit?usp=sharing&ouid=115736651221450989198&rtpof=true&sd=true Sample Proposal]
 #* Then submit the proposal following the applicable rules, e.g. for [https://google.github.io/gsocguides/student/writing-a-proposal GSoC]. 📨
@@ Line 56: / Line 57: @@
 = Suggested projects =
-The following suggested projects are distilled from the [[Projects]] page for the benefit of potential SoC participants.  You can also look at our [[Summer of Code|completed past projects]] for more inspiration.
+The following suggested projects are distilled from the [[Projects]] page for the benefit of potential SoC participants.  You can also look at our [[Summer of Code|completed past projects]], or the current [https://hg.savannah.gnu.org/hgweb/octave/file/tip/etc/ROADMAP.md | Octave Development Roadmap] for more inspiration.
-{{Note|Do you use Octave at your working place or university? Do you have some numerical project in mind?  You are always welcome to '''propose your own projects'''.  If you are passionate about your project, it will be easy to find an Octave developer to mentor and guide you.}}
+{{Note|Do you use Octave at your working place or university? Do you have some numerical project in mind?  You are always welcome to '''propose your own projects'''.  If you are passionate about your project, it will be easy to find an Octave developer to mentor and guide you. Please note that for such a proposal to be successful it will almost certainly involve initiating pre-proposal discussion over at the [https://octave.discourse.group Octave Discourse forum].}}
-== Adding regression GAM and kNN classification functionality in statistics package ==
+== Adding clustering {{Codeline|*Searcher}} classes in statistics package ==
-Generalized Additive Models and k-Nearest Neighbor algorithms are two important tools in advanced statistics used for regression and classification problems, respectively. The statistics package, although heavily developed during the past year, still lacks any functionality regarding these two algorithms.
+Although the statistics package already has {{Codeline|knnsearch}} and {{Codeline|rangesearch}} functions, it misses [https://docs.octave.org/latest/Creating-a-classdef-Class.html classdefs] for extending their functionality. Furthermore, the {{Codeline|KDTree}} method in the aforementioned functions is currently disabled, because it is very slow and poorly implemented (see GitHub issue [https://github.com/gnu-octave/statistics/issues/151 #151]). The goal of this project if to implement {{Codeline|KDTreeSearcher}}, {{Codeline|ExhaustiveSearcher}}, and {{Codeline|hnswSearcher}} classes (including their {{Codeline|knnsearch}} and {{Codeline|rangesearch}} methods) along with the {{Codeline|createns}} helper function. Beyond MATLAB compatibility, the KDTree implementation should ideally utilize a compiled oct library for faster construction and queries of points.
-The scope is to implement both the respective class def objects as well as the relevant functions in a MATLAB compatible way.
 * '''Project size''' [[#Project sizes | [?]]] and '''Difficulty'''
-: ~350 hours (medium)
+: ~350 hours (hard)
 * '''Required skills'''
-: Octave, familiarity with statistical methods
+: Octave, classdef, C++, good knowledge of clustering methods
 * '''Potential mentors'''
 : [https://octave.discourse.group/u/pr0m1th3as Andreas Bertsatos]
@@ Line 74: / Line 74: @@
 == Custom re-implementation of the texi2html (v.1.82) command line tool ==
-Implement a custom perl script to relax the dependency of the pkg-octave-doc package on texi2html (v.1.82) command line tool, which is no longer maintained or further developed but also not readily available to all linux distributions.
+Implement a compiled .oct function to relax the dependency of the pkg-octave-doc package on texi2html (v.1.82) command line tool, which is no longer maintained or further developed but also not readily available to all linux distributions. The idea is to have a `texi2html` function within the pkg-octave-doc package that will replace the functionality of the texi2html (v.1.82) command line tool. This will also help improve the speed of pkg-octave-doc processing large packages, which contain specific tags (such as @math) which are currently handled within Octave code.
-This will also help improve the speed of pkg-octave-doc processing large packages, which contain specific tags (such as @math) which are currently handled within Octave code.
 * '''Project size''' [[#Project sizes | [?]]] and '''Difficulty'''
 : ~350 hours (hard)
 * '''Required skills'''
-: Perl, Octave, Texinfo, HTML
+: Perl, C++, Octave, Texinfo, HTML
 * '''Potential mentors'''
 : [https://octave.discourse.group/u/pr0m1th3as Andreas Bertsatos]
+== Port Chebfun to Octave and improve classdef support ==
+[https://www.chebfun.org| Chebfun] uses interpolation to approximate functions to very high accuracy, giving numerical computing that feels like symbolic computing.
+The software is implemented as collection of "classdef" classes and is Free and Open Source Software.
+However, Chebfun does not yet work with Octave, largely due to differences and issues with Octave's classdef implementation.
+This project has two aims: (1) make changes to the Chebfun code to make it work on Octave and (2) improve Octave's classdef functionality.
+Some initial steps toward to first goal can be found on [https://github.com/cbm755/chebfun/tree/octave_dev| this octave_dev branch].
+The second goal will likely involve a collaborative effort because classdef is a priority on [https://hg.savannah.gnu.org/hgweb/octave/file/tip/etc/ROADMAP.md | Octave's Development Roadmap] and because other proposed projects also involve classdef.
+* '''Project size''' [[#Project sizes | [?]]] and '''Difficulty'''
+: ~350 hours (hard)
+* '''Required skills'''
+: Octave, object-oriented programming, polynomial interpolation and approximation theory, C++.
+* '''Potential mentors'''
+: [https://octave.discourse.group/u/cbm Colin B. Macdonald]
 <!--
@@ Line 103: / Line 120: @@
 == PolarAxes and Plotting Improvements ==
-Octave currently provides supports for polar axes by using a Cartesian 2-D axes and adding a significant number of properties and callback listeners to get things to work.  What is needed is the implementation of a dedicated "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" exists 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.  This relates to bug {{bug|49804}}.
+Octave currently provides support for polar axes by using a Cartesian 2-D axes and adding a significant number of properties and callback listeners to get things to work.  What is needed is the implementation of a dedicated "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" exists 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.  This relates to bug {{bug|49804}}.
 * '''Project size''' [[#Project sizes | [?]]] and '''Difficulty'''
@@ Line 210: / Line 227: @@
 = Project sizes =
-Since GSoC 2022 there exist two project sizes<ref>https://groups.google.com/g/google-summer-of-code-announce/c/_ekorpcglB8</ref><ref>https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list</ref>:
+As of 2024, possible project sizes are 90 (small), 175 (medium), or 350 hours (large) <ref>https://developers.google.com/open-source/gsoc/faq#how_much_time_does_gsoc_participation_take</ref>.
-* '''~175 hours''' (~12 weeks, Jun 13 - Sept 12)
-* '''~350 hours''' (~22 weeks, Jun 13 - Nov 21)
 = Footnotes =