Return-Path: X-Original-To: apmail-hama-dev-archive@www.apache.org Delivered-To: apmail-hama-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 53F5ED397 for ; Mon, 12 Nov 2012 18:09:12 +0000 (UTC) Received: (qmail 79276 invoked by uid 500); 12 Nov 2012 18:09:12 -0000 Delivered-To: apmail-hama-dev-archive@hama.apache.org Received: (qmail 79250 invoked by uid 500); 12 Nov 2012 18:09:12 -0000 Mailing-List: contact dev-help@hama.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hama.apache.org Delivered-To: mailing list dev@hama.apache.org Received: (qmail 79231 invoked by uid 99); 12 Nov 2012 18:09:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 18:09:12 +0000 Date: Mon, 12 Nov 2012 18:09:12 +0000 (UTC) From: "Thomas Jungblut (JIRA)" To: dev@hama.apache.org Message-ID: <1981887279.101606.1352743752073.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HAMA-675) Deep Learning Computation Model MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Thomas Jungblut created HAMA-675: ------------------------------------ Summary: Deep Learning Computation Model Key: HAMA-675 URL: https://issues.apache.org/jira/browse/HAMA-675 Project: Hama Issue Type: New Feature Reporter: Thomas Jungblut Jeff Dean mentioned a computational model in this video: http://techtalks.tv/talks/57639/ There they are using the same idea of the Pregel system, they are defining a upstream and a downstream computation function for a neuron (for cost and its gradient). Then you can roughly tell about how the framework should partition the neurons. All the messaging will be handled by the underlying messaging framework. Can we implement something equally? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira