11–20 of 33 posts
I can post on hacker news with only 4.
... and that's three more than the average Atari marketing exec had back then. No wonder they had trouble understanding the game industry :-)
As someone working on a reinforcement learning/neuroevolution problem right now, I find this to be extremely exciting. Fewer parameters, ceteris paribus , is always better—the fact that the experiments in this paper were run on one workstation, rather than on a massive farm of TPUs à la AlphaGo, implies quicker development iteration time and more accessibility to the average researcher. The staging of components in t…
care to elaborate?
... and that's three more than the average Atari marketing exec had back then. No wonder they had trouble understanding the game industry :-)
OK, you're so grayed out but your bio says you've been programming since '79 and you've written games for Atari. So perhaps all we need is some elaboration? They seem like a successful company, don't they?
... and that's three more than the average Atari marketing exec had back then. No wonder they had trouble understanding the game industry :-)
OK, you're so grayed out but your bio says you've been programming since '79 and you've written games for Atari. So perhaps all we need is some elaboration? They seem like a successful company, don't they?
The Atari that brought out the Atari ST etc. was one of those, but that pretty much failed and Tramiel merged it into JTS and later sold the remains to Hasbro which then sold it to Infogrames Entertainment. The current Atari Inc. used to be Infogrames, and just licensed the name. Infogrames Entertainment itself then renamed itself to Atari SA.
The other part of the original Atari, Atari Games Inc. failed in 2003. The intellectual property of that division is as far as I know now owned by Warner.
Earlier quoted context omitted.
Ruby should be perfectly legible with a Python background, but for any question just ping me on twitter. I would be happy to build a dialog :)
Just curious, why did you pick ruby over python? Personal familiarity?
I am tempted to blame inconsistency across terminology and implementations for this lack of understanding but I suspect it has more to do with approaching this field through the lens of a developer and not a researcher or academic. Trying to understand the code without grasping the "science" of the mechanisms completely.
Either way if you feel to be in a similar spot check out this resource: https://reinforce.io and their respective Github repo: https://github.com/reinforceio/tensorforce.
Just reading through their code, and documentation has made a lot of the concepts clearer.
And a few more resources I found really helpful: http://karpathy.github.io/2016/05/31/rl/ https://www.analyticsvidhya.com/blog/2017/01/introduction-to... https://www.oreilly.com/ideas/reinforcement-learning-with-te...
Edit: My point that I forgot to mention was that I always feel like I am playing catch-up to understand what is going on half the time as the amount of new content being released exceeds what I can absorb.
Earlier quoted context omitted.
OK, you're so grayed out but your bio says you've been programming since '79 and you've written games for Atari. So perhaps all we need is some elaboration? They seem like a successful company, don't they?
Story time maybe? Atari were successful for a while but they crashed pretty hard.
... and that's three more than the average Atari marketing exec had back then. No wonder they had trouble understanding the game industry :-)