Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4183C10A43 for ; Fri, 8 Nov 2013 05:18:57 +0000 (UTC) Received: (qmail 49431 invoked by uid 500); 8 Nov 2013 05:18:48 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 49333 invoked by uid 500); 8 Nov 2013 05:18:48 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 49326 invoked by uid 99); 8 Nov 2013 05:18:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Nov 2013 05:18:47 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,HTML_OBFUSCATE_05_10,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mirko.kaempf@gmail.com designates 209.85.192.173 as permitted sender) Received: from [209.85.192.173] (HELO mail-pd0-f173.google.com) (209.85.192.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Nov 2013 05:18:43 +0000 Received: by mail-pd0-f173.google.com with SMTP id r10so1627562pdi.32 for ; Thu, 07 Nov 2013 21:18:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=4uuJm3064ilkgbwznwOk6lE3p0dRztNH2+DdU7m3mQg=; b=OFWbAVMqIo6Z7avZOawcU3UumFxwgnkugO7BaLf7jv4RApjELE3zTEWBiUIwBOfLuf fXAT1U42rHNaq9ei93QJ+KQXUJ3xmikqHT7MevXyMdpagBX9C0PlgiMmKJdZDt9LWUhi Y4Q5KEO4EAnrAm940jLQ9bdhJjqh0H58Tm48BcBcqa4jvtNcCWdRmY/6M8cBHjDmmf3f qM7DZxfOnvxOP24TJiwL3h7NdfYmqlFDzDQY5kkFySQJi6WntCDraiuNoVE+ckYtn2W1 KnIhaRv6Sdpf31RZxgHYVuQHH5w8Q1elTt/weTr1rvH/EWXzRhmsutWbUJuY2AqsCkpV R+9g== X-Received: by 10.68.161.2 with SMTP id xo2mr12806362pbb.179.1383887902882; Thu, 07 Nov 2013 21:18:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.66.197.195 with HTTP; Thu, 7 Nov 2013 21:18:02 -0800 (PST) In-Reply-To: References: From: =?ISO-8859-1?Q?Mirko_K=E4mpf?= Date: Fri, 8 Nov 2013 13:18:02 +0800 Message-ID: Subject: Re: SVM implementaion To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=047d7bd7562adc4bcb04eaa38265 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd7562adc4bcb04eaa38265 Content-Type: text/plain; charset=ISO-8859-1 There are three Jira issues about it: Mahout-14 and Mahout-334 have been closed as won't fix. Mahout-232 was assigned later because some code was contributed early (2009) but it did not work so it was not incorporated into Mahout. Since then Mahout has changed, so porting the code would be difficult, and if you look at the issue there is some disagreement about whether it approaches the problem in the best way. There is some code for a cascadeSVM implementation but the training part - the hard part - was never published. There is a parallel SVM implementation that runs on MPI rather than Hadoop. This San Francisco Meetup abstract has some discussion of current state of the art and issues for parallel SVM. 2013/11/8 unmesha sreeveni > Do we have an SVM implementation? > > -- > *Thanks & Regards* > > Unmesha Sreeveni U.B > > *Junior Developer* > > *Amrita Center For Cyber Security * > > > * Amritapuri.www.amrita.edu/cyber/ * > --047d7bd7562adc4bcb04eaa38265 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

There are three Jira issues about it:=A0Mahout-14=A0and=A0Mahout-334=A0have been c= losed as won't fix.=A0Mahout-232=A0was assigned later because some code wa= s contributed early (2009) but it did not work so it was not incorporated i= nto Mahout. Since then Mahout has changed, so porting the code would be dif= ficult, and if you look at the issue there is some disagreement about wheth= er it approaches the problem in the best way.

There is=A0some co= de for a cascadeSVM implementation=A0but the training part - the hard p= art - was never published.

There is a=A0parallel SV= M implementation=A0that runs on MPI rather than Hadoop.

This San Francisco Meetup abstract=A0has some discussion of current= state of the art and issues for parallel SVM.





2013/11/8 unmesha sreeveni <unmeshabiju@gmail.com>
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Do we have an SVM implementation?
<= font color=3D"#888888">

--
Thanks & Regards

Unmesha Sreeveni U.B
Junior Developer
Amrita Center For Cyber Security

--047d7bd7562adc4bcb04eaa38265--