Thu 08 Oct 2015 05:59:20 PM UTC, comment #4:
Hi Roberto. It took while but I got around to do it now.
I fixed the original issue (hardlims) with:
http://hg.code.sf.net/p/octave/nnet/rev/bd0b831fcbd6
I then also fixed it for satlin and satlins with:
http://hg.code.sf.net/p/octave/nnet/rev/b98d743b7089
I ended up doing some other fixes on those functions, so take a look at http://hg.code.sf.net/p/octave/nnet
|
Wed 26 Aug 2015 07:59:49 PM UTC, comment #3:
Hi,
i post code and attach examples use of functions.
file attached are:
variables.png
hardlims.png
satlin.png
satlins.pg
(file #34744, file #34745, file #34746, file #34747)
|
Mon 24 Aug 2015 05:52:14 PM UTC, comment #2:
The neural net package is currently unmaintained. If you can supply a patch that fixes this with tests, I will apply it.
|
Fri 14 Aug 2015 11:58:09 AM UTC, comment #1:
Same problem (and same solution) for functions satlin and satlins
|
Fri 14 Aug 2015 07:28:36 AM UTC, original submission:
Good morning,
during some exercises about neurual nets functions, i found a difference of results between hardlim function and hardlims (..../packages/nnet-0.1.13).
The first one returned correctly a vector, the second one returned always a scalar.
(Actually the only difference should be that hardlims returns -1 when hardlim returns 0)
You can see, in the image attatched (octave_hardlims_orig.png).
The code of hardlims function was:
I modified that code in this:
Now it returns correctly a vector when input is a vector (attatched image octave_hardlims_modif.png).
I'm not sure that my code is the best way for the function, but i hope that it could be useful.
Thank you.
Roberto Ratti
-unavailable-
|