Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Correction in the formula for mean squared error #845

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from
Closed

Correction in the formula for mean squared error #845

wants to merge 5 commits into from

Conversation

krishnaw14
Copy link
Contributor

@krishnaw14 krishnaw14 commented Mar 14, 2018

There was a minor error in the formula for mean squared error in neural_nets.ipynb

@@ -82,7 +82,7 @@
"\n",
"In both the Perceptron and the Neural Network, we are using the Backpropagation algorithm to train our weights. Basically it achieves that by propagating the errors from our last layer into our first layer, this is why it is called Backpropagation. In order to use Backpropagation, we need a cost function. This function is responsible for indicating how good our neural network is for a given example. One common cost function is the *Mean Squared Error* (MSE). This cost function has the following format:\n",
"\n",
"$$MSE=\\frac{1}{2} \\sum_{i=1}^{n}(y - \\hat{y})^{2}$$\n",
"$$MSE=\\frac{1}{2n} \\sum_{i=1}^{n}(y - \\hat{y})^{2}$$\n",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be \frac{1}{n}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess both conventions are used. In this website, it uses 2n and in this, it uses n.

Anyways, I made the changes.

@norvig
Copy link
Collaborator

norvig commented Mar 15, 2018

Oops, there are conflicts agin, due to another PR. These are really hard to review for .ipynb

@krishnaw14
Copy link
Contributor Author

Should I send another PR after pulling the latest changes from the repository? @norvig

Changes from original repo
@ad71
Copy link
Contributor

ad71 commented Mar 15, 2018

This PR contains duplicated changes. It will be easier if you close this PR, update your working directory, create a new branch and open a fresh pull request. Be sure to make a branch before you commit changes. The master branch is for updating the local directory from the upstream repo.

Bringing up to date with original repo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants