Punctured code status

[David Lucas]

This is a descriptive issue to keep track of progress on punctured codes' implementation. It lists all related issues and gives a glimpse on the key features.

• Issue #125 on the dimension of punctured codes
• Issue #126, #136 on minimum distance computation
• Issue #127 on decoder(s) for punctured codes
• Issue #135 on flattening

Keypoints:

• class skeleton is done, basic functionalities working (can create a code and play around with words)
• one encoder based on a generator matrix is available
• methods returning a vector were overwritten to go through the original code (see issue #128 on encoding)
• programs support the creation of punctured codes with several puncture points (pass these as a list), but several things are untested when passing several points
• basic test session ok, and advanced test sheet written (even with limit cases like 0-code)
• code (python, not math) can be optimized at several places (eg try-all strategy in decoding)
• one decoder available

[David Lucas]

Available in trac #19422