Differences between revisions 5 and 7 (spanning 2 versions)
Revision 5 as of 2015-02-05 12:58:30
Size: 1298
Editor: schilly
Revision 7 as of 2015-02-08 15:11:51
Size: 1386
Editor: vdelecroix
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Projects and ideas for GSoC 2015 = = Project ideas for GSoC 2015 for Sage =
Line 3: Line 3:
== Sage ==
Line 5: Line 4:
=== Notebook mode with execution from top to bottom === == Notebook mode with execution from top to bottom ==
Line 13: Line 12:

== Native GUI ===
== Native GUI ==
Line 19: Line 16:
=== generic dispatcher === See also [[https://groups.google.com/forum/#!topic/sage-devel/87Rlenvcfrs|this thread on sage-devel]].

== generic dispatcher ==

Project ideas for GSoC 2015 for Sage

Notebook mode with execution from top to bottom

In the current notebook (both Sage notebook and IPython notebook) the cells can be executed in any order. From a teaching point of view this is terrible and from a scientific point of view this leads to highly non reproducible computations.

The purpose of this task is to have a new mode for the IPython notebook that would force computations from top to bottom. If a cell is executed, then the state in which it is executed must be the one you obtain by executing all the cells above it. In order to make it work, one needs to save the Python state after each cell.

note: this is note completely Sage oriented... (see with IPython people)

Native GUI

Adapt Spyder to work with Sage.

See also this thread on sage-devel.

generic dispatcher

In Sage there are various places where we have several possibilities to execute a task (e.g. calling pari or gap or a native sage function). It would be interesting to have a way of choosing the default parameters by performing benchmarkings at build time. That would also allow to check coherency between various implementations.

Android App

iOS App



GSoC/2015 (last edited 2015-03-16 20:44:44 by schilly)