#18376: New encoding structure for linear codes
-------------------------+-------------------------------------------------
Reporter: | Owner:
dlucas | Status: needs_review
Type: | Milestone: sage-6.10
enhancement | Resolution:
Priority: major | Merged in:
Component: | Reviewers:
coding theory | Work issues:
Keywords: | Commit:
Authors: David | 43ec64071da5ff5e5f5f700fe61b53f8fa11330e
Lucas | Stopgaps:
Report Upstream: N/A |
Branch: |
u/dlucas/encoder |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by dlucas):
I did that because as far as I tested it, in Sage a vector space of
dimension 0 contains only the empty vector `()` which is I think not
correct mathematically speaking (it should contain the zero vector).
So instead of wondering if I should return the zero of the message space
or the empty vector, the former being the right mathematical answer, the
latter the Sage answer, I chose to return an exception.
Note that before unencoding over a code of dimension 0 "returned'
{{{
Traceback (most recent call last):
...
TypeError: unable to find a common ring for all elements
}}}
I'm not strongly for this solution, so if you prefer to return either `()`
or `0` I'm fine with that.
But returning 0, while being the expected mathematical answer, comes back
to returning something which is *not* an element of the message space -
according to the Sage representation of vector spaces of dimension 0.
--
Ticket URL: <http://trac.sagemath.org/ticket/18376#comment:47>
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.
