#19623: Syndrome decoder is not a syndrome decoder
-------------------------------------+-------------------------------------
Reporter: dlucas | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-7.1
Component: coding theory | Resolution:
Keywords: | Merged in:
Authors: David Lucas | Reviewers: Julien Lavauzelle
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/dlucas/generic_decoders | 4d70e2c87e7c2e50171ee24ca7c6200ff29d0250
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by dlucas):
Okay, thanks!
> Yes, a list should be made of the "common" types (all we have used so
far) of decoders, and an explanation. In the doc-string of decoder_type,
there should be a clear explanation on how to look up what they mean.
(another ticket of course). Perhaps even in the doc-string for
decoder_type, if the explanations can be made short enough, since the
function is always the original Decoder.decoder_type.
Mmhh, I'm not sure i'll be able to keep it short, especially as it might
grow when we will implement new decoders.
I'll give it a try, and if it's too long, I will add an extra paragraph
dedicated to decoders and types in #19897.
--
Ticket URL: <http://trac.sagemath.org/ticket/19623#comment:28>
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.
