Closed obo closed 3 years ago
(This is still not tackled.)
I converted SLTev evaluator and ASRev to the functions and I just use them in the main (SLTev/SLTev file).
Do I get you correctly that there is no longer any plan to have a separate ASRev
?
I fully support that. Just close this issue to confirm.
I still see ASRev.py in the repo. If it is outdated, delete it. Please provide an example of ASR-only evaluation, as a separate section to the README.
@obo ASRev.py just is a module (a set of functions) in the SLTev and it imported in the SLTev. if you think it is confusing we can rename it (e.g. asr-modules.py).
Also, for each submission file that has "asr" suffix, the WER score calculated for it.
Also see #34 - executables such as SLTev
and ASRev
should only be aliases linked to functions in setup.py and pip install
will take care of it.
ASRev does not work independently (ASRev is a function that would be called from SLTev), but I have used entry_points for SLTev. Thanks.
As I see, we don't have ASRev as a separate file anymore, and it is currently a function inside the SLTev code.
I was trying to explain a while ago that
ASRev
should be just a different behaviour ofSLTev
main.ASRev
itself then should be just a symlink toSLTev
.To summarize:
SLTev
should be mixed module-script, importable and runnableASRev
should be just a symlink to this scriptevaluator.py
should be actually merged into SLTev and cease to existThis is the correct top-level strategy for SLTev:
Put that into
SLTevTest
and then try this:And directly in python: