FAQ: Difference between revisions

Jump to navigation Jump to search
1,051 bytes added ,  27 March 2012
→‎Coding: New FAQ on how to get involved with Octave development
(→‎Coding: New FAQ on how to get involved with Octave development)
Line 330: Line 330:


In addition to consulting Octave's source for the precise details, you can read the Octave manual for a complete high-level description of the algorithm that Octave uses to decide how to solve a particular linear system, e.g. how the backslash operator <tt>A\x</tt> will be interpreted. Sections [http://www.gnu.org/software/octave/doc/interpreter/Techniques-Used-for-Linear-Algebra.html#Techniques-Used-for-Linear-Algebra Techniques Used for Linear Algebra] and [http://www.gnu.org/software/octave/doc/interpreter/Sparse-Linear-Algebra.html Linear Algebra on Sparse Matrices] from the manual describe this procedure.
In addition to consulting Octave's source for the precise details, you can read the Octave manual for a complete high-level description of the algorithm that Octave uses to decide how to solve a particular linear system, e.g. how the backslash operator <tt>A\x</tt> will be interpreted. Sections [http://www.gnu.org/software/octave/doc/interpreter/Techniques-Used-for-Linear-Algebra.html#Techniques-Used-for-Linear-Algebra Techniques Used for Linear Algebra] and [http://www.gnu.org/software/octave/doc/interpreter/Sparse-Linear-Algebra.html Linear Algebra on Sparse Matrices] from the manual describe this procedure.
==How can I get involved in Octave development?==
Be around. Be social. Participate in the help and maintainers' mailing lists. Find things about Octave you don't like, and start thinking about how to fix them. Many people who now contribute to Octave first spent several years helping in the mailing list before they started to delve into the code. A good way to learn Octave is to understand the problems other people are having with it, so being helpful in the mailing lists not only helps Octave as a whole, but it also prepares you to be a better Octave contributor.
We also need help with this wiki and the manual, important tasks. The documentation is easier to patch, so you can discuss improvements to it and sumibt patches. Or just edit this wiki! Accurate bug reporting is also very useful. Find and report bugs, making an attempt to diagnose them. Eventually, you will also know how to fix them.
Also look at our [[Projects]] and [[GSoC Project Ideas]] if you need specific inspiration for coding tasks that we would like to get done.


=How do I...?=
=How do I...?=

Navigation menu