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

Definition of the benchmarking metrics #125

Open
1 of 2 tasks
mweidling opened this issue Aug 26, 2022 · 4 comments
Open
1 of 2 tasks

Definition of the benchmarking metrics #125

mweidling opened this issue Aug 26, 2022 · 4 comments
Assignees

Comments

@mweidling
Copy link
Collaborator

mweidling commented Aug 26, 2022

We have identified the following metrics to be relevant for benchmarking:

  • Bag of Words
  • CER/WER
  • Flexible CER
  • Reading Order
  • IoU
  • mAP
  • CPU time
  • wall time
  • I/O
  • memory usage

In order for us and our users to be clear what we exactly mean when we use these terms we have to properly define them and add them to the OCR-D specs.

Prior Art: https://pad.gwdg.de/3S_yuzyERum4WQChxV6UyQ
Link to draft: https://pad.gwdg.de/rLDBVhmYQ8CwOd67KcYHwQ#

  • define each metric
  • add them to the specs
@mweidling mweidling self-assigned this Aug 26, 2022
@mweidling
Copy link
Collaborator Author

See https://pad.gwdg.de/rLDBVhmYQ8CwOd67KcYHwQ# for the current status.

@mweidling mweidling mentioned this issue Aug 31, 2022
2 tasks
@mweidling
Copy link
Collaborator Author

@kba @cneud

My first draft of the metrics is ready. Could you please have a look at them? There are still some open TODOs which indicate points that we should talk about / need to define.

I intentionally left the "scenario based layout evaluation" empty because from what I got from the paper linked this is not a metric in the narrower sense. Maybe we could talk about this as well.

@cneud
Copy link
Member

cneud commented Sep 5, 2022

Thank you @mweidling! I've added a new top level and slightly restructured to make the distinction between the evaluation of text, layout and resource utilization more clear, and added some introductory remarks for those sections. Looks very good otherwise, I guess we can have one more call and then publish a first version to spec.

@mweidling
Copy link
Collaborator Author

Thank you for your feedback and work, @cneud ! I'll schedule a call then.

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

2 participants