-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
:mod
relation ignored
#44
Comments
@jheinecke it looks like this is the same issue as #26 and #39: Smatch does not handle triples when the source is a constant. This situation comes about when inverted roles point to a constant, and since #16 Also for your second set of examples, the PENMAN strings look identical to me, aside from the metadata comments above the first one. Did you mean to paste something different for the second? |
@jheinecke Can you try with SMATCH++ ? When I feed the first two AMRs in SMATCH++ I get:
which is correct (first graph has 15 triples, second has 16 triples, first graph is a subgraph of the second, i.e., recall = 15/16 = 0.9375). |
Hi @flipz357 and @goodmami , I get the same results as you with smatchpp on the first example (so it detects the difference). I'm sorry for the bad copy-and-paste in the second example. The second graph should read
The difference is @goodmami I think there could be a check in amr.py |
@jheinecke I'm not very familiar with |
It has indeed exactly the same function as the penman library. I am working on a version of this smatch which uses the penman library instead of the local |
I came across a difference in AMR graphis which is not detected by smatch.
comparing these two AMR graphs outputs a R/P/F of 1.00/1.00/1.00 by smatch (I am aware that
:mod expressive
is not valid AMR but nevertheless it is what my AMR Parser created, and smatch should detect it)I thinks this is due to the special treatment of
:mod
/:domain
. any other relation is detected by the current version of smatch. For instance changing:mod expressive
into:op1 expressive
or even:toto expressive
makes smatch detecting the error and outputs an F-score of 0.9677. My first guess is, that:mod
is replaced by:domain
(and start and end point reversed) inamr.sty
There is another AMR difference not detected by smatch :
and (note the
:ARG1 "25"
which is:ARG1 "25 bis"
in the graph aboveThe text was updated successfully, but these errors were encountered: