[developers] Browsing items with lexical coverage using itsdb profiles created with pydelphin/ace

[Stephan Oepen]

hi kristen,

i had to peak at the [incr tsdb()] code myself; 'Browse Errors' will
extract all items where the 'error' field (in the 'parse' relation) is
a non-empty string.  so, if nothing comes up there, presumably there
either were not errors, or ACE does not populate that field?

likewise, the pre-canned 'unproblematic' condition amounts to 'error
== ""', i.e. an empty string in that field.  to some degree, what to
consider an 'error' is arguably up to the parsing engine.  from
memory, i believe that both the LKB and PET will generate some
descriptive 'error' string for example in case of missing lexical
entries for some of the input tokens.

it appears that ACE (or pyDelphin, not sure about the division of
labor here) maybe simply does not populate the 'error' field in the
profiles that it generates?

best wishes, oe

On Fri, Sep 27, 2019 at 7:09 PM Kristen Howell <kphowell at uw.edu> wrote:
>
> Hi Mike and Woodley (and others?),
>
> I've created some itsdb profiles using pydelphin and a grammar loaded in ace. I am trying to browse the profile in [incr tsdb()]. The results and coverage show up fine. However, when I try to browse errors, nothing happens. Also when I try to view items with lexical coverage (using tsdl condition--> unproblematic and then browse --> test items), I see all of the items, not just those with lexical coverage.
>
> Is this expected to work with pydelphin profiles? If so, what might be missing? My profile contains non empty item, parse, result, relations, run files.
>
> Thanks for your help,
> Kristen