Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-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 36E4B10FD1 for ; Wed, 9 Sep 2015 21:56:46 +0000 (UTC) Received: (qmail 66938 invoked by uid 500); 9 Sep 2015 21:56:46 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 66848 invoked by uid 500); 9 Sep 2015 21:56:46 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 66833 invoked by uid 99); 9 Sep 2015 21:56:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 21:56:45 +0000 Date: Wed, 9 Sep 2015 21:56:45 +0000 (UTC) From: "Ole Ersoy (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MATH-1267) Grid coordinate of "Neuron" that belongs to a "NeuronSquareMesh2D" 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/MATH-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737657#comment-14737657 ] Ole Ersoy commented on MATH-1267: --------------------------------- I think asking the question 'Does it support being laid out visually' will be true no matter what the structure of the classes are. Java is bendable. We can always come up with a solution. I think it's useful to look at an API design using metaphors. The Neuron2D is a metaphor for the piece of the Neuron that we like to think of as visual, whether it is being displayed on a device or just conceptually. Neuron2D coordinates need to be updated if the Network configuration is changed. IIUC this is the case in general as well? I think the driver for the final design is: - Is it useful to be able to retrieve row and column coordinates from a Neuron2D instances? - When working with Neuron2D instances, is it useful to be able to retrieve the corresponding Neuron? So we have to match this up against the process of working with the LocationFinder. You have the most insight here, so if the LocationFinder is easier to work with, then that is probably the way to go. > Grid coordinate of "Neuron" that belongs to a "NeuronSquareMesh2D" > ------------------------------------------------------------------ > > Key: MATH-1267 > URL: https://issues.apache.org/jira/browse/MATH-1267 > Project: Commons Math > Issue Type: Wish > Reporter: Gilles > Assignee: Gilles > Priority: Minor > Fix For: 4.0, 3.6 > > Attachments: LocationFinder.java > > > When the network layout is a 2D grid, it useful to be able to retrieve the grid coordinate (row, column) of a a neuron. > I propose to define a new class "LocationFinder" (in package "o.a.c.m.ml.neuralnet.twod.util") that will provide the functionality through a "getLocation(Neuron n)" method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)