[developers] Latest ERG not generating unknown names with ACE

[Dan Flickinger]

Mike,


I don't think you'll see much negative effect just now if you comment out that file, since those post-generation rules are intended as a declarative way of dealing with several orthographic conventions many of which are are still dealt with procedurally in the generator code.  From what I see, those older procedural solutions are still in effect, so when I comment out that `post-generation' file, I still see sentence-initial capitalization, attaching of possessive |'s|, and removal of the space between hyphenated tokens.  (I can't remember just now what the `split_mwe" rule is intended for.)


Eventually, we hope to have those rules working well, so we can allow the generator code to get cleaned up by removing these language-specific and grammar-specific accommodations.


 Dan


________________________________
From: Michael Wayne Goodman <goodmami at uw.edu>
Sent: Saturday, April 15, 2017 5:15 PM
To: Dan Flickinger
Cc: Woodley Packard; Stephan Oepen; developers at delph-in.net
Subject: Re: [developers] Latest ERG not generating unknown names with ACE

Stephan:

I'm using ACE. It seems to read SimpleMRS v1.1 (TOP, ICONS, MRS-level lnk and surface values; but it does not recognize EP-level surface strings), but it still writes the v1.0 format.

And you're right that I forgot to (lkb::index-for-generator), but I still get the same error after doing so. Perhaps there's something misconfigured on my computer. If you think this error is interesting I can start a separate thread on developers for it.

Dan and Woodley:

Thanks for finding the source of the problem. I'm having trouble getting generation working with the LKB right now (see above), but do you know if this affects both the LKB and ACE? Also, do the post-generation rules currently do anything useful that I'll miss if I turn them off as you've described?

On Sat, Apr 15, 2017 at 4:28 PM, Dan Flickinger <danf at stanford.edu<mailto:danf at stanford.edu>> wrote:

Woodley, your prediction was a good one.  If I comment out the loading of that file in `english.tdl' and recompile, then the unknown proper names work right again, and similarly if I comment out each of the rules in the file but load it, all is still well.  But if I uncomment any one of the rules, we lose the proper names again.  So it would seem that the very act of tampering with the orthography in post-generation interacts badly with whatever the clever step is that causes the CARG value of the unknown proper name to be realized as its surface orthography.


 Dan


________________________________
From: developers-bounces at emmtee.net<mailto:developers-bounces at emmtee.net> <developers-bounces at emmtee.net<mailto:developers-bounces at emmtee.net>> on behalf of Woodley Packard <sweaglesw at sweaglesw.org<mailto:sweaglesw at sweaglesw.org>>
Sent: Saturday, April 15, 2017 1:59 PM
To: Stephan Oepen
Cc: Michael Wayne Goodman; developers at delph-in.net<mailto:developers at delph-in.net>
Subject: Re: [developers] Latest ERG not generating unknown names with ACE

I wonder whether something may be going on with the ACE-only post-generation token mapping rules?  I believe Dan has started toying with those, although I lack the proper internet connection to investigate this hypothesis currently.

Woodley



On Apr 15, 2017, at 1:38 PM, Stephan Oepen <oe at ifi.uio.no<mailto:oe at ifi.uio.no>> wrote:

>> I attach the relevant MRSs (same sentence; one created with the ERG trunk
>> and the other with the 1214 version).
>
> these MRSs appear equivalent in content; the ERG trunk has not yet
> turned on predicate normalization by default (because that switch also
> turns on SEM-I–based MRS processing, and finalizing the SEM-I prior to
> a release currently is a non-trivial process, hence not applied to the
> trunk yet), hence the spurious string vs. type distinctions and _rel
> suffixes on predicates.  also, which engine did you use?  it still
> outputs old-style LTOP (which should be TOP nowadays).
>
> anyway, the MRSs look fine and give the expected result in the LKB generator:
>
> LKB(42): (pprint
>          (lkb::generate-from-mrs
>           (mrs::read-mrs-from-file "~/Downloads/unity-logon.mrs")))
>
> ("Ubuntu is dropping unity.")
> LKB(43): (pprint
>          (lkb::generate-from-mrs
>           (mrs::read-mrs-from-file "~/Downloads/unity-trunk.mrs")))
>
> ("Ubuntu is dropping unity.")
>
> —i suspect you might not have run (lkb::index-for-generator) after
> loading the grammar?
>
> best, oe
>




--
Michael Wayne Goodman
Ph.D. Candidate, UW Linguistics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.delph-in.net/archives/developers/attachments/20170416/c211f5bd/attachment-0001.html>