Return-Path: X-Original-To: apmail-spark-issues-archive@minotaur.apache.org Delivered-To: apmail-spark-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C6F9184C5 for ; Wed, 6 Apr 2016 23:48:26 +0000 (UTC) Received: (qmail 86213 invoked by uid 500); 6 Apr 2016 23:48:25 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 86163 invoked by uid 500); 6 Apr 2016 23:48:25 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 86135 invoked by uid 99); 6 Apr 2016 23:48:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2016 23:48:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id BA46B2C1F5C for ; Wed, 6 Apr 2016 23:48:25 +0000 (UTC) Date: Wed, 6 Apr 2016 23:48:25 +0000 (UTC) From: "Joseph K. Bradley (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (SPARK-12566) GLM model family, link function support in SparkR:::glm MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SPARK-12566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229368#comment-15229368 ] Joseph K. Bradley edited comment on SPARK-12566 at 4/6/16 11:47 PM: -------------------------------------------------------------------- Here's my preferred design. I prefer to abstract the implementation (solver) from the API (model) as much as possible. * R glm calls Scala GLM, using solver = auto by default * Scala GLM has solver = auto by default. Auto should mean "best effort" ** With few features (< 4K or so), *** For family = gaussian and link = identity, use normal equations. *** For others, use IRLS. ** With many features, use LBFGS if possible (for family, link). Otherwise, throw an exception. * Scala LinearRegression, LogisticRegression call GLM. I.e., they uses normal equations, IRLS when possible. What do yall think? (update: now catching up on PR comments...) was (Author: josephkb): Here's my preferred design. I prefer to abstract the implementation (solver) from the API (model) as much as possible. * R glm calls Scala GLM, using solver = auto by default * Scala GLM has solver = auto by default. Auto should mean "best effort" ** With few features (< 4K or so), *** For family = gaussian and link = identity, use normal equations. *** For others, use IRLS. ** With many features, use LBFGS if possible (for family, link). Otherwise, throw an exception. * Scala LinearRegression, LogisticRegression call GLM. I.e., they uses normal equations, IRLS when possible. What do yall think? > GLM model family, link function support in SparkR:::glm > ------------------------------------------------------- > > Key: SPARK-12566 > URL: https://issues.apache.org/jira/browse/SPARK-12566 > Project: Spark > Issue Type: New Feature > Components: ML, SparkR > Reporter: Joseph K. Bradley > Assignee: yuhao yang > Priority: Critical > > This JIRA is for extending the support of MLlib's Generalized Linear Models (GLMs) to more model families and link functions in SparkR. After SPARK-12811, we should be able to wrap GeneralizedLinearRegression in SparkR with support of popular families and link functions. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org