[
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)
