#19463: A coding/two_weight_db module
-------------------------+-------------------------------------------------
       Reporter:         |        Owner:
  ncohen                 |       Status:  needs_review
           Type:         |    Milestone:  sage-6.10
  enhancement            |   Resolution:
       Priority:  major  |    Merged in:
      Component:         |    Reviewers:
  coding theory          |  Work issues:
       Keywords:         |       Commit:
        Authors:         |  ddcb9e33d277f1fe16512bc8933f47e3b22f17c0
  Nathann Cohen          |     Stopgaps:
Report Upstream:  N/A    |
         Branch:         |
  u/ncohen/19463         |
   Dependencies:         |
-------------------------+-------------------------------------------------
Description changed by ncohen:

Old description:

> This ticket creates a new coding/two_weight_db module.
>
> In it are stored all codes that were stored in
> graphs/strongly_regular_db.pyx. I expect that this file will change
> heavily, if we end up enriching our list of two weight codes for their
> own sake.
>
> A first commit moves out of the `strongly_regular_graph` function the
> code that builds the database of small strongly regular graphs. Which
> turned out to be a good idea later, as building this list actually takes
> some time in order to guess the parameters of the SRG from the 2-weight
> code.
>
> Nathann

New description:

 This ticket creates a new coding/two_weight_db module.

 In it are stored all codes that were stored in
 graphs/strongly_regular_db.pyx. I expect that this file will change
 heavily, if we end up enriching our list of two weight codes for their own
 sake.

 A first commit moves out of the `strongly_regular_graph` function the code
 that builds the database of small strongly regular graphs. Which turned
 out to be a good idea later, as building this list actually takes some
 time in order to guess the parameters of the SRG from the 2-weight code.

 Nathann

 **Note** This ticket must not be merged while this note is here.

 This branch *moves* a chunk of code (list of graphs) to a different place,
 and checking that what is added matches what is removed must be done
 carefully when no other ticket adding a construction is being merged.

--

--
Ticket URL: <http://trac.sagemath.org/ticket/19463#comment:23>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to