From what I can tell, it looks in the classpath for props files. Would it make sense to have it either automatically add something like ~username/.mahout/props to the classpath or alternatively add an option to look in their if there isn't one in the classpath?
On May 17, 2010, at 1:49 PM, Jeff Eastman wrote: > Thanks Jake, glad I asked. I'll continue to follow your convention on this. > Jeff > > On 5/17/10 10:18 AM, Jake Mannix wrote: >> These are commented because they're totally specific to the user. The >> checked in versions are just meant to show users the format they should have >> (and the variety of options which can go in there) for the jobs. >> >> If you have values for kmeans which you use all the time, you should >> uncomment a line in kmeans.props and modify it to have your default values. >> Those will be different than my default values, so don't check that file in >> once you've changed it. Users who use a released version of mahout will of >> course not need to worry about accidentally checking in these changed files. >> :) >> >> -jake >> >> On Mon, May 17, 2010 at 10:12 AM, Jeff Eastman >> <[email protected]>wrote: >> >> >>> Really threw me for a loop when I copied the kmeans.props into >>> dirichlet.props and none of them were noticed by MahoutDriver. Took a little >>> digging to understand the cause. Without the preceeding '#', the defaults >>> load just great; however, none of the existing files contain any uncommented >>> lines. Is there a reason for this or is it just an unfinished WIP? >>> >>> >> >
