-
-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
__call__(message)
on a linear code or encoder should return a codeword.
#20087
Comments
Branch: u/dlucas/shortcut_to_encode |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:3
Setting this as New commits:
|
Author: David Lucas |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
I added the same mechanism with codes: let
|
comment:7
There's a doctest failing which indicates the test suite is broken for codes. It picks |
comment:8
Because of the above, which is related to the way linear codes are set in the category framework, it seems impossible to do the proposed improvement. Setting this to invalid/won't fix. |
This comment has been minimized.
This comment has been minimized.
comment:9
This issue is not a show-stopper: instead of Re-opening. |
E(message)
for a linear code encoder E
should encode message
__call__(message)
on a linear code or encoder should return a codeword.
comment:11
Done. Maybe leave this review for Daniel as he wanted to do it? I just Cc'd him on this ticket. |
comment:12
Hi, Maybe the check of whether the vector passed is a codeword or not can be done before passing it to the encode function. That way if a user means to pass a codeword rather than the message, and passed th wrong vector, he/she will be notified. |
comment:13
David, didn't you accidentally put the Encoder-related code on the GRS encoder? It should be on the abstract class Replying to @sagetrac-panda314:
As far as I can see, the check in |
comment:23
Yes, it's a good idea. Done in the last commit. |
comment:24
are the changes compiling? The copy of this branch is not compiling on my local pc (new to sage, am i missing something?). Here's the error: Detailed message is, Traceback (most recent call last): Error building the Sage library make: *** [sage] Error 1 |
comment:25
It's compiling on my side. According to the error report you sent, a file is missing on your side. |
Changed branch from u/dlucas/shortcut_to_encode to u/danielaugot/shortcut_to_encode |
comment:27
I used the terminology "ambient space" in the doc string, to avoid being specific in details. Daniel New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from u/danielaugot/shortcut_to_encode to u/jsrn/shortcut_to_encode |
comment:32
I mistakenly pushed another branch on top of this one. I've reverted it now -- sorry for the noise. |
Changed keywords from none to rd3 |
comment:33
Doc string of the |
Reviewer: Clément Pernet |
Changed branch from u/jsrn/shortcut_to_encode to u/cpernet/shortcut_to_encode |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:36
It's all good, after the two minor docstring edits that I've pushed to the ticket. Positive review. |
Changed branch from u/cpernet/shortcut_to_encode to |
If
E
is anEncoder
for aLinearCode
C
, one can useE.encode(message)
, wheremessage
is in the appropriate space.E(message)
should default to the same behaviour. So shouldC(message)
.Be aware that the category framework specifies that
C(c) = c
ifc in C
. This needs to be handled.CC: @sagetrac-dlucas @ClementPernet @jlavauzelle @sagetrac-danielaugot
Component: coding theory
Keywords: rd3
Author: David Lucas
Branch/Commit:
8ba64ee
Reviewer: Clément Pernet
Issue created by migration from https://trac.sagemath.org/ticket/20087
The text was updated successfully, but these errors were encountered: