Raul,
I'm using tags3 for your function:
tags3
┌──────┬───┬─────────┬───┬────
───────────────────────┬───┐
│STATUS│ │RESULT[0]│ │CONFIDENCE[0] =│ │
└──────┴───┴─────────┴───┴───────────────────────────┴───┘
The empty boxes actually carry the CR, LF, TAB character string defining
the closing tag for each parameter..
tags6 is the tag string for *Arie's* function:
tags6
┌──────┬──────┬─────────┬─────────────┬──────────────────┐
│start{│STATUS│RESULT[0]│CONFIDENCE[0]│UTTERANCE_FILENAME│
└──────┴──────┴─────────┴─────────────┴──────────────────┘
Arie uses the first element of his tag string to define the string that
starts each event. In our case that is the 'start{' string which identifies
the start of each event. Arie assumes that every line ends in CR, LF, TAB.
So he doesn't need to have the closing tag specified for each parameter.
The more I look over the data, the more I think that the function should
capture EVERY event in the log. Every event starts with 'start{' and ends
with '}end', so it is easy to spot all the events. If a specific event has
NO matching parameter tags in it, then the output will have a row of empty
boxes in it, The number of boxed columns in the output will be the number
of parameters asked for in the tag list. The number of boxed rows in the
output will be the total number of events in the whole text log file.
I think I also need to number each row in the output. However that is one
thing I CAN do myself.
Skip
On Wed, Nov 23, 2011 at 8:44 PM, Raul Miller <[email protected]> wrote:
> There are other reasons why mine might stop (like missing end tags).
>
> What definition are you using for tags6?
>
> --
> Raul
>
> > > >> > Raul
>
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
