#13090: Make LinearCode take minimum distance as a parameter
------------------------------------+---------------------------------------
Reporter: ppurka | Owner: wdj
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-5.1
Component: coding theory | Resolution:
Keywords: minimum distance | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
------------------------------------+---------------------------------------
Comment (by ppurka):
Replying to [comment:2 dimpase]:
> Good, but could you please insert references to the distance data you
are plugging in? E.g. I have no clue where to look for the minimum
distance of toric codes...
> You could insert some (#long time) tests to check your claims for
particular values...
I haven't touched the toric codes. The ones I specified the distance to
are (in order): `BinaryGolayCode`, `HammingCode`, `ReedSolomonCode`,
`TernaryGolayCode` and `WalshCode`. For these the distance is already
present in the documentation of the function. I can make some long tests
which force the computation of the distance.
Looks like I missed the `ExtendedBinaryGolayCode`,
`ExtendedTernaryGolayCode`. I will update the patch with the distances
from those codes.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13090#comment:3>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
