(Discussion of the command-line driver sorta forks from the JIRA state discussion, so changing the subject-line here)
On Wed, Oct 26, 2011 at 2:50 PM, Dan Brickley <[email protected]> wrote: > How much of your Mahout work do you folk manage to do purely via bin/mahout? > Definitely not purely command-line, but I do use it for a great deal of demonstration, ad-hoc work and planning/experimenting with workflows that will eventually be stitched together. I think it also serves as a gateway to new users that are kicking the tires, most frequently as a follow on to other command-line tools such as build-reuters, etc. A good portion of my use of it is for dumping sequence files in readable form for visual verification. If there were the equivalent to Luke for Mahout, I would likely be using that instead. I think there's definitely a story about command-line examples/tools in Mahout, but I see it as a gateway to the library, which will likely end up embedded in something else. I think bin/mahout (and the examples) have suffered from not being exercised regularly as a part of the build. Patches change some functionality, change expected output of one part of the workflow, and poof it's gone. Along these lines it would be good to see some targets that would run the various tools and verify the output. Drew
