Click here to Skip to main content
15,616,585 members
Articles / Programming Languages / C#
Posted 9 Nov 2016

Tagged as


6 bookmarked

Trick/Tip: A Feedforward Neural Network with Neurons with "arbitrary" gradient/functions and connections

Rate me:
Please Sign up or sign in to vote.
4.96/5 (7 votes)
9 Nov 2016CPOL20 min read
Short introduction and first trial implementation in C#


Decades ago I worked on experimental Pattern Recognition (Handwritten Character and Word Recognition) and I did also some small experiments with Neural Networks. I had some simple but well tested software ((in VMS Pascal :=) ) but code and datasets are gone by now.
In that time vanishing gradients, LSTM with error carousels and deep learning were not mainstream yet. Note that nowadays frameworks for deep learning are publicly available (hey, might even work on your graphic card)
When I read an article that applied deep learning I was curious how a Feedforward Neural Network with arbitrary Neuron Functions in C# would look like. For nostalgic reasons I decided as a little hobby project to make a first iteration /implementation /design in C# for the network and neurons. This trick/tip presents:
  • The foundation of the approach, a neuron class with abstract functions ComputeOutput() and ComputeGradient().
  • "Arbitrary" Neurons/functions can be implemented in child classes and some samples are given like such as sigmoid, linear, sum, product, max Neuron etc.  
  • Some design decisions have to be made on where and how to implement network input, neuron inputs and outputs, network outputs, connections ( "arbitrary" feedforward), weights (parameters of the "arbitrary" neuron function) and gradients.
Later I was curious if an optimal step in the gradient was easy to implement so I added a sketchy implementation of a training Algorithm.
Since I had no practical application with experiments on real datasets in mind this was a very low priority and never ending project. I decided to end this project by publishing this code as a CodeProject trick/tip because the approach with "arbitrary" gradient/functions and the first design considerations might be of some interest.
The emphasis of this trick/tip is on the Neuron class with  "arbitrary" functions ComputeOutput and ComputeGradient and the design considerations of the network and neuron with a first sketchy proof of concept implementation. The software is not intended for practical use.
When using standard QuickProp provisional test results on the XOR problem look a factor worse than reported by Fahlman, so I am not totally convinced that the implementation is correct. Please report major errors, although it is not likely that I make an an article from this trick/tip.

Feedforward network architectures

I assume that the reader is familiar with Feedforward Networks and its training. See for some popular C# stuff for example visualstudiomagazine. A Network of Neurons is used. A standard sigmoid Neuron computes a weighted sum of its inputs and then applies a sigmoid function to compute its output. Neurons are successively computed in a feedforward way using the network input and outputs of previous computed neurons.

Several topologies are possible for example
  • In a one layer network (all neuron are output neurons, connected to all inputs; in classification the neuron with the highest output depicts the class recognized).
  • In a 2 layer network the inputs are connected with a layer of hidden neurons, the output neurons are fully connected with the hidden neurons and in a 3 layer network there are 2 layers of hidden neurons.
  • In the cascade network (introduced by Fahlman, who used growing networks during training) all successive hidden neurons are connected with all inputs and previous hidden neurons and its output is connected to all output neurons. The number of extra parameters compared to a one layer network is moderate. 
  • Other well known "Feedforward" Networks are the Time Delayed Neural Network (TDNN) introduced by Waibel to classify a phoneme by its context using shared weights. We will not implement these. Handling shared weights is simple, but constructing a network topology from a high level text/XML specification is more work.
  • Recurrent networks with time delays/ connections between successive time steps can be considered as a Feedforward Network if the input sequence is limited/finite by unfolding the network and input in time (construct each time step a input, network and desired value). Given the right topology even negative time delays can be implemented.

Feedforward Networks for Classification

The weights/parameters of a network have to be trained. In Pattern Recognition we have often a Learning Set and a Test Set. On the Learning Set we train the parameters (fitting), ideally we use the Test Set once/sparsely to determine the score of the trained network (generalization).
Larger networks with lots of free weights/parameters will fit a learning set easier but can have worse generalisation on a test set with samples never seen before. This is similar with function approximation given n points. A nth order polynomial can fit the n points exactly, but the interpolation/generalisation on points outside the training data can be worse then for example a linear approximation.
Many classifiers exist in Pattern Recognition such as k-Nearest Neighbour, Tree, SVM, Forest Trees, AdaBoost etc. In the universe of problems there is no free lunch e.g. there is no universal best solution. On the other hand the universe of problems is in certain domains not random :=). So a neural network that is a universal function estimator has its use, and a neural network that approximates a known distribution at hand has also its use.  
It is interesting to note a linear plane (= a one layer network) in N dimensions is able to assign any N+1 samples with different input values any desired label (0/1), see also the VC dimension.  So in 2 dimensional space a one layer network can assign any 3 samples any desired label, but not any 4 samples (XOR problem). In higher dimensional feature spaces our intuition is not always correct and the linear plane can be adequate (see also the principle of SVM, enlarge the dimension of the feature space). If we use a one layer network to recognize a phoneme with for example its context using 15*16 = 240 inputs, it can assign any 241 different samples any label. Normally data of the same class is clustered, so if there is enough separation in feature space we could theoretically cover 241 clusters.
However sometimes a higher VC dimension is needed. Sometimes it can also be useful to incorporate some knowledge into the network. In some domains representation ( features) is crucial and it can be beneficial to train  in a competitive way for example the moving filter "features" of a TDDN.

Training. Minimize Error criterion using gradient search.

Finding the weights given a learning set with samples is computationally hard. Often a heuristic method is used. However a heuristic method may not find the optimal solution and the actual heuristic method used can be crucial for the classification result.
Feedforward networks are often trained using back propagation.  1) An continuous error criterion is defined. 2) Over the Learning Set an Error gradient in respect to the weights is computed in a backward way using the chain rule over all samples. 3) Each iteration the weights are adapted using the gradient with a small step toward a smaller error. 4) The training must be stopped at the right time to prevent over fitting.  For simplicity I will consider here only computation of the gradient over the whole learning set per iteration here, so not online learning.
A gradient search may require many steps and can get stuck in a local minimum. The search process starts with small random weights for breaking the symmetry for hidden neurons in a layer.
The most simple way is to step with a given small step size into the direction opposite the gradient. Sometimes a momentum term is added e.g. the weighted previous adaptation of the weights. The new step can also be computed using the previous gradient and adaptation of the weights. If the optimal step size is computed (only Error has to be computed in the direction of the gradient) it is possible to use a conjugate direction method such as Polak Ribiere.
In this trick/tip I used the quickprop algorithm, introduced by Fahlman. On the limited pattern recognition problems I worked on in the past it performed reasonably well on classification and training time.
The final step is to decide when to stop the training. We can stop if the error or score on the learning set does not improve after a number of iterations (fitting). However in Pattern Recognition problems the network can be overtrained and at some time its score on the Test Set may get worse (generalisation). In my former experiments I used the score on a separate stop set to determine when a training could be stopped, and in this trick/tip I also implemented the use of a stop set.
The competitive training of outputs does normally not require a normalisation in the model/network architecture and sometimes application dependent knowledge can be implemented in the network architecture. However the norm of the weights in relation to the inputs is an important factor (for large weights the continuous error landscape behaves more discrete with gradients zero in large parts of the weight space). It can be beneficial to norm the network inputs, use symmetrical hidden neurons, play with the initialization of the weights of a neuron, adapt the error criterion (add a weight decay in the gradient step) etc.

Computing the gradient with the chain rule in a network with "arbitrary" neurons

Suppose we choose a quadratic error measured over all Learning Samples L and the outputs of the C output neurons, see Figure 1. The desired value d for sample with a feature vector of x (network input) is 1 if the neuron depicts the desired class, otherwise 0.
Image 1
Figure 1. Error Criterion.
The derivative of E with respect to Yj of the output neurons of one sample can be computed, see figure 2 lower right formula. Next the neurons are handled in a backward direction compared to the Feedforward computation. Given the derivative of the Error with respect to a neuron output, the contribution to the derivative of E with respect to its inputs s can be computed by using the chain rule, see figure 2 top right formula.
Image 2
Figure 2. Chain rule to backpropagate error from output neuron y to neuron input s (output neurons bottom-right formula, hidden neurons top-right formula)
It is possible to choose several functions y=F(w,s). By applying the chain rule it is possible to compute the derivative of E in respect to the weights. See figure 3 for some examples. Note that it is of course more efficient to use larger units then to construct a network with elementary multiplication, sum etc. neurons.
Image 3
Figure 3. Some sample neurons and their derratives for inputs and weights.
The weighted distance is mentioned for a small experiment to find multiple clusters in the Timit database (failed, an optimised distance method behaves somewhat as a one layer Feedforward network), the max function is mentioned (not quite correct in the table, output derivative zero for non maximum inputs) because in one experiment I did optimize the selected substitution costs from the best path of a Minimal Edit Distance (so not really a max/min in the feedforward network).

Design Considerations Network/Neuron

We took a neuron class with functions ComputeOutput() and ComputeGradient() as basis of our design. Next we have to decide where and how to implement network input and output, neuron inputs and outputs, weights, derivatives  and connections. We can choose to implement these in the network or in the neurons. Several choices are possible and valid. I have chosen in this first iteration for what seems the most convenient, in a next iteration run times could be a design factor. 
  • In the network an array y is used to store network input, output of the hidden neurons and output of the output neurons. As I remember this is convenient for implementing RNN.
  • A minor decision is to implement in the neuron an integer yIndexOut, y[yIndexOut] depicts the value in the y array of the Neuron output. The neuron has only one output.
  • In the network Weights (array wf) and derivatives (array dEdy and dEdwf) are stored. This is most convenient for the gradient search. With growing networks,  normalisation per neuron or for feedforward computing speed storing these weights (or a shadow copy) in the neurons could be more convenient.
  • A minor decision is to implement in the neuron wL and wH, in wf[wL..wH] the weights/parameters of the neuron are stored.
  • Connections from or to y can be coded in explicit as "for" loops in forward and backward direction. We have chosen to use per Neuron an yIndexIn[] array that is constructed in network initialisation. This will cost an extra array access in comparison to explicit for loops.
  • In the neuron the array yIndexIn[] and integer yIndexInH are stored, yIndexIn[0..yIndexInH] are the indices of the inputs of the neuron in the y array. 
Given these choices ComputeOutput() and ComputeGradient() must have parameters to access the network variables, I have chosen for ComputeOutput(double[] wf, ref double[] y) and ComputeGradientBackward double[] wf, double[] y, ref double[] dEdy, ref double[] dEdwf).
However it is possible give the neuron a network a property that points to its parent network (set at neuron/ network initialisation), or use a function with as single parameter the (parent) network of the neuron. This could be considered for the next iteration, where run times could be considered in the design. I do not like the other option to define all neurons within the network class.
As said, several choices are valid and a next iteration can learn from the choices shown. In the following I give a short introduction to the code. Note that I defined some interfaces for documentation purposes only. 

Networks and Neurons

Image 4

INeuron.cs contains an interface defined for documentation purposes, Neuron.cs contains an abstract class Neuron.
    public interface INeuron
        // wf, parameters for this Neuron in wf[wL..wH], wf[] in network
        int wL { get; set; }
        int wH { get; set; }

        IEnumerable<int> wfIndexNeuron();

        // connections from y[] of network to inputs of this neuron locally;
        // yIndexIn[0]..yIndexIn[xx]..yIndexIn[yIndexInH].
        int yIndexInH { get; set; }
        int[] yIndexIn { get; set; }

        IEnumerable<int> yIndexInAll();

        // Only one output per neuron.
        // Neuron outputs to y[yIndexOut] FeedForwardNetwork. Gradient dEdy in dEdy[yOutIndex].
        int yIndexOut { get; set; }

        // ComputeOutput uses wf[] and y[] of network to perform forward computation.
        // ComputOutput uses y[ yIndexIn[..] ] as neuron inputs, writes neuron output to y[yIndexOut] 
        // ComputeOutput abstract method, must be implemented in non abstract class, see neurons.cs 

        void ComputeOutput(double[] wf, ref double[] y);

        // given dEdy[yIndexOut] chain rule used to compute dEdy inputs(yIndexIn[]) 
        // and dEdwf of neurons parameters (wfIndexNeuron[])
        void ComputeGradientBackward(double[] wf, double[] y, ref double[] dEdy, ref double[] dEdwf);
In Neurons.cs we define sketchy several neuron classes (from abstract class Neuron) with different ComputeOutput() and ComputeGradient() functions such as LinearNeuron, SigmoidNeuron, SigmoidActivation, TanhNeuron,  SumNeuron, ProductNeuron, DivisionNeuron, MaxNeuron. Note that LinearNeuron, SigmoidNeuron and TanhNeuron have common code. For testing the Xor problem I added some output neurons to play with error criterion such as the EntropieOutputNeuron ().
IFeedforwardNetwork.cs contains again an interface for documentation purposes:
public interface IFeedForwardNetwork
    // Refinement: split interface for forward computation and backward gradient computation

    // y[0..yH] vector
    // y[] input sample + hidden + output map to y;

    // y[] used as input for Neurons, Neurons write to y[Neuron.yIndexOut]
    // y[] not in interface, no property since we can't use properties as procedure parameters;
    // in implementation public double[] y etc

    // double[] y { get; set; }
    // double[] dEdy { get; set; }

    int yH { get; set; }

    // y[0..xH] copy of input; y[hl..hH] output of Hidden Neurons; y[oL..yH] output Output Neurons
    int xH { get; set; }
    int hL { get; }
    int hH { get; set; }
    int oL { get; }
    int oH { get; }

    void SetNetworkDimensions(int nInput, int nHidden, int nOut);

    // Some Enumerable s to access ranges, use: foreach (int iInput in yIndexInputX()) {}
    IEnumerable<int> yIndexAll();
    IEnumerable<int> yIndexAllNotInputNeurons();
    IEnumerable<int> yIndexHiddenNeurons();
    IEnumerable<int> yIndexInputX();
    IEnumerable<int> yIndexOutputNeurons();

    // Some variables defined in Network class, but not as properties, so not in interface:
    // List<INeuron> Neurons;

    // wf[] all wf/parameters of network. Neurons access their own wf[]
    int wH { get; set; }
    // double[] wf { get; set; }
    // double[] dEdwf { get; set; }

    void ComputeNetworkFeedForward(ISample sample);

    // quadratic error outputs and desired outputs
    double ComputeError(int desiredLabel);

    // FeedForwardNetwork[0..], returns values output neurons
    double this[int index] { get; }

    // BestClass for Classification, Delta for reliable reject, dep. error criterion
    int BestClass();
    double DeltaOutput();

    // Computing Gradient, not in separate interface/child class:

    void InitRandomWf(double delta = 0.1);
    void ZerodEdw();

    // set dEdy output layer given criterion, init rest
    void SetdEdyFromDesiredOutput(int desiredLabel);

    // and compute dEdy and dEdWf by backwards propagation
    void ComputeNetworkGradientBackward(int desiredLabel, bool InitDeDw = false);

    // Normalize the gradient on the nrSamples, Gradients computed are summed
    void dEdwfNormalise(int nrSamples);
In FeedForwardNetwork.cs we define the class FeedForwardNetwork. The main loop in ComputeNetworkFeedForward() is:
foreach (Neuron n in Neurons) n.ComputeOutput(wf, ref y);
The main loop in ComputeNetworkGradientBackward() is:
for (int n = Neurons.Count - 1; n >= 0; n--)
     Neurons[n].ComputeGradientBackward(wf,y,ref dEdy, ref dEdwf);
In FeedforwardNetworks.cs we define some networks with functions for initialisation (loosely specified):
  • OneLayerNetwork(NrInputs, NrOutputs)
  • CascadeNetwork(NrInputs,NrHidden,NrOutputs)
  • FullyConnectedOneHiddenLayerNetwork
          (NrInputs,NrHidden,NrOutputs, Func<INeuron> CreateHidden, Func<INeuron> CreateOutput)CreateHidden, CreateOutput can be specified in function call by lambda expression: (.., ()=> new HalfTanhNeuron(), ()=> new SigmoidNeuron()). 
The somewhat tricky code of the connections is in the network initialisation and in the computations of ComputeOutput() and ComputeGradient() of the neuron classes.

Tip: measuring run-times

In this project I did not care about computing times. I also did not consider using my graphic card or the cloud as computing resources. However if computing time is a factor (when experimenting and training on large datasets this is always a major factor) it is noteworthy that there is a NuGet package to run benchmarks. So just like running standard Unit tests it could be possible to run some standard runtimes benchmarks for new versions. I got this tip from Hanselman's Blog ,the GitHub page of the original project of Matt Warren see here.

Points of Interest

  • We presented a first trial design of a feedforward network with neurons with "arbitrary" output/gradient and "arbritrary" feedforward connections.
  • We discussed shortly some design decisions where to implement (in network, in neuron ) network input, output, output of hidden neurons , weights, connections etc.
  • This first iteration trial can be used as a reference for a next iteration of the software.
  • The software is not intended for practical use. There are deep learning frameworks already available.
  • Before actually using the software similar results as reported by Fahlman should be obtained, which is a project of its own.
  • Runtimes are not considered in this first try. Using a GNU package runtimes could be measured.
  • It could be considered to pass the parent network as a function parameter or as property in the neuron. In this way each neuron can access weights etc. from the network directly.  
  • The sample class that allows different kind of extra info is too complex, next iteration samples should be just a label and a feature vector.
  • The approach does have some overhead in Neurons and calls to functions computeOutput() and ComputeGradient(). When using layers and in each layer standard neurons  a few explicitly coded for loops are more efficient in code size, complexity and runtimes .
  • Separating the construction of the connections and the ComputeOutput() and ComputeGradient() makes it somewhat simpler to adapt the network and its neurons.

Appendix A. Samples and Basic IO

Image 5

In BasicIo.cs we find some provisional serialisation. Idea was to read/write samples and network using XML serialisation, also for debugging. If individual samples are serialised using XML and written to file this does not directly result in a valid XML document. The Neurons list of INeurons in a network cannot without some extra code dumped to XML. Finally I ended up using binary serialization as a provisional start. In a next iteration we could consider a faster serialisation.

In ISample.cs and ISampleSet.cs we define some interfaces for the samples and the samplesets used for training.

public interface ISample
    int xH { get;}
    // Pattern with feature vector x of float[]
    float[] x { get; set; }

public interface ISampleInfo
    int label { get; set; }

public interface ISampleWithInfo<TSampleInfo> : ISample where TSampleInfo : ISampleInfo
    TSampleInfo sampleInfo { get; set; }

public interface ISampleSet<out T>
    void First();

    T GetNextSample();
    bool IsLastSample();
Samples are normally just arrays of feature vectors and a label. As I remembered for many projects is was convenient to store extra project info the sample (logical info such as field, layout info such as sequence of rotated snippets to extract pattern from total image). For that reason I added the possibility to add some extra info to the sample using generetics. I did not consider Inversion of Control because I.M.O. generetics is a little more basic.
In samples.cs we define as an example two classes of samples, one using class MySampleInfo that contains only the required label, the other using MySampleInfo1 containing an additional id. In SampleSets an example of the definition of a Xor sample set we used for testing, for more details download code. Make sure that the SampleInfo of the sets used match the SampleInfo of the training class creation.  
public class XOrSampleSet1 : ListSampleSet<MySampleWithInfo1>
  override public void MakeList()
    var x00 = new MySampleWithInfo1 { sampleInfo = new MySampleInfo1 { label = 0, id = 0 },
                                      x = new float[2] { 0, 0 } };
    var x01 = new MySampleWithInfo1 { sampleInfo = new MySampleInfo1 { label = 1, id = 2 },
                                      x = new float[2] { 0, 1 } };
    var x10 = new MySampleWithInfo1 { sampleInfo = new MySampleInfo1 { label = 1, id = 1 },
                                      x = new float[2] { 1, 0 } };
    var x11 = new MySampleWithInfo1 { sampleInfo = new MySampleInfo1 { label = 0, id = 3 },
                                      x = new float[2] { 1, 1 } };

     samples.Add(x00); NrSamples++;
     samples.Add(x01); NrSamples++;
     samples.Add(x10); NrSamples++;
     samples.Add(x11); NrSamples++;

In the design of samples the emphasis was more on software exploration than simplicity. However the chosen approach is too complex and confusing and for educational reasons and to avoid errors,  the sample class could be simplified to a label and a feature vectorin the next iteration of the software.

Appendix B. Training

Image 6

Again the INetworkTraining.cs. an interface for documentation purposes.
public interface INetworkTraining<TSampleInfo> where TSampleInfo : ISampleInfo

  // - Training1() as sample uses default InitTraining1() which sets parameters
  // - Alternatively all parameters can be set and then use: InitTraining1=false; Training1(useInitTraining1)
  // - Training1() can also be overwritten in child class

  int nrMaxIterations { get; set; }
  int nrTrainingSamples { get; set; }

  ISampleSet<ISampleWithInfo<TSampleInfo>> learningSet { get; set; }
  ISampleSet<ISampleWithInfo<TSampleInfo>> testSet { get; set; }
  ISampleSet<ISampleWithInfo<TSampleInfo>> stopSet { get; set; }

  FeedForwardNetwork ffNet { get; set; }

  Training.QuickProp quickProp { get; set; }

  void ComputeGradient(ISampleSet<ISampleWithInfo<TSampleInfo>> learningSet, FeedForwardNetwork ffNet);

  int ComputeScoreSet(ISampleSet<ISampleWithInfo<TSampleInfo>> testSet, FeedForwardNetwork ffNet);

  double ComputeErrorOnSet(ISampleSet<ISampleWithInfo<TSampleInfo>> _Set, FeedForwardNetwork _ffNet);

  void AdaptWeightsUsingGradient();
  void AdaptWeightsGradientWithOptimalStepSize();

  // Methods called (or overridden in child class) for training

  // refinement: stopTrainingAsap can be external set to stop training
  // does not work yet, UI blocks?, start training on other thread?
  bool stopTrainingAsap { get; set; }

  // virtual methods, can be overwritten in child class
  bool ContinueTraining(int iIter);
  bool ContinueTrainingWithStopSet(int iIter, int errorStopSet, int MaxIterationsNoImprovement = 100);

  void ReportEveryIteration();
  void ReportFinalResults();

  // For running sample use Training1()
  // Other possibility specify parameters first and then call Training1(false)
  // Otherwise define derived child class and redefine Training 1 etc.
  // ... or define your own network training module ;=)

   void InitTraining1();
   void Training1(bool useInitTraining1 = true);
The property ffNet holds a Feedforward network (with weights and gradients), so the training software is now specific for training a FeedForward network with using  QuickProp. In a next iteration interfaces could be defined, so the class for "network= something with weights and gradient" and gradient step function can be set as a parameter. NetworkTraining.cs contains a sketchy implementation of the class NetworkTraining. In the code one training example is given. In InitTraining1() the sets, the network used and initialisation with random values and Quickprop parameters are set.
For changing learning parameters, sets etc. it is possible to 1) define a new class that inherits from this class and override function InitTraining1() and possible other functions; 2) set all parameters first and call Training1(False) so that the initialisation is not used or 3) finally to use copy and paste.
It is important to note that in the Main ViewModel (file MainVm.cs) of the minimal WPF MVVM demo program ReportEveryIteration() and ReportFinalResults() are overwritten in the operational class to access the properties of the ViewModel for output. 
The quickprop algorithm adapts the weights. Below the interface, note that the quickprop algorithm itself has 3 parameters mu, epsilon and decay. Note that for the first iteration we explicitly defined WfAdaptFirstStep(), however if deltawOld[] is zero the first iteration WfAdaptQuickPropStep(..) behaves similar. 
public interface IQuickProp
    // Set nrWf, required!!
    int nrWf { get; set; }

    // Internal used variables in Step algorithm
    double[] dEdwOld { get; set; }
    double[] deltawOld { get; set; }

    double stepOld { get; set; }


    // Magic but crucial Quickprop training parameters
    // Note that the initial settings of weights (random size) is also crucial parameter
    double epsilon { get; set; }
    double mu { get; set; }
    double decay { get; set; }

    // double[] generalParameterSettings = new double[3] { 0.1, 1.0, 0.0001 };
    // //public double[] xorParameterSettings = new double[3] { 4.0, 2.25, 0.0001 };
    // //No epsilon sharing; normalisation to nr samples in Fahlman??:
    //double[] xorParameterSettings = new double[3] { 1.0, 2.25, 0.0 };

    double[] GetCurrentParameters();
    void SetCurrentParameters(double[] parameters);

    // GradientStep
    void WfAdaptFirstStep(ref double[] wf, double[] dEdwf, double gradStart = 0.1);
    void WfAdaptQuickPropStep(ref double[] wf, double[] dEdwf);
UtilDeepCloneCopy.cs and UtilGoldenSectionSearch1D.cs where added for a proof of concept of how to incorporate an optimal gradient step. However the GoldenSectionSearch is probable not a correct implementation, I did not take time to understand the algorithm properly. Better is to use the Brent search algorithm.

Appendic C. Provisional Testing

I did only a very provisional test on crashing/convergence. The XOR problem is for Feedforward networks most notorious sample and has local minima. Since its has a few parameters other search techniques could be used. For large dimensional classification problems it may be not be so relevant. I wrote a simple WPF program for testing (see figure).
Image 7
Fahlman did write a report about the quickprop on some encoding/decoding problems and he has discussed his specific approach to the Xor problem shortly. To quote from Scott E.Fahlmans report
"An Empirical Study of Learning Speed
in Back-Propagation Networks
" from September 1988:  "Using quickprop with hyperbolic arctan error, epsilon divided by fan-in, and symmetric activation, and with the restart limit set at 40 epochs, I got the following result for XOR with two hidden units:
Trials Eps Mu Random Max Min Average S.D.
100 4.0 2.25 1.0 66 10 24.22 16.3

 In 100 trials there were 14 restarts. The median learning time was 19 epochs." See for further details Fahlman's report. For stop criterion he required that the outputs had a small error. 
A simple wpf program was used for testing. I used sigmoid Neurons in hidden and output layer. I did 50 runs with maximum iterations iterations set to 40. My (manual) less strict criterion for convergence was 3 successive iterations with 0 errors. Only 50% were successful with an average of 25 iterations. Even with my less strict criterion the results reported by Fahlman are better.
So I did another experiment by mimicking Fahlman's experiment more close. I used an Xor problem with inputs -0.5..0.5. I adapted the initialisation function FullyConnectedOneHiddenLayerNetwork() so that the hidden and output neurons creation could be specified by a lambda expression on function call. For the hidden neurons I used tanh divided by 2. I did not use epsilon divided fan in (can be implemented in ComputeGradient Neurons).
I hacked some output neurons to play with the error criterion. I recently read that a neuron with sigmoid output, M.S.E. criterion and a linear derivative results in minimization of an entropy criterion. So I made 3 classes for output neurons:
  • EntropieOutputNeuron. Sigmoid, linear derivative.
  • FlatSpotOutputNeuron. Sigmoid, 0.1 + standard sigmoid derivative as described in Fahlman's report. At first sight that can be considered as a weighted sum of M.S.E. and entropy criterion.
  • ArcTanhOutputNeuron. FlatspotNeuron, but non linear processing of the error by taking dedy=ArcTanh(dedy) as I understand from Fahlman's report. The ArcTanh on the derivative seems at first sight behave somewhat as the EntropieOutputNeuron, but combination of 0.1 + standard sigmoid derivative I do not understand that yet, although it might work.
So I did another 50 runs (pfft clickerdeclick .. did not wrote an optimisation program for that), epsilon set to 8: 68% (34) were successful with an average of 17 iterations. If we should consider restarts and take 17*2.1 = 35 iterations. Convergence and nr iterations is still not so good as reported by Fahlman's (given S.D. seems statistically significant). 
Before going to any next iteration it should be checked that we have made a correct implementation. First we have to define a good benchmark (encoder/decoder problem?) and start with the most simple gradient steps  (standard backprop, Rprop and so on).


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By
Netherlands Netherlands
Retired hobby programmer.

Comments and Discussions

Questiondouble versus float Pin
sx200822-Nov-16 12:31
sx200822-Nov-16 12:31 
I think 32-bit floating point precision should be enough for a neural network.
Some neural networks even use 16 oder 8 bit OMG | :OMG: floats for the weight factors.

Changing the datatype from double to float would reduce the memory footprint and maybe speedup the calculations a little bit.

the transfer functions (TanhFunction(),SigmoidFunction(),...) should be static functions because the implicit this-parameter is not required.
AnswerRe: double versus float Pin
wim4you23-Nov-16 1:33
wim4you23-Nov-16 1:33 
AnswerRe: double versus float, use of System.MathF instead of Math Pin
wim4you4-Mar-19 0:58
wim4you4-Mar-19 0:58 
QuestionffNetwork.bin not found Pin
Member 1225045517-Nov-16 9:24
Member 1225045517-Nov-16 9:24 
AnswerRe: ffNetwork.bin not found Pin
wim4you17-Nov-16 13:11
wim4you17-Nov-16 13:11 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.