You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
A naive way is to use deepdiff and count the leaves in outputs. But it gets complicated when edits are branches.
proto_compare from proto-matcher. But it only produces text descriptions.
Use graph edit distance like GMatch4py which requires conversion from JSON to networkx.
Some tree edit distance packages
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.
What is this feature about?
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
deepdiff
and count the leaves in outputs. But it gets complicated when edits are branches.proto_compare
fromproto-matcher
. But it only produces text descriptions.The text was updated successfully, but these errors were encountered: