# Lessons Learned From Building a Hello World Neural Network

# Lessons Learned From Building a Hello World Neural Network

My personal experience with Neural Networks began some time ago. Reading about the amazing things a neural network could do made me eager to explore this pro...

Join the DZone community and get the full member experience.

Join For Free**Bias comes in a variety of forms, all of them potentially damaging to the efficacy of your ML algorithm. Read how Alegion's Chief Data Scientist discusses the source of most headlines about AI failures here.**

My personal experience with neural networks began some time ago. Reading about the amazing things a neural network could do made me eager to explore this problem-solving approach that has attracted so much attention during the past few years.

I remember myself impressed by a model that generates natural language descriptions of images and their regions, developed at the Stanford University in 2015, thinking that I would like to be able to do similar things at some point. So I started searching.

From my experience in other machine learning-related topics, very detailed mathematical explanations that are full of derivatives and equations make understanding difficult — at least in the beginning. So, I decided to ignore them for the time being.

Of course, this didn't mean that I could start coding right away. I had to learn about some basic concepts related to neural networks to be able to understand the basics at a conceptual level at first.

Searching Google, I found many online courses, blogs, and tutorials explaining the basic concepts. These included gradient descent, forward and back propagation, and how I had to apply them in the construction of a neural network. Very minimalistically, I would summarize these methods as follows:

Forward propagation is about propagating the output of each layer through all the following layers until we reach the output layer. It refers to the actual computation of the prediction a neural network makes.

Backpropagation, on the other hand, is used so that every time the network outputs a prediction that yields a large error, the input weights that contribute to its minimization are reinforced.

The minimum values the error would take can be computed using gradient descent, an optimization algorithm that is capable of finding local minima of a given function.

Of course, there's much more to it than these terms. Every type of neural network out there, from a simple multilayer perceptron to a recurrent neural network, has each own technical details and mechanisms that one has to learn before deploying it.

Not actually having a particular problem in my mind to solve, I decided to start the exploration from the simplest type of neural networks. With the multilayer perceptrons (MLP), one can easily implement useful regression and classification tasks. With Python being my language of choice, I investigated the available libraries for building neural networks — and from scikit-learn to Google's TensorFlow and Keras, the options were many.

**A Toy Dataset**

I knew that at the end I was going to use one of these libraries as everyone else does. Nevertheless, I chose to implement my first baby perceptron classifier from scratch.

Although the resulting network was very very simple and not at all fancy, I stopped thinking about it as a black box.

And that was a critical step towards understanding. I chose every detail of the architecture, saw the computations performed during training and at last, I evaluated the results.

The input I used for this task was the make_circle toy dataset of 400 points provided by scikit-learn. Although the results seemed satisfactory, it was clear that for a more complex dataset, my perceptron would be inadequate.

**The MNIST Dataset**

Constructing from scratch is quite painful especially as the network's complexity increases.

So, TensorFlow seemed a good way to go.

Personally, I chose it over Keras as for someone like me, who is in the learning process, Keras seemed to be less customizable and more like a black box.

For my new attempt, I wanted a dataset closer to a real-world application than the previous one. The well-known MNIST dataset, which contains images of handwritten digits that need to be classified, seemed a good choice. After experimenting with different tuning parameters, high accuracy was achieved with a perceptron with more hidden layers and much more computational nodes than the first baby net.

If you are going to ask me how I knew the right value of each of the tuning parameters, I'm going to tell you that I didn't. From my short experience in the field and the research I've done, I would say that tuning your neural network is more of an art and less of a deterministic process as generally there is no rule to guide you through every situation. Despite this, as your experience grows, you will develop some intuition around the tuning. My personal bag of tips, gathered mostly by searching and asking others, more expert in the field, include the following:

**Number of inputs and outputs**: This decision is truly very easy. The number of inputs is always set equal to the number of features of the input data, while the number of outputs (in the case of a classification task) is determined by the number of classes we want to classify in.**Number of hidden layers**: The method of choosing is a bit vague. Generally, for the majority of tasks you would like to accomplish, you can start with one or two layers, evaluate the results, and revise your choices. Keep in mind that even complex functions can be modeled with one layer if the number of neurons is high enough. On the other hand, the increase of the hidden layers results in an exponential decrease of the neurons required per layer.**Number of nodes per layer**: For the number of neurons per hidden layer, again you have to experiment. It is quite common to keep their number per layer constant or create a tunnel-ish architecture where each layer has fewer neurons than the previous one.

Following the above tips, I ended up with a perceptron with two hidden layers each one of them having 40 and 30 nodes accordingly. As for the activation and loss functions, my choices were ReLu and softmax activation for the output layer along with cross-entropy loss.

The reason for this decision is that ReLu is a bit faster than others and most importantly doesn't get trapped easily into local minima as it doesn't saturate for large inputs. Softmax is suitable for the output layer on classification tasks where the output classes are exclusive.

The results of this tuning were also satisfactory with achieved accuracy over 95% after 50 iterations over the perceptron.

**A Real-World Example**

Having already built a simple neural network that seemed to work, I decided to use the implementation in a real problem that I would like to be able to solve. For this, I chose a mailing list classification task with data collected from MailChimp with the help of an ETL service like Blendo. The data consist of location information, mail client and type, and of course the mailing list segment to which the recipient belongs.

At first, I experimented with exactly the same architecture I had built for the MNIST, with disappointing results.

My first observation was that as the iterations were going by, although initially the accuracy was increasing, at some point it started to decrease. This failure of my perceptron to converge to the right prediction was due to the learning rate's large value I had set for the gradient descent. With this step, the algorithm, in fact, bypassed the minimum precisely the moment the accuracy started to fall continuously. o fix this problem, I chose to just lower the learning rate up to the point the gradient descent finally converged.

After resolving this, I retrained the perceptron, and again the results seemed to be poor as the accuracy didn't manage to exceed the 25%. After experimenting with the tuning parameters of the network, I managed to achieve at most 50% accuracy.

To my surprise, this accuracy was achieved for a relatively small number of hidden layers and computational nodes.

That was a result I wasn't expecting. I had the impression that the data weren't very informative about the output variable and so a more complex function needed to be fit.

What troubles me the most is the fact that after only eight iterations the accuracy starts to fall drastically on the test dataset while it keeps increasing on the train.

According to my experience, this is an obvious example of overfitting, but it seems weird to me that this effect appeared after only eight iterations.

**Outro**

To me, what became evident through the whole process is that different data may require completely different tuning. There is no such thing as an average case or a common tuning. Furthermore, finding an efficient combination of parameters is mainly a result of experimenting.

As the code developed is not optimized either for results' accuracy or on execution efficiency, there are many ideas for further improvement, including:

**Further experimentation**with tuning parameters, activation functions, and loss functions.**Implementation of a non-constant learning rate**. At first, we need quite high learning rate for gradient descent to move quickly towards the minimum value. As we get closer to the minimum, we lower the step so that the algorithm does not bypass it.**Implementation of early stopping so that the algorithm won’t continue training at the expense of generalization error**in cases where the accuracy of data outside the train set has reached an upper bound.

**Your machine learning project needs enormous amounts of training data to get to a production-ready confidence level. Get a checklist approach to assembling the combination of technology, workforce and project management skills you’ll need to prepare your own training data.**

Published at DZone with permission of Eleni Markou , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

## {{ parent.title || parent.header.title}}

{{ parent.tldr }}

## {{ parent.linkDescription }}

{{ parent.urlSource.name }}