Editing Summer of Code - Getting Started
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
{{Note|GNU Octave is a [https://summerofcode.withgoogle.com/programs/ | {{Note|GNU Octave is a [https://summerofcode.withgoogle.com/programs/2023/organizations/gnu-octave mentoring organization for GSoC 2023].}} | ||
Since 2011 the GNU Octave project has successfully mentored: | Since 2011 the GNU Octave project has successfully mentored: | ||
* [[Summer of Code | ''' | * [[Summer of Code | '''37 participants''' ๐]] | ||
* [[Summer of Code | ''' | * [[Summer of Code | '''39 projects''' ๐]] | ||
in [[Summer of Code]] (SoC) programs by [https://summerofcode.withgoogle.com/ Google] and [https://esa.int/ ESA]. | 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.''' | # ๐๐ฌ '''We want to get to know you (before the deadline).ย Communicate with us.''' | ||
#* Join [https://octave.discourse.group/ '''Octave Discourse'''] or [[IRC]] | #* Join [https://octave.discourse.group/ '''Octave Discourse'''] or [[IRC]]. 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. | #* 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 ๐ฎ | #* '''<span style="color:darkblue;">If you never talked to us, we will likely reject your proposal</span>''', even it looks good ๐ฎ | ||
Line 56: | Line 56: | ||
= Suggested projects = | = 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] | 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. | ||
{{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.}} | ||
== ode15{i,s} : Matlab Compatible DAE solvers == | == ode15{i,s} : Matlab Compatible DAE solvers == | ||
Line 114: | Line 73: | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: Francesco Faccio, [https://octave.discourse.group/u/cdf Carlo de Falco], [https://octave.discourse.group/u/marco_caliari Marco Caliari], Jacopo Corno, [https://octave.discourse.group/u/schoeps Sebastian Schรถps] | : Francesco Faccio, [https://octave.discourse.group/u/cdf Carlo de Falco], [https://octave.discourse.group/u/marco_caliari Marco Caliari], Jacopo Corno, [https://octave.discourse.group/u/schoeps Sebastian Schรถps] | ||
< | == Symbolic package == | ||
ย | |||
The [[Symbolic package]] provides symbolic computing and other [https://en.wikipedia.org/wiki/Computer_algebra_system computer algebra system] 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 much of the 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.ย In 2016 a GSoC project successfully re-implemented this communication using the new [[Pythonic|Pythonic package]].ย In 2022, a GSoC project revitalized and improved the maintainability of the package. | |||
ย | |||
Possible ideas for improving the Symbolic package: | |||
* exposing more functionality of SymPy with ''less glue'' in between.ย For example, we could allow OO-style method calls such as <code>f.diff(x)</code> as well as <code>diff(f, x)</code>. | |||
* Fix the storage of non-expressions by working with upstream SymPy: currently we rely on deprecated functionality in SymPy. | |||
* Fix classdef-related issues in Octave itself. | |||
ย | |||
== PolarAxes and Plotting Improvements == | == PolarAxes and Plotting Improvements == | ||
Octave currently provides | 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}}. | ||
* '''Project size''' [[#Project sizes | [?]]] and '''Difficulty''' | * '''Project size''' [[#Project sizes | [?]]] and '''Difficulty''' | ||
Line 127: | Line 93: | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: [https://octave.discourse.group/u/rik Rik] | : [https://octave.discourse.group/u/rik Rik] | ||
== Table datatype == | == Table datatype == | ||
Line 140: | Line 104: | ||
* '''Required skills''' | * '''Required skills''' | ||
: Octave, C/C++ | : Octave, C/C++ | ||
== TISEAN package == | == TISEAN package == | ||
Line 155: | Line 115: | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: [https://octave.discourse.group/u/kakila KaKiLa] | : [https://octave.discourse.group/u/kakila KaKiLa] | ||
== Better tab completion == | == Better tab completion == | ||
Line 184: | Line 142: | ||
To get more examples, see how bash completion works. You can type git or hg and then tab and it will give the list of available commands. If you type "sort --r" and then tab, it gives the list of options to sort starting with "--r", etc. | To get more examples, see how bash completion works. You can type git or hg and then tab and it will give the list of available commands. If you type "sort --r" and then tab, it gives the list of options to sort starting with "--r", etc. | ||
== Graphics rendering back to front sorting == | == Graphics rendering back to front sorting == | ||
Several incompatibilities have been identified in how Octave plots transparent objects in 3D, causing certain transparent objects to hide opaque objects behind them even though they're not supposed to. The vast majority of them were isolated to one problem: if the objects to be drawn are rendered such that the one farthest away from the viewer is rendered first and nearer objects are rendered on top of that, then transparency would be automatically achieved, but this needs very careful coding to stay performant and to avoid rendering objects that will be overwritten fully by others. See [https://savannah.gnu.org/bugs/?57980] for a summary. | Several incompatibilities have been identified in how Octave plots transparent objects in 3D, causing certain transparent objects to hide opaque objects behind them even though they're not supposed to. The vast majority of them were isolated to one problem: if the objects to be drawn are rendered such that the one farthest away from the viewer is rendered first and nearer objects are rendered on top of that, then transparency would be automatically achieved, but this needs very careful coding to stay performant and to avoid rendering objects that will be overwritten fully by others. See [https://savannah.gnu.org/bugs/?57980] for a summary. | ||
This project can be a GSoC for a student who understands 3D graphics rendering. | |||
ย | |||
ย | |||
ย | |||
ย | |||
= Project sizes = | = 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>: | |||
* '''~175 hours''' (~12 weeks, Jun 13 - Sept 12) | |||
* '''~350 hours''' (~22 weeks, Jun 13 - Nov 21) | |||
= Footnotes = | = Footnotes = |