PREV INDEX NEXT

Author: Unknown
Subject: d-delay
Date: Wednesday, 04 Nov 2020, 18:46:35

If we use d-delay, are there any problems in alignment between encode and decode that must be accounted when pruning because it is one-tick behind? 

When it says d-delay is one tick behind, does that mean it is one code behind? Whenever I call pruning (through a special code), decode has 2^NBITS entries in the table, but I thought it would have 2^NBITS-1 entries in the table.
PREV INDEX NEXT