You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2011/02/07 00:11:30 UTC

[jira] Updated: (MAHOUT-608) Collect various data directories in Mahout dir structure

     [ https://issues.apache.org/jira/browse/MAHOUT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen updated MAHOUT-608:
-----------------------------

    Status: Patch Available  (was: Open)

Here's most of what I think should be done. Tests pass, but, does it make sense?

> Collect various data directories in Mahout dir structure
> --------------------------------------------------------
>
>                 Key: MAHOUT-608
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-608
>             Project: Mahout
>          Issue Type: Improvement
>    Affects Versions: 0.4
>            Reporter: Sean Owen
>            Assignee: Sean Owen
>             Fix For: 0.5
>
>
> The top-level project directory has collected, over time, a number of directories that have a generally similar purpose: to collect various config files, data files, and scripts. In addition toWe have, at first glance:
> bin/
>  mahout
> conf/
>  (various .props files)
> etc/
>  build.xml (reusable  Ant tasks?)
>  findbugs-exclude.xml
>  mahout.importorder
> mahout/
>  conf/
>   arff.vector.props (wrong place?)
> src/
>  main/
>   appended-resources/
>    META-INF/
>     NOTICE
>    supplemental-models.xml
>  site/
>   site.xml
> There are a few top-level generated directories:
> input/
>  ...
> output/
>  ...
> testdata/
>  transactions
>   test.txt
> I'd like to prune whatever isn't needed anymore, and rationalize one directory structure as a start.
> Can anyone help by suggesting things to be removed, or a directory structure?

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira