#20177: Better checks in GRS decoders
---------------------------------+------------------------
Reporter: dlucas | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-7.1
Component: coding theory | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
---------------------------------+------------------------
Description changed by dlucas:
Old description:
> Some checks on the output on `decode_to_code` for Gao, Berlekamp-Welch
> and Key-Equation Syndrome decoders are actually useless.
>
> I also noticed that the nature of the input code of GRS decoders is never
> checked: one can perform the following:
>
> ```
> C = codes.RandomLinearCode(10, 4, GF(7))
> D = codes.decoders.GRSGaoDecoder(C)
> ```
>
> and actually construct the decoder... Whose decoding methods will utterly
> fail with a terrible error message!
New description:
Some checks on the output on `decode_to_code` for Gao, Berlekamp-Welch and
Key-Equation Syndrome decoders are actually useless.
I also noticed that the nature of the input code of GRS decoders is never
checked: one can perform the following:
{{{
C = codes.RandomLinearCode(10, 4, GF(7))
D = codes.decoders.GRSGaoDecoder(C)
}}}
and actually construct the decoder... Whose decoding methods will utterly
fail with a terrible error message!
--
--
Ticket URL: <http://trac.sagemath.org/ticket/20177#comment:1>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
