Computations

Theorem 3 can be directly translated into an algorithm that computes $ \mathfrak{G}$-families. The algorithm simply computes the coset leaders of $\ensuremath{{\mathfrak{G}}}$-codes in the family, from which the remaining parameters may be easily deduced. This computation scheme has the advantage of being exponential in the co-dimension (i.e., the dimension of the dual code) rather than the dimension or the length. Thus, this algorithm is efficient for high-rate codes, and it is presented in Algorithm 1.

\begin{figure}
% latex2html id marker 848
\begin{theorem_type}[algorithm][algori...
...he new-\\
\>\>\hspace{1em} ly computed coset leaders.
\end{tabbing}\end{figure}

In Algorithm 1 we reuse our earlier notation that ${\Delta_i} = d -
\ensuremath{\operatorname{wt}}(f(\ensuremath{ {\mathfrak{G}}_{i-1}}))$. Note that we assume that the coset leaders of the seed code are known or trivially derivable, as is often the case. The correctness of the algorithm follows immediately from Theorem 3. Moreover, we can also compute the running time and space of this algorithm in terms of $ \widehat{m}$ $ \mbox{$\stackrel{\mathrm{\mbox{def}}}{=}$}$ nm - m, the co-dimension of the m-th $\ensuremath{{\mathfrak{G}}}$-code,

Lemma 4   Using an oracle for computing the generating mapping, Algorithm 1 runs in space O(2$\scriptstyle \widehat{m}$) and time O(nmm2$\scriptstyle \widehat{m}$).

An oracle is simply a black box that computes a given function in constant time. In this case, we assume the existence of an oracle for computing the generating mapping because the complexity of such a computation can vary greatly among mappings. The proof of Lemma 4 follows from a straightforward analysis of the pseudo-code for Algorithm 1.

For the specific case of distance 4 lexicodes, this algorithm is particularly fast, since Brualdi and Pless [3, Thm.3.5] show that, under these circumstances:

m = nm - 2 - $\displaystyle \left\lfloor\vphantom{ \log_2 (n_m-1) }\right.$log2(nm - 1)$\displaystyle \left.\vphantom{ \log_2 (n_m-1) }\right\rfloor$ (13)

so that Lemma 4 reduces to time O(nmm log(nm)) and space O(nm). This is not surprising given that the distance 4 lexicodes are simply shortenings of the extended Hamming codes [5].

The analysis of Algorithm 1 assumes an oracle computation of the generating mapping. For the case of lexicodes and trellis-oriented lexicodes, however, Method 1 provides an efficient means of computing this mapping in time $O(n_m \times
\ensuremath{\char93 \mbox{\texttt{COSET}}_{m}})$ and O(nm) space, where $\ensuremath{\char93 \mbox{\texttt{COSET}}_{m}}$ represents the number of cosets in the m-th corresponding $\ensuremath{{\mathfrak{G}}}$-code. As in the case of lexicodes and trellis-oriented codes, the overhead of computing $f(\ensuremath{ {\mathfrak{G}}_{i-1}})$ is usually eclipsed by the running time of the remainder of the algorithm.

Corollary 3   Algorithm 1 requires time O(nmm2$\scriptstyle \widehat{m}$) and space O(2$\scriptstyle \widehat{m}$) to compute lexicodes and trellis-oriented lexicodes.

The complexity of Algorithm 1 is thus bounded by the co-dimension of the code and by the difficulty of computing the generating mapping. Under practical conditions, we were able to compute lexicodes well beyond length 44 initially reported in [5].

In addition, we were able to construct trellis-oriented codes with code parameters rivaling those of lexicodes, but with much better trellis state complexities. As an example, we generated a trellis-oriented $ \mathfrak{G}$-code with code parameters similar to lexicodes, but with better state complexity than the corresponding BCH codes heuristically minimized in [7]. These result were predicted by [7] and are demonstrated in Table 4.


Table 4: A comparison of the trellis state complexities of the (31, 16, 7) trellis-oriented lexicode (TRE) and a (31, 16, 7) extended BCH code (BCH) heuristically minimized in [7] .
TRE: 0: 1: 2: 3: 4: 5: 6: 6: 7: 8: 9: 8: 9: 8: 7: 6: 7: 6: 6: 6: 5: 5: 4: 3: 4: 4: 4: 3: 3: 2: 1: 0
BCH: 0: 1: 2: 3: 4: 5: 6: 6: 7: 8: 9: 8: 9: 8: 7: 6: 7: 8: 9: 8: 9: 8: 7: 6: 7: 6: 5: 4: 3: 2: 1: 0


Finally, the trellis state bounded codes that we have computed show improvements, for various code parameters, over the state-bounded codes computed in [15] using different techniques.