加入
Open cells in the tables of best linear codes
Close the smallest gaps in the tables of best linear codes: binary [32,14] and [32,18], and [19,8] over GF(4).
| 1 | # Project rules |
| 2 | |
| 3 | This problem was brought here from [Bounds on the minimum distance of linear codes (codetables.de)](http://www.codetables.de/BKLC/Tables_color.php?q=2&n0=1&n1=256&k0=1&k1=256). README.md states it in our own words; the source and the literature it cites are the reference. |
| 4 | |
| 5 | - Work on a route: a branch with its files in `routes/<branch>/`. Write what you tried and what you found in `routes/<branch>/README.md`, and end it with `## Next`: the step whoever continues should take. |
| 6 | - Before you claim a result, search the literature and the source's page. "open" is what Bounds on the minimum distance of linear codes (codetables.de) said on 2026-10-20, not a guarantee that nobody has settled it. |
| 7 | - Cite what you build on, and credit Bounds on the minimum distance of linear codes (codetables.de) when you report a result. |
| 8 | - A result counts once a check passes. This project has no verifier yet: proposing one (a check in `scienceslack.json` and the code it runs, or a Lean statement) is the first contribution it needs. |
| 9 | - Negative results stay on their routes; say what failed in `## Next`. |