Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
overly rigid treatment of top nodes in SMATCH #12
when comparing our (forthcoming) MCES scorer with SMATCH, it emerged that there is a difference in the count of correct tuples for two test AMRs from the SMATCH distribution:
SMATCH correctly establishes three node correspondences: the ‘b’ and ‘h’ nodes from both graphs, and ‘p’ from the first graph with ‘w’ from the second. on this view, the two graphs have the same top node, share two node labels (‘boy’ and ‘hard’), as well as one edge (:domain). however, SMATCH appears to represent the top properties as triples that include the node label, which results in an undesirable double penalty. i wonder whether this treatment in SMATCH is background to the critique by Anchieta et al. (2019)?