Following on from Wednesday’s briefing, we are still thinking about government and regulation of AI as yesterday the US government issue their paper Preparing For The Future Of Artificial Intelligence.
Megan Smith U.S. Chief Technology Officer and John P. Holdren, Assistant to the President for Science and Technology Director, Office of Science and Technology Policy present this contribution toward preparing the United States for a future in which AI plays a growing role, this report surveys the current state of AI, its existing and potential applications, and the questions that are raised for society and public policy by progress in AI. The report also makes recommendations for specific further actions by Federal agencies and other actors. A companion document lays out a strategic plan for Federally-funded research and development in AI. Additionally, in the coming months, the Administration will release a follow-on report exploring in greater depth the effect of AI-driven automation on jobs and the economy.
At first “let a thousand flowers bloom” then “government needs to be involved” but “not always to force the new technology into the square peg that exists but to make sure the regulations reflect a broad base set of values.”
These researchers use data from video game GTAV to train a model for object identification using neural networks and the model performed promisingly for real world test data. An incredibly important result which opens the possibility of using training data from simulated worlds.
In a recent paper, you can see here they showed how neural networks and memory systems can be combined to make learning machines that can store knowledge quickly and reason about it flexibly.
They call the model the differentiable neural computer (DNC), and show how they can can learn from examples like neural networks, but they can also store complex data like computers.
Education, training and advice we rate
The open guide to AWS on GitHub A lot of information on AWS is already written. Most people learn AWS by reading a blog or a “getting started guide” and referring to the standard AWS references. Nonetheless, believes “trustworthy and practical information and recommendations aren’t easy to come by. AWS’s own documentation is a great but sprawling resource few have time to read fully, and it doesn’t include anything but official facts, so omits experiences of engineers. The information in blogs or Stack Overflow is also not consistently up to date.” and so they put this awesome guide together. Hope it helps.