#20526: A benchmarking tool for linear codes
-------------------------------------+-------------------------------------
Reporter: dlucas | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-7.2
Component: coding theory | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/dlucas/benchmarking_tool | 8e363dd7ecf203cc4f203ea2b985573e4d59423c
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jsrn):
Replying to [comment:13 dlucas]:
> > Hmm, probably that's the reason I called that exception
DecodingFailedError in Codinglib :-)
>
> Yes, that's much better! Do you think changing its name is worth the
deprecation warning?
Hmm, how would you even deprecate this? Issue a deprecation warning only
when the error is thrown?
But, thinking more about it, this name is also no good: the exception is
used by a decoding algorithm when it realises that something went wrong,
e.g. the polynomial division in Berlekamp-Welch doesn't go well. But this
is exactly a case of `DecodingFailure\DecodingError` where `\` indicates
set difference; that is, it is a decoding failure that is surely not a
decoding error (since no codeword is returned).
Justesen and Høholdt do not give a name to this event, but we need such a
name for the decoding exception.
`DecodingException`? `DecodeAbortError`? `DecodingAborted`?
--
Ticket URL: <http://trac.sagemath.org/ticket/20526#comment:15>
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.
