#18376: New encoding structure for linear codes
-------------------------+-------------------------------------------------
Reporter: | Owner:
dlucas | Status: needs_review
Type: | Milestone: sage-6.8
enhancement | Resolution:
Priority: major | Merged in:
Component: | Reviewers:
coding theory | Work issues:
Keywords: | Commit:
Authors: David | 188b56f3367da3bcd1e5298dc012c663f5f08025
Lucas | Stopgaps:
Report Upstream: N/A |
Branch: |
u/dlucas/encoder |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by dlucas):
Hello,
I think the term "lift" is not that good to describe such an operation.
The operation we're talking about here consists in taking an element of
the "bigger space" (the ambient space) to the "smaller space" (the message
space), while "lift" usually means going from the small space to the big
one.
Furthermore, I think it's not really intuitive when it comes to discovery
by <tab> completion: if one writes
`sage: C.<tab>` or `sage: E.<tab>` (with `C` a code and `E` an encoder)
and sees the word `unencode`, he understands immediately (imho) the
meaning of it, while the term "lift" does not seem to be that
straightforward.
--
Ticket URL: <http://trac.sagemath.org/ticket/18376#comment:11>
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.
