Changes between Version 46 and Version 47 of Ticket #11880


Ignore:
Timestamp:
04/10/12 10:14:08 (8 years ago)
Author:
ncohen
Comment:

One patch to apply them all,
One patch to use them,
One patch to contain them all,
And in Sage-5 bind them.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11880 – Description

    v46 v47  
    44sage/graphs/isgci.py
    55}}}
    6 That is a '''first implementation''' of an interface between Sage and the Graph Classes database ISGCI ![1]. With this interface, the XML content of the database can be read using dictionaries and lists (much easier to work with), and some operations are implemented like the comparison (relatively to inclusion) of graph classes.
     6
     7That is an interface between Sage and the Graph Classes database ISGCI[1]. With this interface, the XML content of the database can be read using dictionaries and lists (much easier to work with), and some operations are implemented like the comparison (relatively to inclusion) of graph classes.
    78
    89There will be more work needed on this new feature, for instance the implementation of an easy way to query the database.
    910
    10 Along with the patch, two `.sobj` files should be added to the directory `$SAGE_ROOT/data/graphs/`. These files are an `.sobj` version of the database that I created on my own computer.
     11The database used by this patch is installed in Sage through the "graphs" spkg, which this ticket updates.
    1112
    12 When this patch will be merged into Sage, it is likely that users that do not update their version of Sage will progressively then be working with an outdated version of the database, as the version will be the one used the day they downloaded their copy of Sage. To avoid that, this patch implements a function `sage.graphs.isgci.update_db()` that downloads a new version of the database from ISGCI's website and updates the current `.sobj` files.
    13 
    14 Hence, instead of using my two files attached to this ticket, one can also call this method which will create them automatically.
     13When this patch will be merged into Sage, it is likely that users that do not update their version of Sage will progressively then be working with an outdated version of the database, as the version will be the one used the day they downloaded their copy of Sage. To avoid that, this patch implements a function lets the users update their local copy when necessary.
    1514
    1615I tried to make the documentation clear enough about all that is currently possible with ISGCI.
     
    2827
    2928 * [attachment:trac_11880-ISGCI-all-in-one.patch]
    30  * [attachment:trac_11880-XML_storage.patch]
    3129
    3230Or all of the following :