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
How to store information on codes built from other ones #21062
Comments
comment:1
If I understand it well, the new coding theory framework aims at keeping as much information as possible on the (algebraic) structure of the manipulated codes. I also noticed that this structure is memorized even after building a new code from older ones (I'll call this a "code derivation"). For instance, puncturing (resp. extension) is made in a way that the punctured (resp. extended) code keeps a pointer to the original code (and this is useful for decoding, or getting bounds on the parameters). It's natural to think that in the future, Sage intents to have many other linear code derivations (dual code, sum, product or intersection of two codes, concatenation, trace code, subfield subcode, etc.). But I find a bit messy to define a class for each kind of derivation, especially for the sum and the dual code (I can't imagine a DualCode or a SumCode class). If you agree with my feeling (of course it's arguable), maybe it would be better to instanciate these derivations in a different way. I propose the following. Let
For instance, if
and the Well, maybe these considerations come a bit early in the development, but I'll be glad to read your ideas about them. Julien |
comment:2
Hello Julien, Thanks for writing this! Elaborating a bit on your structure, -well, that's what we discussed a few hours ago It's the first idea that came to my mind, and is of course open to discussion! David |
This ticket is about discussing the way to store the information on the structure of codes built from other ones.
CC: @sagetrac-dlucas @johanrosenkilde @ClementPernet
Component: coding theory
Issue created by migration from https://trac.sagemath.org/ticket/21062
The text was updated successfully, but these errors were encountered: