<div><div dir="auto">the export code will want to rebuild the derivation, i.e. the version of the grammar loaded needs to be fully compatible with the treebank (or parsed profile). i wonder whether ‘a_det_rbst’ is available at the time of exporting? it sounds like a mal-configuration of the grammar, maybe? which you would have to match on the LKB side then, e.g. push the right feature or load the right ‘script’ file?</div></div><div dir="auto"><br></div><div dir="auto">greetings from the road (metaphorically), oe</div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 28 Jul 2020 at 16:38 Alexandre Rademaker <<a href="mailto:arademaker@gmail.com">arademaker@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi Stephan,<br>
<br>
While processing a sample of the wordnet glosses, the redwoods script produced two invalid .gz files. One example is for the sentence: "a historical region in central and northern Yugoslavia; Serbs settled the region in the 6th and 7th centuries"<br>
<br>
See the derivation node:<br>
<br>
(527 #<Printer Error, obj=#x10000000fc9: Null lexical entry type NIL>)<br>
<br>
In the result file of the profile, the derivation node looks fine, the 334.gz is attached.<br>
<br>
(527 a_det_rbst 0.000000 0 1 ("a" 347 "token [ +FORM \\"a\\" +FROM \\"0\\" +TO \\"1\\" +ID *diff-list* [ LIST *cons* [ FIRST \\"0\\" REST *list* ] LAST *list* ] +TNT null_tnt [ +TAGS *null* +PRBS *null* +MAIN tnt_main [ +TAG \\"DT\\" +PRB \\"1.0\\" ] ] +CLASS alphabetic [ +CASE non_capitalized+lower +INITIAL + ] +TRAIT token_trait [ +UW - +IT italics +LB bracket_null [ LIST *list* LAST *list* ] +RB bracket_null [ LIST *list* LAST *list* ] +LD bracket_null [ LIST *list* LAST *list* ] +RD bracket_null [ LIST *list* LAST *list* ] +HD token_head [ +TI \\"<0:1>\\" +LL ctype [ -CTYPE- string ] +TG string ] ] +PRED predsort +CARG \\"a\\" +TICK + +ONSET c-or-v-onset ]”))<br>
<br>
I am trying to understand the lisp code of redwoods.lisp, but without being able to load it in my slime environment, navigating in the source code and debugging is a nightmare. I know that export-tree is doing more than just copy the derivation tree from the profile, but I didn’t understand what it is doing with the derivations, it is hard to have the `big picture`. BTW, you really like the `loop` macro! ;-)<br>
<br>
These errors cause the dtm script to fail, although I should not expect it to work with the current trunk version of ERG, dm.cfg was not changed since 2012.<br>
<br>
% svn info etc/dm.cfg<br>
Path: etc/dm.cfg<br>
Name: dm.cfg<br>
Working Copy Root Path: /Users/ar/hpsg/terg<br>
URL: <a href="http://svn.delph-in.net/erg/trunk/etc/dm.cfg" rel="noreferrer" target="_blank">http://svn.delph-in.net/erg/trunk/etc/dm.cfg</a><br>
Relative URL: ^/erg/trunk/etc/dm.cfg<br>
Repository Root: <a href="http://svn.delph-in.net" rel="noreferrer" target="_blank">http://svn.delph-in.net</a><br>
Repository UUID: 3df82f5b-d43a-0410-af33-fce91db48ec5<br>
Revision: 28882<br>
Node Kind: file<br>
Schedule: normal<br>
Last Changed Author: oe<br>
Last Changed Rev: 12172<br>
Last Changed Date: 2012-12-01 18:54:20 -0200 (Sat, 01 Dec 2012)<br>
Text Last Updated: 2019-02-07 20:21:10 -0200 (Thu, 07 Feb 2019)<br>
Checksum: b8097dfbd5cc9b9d654233314006f8c8b0fcecaa<br>
<br>
Since my goal is to have at least one bi-lexical format in the WSI interface, I am still trying to understand what the dtm (converter) does. The converter.pdf explains how to use the code, input/output, but it doesn't disclose its logic, the high-level description of the system. Eventually, we can reimplement the dtm using pydelphin (see <a href="https://github.com/delph-in/pydelphin/issues/122" rel="noreferrer" target="_blank">https://github.com/delph-in/pydelphin/issues/122</a>). The error that I have reported in my previous message when I call redwoods with the dm in `--export input,derivation,mrs,eds,dm` is probably related to what I am showing here since the `dm-construct` function end ups calling the python dtm.py code. Finally, the handling of `:dm` keyword was not copied to the lkb-fos/src/tsdb/lisp/ source code. But I am sure you and John are both aware of that.<br>
<br>
As always, comments and possible references are welcome! ;-)<br>
<br>
Best,<br>
Alexandre<br>
<br>
PS: I know that all these errors are expected since, as you said, `I am venturing into unexplored territory` by mixing the ‘classic’ DELPHIN toolchain with the 'modern tools from the pacific northwest’. Yes, I am processing the profiles with ACE/pydelphin and ‘exporting’ data (derivation, input, MRS and EDS) from them with redwoods lisp code. But I assume we aim at have interoperability between the tools, right? That is my motivation to keep reporting the errors. Please, correct me if I am wrong.<br>
<br>
<br>
<br>
<br>
</blockquote></div></div>