[developers] results after edge limit reached?
bec.dridan at gmail.com
Sat Aug 15 14:18:14 CEST 2009
Maybe this related to an inconsistency I am seeing between test runs
using the export script (with --terg) and running cheap with the
Running cheap directly, all time outs have readings = -1, but through
the export script they are mostly 0, and some greater than 0. As you
say, it changes the [incr tsdb()] statistics. Should I assume the export
script represents consensus and time outs should be considered in the
time and memory use figures? (Ultimately I'm using a perl script anyway,
to save loading the fine system, so my calculations can go either way.)
Stephan Oepen wrote:
> i have no source code accessible right now, but i'm pretty sure that PET
> vs. the LKB differ in this respect. from the profiling point of view, i
> (used to) think that items that hit any kind of resource limit should be
> flagged (readings = -1) and excluded from many of the [incr tsdb()]
> statistics. years ago, stefan müller argued forcefully for results that
> had been found at that point to be returned, nevertheless, which is what
> PET implements today. note that the time-out is recorded in the error
> field alright, but seeing that the search for analyses was not complete,
> selective unpacking cannot guaratee returning the correct n-best list.
> in the LKB, on the other hand, time-outs are signalled (internally) by
> raising an exception. in these cases, control is returned immediately
> to [incr tsdb()], and no attempt is made at enumerating solutions.
> hence, i would expect that you are seeing the results of a complete
> search whenever readings >= 0. this should be true of parsing and
> generation alike (in the LKB).
> all best, oe
> On Aug 14, 2009, at 1:47 PM, Michael Wayne Goodman
> <goodmami at u.washington.edu> wrote:
>> Hi there,
>> In parsing with PET and (particularly) generation with the LKB, if the
>> edge-limit has been exhausted after some results have been found, are
>> those results returned? I checked some items where the edge-limit was
>> reached and did not observe any results for them, but I can't be
>> certain that that will always be the case.
>> Any help or insight would be appreciated.
>> -Michael Wayne Goodman
More information about the developers