Is there a plan to bubble these annotations out further? Say to the wiki or as command-line feedback?
I think it would be really helpful (and promote uptake of Mahout) to have metadata and prominent documentation that describes the general scaling/stability properties of the different methods. I know of a few places where Mahout's been rejected after a quick sniff check because, say, Naive Bayes couldn't be used beyond a few dozen classes. I have seen this crop up on the list, too, and the response tends to be something along the lines of "You probably don't really want to use NB anyway, and it might be better to try a SGD-based classifier". That's probably good advice, but a lot of times people are specifically running a simple, well understood method to sniff-check Mahout. When you're just trying out a package - especially one where a prime benefit you're hoping for is scalability - and you hit an unadvertised limit in scaling, there's a strong tendency to write off the entire project as "not quite ready". Especially when you don't have a lot of time dig into code to understand problems. -tom On Thu, Dec 22, 2011 at 5:48 PM, Ted Dunning <[email protected]> wrote: > Hmm... this looks promising: > > http://docs.oracle.com/javase/1.5.0/docs/api/java/lang/annotation/Documented.html > > See the documentation section here: > http://docs.oracle.com/javase/tutorial/java/javaOO/annotations.html > > On Thu, Dec 22, 2011 at 2:43 PM, Ted Dunning <[email protected]> wrote: > >> I think annotations are significantly better. The integration with >> javadoc isn't impossible and the integration from javadoc markup to >> annotation is impossible. >> >> Interestingly, the javadoc tool documentation tends to recommend an >> annotation *and* a javadoc tag. That does make the integration simple. >> >> >> On Thu, Dec 22, 2011 at 12:54 PM, Dmitriy Lyubimov <[email protected]>wrote: >> >>> just a custom javadoc tag would be easy though bit it would be visible >>> to javadoc tool only (and not even IDEs, so typo-prone). Maybe that's >>> what we need, but the trend in the rest of hadoop world seems to be to >>> use annotation-driven markers in this case. >>> >> >>
