Data checker fails when runstatus in algorithm_runs is disallowed value about aslib-spec

[mlindauer]

Could you please provide a small example?
From the exception, I would expect another problem.

I can look at it on Monday.

[larskotthoff]

Here are the first few lines from algorithm_runs.arff:

@RELATION ALGORITHM_RUNS_CSP-MZN-2013

@ATTRIBUTE instance_id STRING
@ATTRIBUTE repetition NUMERIC
@ATTRIBUTE algorithm {bprolog, fzn2smt, g12cpx, g12fd, g12lazyfd, g12mip, gecode, izplus, minisatid, mistral, ortools}
@ATTRIBUTE solved NUMERIC
@ATTRIBUTE time NUMERIC
@ATTRIBUTE runstatus {ok, timeout, other}

@DATA
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, izplus, 0, 1800, timeout
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, g12lazyfd, 0, 1800, other
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, ortools, 0, 1800, timeout
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, g12fd, 0, 1800, timeout
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, g12cpx, 0, 1800, other
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, gecode, 0, 1800, timeout
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, g12mip, 0, 1800, other
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, bprolog, 0, 1800, other
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, minisatid, 0, 1800, timeout
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, mistral, 0, 1800, timeout
/public/xcsp_instances/flatzinc_conversion/zinc_instances/normalized-fapp06-0500-1.xml.mzn_AND_NODATA, 1, fzn2smt, 0, 1800, other
/home/phd-students/amadini/new/solvers/minizinc-1.6/benchmarks/langford/langford.mzn_AND_/home/phd-students/amadini/new/solvers/minizinc-1.6/benchmarks/langford/l_3_17.dzn, 1, izplus, 1, 1.3, sat
/home/phd-students/amadini/new/solvers/minizinc-1.6/benchmarks/langford/langford.mzn_AND_/home/phd-students/amadini/new/solvers/minizinc-1.6/benchmarks/langford/l_3_17.dzn, 1, g12lazyfd, 1, 12.76, sat
/home/phd-students/amadini/new/solvers/minizinc-1.6/benchmarks/langford/langford.mzn_AND_/home/phd-students/amadini/new/solvers/minizinc-1.6/benchmarks/langford/l_3_17.dzn, 1, ortools, 1, 4.51, sat
/home/phd-students/amadini/new/solvers/minizinc-1.6/benchmarks/langford/langford.mzn_AND_/home/phd-students/amadini/new/solvers/minizinc-1.6/benchmarks/langford/l_3_17.dzn, 1, g12fd, 1, 9.1, sat

[mlindauer]

Hi,

indeed, there was an uncaught exception in this case (I implemented a somehow better error message). However, the error message was another one than reported by you.
Could you please check that you installed "liac-arff" as the arff package and not "arff".

$ python
$ import arff
$ arff.doc

The doc string should start with something like "The liac-arff module implements functions to read and write ARFF files in Python."

Cheers,
Marius

[larskotthoff]

Thanks for checking Marius. Apparently the user also had the wrong version of the ARFF package installed. Will close.