#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: | 73930f28c0d15ac1cbe1b6fd2741817608dec0ec
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
u/ncohen/19463 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by jsrn):
> As you saw in the emails I sent about 2-weight codes the plan is to make
it the 'new database' for those objects, and from what Eric Chen was
saying it seems that all these codes belong to known families that we will
be able to generate easily later.
My suggestion would make even more sense in this case, almost no matter
how the future code will be written. Encapsulating the two-weight code
properties and algorithms in a class is much more tidy and more easily
supports computing things on demand.
--
Ticket URL: <http://trac.sagemath.org/ticket/19463#comment:14>
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.
