TCA creates a temporary bank in the /Z/ dynamic store and divides it into
two parts:-
Input Buffer
This is a large buffer that holds all the events in the
time gate.
Output Buffer
This is a small buffer that holds all the associations for
the current primary.
The user controls the size of these two buffers with the commands e.g:-
$tca_buffer_frac 1.0
$tca_ambig_max 10
These sizes are recorded in the output log.
Making the buffers too small results in
overflows. In this case TCA will abort if the command:-
$tca_quit_on_ovfl $on
has been issued, otherwise it continues but some associations will be
lost.
If an overflow occurs TCA will attempt to calculate the capacity required
to prevent the overflow and writes this to the output log but, in the case of
input buffer overflow, this is going to be little more than a guess. Increasing
a buffer size may involve increasing the size of the /Z/ store.
The best way to make efficient use of the buffer
is to include tests that define primaries and secondaries as tightly as
possible. That way anything that can be neither is not placed in the buffer.
