From: Rajarshi G. <rx...@ps...> - 2006-05-23 17:11:22
|
On Tue, 2006-05-23 at 19:02 +0200, Egon Willighagen wrote: > On Tuesday 23 May 2006 18:49, Rajarshi Guha wrote: > > On Tue, 2006-05-23 at 18:07 +0200, Egon Willighagen wrote: > > > How does Weka address this? > > > > I think one strategy would be to make a IWekaModel class which > > subclasses IModel - and any modeling class that builds on Weka would > > implement IWekaModel and so on. > > I was thinking along these lines too, but then even make the interfaces > library independent. > > It would be great to just do something like: > > // setup data > IData xData = new DoubleDoubleArrayData((double[][])myData); > IData yData = new StringArrayData((String[])myClasses); > > IModelMethod[] modelMethods = ModelingMethodsFactory.getModelingMethods(); > for (int i=1; i<modelMethods.length; i++) { > try { > IModel model = modelMethods[i].build(xData, yData); > } catch (UnsupportedIDataException e) { > // e.g. when using non-numerical data in PLS > }; > } > > But this obviously neglects the problem that many of the methods need tuning > of parameter... Hmm, sounds good. Parameters could be set via a HashMap like we do for descriptors. But at the same time I'm not sure that we want such a genericized interface to modeling methods - since in many cases a specific model is appropriate for specific data. ------------------------------------------------------------------- Rajarshi Guha <rx...@ps...> <http://jijo.cjb.net> GPG Fingerprint: 0CCA 8EE2 2EEB 25E2 AB04 06F7 1BB9 E634 9B87 56EE ------------------------------------------------------------------- The most important statistic for car manufacturers is autocorrelation. |