-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Proposal: Evaluator and/or Benchmark repositories #33
Comments
I love the idea. Maybe we can use GitHub actions to automate the benchmarks and evaluators whenever a repo get's a push to master. |
Yeah ! If it can download x00 megs datasets then I can't see why not ! |
There's no reason it couldn't. All you need is a docker container that can do it. |
Yeah, you're right. One thing to keep in mind : |
6 hours is insane. I doubt we'll even come close. |
Preface
Evaluating the accuracy of the output of an NLP component is a science in itself.
When a new NLP algorithm, method or tool is published, it is always accompanied by benchmarks against existing systems.
Those benchmarks are produced using standard evaluation techniques and dataset.
These evaluation techniques are not always automatic.
A human judgment is sometimes necessary. In this case, there's nothing Cadmium can do to help.
However a set of existing tools exist depending on the NLP task to be tested :
We can add to those tools standard dataset and corpora already gold labeled and human checked.
These are just examples found after a cursory search. The list is bigger and the tools get better fast.
Details
The main idea of this proposal is to :
Create a
cadmiumcr/evaluator
repository.This module will have the tools listed above and methods to conveniently download the large datasets of gold labelled data.
Create a
cadmiumcr/benchmark
repository.This repository will be more like a custom set of crystal scripts using the tools of Cadmium::Evaluator to run benchmarks against the vanilla tools of Cadmium (classifiers, pos tagging, language identification, etc.) and display the results next to competing tools results.
The point being to give a glimpse of Cadmium possibilities and routinely check our tools accuracy (which crystal spec is not intended to do).
This proposal is mainly a braindump, as I don't intend to start working on this short term (I have to finish my POS Tagger first !)
The text was updated successfully, but these errors were encountered: