我的NN代码出了什么问题? [英] What's wrong with my NN code?

查看:347
本文介绍了我的NN代码出了什么问题?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好

我是编程的新手

我想在神经网络中为xor函数实现简单的Madaline

我用的是算法(见下面的链接)

但它没有给我正确的答案

它应该在4个时代后给出正确的答案

什么是错的用我的代码?

谢谢... /



这是链接:

>算法

.....



我尝试过:



Hi there
I'm new to programming
I want to implement simple Madaline for xor function in neural network
I used the algorithm(see the link below)
but it does not give me the right response
it should gives right answer after 4 epochs
what's wrong with my code?
thanks.../

this is the link:
algorithm
.....

What I have tried:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace xxxxxxx
{
    class Program
    {
        static void Main(string[] args)
        {
            int[,] x = new int[,] { { 1, 1 }, { 1, -1 }, { -1, 1 } };
            int[] t = new int[] { -1, 1, 1 };
            double[,] w = new double[,] { { 0.05, 0.1 }, { 0.2, 0.2 }, { 0.5, 0.5 } };
            double[] b = new double[] { 0.3, 0.15, 0.5 };
            bool ep = true;
            int x1;
            int x2;
            double zin1;
            double zin2;
            int z1;
            int z2;
            double yin;
            int y;
            while (ep)
            {
                ep = false;
                for (int j = 0; j < 3; j = j + 1)
                {
                    x1 = x[j, 0];
                    x2 = x[j, 1];
                    zin1 = b[0] + (x1 * w[0, 0]) + (x2 * w[1, 0]);
                    zin2 = b[1] + (x1 * w[0, 1]) + (x2 * w[1, 1]);
                    z1 = f(zin1);
                    z2 = f(zin2);
                    yin = b[2] + z1 * w[2, 0] + z2 * w[2, 1];
                    y = f(yin);
                    if (y != t[j])
                    {
                        ep = true;
                        if (t[j] == 1)
                        {
                            if (Math.Abs(zin1) < Math.Abs(zin2))
                            {
                                b[0] = b[0] + 0.5 * (1 - zin1);
                                w[0, 0] = w[0, 0] + 0.5 * (1 - zin1) * x1;
                                w[1, 0] = w[1, 0] + 0.5 * (1 - zin1) * x2;
                            }
                            else
                            {
                                b[1] = b[1] + 0.5 * (1 - zin2);
                                w[0, 1] = w[0, 1] + 0.5 * (1 - zin2) * x1;
                                w[1, 1] = w[1, 1] + 0.5 * (1 - zin2) * x2;
                            }
                        }
                        else if(t[j] == -1)
                        {
                            if (zin1 > 0 && zin2 > 0)
                            {
                                b[0] = b[0] + 0.5 * (-1 - zin1);
                                w[0, 0] = w[0, 0] + 0.5 * (-1 - zin1) * x1;
                                w[1, 0] = w[1, 0] + 0.5 * (-1 - zin1) * x2;
                                b[1] = b[1] + 0.5 * (-1 - zin2);
                                w[0, 1] = w[0, 1] + 0.5 * (-1 - zin2) * x1;
                                w[1, 1] = w[1, 1] + 0.5 * (-1 - zin2) * x2;
                            }
                            else if (zin1 > 0 && zin2 <= 0)
                            {
                                b[0] = b[0] + 0.5 * (-1 - zin1);
                                w[0, 0] = w[0, 0] + 0.5 * (-1 - zin1) * x1;
                                w[1, 0] = w[1, 0] + 0.5 * (-1 - zin1) * x2;
                            }
                            else if (zin1 < 0 && zin2 > 0)
                            {
                                b[1] = b[1] + 0.5 * (-1 - zin2);
                                w[0, 1] = w[0, 1] + 0.5 * (-1 - zin2) * x1;
                                w[1, 1] = w[1, 1] + 0.5 * (-1 - zin2) * x2;
                            }
                        }
                    }
                }
            }

            Console.WriteLine("b1:{0} , b2:{1} , b3:{2} \n w00:{3} , w10:{4} , w01:{5}, w11:{6}", b[0], b[1], b[2], w[0, 0], w[1, 0], w[0, 1], w[1, 1]);

            int[,] test = new int[,] { { -1, -1 } };
            x1 = test[0, 0];
            x2 = test[0, 1];
            zin1 = b[0] + (x1 * w[0, 0]) + (x2 * w[1, 0]);
            zin2 = b[1] + (x1 * w[0, 1]) + (x2 * w[1, 1]);
            z1 = f(zin1);
            z2 = f(zin2);
            yin = b[2] + z1 * w[2, 0] + z2 * w[2, 1];
            y = f(yin);
            if (y == 1)
            {
                Console.WriteLine("1");
            }
            else
            {
                Console.WriteLine("-1");
            }
            Console.ReadLine();
        }

  private static int f(double zin)
        {
            return (zin >= 0) ? 1 : -1;
        }
    }
}

推荐答案

既然你转发了这个问题,我会重新发布解决方案......





几件事:

1)不要使用单字符变量名:它们很容易输入,但无法阅读和解决发生的事情。使用描述变量的名称,特别是如果你想要一些其他可怜的草皮尝试阅读它。



2)如果你不这样做(1)上面,记录您的代码。实际上,无论如何都要记录您的代码。我完全不知道代码应该做什么,更不用说你做什么或不做什么,你认为错误或我应该如何测试以找出它。



3)编译并不意味着你的代码是正确的! :笑:

将开发过程想象成编写电子邮件:成功编译意味着您使用正确的语言编写电子邮件 - 例如英语而不是德语 - 而不是电子邮件包含您的邮件想发送。



所以现在你进入第二阶段的发展(实际上它是第四或第五阶段,但你将在之后的阶段进入):测试和调试。



首先查看它的作用,以及它与你想要的有何不同。这很重要,因为它可以为您提供有关其原因的信息。例如,如果程序旨在让用户输入一个数字并将其翻倍并打印答案,那么如果输入/输出是这样的:

Since you reposted the question, I'll repost the solution...


Several things:
1) Don't use single character variable names: they are easy for you to type, but impossible to read and work out what is going on. Use names that describe what the variables do, particularly if you want some other poor sod to try and read it.

2) If you don't do (1) above, document your code. In fact, document your code anyway. I have absolutely no idea looking at that what the code is supposed to do, much less what it does or doesn't do that you consider "wrong" or how I should test it to find out.

3) Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16

然后很明显问题出在将它加倍的位 - 它不会将自身加到自身上,或者将它乘以2,它会将它自身相乘并返回输入的平方。

所以,你可以查看代码和很明显,它在某处:

Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:

private int Double(int value)
   {
   return value * value;
   }



一旦你知道可能出现的问题,就开始使用调试器找出原因。在您的行上设置一个断点:


Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on your line:

while (pp < 15)



并运行您的应用。在执行代码之前,请考虑代码中的每一行应该做什么,并将其与使用Step over按钮依次执行每一行时实际执行的操作进行比较。它符合您的期望吗?如果是这样,请转到下一行。

如果没有,为什么不呢?它有何不同?



这是一项非常值得开发的技能,因为它可以帮助你在现实世界和发展中。和所有技能一样,它只能通过使用来改善!


and run your app. Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?

This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!


引用:

但它不会给我正确的回复

but it does not give me the right response



你忘了告诉我们你期望的结果以及你实际得到的结果。

没有这些信息,就不可能给你真实的答案。



有一个工具可以让你看到你的代码在做什么,它的名字是调试器。它也是一个很好的学习工具,因为它向你展示了现实,你可以看到哪种期望与现实相符。

当你不明白你的代码在做什么或为什么它做它做的时候,答案就是答案是调试器

使用调试器查看代码正在执行的操作。只需设置断点并查看代码执行情况,调试器允许您逐行执行第1行并在执行时检查变量。



调试器 - 维基百科,免费的百科全书 [ ^ ]

在Visual中调试C#代码工作室 - YouTube [ ^ ]

调试器在这里向您展示您的代码正在做什么,您的任务是与它应该做什么进行比较。

调试器中没有魔法,它不是'找到错误,它只是帮助你。当代码没有达到预期的效果时,你就会接近一个错误。


You forgot to tell us that results you expect and what results you actually get.
Without these informations, it is impossible to give you real answers.

There is a tool that allow you to see what your code is doing, its name is debugger. It is also a great learning tool because it show you reality and you can see which expectation match reality.
When you don't understand what your code is doing or why it does what it does, the answer is debugger.
Use the debugger to see what your code is doing. Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.

Debugger - Wikipedia, the free encyclopedia[^]
Debugging C# Code in Visual Studio - YouTube[^]
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't find bugs, it just help you to. When the code don't do what is expected, you are close to a bug.


这篇关于我的NN代码出了什么问题?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆