Earlier quoted context omitted.
>As a practical example, figuring out where a given pixel moves from one video frame to the next one, when working on real-world videos, the best known algorithms get about 50% of the pixels correct. With clever filtering, you can maybe bump that to 60 or 70%, but in any case you will be left with a 30%+ error rate. what do you mean by this? optical flow isn't really a learning problem? it's a classical problem with…
It used to be. Then the AI fanboys arrived and started treating it like a learning problem. https://arxiv.org/abs/1612.01925 https://arxiv.org/abs/1709.02371 https://arxiv.org/abs/1904.09117 BTW, also the classical algorithms deal very badly with noise and repetitive textures, e.g. a video of a forest in the afternoon.
Dive into Deep Learning
81–90 of 94 posts
Re: Dive into Deep Learning
#82this looks pretty good. certainly much better than goodfellow's deep learning book. definitely much the diagrams and code are much appreciated but i'm curious why mxnet over pytorch?
I find this comment amusing, have you read the goodfellow's book? That book is amazing.
Re: Dive into Deep Learning
#83Earlier quoted context omitted.
I'm somewhat surprised at the responses for this. I believe your issue can be easily solved - have supervisors wear a distinctive color from a non-supervisor. For example let's say it's yellow. OK so now you have yellow wearing supervisors and everyone else. To resolve the issue you have described acquire a month or so of footage, with labels per minute describing how many yellow wearing supervisors and how many peop…
"Easily solved - just have them wear special clothes." Everything is easy if you can arbitrarily change the requirements!
Re: Dive into Deep Learning
#84Earlier quoted context omitted.
I really don't understand your comment. 1. Supervisors are already by definition "superior" than their subordinates. 2. Supervisors on factories already wear distinctive clothing - especially in fully automated factories. Finally, you have yet to propose a solution to the problem yourself that would be highly accurate and easy to train. You vastly underestimate the difficulty to create a bespoke solution from scratch…
I don't have a deep-learning solution to the problem (I know nothing about it, that's why I clicked on it!). Seems really hard to me. I'd certainly go with an obvious "clock in and out" or "rfid" approaches... but I've worked in factories - and if you make someone wear some special clothes (or do some special tasks) when they didn't have to before - you're asking for trouble. People really hate change. That's presuma…
Re: Dive into Deep Learning
#85Earlier quoted context omitted.
I'm somewhat surprised at the responses for this. I believe your issue can be easily solved - have supervisors wear a distinctive color from a non-supervisor. For example let's say it's yellow. OK so now you have yellow wearing supervisors and everyone else. To resolve the issue you have described acquire a month or so of footage, with labels per minute describing how many yellow wearing supervisors and how many peop…
This is a pragmatic and valid approach. No matter what anyone else says. Imagine, you told a 10 YO child to do this task. Even the child would ask the same question - how do I know who is a supervisor and who is not. Not only is face recognition hard, it is almost impossible to accomplish in a factory floor like setting. Not totally impossible but it is really really hard. Face detection is still possible but face re…
Re: Dive into Deep Learning
#86Re: Dive into Deep Learning
#87Earlier quoted context omitted.
Thanks - this validates many of the assumptions I had about this part of the process. It has been challenging communicating many of these realities to non-technical folks, who seem to be quite misguided about implementing these types of systems as opposed to "non-ML" systems where there is a less imperfect and more predictable idea of what's possible, how well it will work, and how much effort is required to pull it…
Yeah IME expectations with ML are just the worst. Somehow, non-ML-educated stakeholders expect it to be predictable, like they pretend traditional software engineering is... but also to be magical in scope.
I personally believe this is false, but also false in a way that we're remarkably far away from that. Even more than software, predictive automation is a process. It often relies on particular customization to your own situation to be successful. It can demand vast resources. It's wildly difficult to debug.
So we should be working to retrain those around us. ML is a process.
Re: Dive into Deep Learning
#88As an engineer I find myself in this type of situation quite often - if anyone can point me to some good resources or has any advice, I'd be quite grateful: - Some non-technical stakeholder comes to me and says "can we solve this problem with Machine Learning?" usually it's something like "there need to be two supervisors on the factory floor at all times, and I want an email alert everytime there are less than 2 sup…
I'm somewhat surprised at the responses for this. I believe your issue can be easily solved - have supervisors wear a distinctive color from a non-supervisor. For example let's say it's yellow. OK so now you have yellow wearing supervisors and everyone else. To resolve the issue you have described acquire a month or so of footage, with labels per minute describing how many yellow wearing supervisors and how many peop…
Re: Dive into Deep Learning
#89Has anyone read this book ? It look very attractive but I want to hear some feedback before bookmarking another ML book.
Re: Dive into Deep Learning
#90Earlier quoted context omitted.
Only a limited hand-crafted hardcover edition is planned. That being said, you can print a dead tree version from the PDF at your local printing shop (or at home) if you care about the text, and not that much about binding.
Yes, that would be an option.