[
https://issues.apache.org/jira/browse/MATH-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737456#comment-14737456
]
Ole Ersoy commented on MATH-1267:
---------------------------------
Gilles I understand what you are saying. The classes may be purely
computational, but it's useful to think of the Neurons as being laid out in a
2d, 3d, mesh like coordinate system.
The design idea that I'm advocating comes from MVC theory, hence the references
to things you can do. I think it's nice that you can do these things and that
the design easily supports it, even though the classes are purely used for
computation ATM.
In general we have a network with neurons that are interconnected and we train
it. Then there are utility classes that are used to conceptualize the layout
of the Neurons onto a grid. Even though there may not be a Neuron at every
point in a square mesh / coordinate system, we can still think of a Neuron as
belonging to a row, column coordinate, right?
We may want to draw the Nework on a canvas, and display things like the
Neuron's ID, which makes the Neuron visual.
> 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)
