I wouldn't build out skeletons until somebody starts doing the code. Pick ONE algorithm and do it up and then document it as a sample. Let the implementers of various algorithms do their thing.
There is nothing worse to read than a whole lot of code that doesn't actually do anything. On 2/5/08 9:09 AM, "Jeff Eastman" <[EMAIL PROTECTED]> wrote: > I'm looking at the package structure in SVN and it begs for additional > structure. Something like the following seems obvious but needs discussion > since it involves naming conventions. I'd be happy to generate driver, map and > reducer classes in Eclipse just to have some skeletons where real code could > be added later, and also create similar structure in the test branch. It's > just administrative work, turning the crank, but somebody needs to do it and > I'd like to volunteer. > > > > org.apache.mahout. > > classification. > > naïve_bayes. > > svm. > > neural_net > > clustering. > > k_means. > > em. > > regression. > > lwlr. > > lr. > > dimension. > > pca. > > ica. > > gda. > > non_mr. > > hmm. > > rl. > > > > Jeff >
