At the ReworkDL conference in Boston last month I listened to a fantastic presentation by Ryan Adams of Whetlab on how they’d created a business to add some science to the art of tuning deep learning engines. I signed up to participate to their closed beta and came back to the UK very excited to use their system once I’d got my architecture in place. Yesterday they announced that they had signed a deal with Twitter and the beta would be closed. I was delighted for the team – the business side of me is always happy when a start-up is successful enough to get attention of a big corporate, although I was personally gutted as it means I won’t be able to make use of their software to improve my own project.
It’s been a while since I’ve had the time to really dedicate to gaming in the way I’d like. My XBox360 is languishing unloved, my World of Warcraft account dormant since I got the Insane achievement in Cataclysm and the most I can manage now is the odd game of Hearthstone on my Nexus 71. I still keep an eye on what’s going on as the gaming industry is pushing the development of a lot of technologies that make their way into our lives in one way or another and I always have that hope that maybe something will give me the free time to immerse myself into some of the latest games again.
I was watching the announcements for XBox at E3 as they popped up on twitter this evening and two things really stood out for me.
At the end of my last post, we had started to build the x-axis assembly and got both shafts and the bearing block in place. This post looks at adding the timing belt and the x-axis motor, covering issues 20 to 23 of 3D Create and Print by Eaglemoss Technology. If you’ve skipped a part of this series you can start from the beginning, including details of the Vector 3 printer I’m building on my 3D printer page.
You’ll need to dig out the motor test circuit board and AC adaptor to completed these steps and they are very similar to that for the y-axis so should be fairly quick for you to go through. If you’re a subscriber then this drop also comes with four packs of filament in different colours, which you’ll just have to keep somewhere safe until we’re in a position to use them.
So, a few days ago I tweeted that I had this snippet from World of Warcraft going round my head where Illidan taunted that we weren’t prepared for what awaited us. It was how I felt going into MS2211 and now that I’ve done the exam I wanted to reflect on why I’d ended up feeling unprepared for a test in a subject I am very enthusiastic about for a degree I’m doing for no direct gain other than for the fun of learning.
I started this degree back in 2013 because I was intellectually unstimulated in my job. I was busy, spinning many plates and wasn’t bored, but there just wasn’t anything to do that really set my neurons firing. I’d started the process of looking for another job for a whole host of reasons I won’t go into, but I could feel my brain getting “comfortable” at not having to think much beyond which of my team needed to do which task in what order in response to changing priorities. So I signed up to do the maths degree I’d always wished I’d done. Continue reading MS221 – was Illidan right?
So – I’m approaching the end of my third OU module, MS2211, and the exam is in a few days. I missed all the local revision tutorials through being away with work2 and, despite some good intentions, I am woefully behind. Consider this a crammer’s guide for learning university level mathematics in 3 and a half days 😉3.
MS221 consists of four blocks: block A covering sequences, conics and geometry; block B covering iteration and matrices; block C covering more complex4 integration and differentiation and Taylor Polynomials; and block D covering complex numbers, number theory, groups and logic and reasoning5. The exam allows an annotated handbook and so it is fairly easy to prepare given a few days of dedicated effort, which (if you’re reading this in time, may help6. Continue reading Preparation for MS221
The first session kicked off with Kevin O’Brian from GreatHorn. There are 3 major problems facing the infosec community at the moment:
Modern infrastructure is far more complex than it used to be – we are using AWS, Azure as extensions of our physical networks and spaces such as GitHub as code repositories and Docker for automation. It is very difficult for any IT professional to keep up with all of the potential vulnerabilities and ensure that everything is secure.
(Security) Technical debt – there is too much to monitor/fix even if business released the time and funds to address it.
Shortfall in skilled people – there is a 1.5 million shortage in infosec people – this isn’t going to be resolved quickly.
So, day one of the ReWork Deep Learning Summit Boston 2015 is over. A lot of interesting talks and demonstrations all round. All talks were recorded so I will update this post as they become available with the links to wherever the recordings are posted – I know I’ll be rewatching them.
Following a brief introduction the day kicked off with a presentation from Christian Szegedy of Google looking at the deep learning they had set up to analyse YouTube videos. They’d taken the traditional networks used in Google and made them smaller, discovering that an architecture with several layers of small networks was more computationally efficient that larger ones, with a 5 level (inception-5) most efficient. Several papers were referenced, which I’ll need to look up later, but the results looked interesting.
While on my flight to Boston for ReWorkDL I watched Ex Machina the “must see” latest AI film. I’d been warned that it wasn’t very good by my husband (who’d just flown home the day before!) but I thought that since he’d already seen it, I’d better take the chance to watch it since it’s unlikely to be something we’d watch together in the future. If you haven’t seen it, then please be aware that this post does contain spoilers so read on with caution. Continue reading Ex Machina – film review
At the end of my last post, we had a completed y-axis and had also built the main frame of the printer, this post looks at building the x-axis assembly, covering issues 16 to 19 of 3D Create and Print by Eaglemoss Technology. If you’ve skipped a part of this series you can start from the beginning, including details of the Vector 3 printer I’m building on my 3D printer page.
While this is mainly an exact copy of the steps that we undertook for the y-axis, we are working directly on the mainframe, which presents its own challenges. There are a few tips I suggest to make life a little easier for yourself, especially if you’ve been saving parts or have received several issues in the same drop.
If you’ve been following this blog you’ll know that I’ve started a new role that requires me to build a deep learning system and I’ve been catching up on the 10+ years of research since I completed my PhD. With a background in computing and mathematics I jumped straight in to what I thought would be skimming through the literature. I soon realised that it would be better all round to jump back to first principles rather than be constrained with the methods I had learned over a decade ago.
So, I found a lot of universities who had put their machine learning courses online and have decided to work through what’s out there as if I was an undergraduate and then use my experience to build on top of that. I don’t want to miss an advantage because I wasn’t aware of it.