<div dir="ltr">Thank you Stephan. Would the 'parse' relations be the lines the parse file? They each look something like this:<div>0@0@0@-1@@-1@@0@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@-1@@@<br></div><div>Perhaps this means that the error field among other things is not being populated?</div><div>Then the question for Mike and/or Woodley would be if it is expected to be populated.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 27, 2019 at 12:33 PM Stephan Oepen <<a href="mailto:oe@ifi.uio.no">oe@ifi.uio.no</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">hi kristen,<br>
<br>
i had to peak at the [incr tsdb()] code myself; 'Browse Errors' will<br>
extract all items where the 'error' field (in the 'parse' relation) is<br>
a non-empty string. so, if nothing comes up there, presumably there<br>
either were not errors, or ACE does not populate that field?<br>
<br>
likewise, the pre-canned 'unproblematic' condition amounts to 'error<br>
== ""', i.e. an empty string in that field. to some degree, what to<br>
consider an 'error' is arguably up to the parsing engine. from<br>
memory, i believe that both the LKB and PET will generate some<br>
descriptive 'error' string for example in case of missing lexical<br>
entries for some of the input tokens.<br>
<br>
it appears that ACE (or pyDelphin, not sure about the division of<br>
labor here) maybe simply does not populate the 'error' field in the<br>
profiles that it generates?<br>
<br>
best wishes, oe<br>
<br>
On Fri, Sep 27, 2019 at 7:09 PM Kristen Howell <<a href="mailto:kphowell@uw.edu" target="_blank">kphowell@uw.edu</a>> wrote:<br>
><br>
> Hi Mike and Woodley (and others?),<br>
><br>
> 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.<br>
><br>
> 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.<br>
><br>
> Thanks for your help,<br>
> Kristen<br>
</blockquote></div>