[developers] The WeSearch interface

[Alexandre Rademaker]

Hi Stephan,

Thank you for your answer. I am actually trying to reproduce the results from https://www.aclweb.org/anthology/W15-2205/ and the code that transforms EDS/MRS to RDF seems to live in the WeSearch Java code, right? Anyway, having the WeSearch interface running will be also VERY helpful. 

In the future, I surely would like to explore more and understand the lisp code that redwoods script is calling, the main part seems to be in the TSDB package and the function `browse-trees` but there are many auxiliar scripts loaded before it and many variables and other functions from the LKB and TSDB packages. It is still not clear to me how to decouple the lisp code from the LOGON scripts and all PVM related stuff.


I have created the profile with:

% delphin mkprof --input sample.txt --relations ~/hpsg/logon/lingo/lkb/src/tsdb/skeletons/english/Relations --skeleton treebank

Then with pydelphin I analysed it with ACE:

////

from delphin import ace
from delphin import tsdb
from delphin import itsdb
ts = itsdb.TestSuite('treebank')
with ace.ACEParser('erg.dat') as cpu:
  ts.process(cpu)

////


For exporting, I tried many different alternatives of parameters. Unfortunately, I didn’t find much documentation about the redwoods script parameters. I would like to obtain the eds, mrs and dm (for that, I remember an old emails from you pointing to a python script that I will need to revisit) formats. Many combinations of parameters result in case (1) below. The last try gives me the result (2).


1) 

$ ./redwoods --binary --erg --default --composite --target /tmp --export mrs,eds --active all /home/user/tmp/treebank
redwoods: invalid `erg' profile `/home/user/tmp/treebank'; exit.

2) 

$ ./redwoods --binary --target /tmp --export mrs,eds /home/user/tmp/treebank

exporting `/home/user/tmp/treebank' [1 -- 1001]

International Allegro CL Enterprise Edition
10.0 [64-bit Linux (x86-64)] (Feb 20, 2019 18:22)
Copyright (C) 1985-2015, Franz Inc., Oakland, CA, USA.  All Rights Reserved.

This standard runtime copy of Allegro CL was built by:
   [TC13152] Universitetet i Oslo

; Loading /home/user/logon/dot.tsdbrc
; Loading /home/user/.tsdbrc

[changing package from "COMMON-LISP-USER" to "TSDB"]
TSNLP(1): NIL
TSNLP(2): Error: "" does not exist, cannot load
  [condition type: FILE-DOES-NOT-EXIST-ERROR]

Restart actions (select using :continue):
 0: retry the load of
 1: skip loading
 2: Return to Top Level (an "abort" restart).
 3: Abort entirely from this (lisp) process.

[changing package from "TSDB" to "LKB"]
[1] LKB(3): :pop

[changing package from "LKB" to "TSDB"]
TSNLP(3): EOF
Really exit lisp [n]?


Best,
Alexandre



> On 5 Jul 2020, at 18:40, Stephan Oepen <oe at ifi.uio.no> wrote:
> 
> hi alexandre,
> 
> it appears roman (who worked on WSI improvements at UW for a while) created the script that you are missing.  i am not sure i actually have a copy myself (and cannot easily check while traveling this week).
> 
> but we used to create the WSI indices from the standard export files created by the LOGON ‘redwoods’ script.  that should work with any valid [incr tsdb()] treebank, no matter how it was created. somewhere in the ERG, there should be a file Notes, or Readme, or the like with export instructions.
> 
> so, how did you create your treebank(s), how do you call the ‘redwoods’ script, and (most importantly) what exactly happens?
> 
> best wishes, oe