search

google-code-export / dkpro-tc

Automatically exported from code.google.com/p/dkpro-tc
Other
1 stars 0 forks source link

Invalid column index in reports which produce XLS files #160

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello All!

I'm new to DKPro TC and trying to classify some train and test data I have. I 
have checked and run all the examples in dkpro-tc-examples package. I picked 
SimpleDkproTCReaderDemo beacause I think it matches the format of my data 
(labels in one file, and instances in one file, with line numbers matching). I 
tried to run SimpleDkproTCReaderDemo on just my training data with ~255 lines 
in both files, and this returned an error saying: "Invalid column index (256).  
Allowable column range for BIFF8 is (0..255) or ('A'..'IV');"

Is it that I'm using too much data?

However, Most other examples use the name of the parent folder as labels. I'm 
not sure if I should have ~255 folders to represent labels?

At the moment, I'm just trying to run a first-experiment rather than creating 
some custom-TC-runner.. Any thoughts?

Original issue reported on code.google.com by alot...@gmail.com on 1 Jul 2014 at 12:58

GoogleCodeExporter commented 9 years ago 
Sounds like there is a report configured to write its results as an Excel table 
which only supports a limited number of columns.

(http://stackoverflow.com/questions/2326668/how-to-get-more-than-255-columns-in-
an-excel-sheet-using-apache-poi-3-6)

Maybe Excel reports should be skipped for sets with so many labels? There are 
still the CSV versions I suppose.

Original comment by richard.eckart on 1 Jul 2014 at 1:04

GoogleCodeExporter commented 9 years ago 
As Richard says, this is most probably caused by a report trying to write an 
Excel file. Could you find out which report causes that problem or paste a 
stack trace?

Original comment by daxenber...@gmail.com on 1 Jul 2014 at 1:09

GoogleCodeExporter commented 9 years ago 
Exception in thread "main" 
de.tudarmstadt.ukp.dkpro.lab.engine.LifeCycleException: 
org.springframework.dao.DataAccessResourceFailureException: Invalid column 
index (256).  Allowable column range for BIFF8 is (0..255) or ('A'..'IV'); 
nested exception is java.lang.IllegalArgumentException: Invalid column index 
(256).  Allowable column range for BIFF8 is (0..255) or ('A'..'IV')
    at de.tudarmstadt.ukp.dkpro.lab.engine.impl.DefaultLifeCycleManager.complete(DefaultLifeCycleManager.java:98)
    at de.tudarmstadt.ukp.dkpro.lab.engine.impl.ExecutableTaskEngine.run(ExecutableTaskEngine.java:72)
    at de.tudarmstadt.ukp.dkpro.lab.task.impl.BatchTask.runNewExecution(BatchTask.java:350)
    at de.tudarmstadt.ukp.dkpro.lab.task.impl.BatchTask.executeConfiguration(BatchTask.java:255)
    at de.tudarmstadt.ukp.dkpro.lab.task.impl.BatchTask.execute(BatchTask.java:185)
    at de.tudarmstadt.ukp.dkpro.tc.weka.task.BatchTaskCrossValidation.execute(BatchTaskCrossValidation.java:230)
    at de.tudarmstadt.ukp.dkpro.lab.engine.impl.ExecutableTaskEngine.run(ExecutableTaskEngine.java:55)
    at de.tudarmstadt.ukp.dkpro.lab.engine.impl.DefaultTaskExecutionService.run(DefaultTaskExecutionService.java:48)
    at de.tudarmstadt.ukp.dkpro.lab.Lab.run(Lab.java:97)
    at de.tudarmstadt.ukp.experiments.AA.VSD_TC.SimpleDkproTCReaderDemo.runCrossValidation(SimpleDkproTCReaderDemo.java:82)
    at de.tudarmstadt.ukp.experiments.AA.VSD_TC.SimpleDkproTCReaderDemo.main(SimpleDkproTCReaderDemo.java:66)
Caused by: org.springframework.dao.DataAccessResourceFailureException: Invalid 
column index (256).  Allowable column range for BIFF8 is (0..255) or 
('A'..'IV'); nested exception is java.lang.IllegalArgumentException: Invalid 
column index (256).  Allowable column range for BIFF8 is (0..255) or ('A'..'IV')
    at de.tudarmstadt.ukp.dkpro.lab.storage.filesystem.FileSystemStorageService.storeBinary(FileSystemStorageService.java:224)
    at de.tudarmstadt.ukp.dkpro.lab.engine.impl.DefaultTaskContext.storeBinary(DefaultTaskContext.java:151)
    at de.tudarmstadt.ukp.dkpro.tc.weka.report.BatchTrainTestReport.execute(BatchTrainTestReport.java:122)
    at de.tudarmstadt.ukp.dkpro.lab.engine.impl.DefaultLifeCycleManager.complete(DefaultLifeCycleManager.java:91)
    ... 10 more
Caused by: java.lang.IllegalArgumentException: Invalid column index (256).  
Allowable column range for BIFF8 is (0..255) or ('A'..'IV')
    at org.apache.poi.hssf.usermodel.HSSFCell.checkBounds(HSSFCell.java:926)
    at org.apache.poi.hssf.usermodel.HSSFCell.<init>(HSSFCell.java:162)
    at org.apache.poi.hssf.usermodel.HSSFRow.createCell(HSSFRow.java:141)
    at org.apache.poi.hssf.usermodel.HSSFRow.createCell(HSSFRow.java:119)
    at org.apache.poi.hssf.usermodel.HSSFRow.createCell(HSSFRow.java:38)
    at de.tudarmstadt.ukp.dkpro.lab.reporting.FlexTable$5.write(FlexTable.java:462)
    at de.tudarmstadt.ukp.dkpro.lab.storage.filesystem.FileSystemStorageService.storeBinary(FileSystemStorageService.java:221)
    ... 13 more

Original comment by alot...@gmail.com on 1 Jul 2014 at 1:59

GoogleCodeExporter commented 9 years ago 
commenting all/some of these report lines did not seem to make a difference:
        batch.addInnerReport(ClassificationReport.class);
        batch.setParameterSpace(pSpace);
        batch.addReport(BatchCrossValidationReport.class);
        batch.addReport(BatchRuntimeReport.class);

Original comment by alot...@gmail.com on 1 Jul 2014 at 2:02

GoogleCodeExporter commented 9 years ago 
That is because BatchTrainTestReport is added hard-coded. The problem is caused 
by the creation of the confusion matrix (which has one column per label). We 
should change this behaviour to create csv files only (no xls).

Original comment by daxenber...@gmail.com on 1 Jul 2014 at 2:06

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r943.

Original comment by daxenber...@gmail.com on 1 Jul 2014 at 2:21

GoogleCodeExporter commented 9 years ago 
This needs to be fixed for *all* reports which generate XLS files.

Original comment by daxenber...@gmail.com on 6 Aug 2014 at 11:18

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r1021.

Original comment by daxenber...@gmail.com on 6 Aug 2014 at 11:46