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: | ||
Since 2011 the GNU Octave project has mentored 38 students in [[Summer of Code]] (SoC) programs by [https://summerofcode.withgoogle.com/ Google] and [https://socis.esa.int/ ESA]. Those programs aim to populate open-source software development and to attract potential new Octave developers. | |||
Since 2011 the GNU Octave project has | |||
in [[Summer of Code]] (SoC) programs by [https://summerofcode.withgoogle.com/ Google] and [https://esa.int/ ESA]. | |||
Those | |||
= Steps toward a successful application = | = Steps toward a successful application = | ||
# 😉💬 '''We want to get to know you | # 😉💬 '''We want to get to know you. Communicate with us.''' | ||
#* Join [https://octave.discourse.group/ '''Octave Discourse'''] or [ | #* Join [https://octave.discourse.group/ '''Octave Discourse'''] or our [https://webchat.freenode.net/?channels=#octave '''IRC channel''']. | ||
#* | #* We are interested in you as motivated developer 💻 There is no need to present an overwhelming CV with prestigious universities 🏰 and programming contest awards 🏆 in it. We are very fine if you just communicate using a nickname with us. | ||
#* ''' | #* If your first question is "Hi I'm new to Octave. What should I do?" '''you are out''' 🤦 | ||
#* Remember, '''we are mentors and not your boss 🙂''' | |||
# 📝💡 '''Tell us what you are going to do.''' | |||
#* When you contact us for the first time, do not write just to say in what project you're interested in. Be specific about what you are going to do, post many links 🔗, show us you know what you are talking about 💡, and ask many [http://www.catb.org/esr/faqs/smart-questions.html smart questions] 🤓 | |||
# 👩🔬 '''Get your hands dirty.''' | # 👩🔬 '''Get your hands dirty.''' | ||
#* We are curious about your programming skills | #* We are curious about your programming skills ⌨️ | ||
#** | #** Try to [https://savannah.gnu.org/bugs/?group=octave fix Octave bugs] or [https://savannah.gnu.org/patch/?group=octave submit patches] '''before''' the end of the application deadline. | ||
#** | #** Take a look at the [[Short projects]] for simple bugs to start with. | ||
#* '''Use Octave!''' | #* '''Use Octave!''' | ||
#** If you come across something that does not work the way you like ➡️ try to fix that 🔧 | #** If you come across something that does not work the way you like ➡️ try to fix that 🔧 | ||
#** Or | #** Or you come across a missing function ➡️ try to implement it. | ||
# 📔 '''Prepare your proposal with us.''' | # 📔 '''Prepare your proposal with us.''' | ||
#* | #* GSoC, for example, [https://google.github.io/gsocguides/student/writing-a-proposal requires to submit a proposal]. | ||
#* If we see your proposal for the first time after the application deadline, it might | #* If we see your proposal for the first time after the application deadline, you can easily imagine that it might contain ambiguities or some paragraphs are not fully clear to us. We easily get doubts if you are capable of working on your project 😓 | ||
#* | #* Try to show us as early as possible a draft of your proposal 👍 | ||
= How do we judge your application? = | = How do we judge your application? = | ||
Line 47: | Line 40: | ||
You should know: | You should know: | ||
# How to build Octave from | # How to build Octave from it's source code using [http://en.wikipedia.org/wiki/GNU_build_system the GNU build system]. | ||
#* Read in this wiki: [[Developer FAQ]], [[Building]] | #* Read in this wiki: [[Developer FAQ]], [[Building]] | ||
#* Tools to know: [https://en.wikipedia.org/wiki/GNU_Compiler_Collection gcc], [https://en.wikipedia.org/wiki/Make_(software) make] | #* Tools to know: [https://en.wikipedia.org/wiki/GNU_Compiler_Collection gcc], [https://en.wikipedia.org/wiki/Make_(software) make] | ||
Line 56: | Line 49: | ||
= Suggested projects = | = Suggested projects = | ||
The following suggested projects are distilled from the [[Projects]] page for the benefit of potential SoC | The following suggested projects are distilled from the [[Projects]] page for the benefit of potential SoC students. You can also look at our [[Summer of Code|completed past projects]] for more inspiration. | ||
{{Note|Do you use Octave at your university or 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 == | ||
An initial implementation of Matlab compatible Differential Algebraic Equations (DAE) solvers, {{manual|ode15i}} and {{manual|ode15s}}, based on [https://computing.llnl.gov/projects/sundials SUNDIALS], | |||
was done by [https://gsoc2016ode15s.blogspot.com/ Francesco Faccio during GSoC 2016]. The code is maintained in the main Octave repository and consists mainly of the following three files: [https://hg.savannah.gnu.org/hgweb/octave/file/tip/libinterp/dldfcn/__ode15__.cc {{path|libinterp/dldfcn/__ode15__.cc}}], [https://hg.savannah.gnu.org/hgweb/octave/file/tip/scripts/ode/ode15i.m {{path|scripts/ode/ode15i.m}}] and [https://hg.savannah.gnu.org/hgweb/octave/file/tip/scripts/ode/ode15s.m {{path|scripts/ode/ode15s.m}}]. | |||
The {{manual|decic}} function for selecting consistent initial conditions for ode15i can be made more Matlab compatible by using [https://faculty.smu.edu/shampine/cic.pdf another algorithm]. Another useful extension is to make ode15{i,s} work with datatypes other than double and to improve interpolation at intermediate time steps. | |||
* '''Required skills''' | * '''Required skills''' | ||
: Octave, | : Knowledge of Octave, C/C++; familiarity with numerical methods for DAEs | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: | : Francesco Faccio, Carlo de Falco, Marco Caliari, Jacopo Corno, Sebastian Schöps | ||
== | == Using Python within Octave == | ||
[[Pythonic]] allows one to call Python functions and interact with Python objects from within Octave .m file code and from the Octave command line interface. Pythonic may eventually not be a separate package, but rather a core feature of Octave. This project aims to improve Pythonic with the goal of making the package more stable, maintainable, and full-featured. | |||
Based on a previous summer project related to Pythonic, this work will consist of fast-paced collaborative software development based on tackling the [https://gitlab.com/mtmiller/octave-pythonic/issues Pythonic 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 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? | |||
* '''Required skills''' | * '''Required skills''' | ||
: Octave, | : Knowledge of Octave, C/C++, Python | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: | : Mike Miller, Colin B. Macdonald, Abhinav Tripathi | ||
== Improve TIFF image support == | |||
[https://en.wikipedia.org/wiki/TIFF Tag Image File Format (TIFF)] is the de facto standard for scientific images. Octave uses the [http://www.graphicsmagick.org/ GraphicsMagic] (GM) C++ library to handle [http://www.graphicsmagick.org/formats.html TIFF and many others image formats]. However, GM still has several limitations: | |||
* 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. | |||
** Building GM with '''low quantum''' 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. | |||
* GM supports unsigned integers only, thus incorrectly reading files such as TIFF with floating-point data. | |||
* GM hides details of the image such as whether the image file is indexed. This makes it hard to access the real data stored on file. | |||
This project aims to implement better TIFF image support using [https://en.wikipedia.org/wiki/Libtiff libtiff], while leaving GM handle all other image formats. After writing a [https://octave.org/doc/v6.1.0/classdef-Classes.html classdef] interface to libtiff, improve the Octave functions {{manual|imread}}, {{manual|imwrite}}, and {{manual|imfinfo}} to make use of it. | |||
* '''Required skills''' | * '''Required skills''' | ||
: Octave, C/C++ | : Knowledge of Octave, C/C++ | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: | : Carnë Draug | ||
== 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}}. | ||
* '''Required skills''' | * '''Required skills''' | ||
: Octave, C/C++; optional experience with OpenGL programming | : Knowledge of Octave, C/C++; optional experience with OpenGL programming | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: | : Rik | ||
== Table datatype == | == Table datatype == | ||
Line 136: | Line 108: | ||
Based upon the existing approaches, the goal of this project is to define an initial subset of [https://www.mathworks.com/help/matlab/tables.htmlMatlab's table functions], which involve sorting, splitting, merging, and file I/O and implement it within the given time frame. | Based upon the existing approaches, the goal of this project is to define an initial subset of [https://www.mathworks.com/help/matlab/tables.htmlMatlab's table functions], which involve sorting, splitting, merging, and file I/O and implement it within the given time frame. | ||
* '''Required skills''' | * '''Required skills''' | ||
: Octave, C/C++ | : Knowledge of Octave, C/C++ | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: | : [[User:siko1056|Kai]] | ||
== Adding functionality to packages == | |||
=== OCS package === | |||
== | |||
The [[ | The [[Ocs package | OCS package]] is a circuit simulator. The objective of this project is to increase compatibility with [https://en.wikipedia.org/wiki/SPICE SPICE] and improve compatibility with other Octave packages, e.g. the [[Control package]]. Please study the [https://octave.sourceforge.io/ocs/overview.html available functions] of this package. | ||
* '''Required skills''' | * '''Required skills''' | ||
: Octave, C/C++; FORTRAN API knowledge | : Knowledge of Octave, C/C++; FORTRAN API knowledge | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: | : Sebastian Schöps, Carlo de Falco | ||
=== 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 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. In 2016 another GSoC project successfully re-implemented this communication using the new [[Pythonic|Pythonic package]]. | |||
This project proposes to go further: instead of using Pythonic 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 Pythonic 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 <code>f.diff(x)</code> instead of <code>diff(f, x)</code>. | |||
* '''Required skills''' | * '''Required skills''' | ||
: | : Knowledge of Octave, C/C++, Python; object-oriented programming (OOP) in Octave | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: | : Colin B. Macdonald, Mike Miller, Abhinav Tripathi | ||
=== TISEAN package === | |||
== | |||
The [[TISEAN package]] provides an Octave interface to [https://www.pks.mpg.de/~tisean/Tisean_3.0.1/index.html TISEAN] is a suite of code for nonlinear time series analysis. In 2015, another GSoC project started with the work to create interfaces to many TISEAN functions, but [[TISEAN_package:Procedure | there is still work left to do]]. There are missing functions to do computations on spike trains, to simulate autoregresive models, to create specialized plots, etc. Which are of importance for many scientific disciplines involving statistical computations and signal processing. | |||
There are | |||
* '''Required skills''' | * '''Required skills''' | ||
: | : Knowledge of Octave, C/C++; FORTRAN API knowledge | ||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: | : [[User:KaKiLa|KaKiLa]] | ||
[[Category:Summer of Code]] | [[Category:Summer of Code]] | ||
[[Category:Project Ideas]] | [[Category:Project Ideas]] |