Difference between revisions of "Evaluation/documentation"
(→Biological Event Extraction) |
(→Fine-Grained Opinion Analysis) |
||
Line 14: | Line 14: | ||
sbatch /projects/ltg/epe/abel/tees -i <input> -o <output> | sbatch /projects/ltg/epe/abel/tees -i <input> -o <output> | ||
− | |||
* /projects/ltg/python/bin/python EvaluateEPE.py -i /projects/ltg/epe/2017/submissions/ecnu/00/events -o ~/epe/events/ecnu/00 -n 8 | * /projects/ltg/python/bin/python EvaluateEPE.py -i /projects/ltg/epe/2017/submissions/ecnu/00/events -o ~/epe/events/ecnu/00 -n 8 | ||
+ | |||
+ | = Fine-Grained Opinion Analysis = | ||
= Negation Resolution = | = Negation Resolution = |
Latest revision as of 20:40, 8 July 2018
Contents
Background
This page provides instructions for how to invoke the EPE 2017 infrastructure for extrinsic (dependency) parser evaluation on the Abel system
Biological Event Extraction
The Turku Event Extraction System is installed from its GitHub development branch into /projects/ltg/epe/tees/. Assuming a directory structure containing a complete set of parser output files in EPE format, training and scoring can be invoked as follows
sbatch /projects/ltg/epe/abel/tees -i <input> -o <output>
* /projects/ltg/python/bin/python EvaluateEPE.py -i /projects/ltg/epe/2017/submissions/ecnu/00/events -o ~/epe/events/ecnu/00 -n 8