The input and output format, from my view, have nothing to do with the parallel execution. It is the nature of model and the design of learning algorithm determine the parallel manner.
Criteria may contain: (1) Mature; (2) Reasonable; (3) Wide acceptance; (4) Easy for extension; (5) Suitable for Mahout; (6) more.... -----邮件原件----- 发件人: Ted Dunning (JIRA) [mailto:[EMAIL PROTECTED] 发送时间: 2008年3月19日 8:56 收件人: [email protected] 主题: [jira] Commented: (MAHOUT-18) Embrace interoperability with other softwares [ https://issues.apache.org/jira/browse/MAHOUT-18?page=com.atlassian.jira.plug in.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580199#action_1 2580199 ] Ted Dunning commented on MAHOUT-18: ----------------------------------- What are the possible formats? Do any of the formats express parallel execution? What are the criteria that we should use to decide which formats to support? > Embrace interoperability with other softwares > --------------------------------------------- > > Key: MAHOUT-18 > URL: https://issues.apache.org/jira/browse/MAHOUT-18 > Project: Mahout > Issue Type: New JIRA Project > Reporter: Shunkai Fu > Priority: Minor > > This is an open issue. It is related with all possible components existing or to born in the future. > ML or DM models normally have two phases: training and scoring (or predicting). If we agree "updating" is an independent one, we will have 3 phases. > There are many softwares about ML/DM outside. We want the users of Mahout be able to import models got built from other software here, update them and/or use them for scoring. To achieve this goal, we need to recognize the commonly used formats. > Besides, users may choose Mahout because Mahout is speedy in learning. After a model is ready, they may export the model trained, view it with some visualization tool, or import it into other software or application for scoring (or predicting). In this case, exporting into widely recognized format is expected. > Finally, I want to say that the importing and exporting will not influence the ongoing projects, so developers of other components need not worry about this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
