verne.freenode.net changed the topic of #mlpack to: http://www.mlpack.org/ -- We don't respond instantly... but we will respond. Give it a few minutes. Or hours. -- Channel logs: http://www.mlpack.org/irc/
Nilabhra has joined #mlpack
Nilabhra has quit [Remote host closed the connection]
ftuesca has quit [Quit: Leaving]
mentekid has joined #mlpack
mentekid_ has joined #mlpack
Mathnerd314 has quit [Ping timeout: 244 seconds]
mrbean has quit [Ping timeout: 252 seconds]
mrbean has joined #mlpack
tsathoggua has quit [Quit: Konversation terminated!]
ank_95_ has joined #mlpack
agobin has joined #mlpack
ank_95_ has quit [Quit: Connection closed for inactivity]
agobin has quit [Quit: Connection closed for inactivity]
KeonKim has joined #mlpack
agobin has joined #mlpack
skon46 has joined #mlpack
Keon has joined #mlpack
KeonKim has quit [Ping timeout: 276 seconds]
skon46 has quit [Quit: Leaving]
Mathnerd314 has joined #mlpack
palashahuja has joined #mlpack
virtualgod has joined #mlpack
KeonKim has joined #mlpack
KeonKim has quit [Read error: Connection reset by peer]
< virtualgod>
zoq: in the nes emulator, fceux stops responding for me once mario spawns. But it receives commands when sent through communication module and updates game state
< virtualgod>
zoq: is this normal behaviour?
mentekid__ has joined #mlpack
mentekid__ has quit [Remote host closed the connection]
mentekid_ has quit [Remote host closed the connection]
mentekid has quit [Remote host closed the connection]
mentekid has joined #mlpack
mentekid has quit [Client Quit]
< zoq>
virtualgod: yeah, once mario spawns; the game waits for user inputs via the communication module (server). Once it received a command, it processes the next x frames using the last command (moving command).
< virtualgod>
zoq: so visually there will be no change?
< zoq>
virtualgod: right, nothing happens until the emulator receives the next command.
< virtualgod>
zoq: ok
< zoq>
virtualgod: I set the default 'frame rate' to 30 frames for testing, so if you type d ('moving right'), it will use the 'moving right' command for the next 30 frames until it waits for the next command. But this is only for testing, because you have to type 'd' 30 times to see some progress if you set it to 1. If you use a machine learning approach I would set it to a lower value probably 1.
< virtualgod>
zoq: I will change it when I test it with some ml algorithm later. Right now I was just trying out things that I could do with it
< virtualgod>
zoq: can the game info which is obtained be modified to get some other stuff like time?
< zoq>
virtualgod: I guess it would be more clear if you test it yourself. You could run the game without the lua script, and see what happens with mario if you press the 'moving forward' key once, you have to press 28 or 14 times the 'moving forward' key to move one block forward.
< zoq>
virtualgod: Yeah, if you need more information, we can certainly add that information, time, number of coins, etc.