|
The other day I was playing with the idea of a generic processor emulator. Would someone like to join the experiment to implement it faster? Here's what I am up to.
1) I am going to produce a gigabyte of random bytes ( I know, I know, you volunteer for that  )
2) I am going to treat these bytes as Z80 op-codes,
3) I am going to feed them into neural network,
4) I am going to interpret them with an emulator and use expected processor behavior (i.e. state of registers, pc, flags, memory location read/writes, stack read/writes) to train the network,
5) I am going to wait for a week.
And if I am lucky I am going to end up with Z80 neural network. But in reality /if it works/ I am going to end up with a generic interpreter generator / duplicator.
...and with it we are going to start "the era of neuro-device" where a software is just a bunch of weights (and infos about the network structure)...a trained puppy, really...muwhahaha...
modified 15-Aug-16 4:45am.
|
|
|
|
|
Um...wouldn't it be better to start from a known-working Z80 program, rather than random data? If you're trying to train it to work as a Z80 then starting from stuff that only includes valid Z80 opcodes has got to be better than stuff that will immediately crash if fed to a real Z80?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Actually all 8 bit codes are valid Z80 codes - not that those will necessary make a valid program...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Not all of them - the ED extension codes don't define an operation for some values.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Decoding Z80 Opcodes[^]
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
That could be actually the most interesting part of a self-learning Z80 emulator...Will it learn to handle illegal opcode sequences as error and crash, or will behave like a true Z80 - wait and continue...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Funnily enough, random data would probably serve better, especially if backprop were used in place of the neural network.
With AI, the best starting point is often not the one that makes logical (programming-type) sense, because it has to learn how to work processes out for itself, not how to take data and reprocess it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Tomaž Štih wrote: 2) I am going to treat these bytes as Z80 op-codes,
Who will threat them like that? The ANN? Some pre-interpreter? Not clear at what point those codes will have meaning...
Tomaž Štih wrote: 3) I am going to feed them into neural network,
What? The byte or it's meaning?
Tomaž Štih wrote: 4) I am going to interpret them with an emulator and use expected processor behavior (i.e. state of registers, pc, flags, memory location read/writes, stack read/writes) to train the network,
What will you interpret? The output of the feed? And what exactly will be the training data after all this? The op-codes? The interpreted data (whatever that data is)?
And most importantly - you should state what kind of collaborations you are looking for!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: Who will threat them like that? The ANN? Some pre-interpreter? Not clear at what point those codes will have meaning...
Input bytes should be raw data. No interpreting. One could try feeding the classic net with 24 inputs (3 bytes) at a time and doing the convolution (sliding 1 byte instead of 3 bytes) across the raw data to enable long instructions. Or one could try a recurring neural network.Kornfeld Eliyahu Peter wrote: What? The byte or it's meaning?
The byte.Kornfeld Eliyahu Peter wrote: What will you interpret? The output of the feed? And what exactly will be the training data after all this? The op-codes? The interpreted data (whatever that data is)?
Neural network structure -
Input layer: op-code stream
Hidden layer: no idea. 
Output layer: task to execute
- one output for address write
- one output for address read
- one output for register write
- one output for register read
- 16 outputs for data
- 16 outputs for address
- 3 outputs for register 1
- 3 outputs for register 2
- one output for each flag
...
So if the instruction is LD A,10. Then it triggers register write with lower outputs filled with 10. If it is POP DE then it triggers stack read and the registers are D and E. So basically interpreting commands and reducing them to simpler commands ( hmm, well, actually almost the same commands; of course one may end up with decoding logic that is way more complex then the actual logic, but it is just weights so it is in a way "learned" ).
Training is done with help of an actual z80 emulator (an existing c# code can be used). The emulator should interpret the input bytes and set correct outputs. These should then be compared to the ones produced by our NN and used for back-propagation.Kornfeld Eliyahu Peter wrote: And most importantly - you should state what kind of collaborations you are looking for!
Any sort of programming/theoretical cooperation is fine. I'm new to neural networks. I mastered classic neural nets and am now into convolution neural nets, but could use some help in understanding recurring neural networks. I'm sure someone else could use something I've got. And a result can be a shared article for CP?
I'm interested in testing if the idea works and learning new stuff while doing it.
Sincerely,
T.
modified 15-Aug-16 6:29am.
|
|
|
|
|
Now I'm lost you even more...
Do you want to train an ANN from nothing to a Z80 interpreter or from a Z80 interpreter to a all-purpose interpreter?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
1) Ok. For start I want to train ANN from nothing to Z80 interpreter. That's a limited, not to difficult task. It will provide a proof of concept and I will learn a lot about how to approach such problem.
2) Then, if concept is good and it works, it could be used to train to interpret, compile, optimize other programming languages.
|
|
|
|
|
That's more clear now...
All you have to understand, that 'nothing' means that there is no hidden layer in your ANN, and that means nothing will build as the ANN lack any connection that would change the input...
So first thing is to set up minimal rules, that can be the hearth of a Z80 interpreter (like one of the basic rules of the Z80 is that there is no such thing as unknown op-code)...
As you want to feed back the output errors as new training material, you have to have a second rule set (a parallel hidden layer) to start with from that point of view...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
A bit like an infinite number of monkeys with typewriters. Let us know when it's finished.
|
|
|
|
|
That's the usual definition we use for AI procedures.
The thing is, we settle for one line of Shakespeare, and use billions of iterations, rather than infinite monkeys.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Tomaž Štih wrote: I am going to produce a gigabyte of random bytes
Well, as the saying goes, "garbage in, garbage out" 
Marc
|
|
|
|
|
Isn't that the premise behind Man V Food?
This space for rent
|
|
|
|
|
Garbage in 1,000,000,000 times : garbage out 999,999,999 times is a good start.
Iterate until it's:
Garbage in 1,000,000,000 times : Whoa!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
A long time ago in a laboratory far far away I used to do Monte-carlo simulations of molecular surface interactions. Although the data was random (the Monte-carlo part) it had rules to follow.
Your proposal seems to just be feed a ton of random into a system and . . . well that's what I don't get.
Chaos begets chaos (localized pockets of order are implicit for true chaos as the sample grows large). Perhaps explain how your neural network will digest the information ?
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
1) Every byte is more or less a valid Z80 instruction.
2) Hence - if you have a real Z80 emulator to decode instruction and produce outputs as they should be then you can feed the same byte into ANN and from outputs produced by real emulator calculate error of network and back propagate.
3) So a 1 GB is not garbage. It is simply 1 billion Z80 instructions (little less due to the fact that some are 2 or 3 bytes long). You could limit feed to only valid instructions. But for the ANN to learn Z80 alone you do not need to interpret multiple instructions together (i.e. the whole program). You can train the network instruction by instruction and each byte is a self-sustained perfectly meaningful sample.
|
|
|
|
|
I still don't see what would really be learned from a scillion randomized one-byte instructions. If they're all essentially Z80 instructions 'as is' then they all would be 'true' - and so the result for the training set would be, in Carribian style: "It's All OK".
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
W∴ Balboos wrote: I still don't see what would really be learned from a scillion randomized one-byte instructions. If they're all essentially Z80 instructions 'as is' then they all would be 'true' - and so the result for the training set would be, in Carribian style: "It's All OK".
Not all instructions are one byte long; you could insert a 2-byte or 3-byte instruction(s) to training samples. And there would be multiple outputs as described earlier.
Imagine emulator like this:
case clear_a_instruction:
setflag(z);
clearreg(a); /* write data value 0 to register a */
break;
case clear_z_instruction:
setflag(z);
break;
...
Neural network would have following outputs (each 1 bit):
- output to say that we are writing data
- 3 outputs, each 1 float, to say what is the source (7 possible registers)
- output to say we want to set zero flag
- 8 outputs for data
So when our neural net obtains a byte with value "clear_a_instruction" it's output would be:
a) output setflag(z) set between 0.5 and 1 which means it fires,
b) output for write to register set between 0.5 and 1 which means it fires,
c) three outputs for registers set so that it fires 'A' out of them,
d) and data bits set to < 0.5 which gives binary 0.
So you would do a write operation with source = 0, destionation = register A, and set the zero flag. Which is what this instruction is supposed to do.
|
|
|
|
|
Well - I admit I'm not following - or it seems that the neural net already has been trained. That is, effectively, a rule set.
Tomaž Štih wrote: Not all instructions are one byte long; you could insert a 2-byte or 3-byte instruction(s) to training samples.
You did say a gigabyte of random data, did you not? One does not insert things into random data, deliberately, and maintain calling it random.
Perhaps you're trying to seed code in a sea of random data in order that the Neural Net will learn how to find it? I could see that as a way to search for messages or embedded code.
But, as I started out - I guess I'm not following your vision.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
My fault, I am not a native speaker. Perhaps it is better to prepare a small sample and come back later.
Just one last try, simplified case of fictional processor with just four 8 bit registers and only 8 bit instructions that only affect these registers and nothing else.
So...
1. Neural network outputs can be from 0 .. 1. These values are float. This means that a single neural network output can -for example- assume value between 0 and 255 and even 0 and 65535 (if you want to represent values from 0 to 255 as values between 0 and 1 then you use n/255 for value n and 1 for value 255).
2. This means that a single neural network output can represent 8 or 16 bit register. For simplicity let us assume our neural network has only four 8 bit registers: A, B, C, and D. So we have four outputs.
3. Now let us feed neural network with 10 sequential bytes. Since values to feed the net are 0-255 we can use one single input for that (...or 8 inputs, and feed them binary pattern, it is a matter of choice).
Structure of ANN: so let us have 8 inputs, we have 4 outputs and we have (let's invent it right now eight invisible levels, each one 8 inputs.
4. We now produce an emulation software (not a neural network, but a real emulator) for this fictional processor. And we execute these 10 sequential bytes on the emulator. Emulator will interpret instructions and correctly set the four registers after each instruction.
5. Now we have possibility to train our network. We feed it one byte. We then feed the same byte to the emulator too. Emulator provides correct value for each register after instruction. Neural network provides output. We calculate error (as difference between correct value and ANN output) and back-propagate into the network i.e. update weights.
6. Now we feed neural net with 100.000 random instructions (bytes) and we do the same with emulator, back propagating after each byte fed into network. The assumption is that after this training the neural network will actually know how to emulate our fictional processor and will produce correct values in registers (4 outputs) based on input (8 inputs).
T.
|
|
|
|
|
OK, let's simplify AI training*:
0. You have data. You might have an idea what it means to you, but it's really only ones and zeroes.
1. You stream this data into a neural network/backprop routine/whatever, which does something (it doesn't matter what) with the data and gives you output.
2a. If the output is useless (99.99999% of the first very many iterations, if you've got it right), you tell it "That output is not useful" (in a coded manner, of course).
2b. If the output is useful, you tell it "That output is useful"
3. Rinse and repeat.
Eventually, you get quasi-self-written code that does exactly what you want it to do, and actually does better than you could code it, because, as in facial recognition, where you'd need a hundred billion lines of code to deal with every possible detail/angle/lighting effect/mm of hair growth, it can just look at a face and tell you who it is.
* As in training an AI, not training people to use it
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: OK, let's simplify AI training
That's pretty much how genetic algorithms do auto programming. Only they combine useful programs in hope that they'll become even more useful.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
