en:Bugs (3.5.7)
From WekaDoc
This article lists known bugs in this release of Weka. This is not used as a bug-tracker, only as information. If you find a bug, please report it on the Wekalist.
| Table of contents |
|
1.1 Explorer |
[edit]
GUI
[edit]
Explorer
[edit]
Experimenter
[edit]
KnowledgeFlow
[edit]
SimpleCLI
[edit]
ArffViewer
[edit]
SqlViewer
[edit]
EnsembleLibrary
[edit]
Command line
[edit]
Associators
[edit]
Attribute selection
[edit]
Classifiers
[edit]
weka.classifiers.meta.ThresholdSelector
- option handling of -C parameter was incorrect: initial value for
m_ClassModewasOPTIMIZE_POS_NAME, default insetOptionswasOPTIMIZE_LFREQinstead,getOptionsreturnedm_DesignatedClassinstead ofm_ClassMode- 08/04/2008 - found and fixed by FracPete
[edit]
Clusterers
[edit]
Data generators
[edit]
Experiments
[edit]
Filters
[edit]
weka.filters.supervised.attribute.AddClassification
- AddClassification filter wasn't copying the values of string and relational attributes to the output, resulting in
NullPointerExceptions
[edit]
weka.filters.supervised.instance.Resample
- Resample filter crapped out if using 100% sample size and
-no-replacementoption: as soon as one of the vectors holding the indices for a class became empty, the Random.nextInt call was given an upper limit of 0, which resulted in an exception that n has to be positive.- 22/01/2008 - found by Daniel Rodriguez
- 22/01/2008 - fixed by FracPete
[edit]
weka.filters.unsupervised.attribute.AddCluster
- The filter generated a error message "problem filtering instances:null". This was due to an exception thrown in case an instance couldn't be clustered. Exceptions are now caught and a missing value is set as cluster.
[edit]
weka.filters.unsupervised.attribute.ClassAssigner
- the method setClassIndex didn't not subtract 1 from the index after parsing the integer value (internal index is 0-based, whereas the one returned is 1-based).
- 16/01/2008 - found and fixed by FracPete
[edit]
Other
[edit]
weka.core.Capabilities
-
getAttributeCapabilities()/getClassCapabilities()were not necesssarily returning the correct capabilities due to the use ofCapabilities.enable(...)instead of just filling theHashSet. Theenablemethod automatically enables encompassed capabilties, i.e., if one enables NOMINAL_ATTRIBUTES, then UNARY/EMPTY will be enabled as well. Led to display discrepancies in the Explorer's Capabilities dialog.
[edit]
weka.core.stemmers.SnowballStemmer
- method objects for calling the snowball library weren't re-initialized after de-serialization and generated NullPointerExceptions. Just running the stemmer as part of the StringToWordVector from commandline was fine though.
- 12/03/2008 - found and fixed (https://list.scms.waikato.ac.nz/mailman/htdig/wekalist/2008-March/012593.html) by FracPete
Categories: En | Bugs | Weka 3.5.7
