Closed GoogleCodeExporter closed 9 years ago
I suggest throwing an Exception in a different place for both examples. The
Demo example above throws an exception when splitting the instances into folds
for CV. The Raw example throws an exception when writing arff files for Weka,
when it notices the list of instance outcomes is empty. Both Exceptions are
distant downstream effects of a Reader that found 0 resources.
Perhaps we can throw an Exception somewhere in the Reader inheritance family.
I will query the DKPro Core mailing list about the proper place to do this, TC
or Core, and which class.
Original comment by EmilyKJa...@gmail.com
on 17 Jun 2014 at 3:00
IMHO it is perfectly acceptable that a reader produces 0 results. Why can TC
not just gracefully handle that? If there is no input data, then there should
be no results - not an exception - my 10 cents.
Original comment by richard.eckart
on 17 Jun 2014 at 3:06
Said otherwise: in my opinion, experiments shouldn't fail at all if no data was
found.
Original comment by richard.eckart
on 17 Jun 2014 at 3:07
TC should definitely handle that and just (as was already said) gracefully and
with a meaningful error message terminate the experiment.
Original comment by torsten....@gmail.com
on 17 Jun 2014 at 3:13
Possibly the pre-process task could check at its end if any data has been
written to its output location.
Original comment by richard.eckart
on 17 Jun 2014 at 3:30
There seems to be no collectionProcessComplete()-type method anywhere in the
Reader inheritance. I think we would need to throw an Exception elsewhere in
TC, besides the Reader. But, there's got to be a better place before all the
preprocessing has been attempted, right?
-Emily
Original comment by EmilyKJa...@gmail.com
on 17 Jun 2014 at 4:38
Well, the preprocessing won't take too long, if there is no data... So, why not
check at the end?
Original comment by daxenber...@gmail.com
on 17 Jun 2014 at 4:46
Original comment by daxenber...@gmail.com
on 4 Jul 2014 at 9:37
Original comment by torsten....@gmail.com
on 11 Sep 2014 at 7:33
This issue was closed by revision r1101.
Original comment by torsten....@gmail.com
on 12 Sep 2014 at 1:55
Original comment by daxenber...@gmail.com
on 1 Apr 2015 at 5:10
Original issue reported on code.google.com by
ivan.hab...@gmail.com
on 6 Jun 2014 at 1:12