compared with
Current by Andrew Jackson
on Mar 19, 2012 11:54.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
| *Corresponding Issue(s)* \\ | \\ |
| *myExperiment Link* \\ | \\ |
| *Tool Registry Link* \\ | \\ |
| *Tool Registry Link* \\ | The tool testing framework is hosted here: https://github.com/openplanets/Scape-Tool-Tester |
| *Evaluation* \\ | \\ |

Currently, the framework consist of two scripts for running the tools recursively

Testframework: [^testframework_v1.tgz]


h3. Invoking - Tools that read the datafile themselves

{code:language=bash}recursive_invoke.sh DATADIR REPORTDIR PRECOMMAND [POSTCOMMAND]{code}

Datadir is the directory where the datafiles reside.

Report dir is where the output reports of the tool should be dumped. Each file will produce an output file, so the directory structure in REPORTDIR will come to resemble the one in DATADIR.

PreCommand is the bash command the place before the file. Postcommand is the bit to place afterwards.

To run Tika (java \-jar tika-app-1.0.jar <datafile>) on every file in the folder \~/testdata and have it report to \~/testdatareports, this would be the command

{code:language=bash}./recursive_invoke.sh ~/testdata ~/testdatareports "java -jar tika-app-1.0.jar"{code}

Since performance information is relevant, this is recorded in a CSV file in the REPORTDIR by the name of time.log

h3. Piping - Tools that read stdin

{code:language=bash}recursive_pipe.sh DATADIR REPORTDIR COMMAND{code}

Functions almost like recursive_invoke.sh

To run Tika (cat <datafile> \| java \-jar tika-app-1.0.jar \-) on every file in the folder \~/testdata and have it report to \~/testdatareports, this would be the command

{code:language=bash}./recursive_pipe.sh ~/testdata ~/testdatareports "java -jar tika-app-1.0.jar -"{code}
Since performance information is relevant, this is recorded in a CSV file in the REPORTDIR by the name of time.log

h3. Test dataset