<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Thanks, this is the type of feedback I was looking for. Does the lexical type info fit into the restful interface, or is it something you'd like for other purposes? There is of course all manner of information contained in the grammar that is not exposed by normal interfaces.</div><div>-Woodley<br><br><br></div><div><br>On Jun 23, 2016, at 5:30 PM, Michael Wayne Goodman <<a href="mailto:goodmami@uw.edu">goodmami@uw.edu</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Thanks, Woodley,<div><br></div><div>I was able to compile ACE (with a change to Makefile to dynamically link libutil instead of statically; if anyone wants my notes for compiling just ask).</div><div><br></div><div>The data now output by ACE will make things much easier, so thanks for that! I compared the output to what Stephan offers from his RESTful server, and note a couple of differences:</div><div><br></div><div>1. tcpu</div><div>2. rule and lexical types in the derivation (e.g. the <span style="line-height:normal;white-space:pre-wrap">"arrive_v1" in the derivation for "Abrams arrived." would have type "v_-_le")</span></div><div><br></div><div><span style="line-height:1.5">I can get (1) with --tsdb-notes, but when combined with --tsdb-stdout it is concatenated to the stdout line instead of appearing on its own. E.g.:</span></div><div><span style="line-height:1.5"> [...] </span>(:aedges . 23) NOTE: tsdb parse: (:total . 9) [...]</div><div>Since the syntax is the same, maybe they can be concatenated without the "NOTE: tsdb parse: " string?</div><div><br></div><div>As for (2), it's not part of UDF derivation trees, nor is it stored in [incr tsdb()] profiles as far as I know, so I don't think I can reasonably ask for this. It's not necessary, but it would be nice, if it is something ACE can easily provide. But I'm not sure where to put it (maybe in the :flags of a result?).</div><div><br></div><div>Also, it seems the --tsdb-stdout is not working fully with generation. The surface string is being printed in the middle of the s-expression:</div><div><br></div><div>$ echo "Abrams arrived." | ./ace -g ~/erg-1214-x86-64-0.9.23.dat | ./ace -g ~/erg-1214-x86-64-0.9.23.dat -e --tsdb-stdout --report-labels<br></div><div>[...]</div><div><div>(:results . (Abrams arrived.</div><div>((:result-id . 0)(:surface . "Abrams arrived.") [...]</div></div><div><br></div><div>I assume you just got it working in ACE's SVN as a preview for parsing and not generation, so this is fine for now.</div><div><br></div><div>Thanks again!</div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jun 23, 2016 at 4:48 PM Stephan Oepen <<a href="mailto:oe@ifi.uio.no" target="_blank">oe@ifi.uio.no</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> The output is formatted as (a list of) s-expressions, and is identical to<br>
> the data sent to [incr tsdb()] [...]<br>
<br>
thanks, woodley. that was in fact a thought i too had entertained<br>
during the API discussion: my RESTful server actually works off [incr<br>
tsdb()] item structures, so ACE communicating with different callers<br>
in the outside world using that same format seems utterly plausible to<br>
me :-).<br>
<br>
cheers, oe<br>
</blockquote></div></div>
</div></blockquote></body></html>