Skip to content
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

[FEATURE] Tree edit distance for evaluation #9

Open
qai222 opened this issue Jul 22, 2023 · 0 comments
Open

[FEATURE] Tree edit distance for evaluation #9

qai222 opened this issue Jul 22, 2023 · 0 comments
Assignees

Comments

@qai222
Copy link
Owner

qai222 commented Jul 22, 2023

What is this feature about?

  1. evaluation

Is your feature request related to a problem? Please describe.

Use tree edit distance to describe differences between ground truth and inferred JSON. Preferably field-resolved: ex. 5 edits for all compound.identifiers fields.

Describe the solution you'd like

A function takes into two ORD JSON or messages and produces an edit distance.

Describe alternatives you've considered

  1. A naive way is to use deepdiff and count the leaves in outputs. But it gets complicated when edits are branches.
  2. proto_compare from proto-matcher. But it only produces text descriptions.
  3. Use graph edit distance like GMatch4py which requires conversion from JSON to networkx.
  4. Some tree edit distance packages
    1. Apted, it only takes in bracket notations. Here is a parser that may be useful. Some useful tools by the same authors can be found here.
    2. zss, seems buggy tho.
@qai222 qai222 self-assigned this Jul 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant