Audio player
On this page
On this page
Audio player
Edit element properties
import '@rhds/elements/rh-audio-player/rh-audio-player.js';rh-audio-player {
margin: var(--rh-space-xl, 24px);
}<rh-audio-player id="player" layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<rh-audio-player-about slot="about">
<h4 slot="heading">About the episode</h4>
<p>
There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.
</p>
<p>
Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.
</p>
<rh-avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools, <em>Intel®</em></span>
</rh-avatar>
</rh-audio-player-about>
<audio crossorigin="anonymous" slot="media" controls="">
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3">
</audio>
<rh-audio-player-subscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts">
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify">
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts">
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img class="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed">
</a>
</rh-audio-player-subscribe>
<rh-transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<rh-cue start="00:02" voice="Burr Sutter">
Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to
success, including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is
Code Comments, an original podcast from Red Hat.
</rh-cue>
<rh-cue start="00:29" voice="Burr Sutter">
I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.
</rh-cue>
<rh-cue start="01:14" voice="Burr Sutter">
In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And
we also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of
an enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's
say an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at
them and trying to determine if there is an error or not.
</rh-cue>
<rh-cue start="01:56" voice="Burr Sutter">
Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.
</rh-cue>
<rh-cue start="02:20" voice="Ryan Loney">
I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is
happening on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may
have been trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.
</rh-cue>
<rh-cue start="02:57" voice="Burr Sutter">
Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more
about it and how it came to be and why it came out of Intel.
</rh-cue>
<rh-cue start="03:12" voice="Ryan Loney">
Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which
is another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel
that were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing
inferences as part of a Computer Vision pipeline, or at least that's how we started.
</rh-cue>
<rh-cue start="03:58" voice="Ryan Loney">
But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now
we're moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer
Vision and don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started
in 2018. And the major focus of that release was optimizing for use cases that go beyond Computer Vision.
</rh-cue>
<rh-cue start="04:41" voice="Burr Sutter">
And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete
examples of Computer Vision?
</rh-cue>
<rh-cue start="04:50" voice="Ryan Loney">
Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or
sensors to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like
infrared or computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or,
"This is not a defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an
alert if somebody forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware
and help to analyze.
</rh-cue>
<rh-cue start="05:58" voice="Ryan Loney">
And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store
and using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the
stores, detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about
automating the process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail
examples that we can walk through.
</rh-cue>
<rh-cue start="06:55" voice="Burr Sutter">
And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.
</rh-cue>
<rh-cue start="07:28" voice="Burr Sutter">
It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength
from one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a
camera and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?
</rh-cue>
<rh-cue start="07:56" voice="Ryan Loney">
What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone
who walked into a grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do
that.
</rh-cue>
<rh-cue start="08:53" voice="Ryan Loney">
The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they
can track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that
they're protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their
products. That's one really good example of how Computer Vision, AI with OpenVINO is being used today.
</rh-cue>
<rh-cue start="09:49" voice="Burr Sutter">
And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store,
our mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I
want to talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a
quality assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?
</rh-cue>
<rh-cue start="10:23" voice="Ryan Loney">
One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're
also doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.
</rh-cue>
<rh-cue start="11:21" voice="Ryan Loney">
I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and
look up their personal information, they can do that.
</rh-cue>
<rh-cue start="12:17" voice="Ryan Loney">
But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification,
identifying people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be
in a situation where they might be violating someone's rights.
</rh-cue>
<rh-cue start="12:56" voice="Burr Sutter">
Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.
</rh-cue>
<rh-cue start="13:20" voice="Ryan Loney">
I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process,
there's other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really
easily identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.
</rh-cue>
<rh-cue start="14:17" voice="Ryan Loney">
So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and
start detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch
on it, or one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small
data set. And I think that's really one of the most important things today.
</rh-cue>
<rh-cue start="15:11" voice="Ryan Loney">
Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.
</rh-cue>
<rh-cue start="15:37" voice="Burr Sutter">
That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input
for the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort
out the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of
anomalies." Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some
cases, to just simply get my model training underway.
</rh-cue>
<rh-cue start="16:30" voice="Ryan Loney">
Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the
defects." And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non
defective item. So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the
approach that we're taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a
factory and they're the ones who know best when they look at these images, which one's going to have an issue, which one's defective.
</rh-cue>
<rh-cue start="17:31" voice="Ryan Loney">
And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking
those people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images,
it's a much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model.
Even better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have
to convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.
</rh-cue>
<rh-cue start="18:27" voice="Burr Sutter">
And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.
</rh-cue>
<rh-cue start="18:49" voice="Burr Sutter">
So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human
is eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and
specifically Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on
manufacturing, but let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated
into medical imaging equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the
same physical room as the patient.
</rh-cue>
<rh-cue start="19:44" voice="Ryan Loney">
We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway
of a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're
in an operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a
parking lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube
placement, ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors
so that they can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it
correctly. Another example is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements
that are usually hard to calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these
measurements to help the doctor avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And
those are just a few examples.
</rh-cue>
<rh-cue start="21:42" voice="Burr Sutter">
Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.
</rh-cue>
<rh-cue start="22:15" voice="Burr Sutter">
And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with
the application? Can you discuss that more?
</rh-cue>
<rh-cue start="22:38" voice="Ryan Loney">
Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential
classes that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label
that could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have
actual breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may
say 65% confidence that she's a flat coated retriever.
</rh-cue>
<rh-cue start="23:32" voice="Ryan Loney">
And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a
dog? I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an
application to tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated.
Because if you're being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it
doesn't match, well then, the accuracy's going to go down.
</rh-cue>
<rh-cue start="24:25" voice="Ryan Loney">
And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where
even the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is
placed incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost
performance, like quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is
taking a CT scan and then trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?
</rh-cue>
<rh-cue start="25:25" voice="Ryan Loney">
Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the
region of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to
really, they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting
the kidney, may be detecting a tumor.
</rh-cue>
<rh-cue start="26:04" voice="Ryan Loney">
And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that
takes longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of
those details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.
</rh-cue>
<rh-cue start="26:45" voice="Burr Sutter">
I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because
we knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge
device, up into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.
</rh-cue>
<rh-cue start="27:11" voice="Burr Sutter">
And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in
the overall application architecture. Would you agree with that or how do you think about that concept?
</rh-cue>
<rh-cue start="27:56" voice="Ryan Loney">
Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're
talking about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds
for every item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at
the individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going
to be a life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get
the result.
</rh-cue>
<rh-cue start="28:55" voice="Ryan Loney">
They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through
the checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."
</rh-cue>
<rh-cue start="29:30" voice="Burr Sutter">
There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his
team at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you
will, of adopting these technologies and discovering what they can do for us?
</rh-cue>
<rh-cue start="30:06" voice="Ryan Loney">
Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving
into the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that
you can go download that's under Creative Commons license for car batteries. It's just not something that's available.
</rh-cue>
<rh-cue start="30:57" voice="Ryan Loney">
And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from
working with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things
that are like the speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more
sophisticated and on larger images.
</rh-cue>
<rh-cue start="31:50" voice="Ryan Loney">
And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.
</rh-cue>
<rh-cue start="32:34" voice="Burr Sutter">
Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.
</rh-cue>
<rh-cue start="33:00" voice="Ryan Loney">
Thanks, Burr. This was a lot of fun. Thanks for having me.
</rh-cue>
<rh-cue start="33:05" voice="Burr Sutter">
You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was
produced by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison,
Nick Burns, Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you
for joining me today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.
</rh-cue>
</rh-transcript>
</rh-audio-player>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css">import { AudioPlayer } from "@rhds/elements/react/rh-audio-player/rh-audio-player.js";
import { AudioPlayerAbout } from "@rhds/elements/react/rh-audio-player-about/rh-audio-player-about.js";
import { AudioPlayerSubscribe } from "@rhds/elements/react/rh-audio-player-subscribe/rh-audio-player-subscribe.js";
import { Avatar } from "@rhds/elements/react/rh-avatar/rh-avatar.js";
import { Cue } from "@rhds/elements/react/rh-cue/rh-cue.js";
import { Transcript } from "@rhds/elements/react/rh-transcript/rh-transcript.js";
// NOTE: React 19+ does not require these wrapper imports.
// You can use the custom elements directly as-is.
export const Demo = () => (
<AudioPlayer id="player" layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<AudioPlayerAbout slot="about">
<h4 slot="heading">About the episode</h4>
<p>There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.</p>
<p>Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.</p>
<Avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools,<em>Intel®</em></span>
</Avatar>
</AudioPlayerAbout>
<audio crossorigin="anonymous" slot="media" controls>
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3" />
</audio>
<AudioPlayerSubscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts" />
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify" />
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts" />
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img className="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed" />
</a>
</AudioPlayerSubscribe>
<Transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<Cue start="00:02" voice="Burr Sutter">Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to
success, including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is
Code Comments, an original podcast from Red Hat.</Cue>
<Cue start="00:29" voice="Burr Sutter">I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.</Cue>
<Cue start="01:14" voice="Burr Sutter">In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And
we also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of
an enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's
say an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at
them and trying to determine if there is an error or not.</Cue>
<Cue start="01:56" voice="Burr Sutter">Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.</Cue>
<Cue start="02:20" voice="Ryan Loney">I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is
happening on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may
have been trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.</Cue>
<Cue start="02:57" voice="Burr Sutter">Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more
about it and how it came to be and why it came out of Intel.</Cue>
<Cue start="03:12" voice="Ryan Loney">Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which
is another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel
that were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing
inferences as part of a Computer Vision pipeline, or at least that's how we started.</Cue>
<Cue start="03:58" voice="Ryan Loney">But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now
we're moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer
Vision and don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started
in 2018. And the major focus of that release was optimizing for use cases that go beyond Computer Vision.</Cue>
<Cue start="04:41" voice="Burr Sutter">And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete
examples of Computer Vision?</Cue>
<Cue start="04:50" voice="Ryan Loney">Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or
sensors to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like
infrared or computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or,
"This is not a defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an
alert if somebody forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware
and help to analyze.</Cue>
<Cue start="05:58" voice="Ryan Loney">And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store
and using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the
stores, detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about
automating the process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail
examples that we can walk through.</Cue>
<Cue start="06:55" voice="Burr Sutter">And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.</Cue>
<Cue start="07:28" voice="Burr Sutter">It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength
from one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a
camera and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?</Cue>
<Cue start="07:56" voice="Ryan Loney">What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone
who walked into a grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do
that.</Cue>
<Cue start="08:53" voice="Ryan Loney">The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they
can track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that
they're protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their
products. That's one really good example of how Computer Vision, AI with OpenVINO is being used today.</Cue>
<Cue start="09:49" voice="Burr Sutter">And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store,
our mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I
want to talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a
quality assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?</Cue>
<Cue start="10:23" voice="Ryan Loney">One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're
also doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.</Cue>
<Cue start="11:21" voice="Ryan Loney">I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and
look up their personal information, they can do that.</Cue>
<Cue start="12:17" voice="Ryan Loney">But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification,
identifying people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be
in a situation where they might be violating someone's rights.</Cue>
<Cue start="12:56" voice="Burr Sutter">Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.</Cue>
<Cue start="13:20" voice="Ryan Loney">I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process,
there's other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really
easily identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.</Cue>
<Cue start="14:17" voice="Ryan Loney">So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and
start detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch
on it, or one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small
data set. And I think that's really one of the most important things today.</Cue>
<Cue start="15:11" voice="Ryan Loney">Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.</Cue>
<Cue start="15:37" voice="Burr Sutter">That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input
for the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort
out the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of
anomalies." Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some
cases, to just simply get my model training underway.</Cue>
<Cue start="16:30" voice="Ryan Loney">Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the
defects." And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non
defective item. So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the
approach that we're taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a
factory and they're the ones who know best when they look at these images, which one's going to have an issue, which one's defective.</Cue>
<Cue start="17:31" voice="Ryan Loney">And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking
those people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images,
it's a much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model.
Even better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have
to convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.</Cue>
<Cue start="18:27" voice="Burr Sutter">And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.</Cue>
<Cue start="18:49" voice="Burr Sutter">So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human
is eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and
specifically Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on
manufacturing, but let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated
into medical imaging equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the
same physical room as the patient.</Cue>
<Cue start="19:44" voice="Ryan Loney">We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway
of a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're
in an operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a
parking lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube
placement, ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors
so that they can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it
correctly. Another example is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements
that are usually hard to calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these
measurements to help the doctor avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And
those are just a few examples.</Cue>
<Cue start="21:42" voice="Burr Sutter">Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.</Cue>
<Cue start="22:15" voice="Burr Sutter">And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with
the application? Can you discuss that more?</Cue>
<Cue start="22:38" voice="Ryan Loney">Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential
classes that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label
that could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have
actual breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may
say 65% confidence that she's a flat coated retriever.</Cue>
<Cue start="23:32" voice="Ryan Loney">And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a
dog? I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an
application to tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated.
Because if you're being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it
doesn't match, well then, the accuracy's going to go down.</Cue>
<Cue start="24:25" voice="Ryan Loney">And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where
even the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is
placed incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost
performance, like quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is
taking a CT scan and then trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?</Cue>
<Cue start="25:25" voice="Ryan Loney">Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the
region of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to
really, they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting
the kidney, may be detecting a tumor.</Cue>
<Cue start="26:04" voice="Ryan Loney">And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that
takes longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of
those details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.</Cue>
<Cue start="26:45" voice="Burr Sutter">I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because
we knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge
device, up into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.</Cue>
<Cue start="27:11" voice="Burr Sutter">And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in
the overall application architecture. Would you agree with that or how do you think about that concept?</Cue>
<Cue start="27:56" voice="Ryan Loney">Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're
talking about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds
for every item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at
the individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going
to be a life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get
the result.</Cue>
<Cue start="28:55" voice="Ryan Loney">They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through
the checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."</Cue>
<Cue start="29:30" voice="Burr Sutter">There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his
team at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you
will, of adopting these technologies and discovering what they can do for us?</Cue>
<Cue start="30:06" voice="Ryan Loney">Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving
into the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that
you can go download that's under Creative Commons license for car batteries. It's just not something that's available.</Cue>
<Cue start="30:57" voice="Ryan Loney">And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from
working with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things
that are like the speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more
sophisticated and on larger images.</Cue>
<Cue start="31:50" voice="Ryan Loney">And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.</Cue>
<Cue start="32:34" voice="Burr Sutter">Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.</Cue>
<Cue start="33:00" voice="Ryan Loney">Thanks, Burr. This was a lot of fun. Thanks for having me.</Cue>
<Cue start="33:05" voice="Burr Sutter">You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was
produced by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison,
Nick Burns, Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you
for joining me today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.</Cue>
</Transcript>
</AudioPlayer>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css" />
);Color Context
Edit element properties
import '@rhds/elements/rh-audio-player/rh-audio-player.js';
import '@rhds/elements/lib/elements/rh-context-demo/rh-context-demo.js';
const form = document.querySelector('form');
const player = document.querySelector('rh-audio-player');
/**
* update audio player demo based on form selections
*/
function updateDemo() {
const data = new FormData(form);
const values = Object.fromEntries(data.entries());
const { layout } = values;
player.layout = layout;
player.poster =
!values.poster ? undefined
: 'https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png';
}
form.addEventListener('input', updateDemo);
updateDemo();<rh-context-demo id="player-context-demo" target="player">
<form slot="controls">
<label>Poster: <input name="poster" type="checkbox" checked=""></label>
<label>Layout:
<select name="layout">
<option value="full" selected="">Full</option>
<option value="compact-wide">Compact Wide</option>
<option value="compact">Compact</option>
<option value="mini">Mini</option>
</select>
</label>
</form>
<rh-audio-player id="player" layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<rh-audio-player-about slot="about">
<h4 slot="heading">About the episode</h4>
<p>
There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.
</p>
<p>
Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.
</p>
<rh-avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools, <em>Intel®</em></span>
</rh-avatar>
</rh-audio-player-about>
<audio crossorigin="anonymous" slot="media" controls="">
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3">
</audio>
<rh-audio-player-subscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts">
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify">
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts">
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img class="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed">
</a>
</rh-audio-player-subscribe>
<rh-transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<rh-cue start="00:02" voice="Burr Sutter">
Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to success,
including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is Code
Comments, an original podcast from Red Hat.
</rh-cue>
<rh-cue start="00:29" voice="Burr Sutter">
I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.
</rh-cue>
<rh-cue start="01:14" voice="Burr Sutter">
In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And we
also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of an
enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's say
an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at them and
trying to determine if there is an error or not.
</rh-cue>
<rh-cue start="01:56" voice="Burr Sutter">
Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.
</rh-cue>
<rh-cue start="02:20" voice="Ryan Loney">
I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is happening
on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may have been
trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.
</rh-cue>
<rh-cue start="02:57" voice="Burr Sutter">
Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more about
it and how it came to be and why it came out of Intel.
</rh-cue>
<rh-cue start="03:12" voice="Ryan Loney">
Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which is
another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel that
were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing inferences as
part of a Computer Vision pipeline, or at least that's how we started.
</rh-cue>
<rh-cue start="03:58" voice="Ryan Loney">
But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now we're
moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer Vision and
don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started in 2018. And
the major focus of that release was optimizing for use cases that go beyond Computer Vision.
</rh-cue>
<rh-cue start="04:41" voice="Burr Sutter">
And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete examples
of Computer Vision?
</rh-cue>
<rh-cue start="04:50" voice="Ryan Loney">
Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or sensors
to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like infrared or
computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or, "This is not a
defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an alert if somebody
forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware and help to analyze.
</rh-cue>
<rh-cue start="05:58" voice="Ryan Loney">
And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store and
using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the stores,
detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about automating the
process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail examples that we can
walk through.
</rh-cue>
<rh-cue start="06:55" voice="Burr Sutter">
And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.
</rh-cue>
<rh-cue start="07:28" voice="Burr Sutter">
It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength from
one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a camera
and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?
</rh-cue>
<rh-cue start="07:56" voice="Ryan Loney">
What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone who walked into a
grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do that.
</rh-cue>
<rh-cue start="08:53" voice="Ryan Loney">
The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they can
track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that they're
protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their products.
That's one really good example of how Computer Vision, AI with OpenVINO is being used today.
</rh-cue>
<rh-cue start="09:49" voice="Burr Sutter">
And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store, our
mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I want to
talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a quality
assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?
</rh-cue>
<rh-cue start="10:23" voice="Ryan Loney">
One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're also
doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.
</rh-cue>
<rh-cue start="11:21" voice="Ryan Loney">
I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and look
up their personal information, they can do that.
</rh-cue>
<rh-cue start="12:17" voice="Ryan Loney">
But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification, identifying
people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be in a situation
where they might be violating someone's rights.
</rh-cue>
<rh-cue start="12:56" voice="Burr Sutter">
Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.
</rh-cue>
<rh-cue start="13:20" voice="Ryan Loney">
I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process, there's
other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really easily
identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.
</rh-cue>
<rh-cue start="14:17" voice="Ryan Loney">
So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and start
detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch on it, or
one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small data set. And
I think that's really one of the most important things today.
</rh-cue>
<rh-cue start="15:11" voice="Ryan Loney">
Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.
</rh-cue>
<rh-cue start="15:37" voice="Burr Sutter">
That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input for
the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort out
the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of anomalies."
Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some cases, to just simply
get my model training underway.
</rh-cue>
<rh-cue start="16:30" voice="Ryan Loney">
Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the defects."
And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non defective item.
So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the approach that we're
taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a factory and they're the ones
who know best when they look at these images, which one's going to have an issue, which one's defective.
</rh-cue>
<rh-cue start="17:31" voice="Ryan Loney">
And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking those
people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images, it's a
much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model. Even
better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have to
convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.
</rh-cue>
<rh-cue start="18:27" voice="Burr Sutter">
And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.
</rh-cue>
<rh-cue start="18:49" voice="Burr Sutter">
So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human is
eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and specifically
Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on manufacturing, but
let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated into medical imaging
equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the same physical room as
the patient.
</rh-cue>
<rh-cue start="19:44" voice="Ryan Loney">
We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway of
a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're in an
operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a parking
lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube placement,
ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors so that they
can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it correctly. Another example
is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements that are usually hard to
calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these measurements to help the doctor
avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And those are just a few examples.
</rh-cue>
<rh-cue start="21:42" voice="Burr Sutter">
Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.
</rh-cue>
<rh-cue start="22:15" voice="Burr Sutter">
And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with the
application? Can you discuss that more?
</rh-cue>
<rh-cue start="22:38" voice="Ryan Loney">
Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential classes
that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label that
could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have actual
breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may say 65%
confidence that she's a flat coated retriever.
</rh-cue>
<rh-cue start="23:32" voice="Ryan Loney">
And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a dog?
I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an application to
tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated. Because if you're
being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it doesn't match, well
then, the accuracy's going to go down.
</rh-cue>
<rh-cue start="24:25" voice="Ryan Loney">
And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where even
the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is placed
incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost performance, like
quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is taking a CT scan and then
trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?
</rh-cue>
<rh-cue start="25:25" voice="Ryan Loney">
Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the region
of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to really,
they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting the kidney,
may be detecting a tumor.
</rh-cue>
<rh-cue start="26:04" voice="Ryan Loney">
And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that takes
longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of those
details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.
</rh-cue>
<rh-cue start="26:45" voice="Burr Sutter">
I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because we
knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge device, up
into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.
</rh-cue>
<rh-cue start="27:11" voice="Burr Sutter">
And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in the
overall application architecture. Would you agree with that or how do you think about that concept?
</rh-cue>
<rh-cue start="27:56" voice="Ryan Loney">
Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're talking
about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds for every
item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at the
individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going to be a
life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get the result.
</rh-cue>
<rh-cue start="28:55" voice="Ryan Loney">
They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through the
checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."
</rh-cue>
<rh-cue start="29:30" voice="Burr Sutter">
There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his team
at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you will, of
adopting these technologies and discovering what they can do for us?
</rh-cue>
<rh-cue start="30:06" voice="Ryan Loney">
Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving into
the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that you can go
download that's under Creative Commons license for car batteries. It's just not something that's available.
</rh-cue>
<rh-cue start="30:57" voice="Ryan Loney">
And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from working
with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things that are like the
speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more sophisticated and on
larger images.
</rh-cue>
<rh-cue start="31:50" voice="Ryan Loney">
And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.
</rh-cue>
<rh-cue start="32:34" voice="Burr Sutter">
Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.
</rh-cue>
<rh-cue start="33:00" voice="Ryan Loney">
Thanks, Burr. This was a lot of fun. Thanks for having me.
</rh-cue>
<rh-cue start="33:05" voice="Burr Sutter">
You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was produced
by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison, Nick Burns,
Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you for joining me
today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.
</rh-cue>
</rh-transcript>
</rh-audio-player>
</rh-context-demo>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css">import { AudioPlayer } from "@rhds/elements/react/rh-audio-player/rh-audio-player.js";
import { AudioPlayerAbout } from "@rhds/elements/react/rh-audio-player-about/rh-audio-player-about.js";
import { AudioPlayerSubscribe } from "@rhds/elements/react/rh-audio-player-subscribe/rh-audio-player-subscribe.js";
import { Avatar } from "@rhds/elements/react/rh-avatar/rh-avatar.js";
import { Cue } from "@rhds/elements/react/rh-cue/rh-cue.js";
import { Transcript } from "@rhds/elements/react/rh-transcript/rh-transcript.js";
// NOTE: React 19+ does not require these wrapper imports.
// You can use the custom elements directly as-is.
export const Demo = () => (
<rh-context-demo id="player-context-demo" target="player">
<form slot="controls">
<label>
Poster:
<input name="poster" type="checkbox" checked />
</label>
<label>
Layout:
<select name="layout">
<option value="full" selected>Full</option>
<option value="compact-wide">Compact Wide</option>
<option value="compact">Compact</option>
<option value="mini">Mini</option>
</select>
</label>
</form>
<AudioPlayer id="player" layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<AudioPlayerAbout slot="about">
<h4 slot="heading">About the episode</h4>
<p>There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.</p>
<p>Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.</p>
<Avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools,<em>Intel®</em></span>
</Avatar>
</AudioPlayerAbout>
<audio crossorigin="anonymous" slot="media" controls>
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3" />
</audio>
<AudioPlayerSubscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts" />
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify" />
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts" />
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img className="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed" />
</a>
</AudioPlayerSubscribe>
<Transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<Cue start="00:02" voice="Burr Sutter">Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to success,
including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is Code
Comments, an original podcast from Red Hat.</Cue>
<Cue start="00:29" voice="Burr Sutter">I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.</Cue>
<Cue start="01:14" voice="Burr Sutter">In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And we
also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of an
enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's say
an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at them and
trying to determine if there is an error or not.</Cue>
<Cue start="01:56" voice="Burr Sutter">Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.</Cue>
<Cue start="02:20" voice="Ryan Loney">I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is happening
on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may have been
trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.</Cue>
<Cue start="02:57" voice="Burr Sutter">Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more about
it and how it came to be and why it came out of Intel.</Cue>
<Cue start="03:12" voice="Ryan Loney">Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which is
another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel that
were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing inferences as
part of a Computer Vision pipeline, or at least that's how we started.</Cue>
<Cue start="03:58" voice="Ryan Loney">But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now we're
moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer Vision and
don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started in 2018. And
the major focus of that release was optimizing for use cases that go beyond Computer Vision.</Cue>
<Cue start="04:41" voice="Burr Sutter">And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete examples
of Computer Vision?</Cue>
<Cue start="04:50" voice="Ryan Loney">Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or sensors
to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like infrared or
computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or, "This is not a
defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an alert if somebody
forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware and help to analyze.</Cue>
<Cue start="05:58" voice="Ryan Loney">And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store and
using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the stores,
detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about automating the
process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail examples that we can
walk through.</Cue>
<Cue start="06:55" voice="Burr Sutter">And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.</Cue>
<Cue start="07:28" voice="Burr Sutter">It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength from
one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a camera
and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?</Cue>
<Cue start="07:56" voice="Ryan Loney">What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone who walked into a
grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do that.</Cue>
<Cue start="08:53" voice="Ryan Loney">The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they can
track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that they're
protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their products.
That's one really good example of how Computer Vision, AI with OpenVINO is being used today.</Cue>
<Cue start="09:49" voice="Burr Sutter">And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store, our
mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I want to
talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a quality
assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?</Cue>
<Cue start="10:23" voice="Ryan Loney">One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're also
doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.</Cue>
<Cue start="11:21" voice="Ryan Loney">I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and look
up their personal information, they can do that.</Cue>
<Cue start="12:17" voice="Ryan Loney">But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification, identifying
people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be in a situation
where they might be violating someone's rights.</Cue>
<Cue start="12:56" voice="Burr Sutter">Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.</Cue>
<Cue start="13:20" voice="Ryan Loney">I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process, there's
other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really easily
identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.</Cue>
<Cue start="14:17" voice="Ryan Loney">So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and start
detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch on it, or
one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small data set. And
I think that's really one of the most important things today.</Cue>
<Cue start="15:11" voice="Ryan Loney">Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.</Cue>
<Cue start="15:37" voice="Burr Sutter">That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input for
the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort out
the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of anomalies."
Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some cases, to just simply
get my model training underway.</Cue>
<Cue start="16:30" voice="Ryan Loney">Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the defects."
And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non defective item.
So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the approach that we're
taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a factory and they're the ones
who know best when they look at these images, which one's going to have an issue, which one's defective.</Cue>
<Cue start="17:31" voice="Ryan Loney">And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking those
people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images, it's a
much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model. Even
better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have to
convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.</Cue>
<Cue start="18:27" voice="Burr Sutter">And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.</Cue>
<Cue start="18:49" voice="Burr Sutter">So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human is
eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and specifically
Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on manufacturing, but
let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated into medical imaging
equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the same physical room as
the patient.</Cue>
<Cue start="19:44" voice="Ryan Loney">We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway of
a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're in an
operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a parking
lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube placement,
ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors so that they
can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it correctly. Another example
is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements that are usually hard to
calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these measurements to help the doctor
avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And those are just a few examples.</Cue>
<Cue start="21:42" voice="Burr Sutter">Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.</Cue>
<Cue start="22:15" voice="Burr Sutter">And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with the
application? Can you discuss that more?</Cue>
<Cue start="22:38" voice="Ryan Loney">Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential classes
that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label that
could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have actual
breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may say 65%
confidence that she's a flat coated retriever.</Cue>
<Cue start="23:32" voice="Ryan Loney">And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a dog?
I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an application to
tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated. Because if you're
being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it doesn't match, well
then, the accuracy's going to go down.</Cue>
<Cue start="24:25" voice="Ryan Loney">And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where even
the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is placed
incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost performance, like
quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is taking a CT scan and then
trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?</Cue>
<Cue start="25:25" voice="Ryan Loney">Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the region
of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to really,
they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting the kidney,
may be detecting a tumor.</Cue>
<Cue start="26:04" voice="Ryan Loney">And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that takes
longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of those
details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.</Cue>
<Cue start="26:45" voice="Burr Sutter">I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because we
knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge device, up
into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.</Cue>
<Cue start="27:11" voice="Burr Sutter">And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in the
overall application architecture. Would you agree with that or how do you think about that concept?</Cue>
<Cue start="27:56" voice="Ryan Loney">Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're talking
about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds for every
item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at the
individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going to be a
life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get the result.</Cue>
<Cue start="28:55" voice="Ryan Loney">They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through the
checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."</Cue>
<Cue start="29:30" voice="Burr Sutter">There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his team
at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you will, of
adopting these technologies and discovering what they can do for us?</Cue>
<Cue start="30:06" voice="Ryan Loney">Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving into
the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that you can go
download that's under Creative Commons license for car batteries. It's just not something that's available.</Cue>
<Cue start="30:57" voice="Ryan Loney">And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from working
with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things that are like the
speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more sophisticated and on
larger images.</Cue>
<Cue start="31:50" voice="Ryan Loney">And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.</Cue>
<Cue start="32:34" voice="Burr Sutter">Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.</Cue>
<Cue start="33:00" voice="Ryan Loney">Thanks, Burr. This was a lot of fun. Thanks for having me.</Cue>
<Cue start="33:05" voice="Burr Sutter">You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was produced
by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison, Nick Burns,
Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you for joining me
today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.</Cue>
</Transcript>
</AudioPlayer>
</rh-context-demo>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css" />
);Compact Wide
Edit element properties
import '@rhds/elements/rh-audio-player/rh-audio-player.js';rh-audio-player {
margin: var(--rh-space-xl, 24px);
}<rh-audio-player id="player" layout="compact-wide" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<rh-audio-player-about slot="about">
<h4 slot="heading">About the episode</h4>
<p>
There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.
</p>
<p>
Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.
</p>
<rh-avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools, <em>Intel®</em></span>
</rh-avatar>
</rh-audio-player-about>
<audio crossorigin="anonymous" slot="media" controls="">
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3">
</audio>
<rh-audio-player-subscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts">
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify">
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts">
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img class="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed">
</a>
</rh-audio-player-subscribe>
<rh-transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<rh-cue start="00:02" voice="Burr Sutter">
Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to
success, including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is
Code Comments, an original podcast from Red Hat.
</rh-cue>
<rh-cue start="00:29" voice="Burr Sutter">
I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.
</rh-cue>
<rh-cue start="01:14" voice="Burr Sutter">
In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And
we also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of
an enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's
say an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at
them and trying to determine if there is an error or not.
</rh-cue>
<rh-cue start="01:56" voice="Burr Sutter">
Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.
</rh-cue>
<rh-cue start="02:20" voice="Ryan Loney">
I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is
happening on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may
have been trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.
</rh-cue>
<rh-cue start="02:57" voice="Burr Sutter">
Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more
about it and how it came to be and why it came out of Intel.
</rh-cue>
<rh-cue start="03:12" voice="Ryan Loney">
Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which
is another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel
that were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing
inferences as part of a Computer Vision pipeline, or at least that's how we started.
</rh-cue>
<rh-cue start="03:58" voice="Ryan Loney">
But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now
we're moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer
Vision and don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started
in 2018. And the major focus of that release was optimizing for use cases that go beyond Computer Vision.
</rh-cue>
<rh-cue start="04:41" voice="Burr Sutter">
And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete
examples of Computer Vision?
</rh-cue>
<rh-cue start="04:50" voice="Ryan Loney">
Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or
sensors to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like
infrared or computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or,
"This is not a defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an
alert if somebody forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware
and help to analyze.
</rh-cue>
<rh-cue start="05:58" voice="Ryan Loney">
And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store
and using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the
stores, detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about
automating the process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail
examples that we can walk through.
</rh-cue>
<rh-cue start="06:55" voice="Burr Sutter">
And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.
</rh-cue>
<rh-cue start="07:28" voice="Burr Sutter">
It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength
from one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a
camera and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?
</rh-cue>
<rh-cue start="07:56" voice="Ryan Loney">
What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone
who walked into a grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do
that.
</rh-cue>
<rh-cue start="08:53" voice="Ryan Loney">
The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they
can track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that
they're protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their
products. That's one really good example of how Computer Vision, AI with OpenVINO is being used today.
</rh-cue>
<rh-cue start="09:49" voice="Burr Sutter">
And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store,
our mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I
want to talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a
quality assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?
</rh-cue>
<rh-cue start="10:23" voice="Ryan Loney">
One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're
also doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.
</rh-cue>
<rh-cue start="11:21" voice="Ryan Loney">
I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and
look up their personal information, they can do that.
</rh-cue>
<rh-cue start="12:17" voice="Ryan Loney">
But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification,
identifying people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be
in a situation where they might be violating someone's rights.
</rh-cue>
<rh-cue start="12:56" voice="Burr Sutter">
Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.
</rh-cue>
<rh-cue start="13:20" voice="Ryan Loney">
I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process,
there's other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really
easily identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.
</rh-cue>
<rh-cue start="14:17" voice="Ryan Loney">
So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and
start detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch
on it, or one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small
data set. And I think that's really one of the most important things today.
</rh-cue>
<rh-cue start="15:11" voice="Ryan Loney">
Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.
</rh-cue>
<rh-cue start="15:37" voice="Burr Sutter">
That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input
for the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort
out the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of
anomalies." Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some
cases, to just simply get my model training underway.
</rh-cue>
<rh-cue start="16:30" voice="Ryan Loney">
Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the
defects." And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non
defective item. So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the
approach that we're taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a
factory and they're the ones who know best when they look at these images, which one's going to have an issue, which one's defective.
</rh-cue>
<rh-cue start="17:31" voice="Ryan Loney">
And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking
those people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images,
it's a much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model.
Even better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have
to convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.
</rh-cue>
<rh-cue start="18:27" voice="Burr Sutter">
And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.
</rh-cue>
<rh-cue start="18:49" voice="Burr Sutter">
So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human
is eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and
specifically Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on
manufacturing, but let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated
into medical imaging equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the
same physical room as the patient.
</rh-cue>
<rh-cue start="19:44" voice="Ryan Loney">
We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway
of a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're
in an operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a
parking lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube
placement, ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors
so that they can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it
correctly. Another example is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements
that are usually hard to calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these
measurements to help the doctor avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And
those are just a few examples.
</rh-cue>
<rh-cue start="21:42" voice="Burr Sutter">
Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.
</rh-cue>
<rh-cue start="22:15" voice="Burr Sutter">
And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with
the application? Can you discuss that more?
</rh-cue>
<rh-cue start="22:38" voice="Ryan Loney">
Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential
classes that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label
that could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have
actual breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may
say 65% confidence that she's a flat coated retriever.
</rh-cue>
<rh-cue start="23:32" voice="Ryan Loney">
And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a
dog? I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an
application to tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated.
Because if you're being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it
doesn't match, well then, the accuracy's going to go down.
</rh-cue>
<rh-cue start="24:25" voice="Ryan Loney">
And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where
even the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is
placed incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost
performance, like quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is
taking a CT scan and then trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?
</rh-cue>
<rh-cue start="25:25" voice="Ryan Loney">
Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the
region of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to
really, they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting
the kidney, may be detecting a tumor.
</rh-cue>
<rh-cue start="26:04" voice="Ryan Loney">
And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that
takes longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of
those details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.
</rh-cue>
<rh-cue start="26:45" voice="Burr Sutter">
I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because
we knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge
device, up into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.
</rh-cue>
<rh-cue start="27:11" voice="Burr Sutter">
And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in
the overall application architecture. Would you agree with that or how do you think about that concept?
</rh-cue>
<rh-cue start="27:56" voice="Ryan Loney">
Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're
talking about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds
for every item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at
the individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going
to be a life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get
the result.
</rh-cue>
<rh-cue start="28:55" voice="Ryan Loney">
They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through
the checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."
</rh-cue>
<rh-cue start="29:30" voice="Burr Sutter">
There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his
team at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you
will, of adopting these technologies and discovering what they can do for us?
</rh-cue>
<rh-cue start="30:06" voice="Ryan Loney">
Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving
into the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that
you can go download that's under Creative Commons license for car batteries. It's just not something that's available.
</rh-cue>
<rh-cue start="30:57" voice="Ryan Loney">
And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from
working with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things
that are like the speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more
sophisticated and on larger images.
</rh-cue>
<rh-cue start="31:50" voice="Ryan Loney">
And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.
</rh-cue>
<rh-cue start="32:34" voice="Burr Sutter">
Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.
</rh-cue>
<rh-cue start="33:00" voice="Ryan Loney">
Thanks, Burr. This was a lot of fun. Thanks for having me.
</rh-cue>
<rh-cue start="33:05" voice="Burr Sutter">
You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was
produced by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison,
Nick Burns, Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you
for joining me today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.
</rh-cue>
</rh-transcript>
</rh-audio-player>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css">import { AudioPlayer } from "@rhds/elements/react/rh-audio-player/rh-audio-player.js";
import { AudioPlayerAbout } from "@rhds/elements/react/rh-audio-player-about/rh-audio-player-about.js";
import { AudioPlayerSubscribe } from "@rhds/elements/react/rh-audio-player-subscribe/rh-audio-player-subscribe.js";
import { Avatar } from "@rhds/elements/react/rh-avatar/rh-avatar.js";
import { Cue } from "@rhds/elements/react/rh-cue/rh-cue.js";
import { Transcript } from "@rhds/elements/react/rh-transcript/rh-transcript.js";
// NOTE: React 19+ does not require these wrapper imports.
// You can use the custom elements directly as-is.
export const Demo = () => (
<AudioPlayer id="player" layout="compact-wide" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<AudioPlayerAbout slot="about">
<h4 slot="heading">About the episode</h4>
<p>There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.</p>
<p>Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.</p>
<Avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools,<em>Intel®</em></span>
</Avatar>
</AudioPlayerAbout>
<audio crossorigin="anonymous" slot="media" controls>
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3" />
</audio>
<AudioPlayerSubscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts" />
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify" />
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts" />
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img className="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed" />
</a>
</AudioPlayerSubscribe>
<Transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<Cue start="00:02" voice="Burr Sutter">Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to
success, including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is
Code Comments, an original podcast from Red Hat.</Cue>
<Cue start="00:29" voice="Burr Sutter">I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.</Cue>
<Cue start="01:14" voice="Burr Sutter">In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And
we also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of
an enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's
say an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at
them and trying to determine if there is an error or not.</Cue>
<Cue start="01:56" voice="Burr Sutter">Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.</Cue>
<Cue start="02:20" voice="Ryan Loney">I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is
happening on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may
have been trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.</Cue>
<Cue start="02:57" voice="Burr Sutter">Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more
about it and how it came to be and why it came out of Intel.</Cue>
<Cue start="03:12" voice="Ryan Loney">Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which
is another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel
that were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing
inferences as part of a Computer Vision pipeline, or at least that's how we started.</Cue>
<Cue start="03:58" voice="Ryan Loney">But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now
we're moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer
Vision and don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started
in 2018. And the major focus of that release was optimizing for use cases that go beyond Computer Vision.</Cue>
<Cue start="04:41" voice="Burr Sutter">And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete
examples of Computer Vision?</Cue>
<Cue start="04:50" voice="Ryan Loney">Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or
sensors to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like
infrared or computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or,
"This is not a defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an
alert if somebody forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware
and help to analyze.</Cue>
<Cue start="05:58" voice="Ryan Loney">And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store
and using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the
stores, detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about
automating the process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail
examples that we can walk through.</Cue>
<Cue start="06:55" voice="Burr Sutter">And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.</Cue>
<Cue start="07:28" voice="Burr Sutter">It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength
from one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a
camera and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?</Cue>
<Cue start="07:56" voice="Ryan Loney">What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone
who walked into a grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do
that.</Cue>
<Cue start="08:53" voice="Ryan Loney">The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they
can track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that
they're protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their
products. That's one really good example of how Computer Vision, AI with OpenVINO is being used today.</Cue>
<Cue start="09:49" voice="Burr Sutter">And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store,
our mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I
want to talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a
quality assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?</Cue>
<Cue start="10:23" voice="Ryan Loney">One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're
also doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.</Cue>
<Cue start="11:21" voice="Ryan Loney">I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and
look up their personal information, they can do that.</Cue>
<Cue start="12:17" voice="Ryan Loney">But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification,
identifying people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be
in a situation where they might be violating someone's rights.</Cue>
<Cue start="12:56" voice="Burr Sutter">Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.</Cue>
<Cue start="13:20" voice="Ryan Loney">I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process,
there's other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really
easily identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.</Cue>
<Cue start="14:17" voice="Ryan Loney">So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and
start detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch
on it, or one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small
data set. And I think that's really one of the most important things today.</Cue>
<Cue start="15:11" voice="Ryan Loney">Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.</Cue>
<Cue start="15:37" voice="Burr Sutter">That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input
for the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort
out the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of
anomalies." Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some
cases, to just simply get my model training underway.</Cue>
<Cue start="16:30" voice="Ryan Loney">Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the
defects." And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non
defective item. So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the
approach that we're taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a
factory and they're the ones who know best when they look at these images, which one's going to have an issue, which one's defective.</Cue>
<Cue start="17:31" voice="Ryan Loney">And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking
those people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images,
it's a much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model.
Even better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have
to convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.</Cue>
<Cue start="18:27" voice="Burr Sutter">And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.</Cue>
<Cue start="18:49" voice="Burr Sutter">So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human
is eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and
specifically Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on
manufacturing, but let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated
into medical imaging equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the
same physical room as the patient.</Cue>
<Cue start="19:44" voice="Ryan Loney">We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway
of a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're
in an operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a
parking lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube
placement, ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors
so that they can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it
correctly. Another example is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements
that are usually hard to calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these
measurements to help the doctor avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And
those are just a few examples.</Cue>
<Cue start="21:42" voice="Burr Sutter">Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.</Cue>
<Cue start="22:15" voice="Burr Sutter">And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with
the application? Can you discuss that more?</Cue>
<Cue start="22:38" voice="Ryan Loney">Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential
classes that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label
that could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have
actual breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may
say 65% confidence that she's a flat coated retriever.</Cue>
<Cue start="23:32" voice="Ryan Loney">And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a
dog? I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an
application to tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated.
Because if you're being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it
doesn't match, well then, the accuracy's going to go down.</Cue>
<Cue start="24:25" voice="Ryan Loney">And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where
even the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is
placed incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost
performance, like quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is
taking a CT scan and then trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?</Cue>
<Cue start="25:25" voice="Ryan Loney">Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the
region of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to
really, they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting
the kidney, may be detecting a tumor.</Cue>
<Cue start="26:04" voice="Ryan Loney">And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that
takes longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of
those details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.</Cue>
<Cue start="26:45" voice="Burr Sutter">I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because
we knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge
device, up into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.</Cue>
<Cue start="27:11" voice="Burr Sutter">And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in
the overall application architecture. Would you agree with that or how do you think about that concept?</Cue>
<Cue start="27:56" voice="Ryan Loney">Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're
talking about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds
for every item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at
the individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going
to be a life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get
the result.</Cue>
<Cue start="28:55" voice="Ryan Loney">They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through
the checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."</Cue>
<Cue start="29:30" voice="Burr Sutter">There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his
team at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you
will, of adopting these technologies and discovering what they can do for us?</Cue>
<Cue start="30:06" voice="Ryan Loney">Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving
into the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that
you can go download that's under Creative Commons license for car batteries. It's just not something that's available.</Cue>
<Cue start="30:57" voice="Ryan Loney">And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from
working with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things
that are like the speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more
sophisticated and on larger images.</Cue>
<Cue start="31:50" voice="Ryan Loney">And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.</Cue>
<Cue start="32:34" voice="Burr Sutter">Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.</Cue>
<Cue start="33:00" voice="Ryan Loney">Thanks, Burr. This was a lot of fun. Thanks for having me.</Cue>
<Cue start="33:05" voice="Burr Sutter">You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was
produced by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison,
Nick Burns, Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you
for joining me today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.</Cue>
</Transcript>
</AudioPlayer>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css" />
);Compact
Edit element properties
import '@rhds/elements/rh-audio-player/rh-audio-player.js';rh-audio-player {
margin: var(--rh-space-xl, 24px);
}<rh-audio-player id="player" layout="compact" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<rh-audio-player-about slot="about">
<h4 slot="heading">About the episode</h4>
<p>
There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.
</p>
<p>
Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.
</p>
<rh-avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools, <em>Intel®</em></span>
</rh-avatar>
</rh-audio-player-about>
<audio crossorigin="anonymous" slot="media" controls="">
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3">
</audio>
<rh-audio-player-subscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts">
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify">
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts">
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img class="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed">
</a>
</rh-audio-player-subscribe>
<rh-transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<rh-cue start="00:02" voice="Burr Sutter">
Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to
success, including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is
Code Comments, an original podcast from Red Hat.
</rh-cue>
<rh-cue start="00:29" voice="Burr Sutter">
I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.
</rh-cue>
<rh-cue start="01:14" voice="Burr Sutter">
In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And
we also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of
an enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's
say an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at
them and trying to determine if there is an error or not.
</rh-cue>
<rh-cue start="01:56" voice="Burr Sutter">
Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.
</rh-cue>
<rh-cue start="02:20" voice="Ryan Loney">
I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is
happening on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may
have been trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.
</rh-cue>
<rh-cue start="02:57" voice="Burr Sutter">
Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more
about it and how it came to be and why it came out of Intel.
</rh-cue>
<rh-cue start="03:12" voice="Ryan Loney">
Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which
is another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel
that were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing
inferences as part of a Computer Vision pipeline, or at least that's how we started.
</rh-cue>
<rh-cue start="03:58" voice="Ryan Loney">
But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now
we're moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer
Vision and don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started
in 2018. And the major focus of that release was optimizing for use cases that go beyond Computer Vision.
</rh-cue>
<rh-cue start="04:41" voice="Burr Sutter">
And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete
examples of Computer Vision?
</rh-cue>
<rh-cue start="04:50" voice="Ryan Loney">
Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or
sensors to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like
infrared or computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or,
"This is not a defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an
alert if somebody forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware
and help to analyze.
</rh-cue>
<rh-cue start="05:58" voice="Ryan Loney">
And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store
and using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the
stores, detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about
automating the process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail
examples that we can walk through.
</rh-cue>
<rh-cue start="06:55" voice="Burr Sutter">
And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.
</rh-cue>
<rh-cue start="07:28" voice="Burr Sutter">
It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength
from one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a
camera and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?
</rh-cue>
<rh-cue start="07:56" voice="Ryan Loney">
What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone
who walked into a grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do
that.
</rh-cue>
<rh-cue start="08:53" voice="Ryan Loney">
The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they
can track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that
they're protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their
products. That's one really good example of how Computer Vision, AI with OpenVINO is being used today.
</rh-cue>
<rh-cue start="09:49" voice="Burr Sutter">
And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store,
our mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I
want to talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a
quality assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?
</rh-cue>
<rh-cue start="10:23" voice="Ryan Loney">
One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're
also doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.
</rh-cue>
<rh-cue start="11:21" voice="Ryan Loney">
I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and
look up their personal information, they can do that.
</rh-cue>
<rh-cue start="12:17" voice="Ryan Loney">
But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification,
identifying people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be
in a situation where they might be violating someone's rights.
</rh-cue>
<rh-cue start="12:56" voice="Burr Sutter">
Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.
</rh-cue>
<rh-cue start="13:20" voice="Ryan Loney">
I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process,
there's other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really
easily identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.
</rh-cue>
<rh-cue start="14:17" voice="Ryan Loney">
So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and
start detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch
on it, or one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small
data set. And I think that's really one of the most important things today.
</rh-cue>
<rh-cue start="15:11" voice="Ryan Loney">
Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.
</rh-cue>
<rh-cue start="15:37" voice="Burr Sutter">
That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input
for the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort
out the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of
anomalies." Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some
cases, to just simply get my model training underway.
</rh-cue>
<rh-cue start="16:30" voice="Ryan Loney">
Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the
defects." And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non
defective item. So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the
approach that we're taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a
factory and they're the ones who know best when they look at these images, which one's going to have an issue, which one's defective.
</rh-cue>
<rh-cue start="17:31" voice="Ryan Loney">
And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking
those people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images,
it's a much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model.
Even better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have
to convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.
</rh-cue>
<rh-cue start="18:27" voice="Burr Sutter">
And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.
</rh-cue>
<rh-cue start="18:49" voice="Burr Sutter">
So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human
is eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and
specifically Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on
manufacturing, but let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated
into medical imaging equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the
same physical room as the patient.
</rh-cue>
<rh-cue start="19:44" voice="Ryan Loney">
We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway
of a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're
in an operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a
parking lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube
placement, ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors
so that they can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it
correctly. Another example is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements
that are usually hard to calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these
measurements to help the doctor avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And
those are just a few examples.
</rh-cue>
<rh-cue start="21:42" voice="Burr Sutter">
Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.
</rh-cue>
<rh-cue start="22:15" voice="Burr Sutter">
And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with
the application? Can you discuss that more?
</rh-cue>
<rh-cue start="22:38" voice="Ryan Loney">
Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential
classes that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label
that could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have
actual breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may
say 65% confidence that she's a flat coated retriever.
</rh-cue>
<rh-cue start="23:32" voice="Ryan Loney">
And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a
dog? I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an
application to tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated.
Because if you're being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it
doesn't match, well then, the accuracy's going to go down.
</rh-cue>
<rh-cue start="24:25" voice="Ryan Loney">
And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where
even the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is
placed incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost
performance, like quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is
taking a CT scan and then trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?
</rh-cue>
<rh-cue start="25:25" voice="Ryan Loney">
Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the
region of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to
really, they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting
the kidney, may be detecting a tumor.
</rh-cue>
<rh-cue start="26:04" voice="Ryan Loney">
And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that
takes longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of
those details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.
</rh-cue>
<rh-cue start="26:45" voice="Burr Sutter">
I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because
we knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge
device, up into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.
</rh-cue>
<rh-cue start="27:11" voice="Burr Sutter">
And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in
the overall application architecture. Would you agree with that or how do you think about that concept?
</rh-cue>
<rh-cue start="27:56" voice="Ryan Loney">
Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're
talking about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds
for every item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at
the individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going
to be a life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get
the result.
</rh-cue>
<rh-cue start="28:55" voice="Ryan Loney">
They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through
the checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."
</rh-cue>
<rh-cue start="29:30" voice="Burr Sutter">
There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his
team at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you
will, of adopting these technologies and discovering what they can do for us?
</rh-cue>
<rh-cue start="30:06" voice="Ryan Loney">
Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving
into the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that
you can go download that's under Creative Commons license for car batteries. It's just not something that's available.
</rh-cue>
<rh-cue start="30:57" voice="Ryan Loney">
And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from
working with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things
that are like the speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more
sophisticated and on larger images.
</rh-cue>
<rh-cue start="31:50" voice="Ryan Loney">
And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.
</rh-cue>
<rh-cue start="32:34" voice="Burr Sutter">
Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.
</rh-cue>
<rh-cue start="33:00" voice="Ryan Loney">
Thanks, Burr. This was a lot of fun. Thanks for having me.
</rh-cue>
<rh-cue start="33:05" voice="Burr Sutter">
You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was
produced by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison,
Nick Burns, Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you
for joining me today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.
</rh-cue>
</rh-transcript>
</rh-audio-player>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css">import { AudioPlayer } from "@rhds/elements/react/rh-audio-player/rh-audio-player.js";
import { AudioPlayerAbout } from "@rhds/elements/react/rh-audio-player-about/rh-audio-player-about.js";
import { AudioPlayerSubscribe } from "@rhds/elements/react/rh-audio-player-subscribe/rh-audio-player-subscribe.js";
import { Avatar } from "@rhds/elements/react/rh-avatar/rh-avatar.js";
import { Cue } from "@rhds/elements/react/rh-cue/rh-cue.js";
import { Transcript } from "@rhds/elements/react/rh-transcript/rh-transcript.js";
// NOTE: React 19+ does not require these wrapper imports.
// You can use the custom elements directly as-is.
export const Demo = () => (
<AudioPlayer id="player" layout="compact" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<AudioPlayerAbout slot="about">
<h4 slot="heading">About the episode</h4>
<p>There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.</p>
<p>Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.</p>
<Avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools,<em>Intel®</em></span>
</Avatar>
</AudioPlayerAbout>
<audio crossorigin="anonymous" slot="media" controls>
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3" />
</audio>
<AudioPlayerSubscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts" />
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify" />
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts" />
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img className="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed" />
</a>
</AudioPlayerSubscribe>
<Transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<Cue start="00:02" voice="Burr Sutter">Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to
success, including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is
Code Comments, an original podcast from Red Hat.</Cue>
<Cue start="00:29" voice="Burr Sutter">I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.</Cue>
<Cue start="01:14" voice="Burr Sutter">In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And
we also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of
an enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's
say an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at
them and trying to determine if there is an error or not.</Cue>
<Cue start="01:56" voice="Burr Sutter">Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.</Cue>
<Cue start="02:20" voice="Ryan Loney">I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is
happening on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may
have been trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.</Cue>
<Cue start="02:57" voice="Burr Sutter">Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more
about it and how it came to be and why it came out of Intel.</Cue>
<Cue start="03:12" voice="Ryan Loney">Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which
is another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel
that were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing
inferences as part of a Computer Vision pipeline, or at least that's how we started.</Cue>
<Cue start="03:58" voice="Ryan Loney">But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now
we're moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer
Vision and don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started
in 2018. And the major focus of that release was optimizing for use cases that go beyond Computer Vision.</Cue>
<Cue start="04:41" voice="Burr Sutter">And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete
examples of Computer Vision?</Cue>
<Cue start="04:50" voice="Ryan Loney">Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or
sensors to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like
infrared or computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or,
"This is not a defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an
alert if somebody forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware
and help to analyze.</Cue>
<Cue start="05:58" voice="Ryan Loney">And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store
and using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the
stores, detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about
automating the process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail
examples that we can walk through.</Cue>
<Cue start="06:55" voice="Burr Sutter">And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.</Cue>
<Cue start="07:28" voice="Burr Sutter">It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength
from one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a
camera and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?</Cue>
<Cue start="07:56" voice="Ryan Loney">What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone
who walked into a grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do
that.</Cue>
<Cue start="08:53" voice="Ryan Loney">The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they
can track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that
they're protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their
products. That's one really good example of how Computer Vision, AI with OpenVINO is being used today.</Cue>
<Cue start="09:49" voice="Burr Sutter">And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store,
our mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I
want to talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a
quality assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?</Cue>
<Cue start="10:23" voice="Ryan Loney">One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're
also doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.</Cue>
<Cue start="11:21" voice="Ryan Loney">I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and
look up their personal information, they can do that.</Cue>
<Cue start="12:17" voice="Ryan Loney">But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification,
identifying people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be
in a situation where they might be violating someone's rights.</Cue>
<Cue start="12:56" voice="Burr Sutter">Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.</Cue>
<Cue start="13:20" voice="Ryan Loney">I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process,
there's other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really
easily identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.</Cue>
<Cue start="14:17" voice="Ryan Loney">So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and
start detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch
on it, or one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small
data set. And I think that's really one of the most important things today.</Cue>
<Cue start="15:11" voice="Ryan Loney">Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.</Cue>
<Cue start="15:37" voice="Burr Sutter">That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input
for the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort
out the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of
anomalies." Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some
cases, to just simply get my model training underway.</Cue>
<Cue start="16:30" voice="Ryan Loney">Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the
defects." And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non
defective item. So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the
approach that we're taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a
factory and they're the ones who know best when they look at these images, which one's going to have an issue, which one's defective.</Cue>
<Cue start="17:31" voice="Ryan Loney">And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking
those people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images,
it's a much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model.
Even better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have
to convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.</Cue>
<Cue start="18:27" voice="Burr Sutter">And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.</Cue>
<Cue start="18:49" voice="Burr Sutter">So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human
is eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and
specifically Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on
manufacturing, but let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated
into medical imaging equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the
same physical room as the patient.</Cue>
<Cue start="19:44" voice="Ryan Loney">We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway
of a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're
in an operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a
parking lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube
placement, ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors
so that they can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it
correctly. Another example is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements
that are usually hard to calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these
measurements to help the doctor avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And
those are just a few examples.</Cue>
<Cue start="21:42" voice="Burr Sutter">Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.</Cue>
<Cue start="22:15" voice="Burr Sutter">And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with
the application? Can you discuss that more?</Cue>
<Cue start="22:38" voice="Ryan Loney">Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential
classes that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label
that could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have
actual breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may
say 65% confidence that she's a flat coated retriever.</Cue>
<Cue start="23:32" voice="Ryan Loney">And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a
dog? I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an
application to tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated.
Because if you're being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it
doesn't match, well then, the accuracy's going to go down.</Cue>
<Cue start="24:25" voice="Ryan Loney">And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where
even the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is
placed incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost
performance, like quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is
taking a CT scan and then trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?</Cue>
<Cue start="25:25" voice="Ryan Loney">Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the
region of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to
really, they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting
the kidney, may be detecting a tumor.</Cue>
<Cue start="26:04" voice="Ryan Loney">And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that
takes longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of
those details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.</Cue>
<Cue start="26:45" voice="Burr Sutter">I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because
we knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge
device, up into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.</Cue>
<Cue start="27:11" voice="Burr Sutter">And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in
the overall application architecture. Would you agree with that or how do you think about that concept?</Cue>
<Cue start="27:56" voice="Ryan Loney">Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're
talking about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds
for every item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at
the individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going
to be a life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get
the result.</Cue>
<Cue start="28:55" voice="Ryan Loney">They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through
the checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."</Cue>
<Cue start="29:30" voice="Burr Sutter">There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his
team at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you
will, of adopting these technologies and discovering what they can do for us?</Cue>
<Cue start="30:06" voice="Ryan Loney">Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving
into the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that
you can go download that's under Creative Commons license for car batteries. It's just not something that's available.</Cue>
<Cue start="30:57" voice="Ryan Loney">And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from
working with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things
that are like the speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more
sophisticated and on larger images.</Cue>
<Cue start="31:50" voice="Ryan Loney">And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.</Cue>
<Cue start="32:34" voice="Burr Sutter">Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.</Cue>
<Cue start="33:00" voice="Ryan Loney">Thanks, Burr. This was a lot of fun. Thanks for having me.</Cue>
<Cue start="33:05" voice="Burr Sutter">You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was
produced by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison,
Nick Burns, Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you
for joining me today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.</Cue>
</Transcript>
</AudioPlayer>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css" />
);Customization
Edit element properties
#customization {
height: 100%;
& form {
display: contents;
}
/**
* Warning:
* The following are demonstrations of using CSS variables to customize player color.
* They do not use our design token values for color.
*/
& rh-audio-player {
--purple: oklch(48.72% 0.198 289.56);
--cyan: oklch(70.5% 0.143 231.78);
--purple-light: oklch(78.72% 0.198 289.56);
--cyan-dark: oklch(30.5% 0.143 231.78);
/* --purple-light: oklch(from var(--purple) calc(l + 10%) c h); */
/* --cyan-dark: oklch(from var(--cyan) calc(l - 10%) c h); */
&.purple {
--rh-color-surface-lightest: var(--purple-light);
--rh-color-surface-darkest: var(--purple);
--rh-audio-player-range-thumb-color: #f56d6d;
--rh-audio-player-range-progress-color: #f56d6d;
&.img {
--rh-color-surface-darkest: black;
--rh-color-surface-lightest: white;
&::part(toolbar) {
background-image: url("https://www.redhat.com/cms/managed-files/episode-1-art-hero.png");
background-size: cover;
background-repeat: no-repeat;
background-position: right;
background-blend-mode: difference;
}
}
}
&.cyan {
--rh-color-surface-lightest: var(--cyan);
--rh-color-surface-darkest: var(--cyan-dark);
--rh-audio-player-range-thumb-color: #ffe953;
--rh-audio-player-range-progress-color: #ffe953;
}
}
}import '@rhds/elements/rh-audio-player/rh-audio-player.js';
import '@rhds/elements/lib/elements/rh-context-demo/rh-context-demo.js';
const form = document.querySelector('form');
const player = document.querySelector('rh-audio-player');
/**
* update audio player demo based on form selections
*/
function updateDemo() {
const data = new FormData(form);
const values = Object.fromEntries(data.entries());
const { custom, layout } = values;
const colorClass = custom || '';
player.layout = layout;
player.className = colorClass;
player.hasAccentColor = custom.match(/^(cyan|purple)/);
player.poster =
!values.poster || colorClass === 'purple img' ? undefined
: 'https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png';
}
form.addEventListener('input', updateDemo);
updateDemo();<section id="customization">
<rh-context-demo target="player">
<form slot="controls">
<label>Poster: <input name="poster" type="checkbox" checked=""></label>
<label>Custom color theme:
<select name="custom">
<option value="purple">Purple</option>
<option value="purple img">Purple with Image</option>
<option value="cyan">Cyan</option>
</select>
</label>
<label>Layout:
<select name="layout">
<option value="full" selected="">Full</option>
<option value="compact-wide">Compact Wide</option>
<option value="compact">Compact</option>
<option value="mini">Mini</option>
</select>
</label>
</form>
<rh-audio-player id="player" layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<rh-audio-player-about slot="about">
<h4 slot="heading">About the episode</h4>
<p>
There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.
</p>
<p>
Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.
</p>
<rh-avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools, <em>Intel®</em></span>
</rh-avatar>
</rh-audio-player-about>
<audio crossorigin="anonymous" slot="media" controls="">
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3">
</audio>
<rh-audio-player-subscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts">
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify">
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts">
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img class="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed">
</a>
</rh-audio-player-subscribe>
<rh-transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<rh-cue start="00:02" voice="Burr Sutter">
Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to success,
including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is Code
Comments, an original podcast from Red Hat.
</rh-cue>
<rh-cue start="00:29" voice="Burr Sutter">
I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.
</rh-cue>
<rh-cue start="01:14" voice="Burr Sutter">
In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And we
also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of an
enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's say
an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at them and
trying to determine if there is an error or not.
</rh-cue>
<rh-cue start="01:56" voice="Burr Sutter">
Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.
</rh-cue>
<rh-cue start="02:20" voice="Ryan Loney">
I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is happening
on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may have been
trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.
</rh-cue>
<rh-cue start="02:57" voice="Burr Sutter">
Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more about
it and how it came to be and why it came out of Intel.
</rh-cue>
<rh-cue start="03:12" voice="Ryan Loney">
Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which is
another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel that
were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing inferences as
part of a Computer Vision pipeline, or at least that's how we started.
</rh-cue>
<rh-cue start="03:58" voice="Ryan Loney">
But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now we're
moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer Vision and
don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started in 2018. And
the major focus of that release was optimizing for use cases that go beyond Computer Vision.
</rh-cue>
<rh-cue start="04:41" voice="Burr Sutter">
And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete examples
of Computer Vision?
</rh-cue>
<rh-cue start="04:50" voice="Ryan Loney">
Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or sensors
to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like infrared or
computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or, "This is not a
defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an alert if somebody
forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware and help to analyze.
</rh-cue>
<rh-cue start="05:58" voice="Ryan Loney">
And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store and
using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the stores,
detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about automating the
process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail examples that we can
walk through.
</rh-cue>
<rh-cue start="06:55" voice="Burr Sutter">
And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.
</rh-cue>
<rh-cue start="07:28" voice="Burr Sutter">
It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength from
one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a camera
and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?
</rh-cue>
<rh-cue start="07:56" voice="Ryan Loney">
What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone who walked into a
grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do that.
</rh-cue>
<rh-cue start="08:53" voice="Ryan Loney">
The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they can
track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that they're
protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their products.
That's one really good example of how Computer Vision, AI with OpenVINO is being used today.
</rh-cue>
<rh-cue start="09:49" voice="Burr Sutter">
And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store, our
mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I want to
talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a quality
assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?
</rh-cue>
<rh-cue start="10:23" voice="Ryan Loney">
One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're also
doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.
</rh-cue>
<rh-cue start="11:21" voice="Ryan Loney">
I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and look
up their personal information, they can do that.
</rh-cue>
<rh-cue start="12:17" voice="Ryan Loney">
But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification, identifying
people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be in a situation
where they might be violating someone's rights.
</rh-cue>
<rh-cue start="12:56" voice="Burr Sutter">
Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.
</rh-cue>
<rh-cue start="13:20" voice="Ryan Loney">
I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process, there's
other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really easily
identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.
</rh-cue>
<rh-cue start="14:17" voice="Ryan Loney">
So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and start
detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch on it, or
one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small data set. And
I think that's really one of the most important things today.
</rh-cue>
<rh-cue start="15:11" voice="Ryan Loney">
Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.
</rh-cue>
<rh-cue start="15:37" voice="Burr Sutter">
That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input for
the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort out
the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of anomalies."
Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some cases, to just simply
get my model training underway.
</rh-cue>
<rh-cue start="16:30" voice="Ryan Loney">
Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the defects."
And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non defective item.
So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the approach that we're
taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a factory and they're the ones
who know best when they look at these images, which one's going to have an issue, which one's defective.
</rh-cue>
<rh-cue start="17:31" voice="Ryan Loney">
And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking those
people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images, it's a
much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model. Even
better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have to
convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.
</rh-cue>
<rh-cue start="18:27" voice="Burr Sutter">
And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.
</rh-cue>
<rh-cue start="18:49" voice="Burr Sutter">
So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human is
eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and specifically
Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on manufacturing, but
let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated into medical imaging
equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the same physical room as
the patient.
</rh-cue>
<rh-cue start="19:44" voice="Ryan Loney">
We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway of
a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're in an
operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a parking
lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube placement,
ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors so that they
can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it correctly. Another example
is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements that are usually hard to
calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these measurements to help the doctor
avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And those are just a few examples.
</rh-cue>
<rh-cue start="21:42" voice="Burr Sutter">
Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.
</rh-cue>
<rh-cue start="22:15" voice="Burr Sutter">
And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with the
application? Can you discuss that more?
</rh-cue>
<rh-cue start="22:38" voice="Ryan Loney">
Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential classes
that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label that
could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have actual
breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may say 65%
confidence that she's a flat coated retriever.
</rh-cue>
<rh-cue start="23:32" voice="Ryan Loney">
And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a dog?
I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an application to
tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated. Because if you're
being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it doesn't match, well
then, the accuracy's going to go down.
</rh-cue>
<rh-cue start="24:25" voice="Ryan Loney">
And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where even
the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is placed
incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost performance, like
quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is taking a CT scan and then
trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?
</rh-cue>
<rh-cue start="25:25" voice="Ryan Loney">
Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the region
of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to really,
they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting the kidney,
may be detecting a tumor.
</rh-cue>
<rh-cue start="26:04" voice="Ryan Loney">
And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that takes
longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of those
details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.
</rh-cue>
<rh-cue start="26:45" voice="Burr Sutter">
I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because we
knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge device, up
into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.
</rh-cue>
<rh-cue start="27:11" voice="Burr Sutter">
And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in the
overall application architecture. Would you agree with that or how do you think about that concept?
</rh-cue>
<rh-cue start="27:56" voice="Ryan Loney">
Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're talking
about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds for every
item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at the
individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going to be a
life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get the result.
</rh-cue>
<rh-cue start="28:55" voice="Ryan Loney">
They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through the
checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."
</rh-cue>
<rh-cue start="29:30" voice="Burr Sutter">
There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his team
at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you will, of
adopting these technologies and discovering what they can do for us?
</rh-cue>
<rh-cue start="30:06" voice="Ryan Loney">
Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving into
the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that you can go
download that's under Creative Commons license for car batteries. It's just not something that's available.
</rh-cue>
<rh-cue start="30:57" voice="Ryan Loney">
And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from working
with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things that are like the
speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more sophisticated and on
larger images.
</rh-cue>
<rh-cue start="31:50" voice="Ryan Loney">
And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.
</rh-cue>
<rh-cue start="32:34" voice="Burr Sutter">
Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.
</rh-cue>
<rh-cue start="33:00" voice="Ryan Loney">
Thanks, Burr. This was a lot of fun. Thanks for having me.
</rh-cue>
<rh-cue start="33:05" voice="Burr Sutter">
You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was produced
by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison, Nick Burns,
Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you for joining me
today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.
</rh-cue>
</rh-transcript>
</rh-audio-player>
</rh-context-demo>
</section>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css">import { AudioPlayer } from "@rhds/elements/react/rh-audio-player/rh-audio-player.js";
import { AudioPlayerAbout } from "@rhds/elements/react/rh-audio-player-about/rh-audio-player-about.js";
import { AudioPlayerSubscribe } from "@rhds/elements/react/rh-audio-player-subscribe/rh-audio-player-subscribe.js";
import { Avatar } from "@rhds/elements/react/rh-avatar/rh-avatar.js";
import { Cue } from "@rhds/elements/react/rh-cue/rh-cue.js";
import { Transcript } from "@rhds/elements/react/rh-transcript/rh-transcript.js";
// NOTE: React 19+ does not require these wrapper imports.
// You can use the custom elements directly as-is.
export const Demo = () => (
<section id="customization">
<rh-context-demo target="player">
<form slot="controls">
<label>
Poster:
<input name="poster" type="checkbox" checked />
</label>
<label>
Custom color theme:
<select name="custom">
<option value="purple">Purple</option>
<option value="purple img">Purple with Image</option>
<option value="cyan">Cyan</option>
</select>
</label>
<label>
Layout:
<select name="layout">
<option value="full" selected>Full</option>
<option value="compact-wide">Compact Wide</option>
<option value="compact">Compact</option>
<option value="mini">Mini</option>
</select>
</label>
</form>
<AudioPlayer id="player" layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<AudioPlayerAbout slot="about">
<h4 slot="heading">About the episode</h4>
<p>There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.</p>
<p>Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.</p>
<Avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools,<em>Intel®</em></span>
</Avatar>
</AudioPlayerAbout>
<audio crossorigin="anonymous" slot="media" controls>
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3" />
</audio>
<AudioPlayerSubscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts" />
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify" />
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts" />
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img className="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed" />
</a>
</AudioPlayerSubscribe>
<Transcript id="regular" slot="transcript">
<h4 slot="heading">Transcript</h4>
<Cue start="00:02" voice="Burr Sutter">Hi, I'm Burr Sutter. I'm a Red Hatter who spends a lot of time talking to technologists about technologies. We say this a lot at Red Hat. No single technology provider holds the key to success,
including us. And I would say the same thing about myself. I love to share ideas, so I thought it would be awesome to talk to some brilliant technologists at Red Hat Partners. This is Code
Comments, an original podcast from Red Hat.</Cue>
<Cue start="00:29" voice="Burr Sutter">I'm sure, like many of you here, you have been thinking about AI/ML, artificial intelligence and machine learning. I've been thinking about that for quite some time and I actually had the
opportunity to work on a few successful projects, here at Red Hat, using those technologies, actually enabling a data set, gathering a data set, working with a data scientist and data
engineering team, and then training a model and putting that model into production runtime environment. It was an exciting set of projects and you can see those on numerous YouTube videos that
have published out there before. But I want you to think about the problem space a little bit, because there are some interesting challenges about a AI/ML. One is simply just getting access to
the data, and while there are numerous publicly available data sets, when it comes to your specific enterprise use case, you might not be to find publicly available data.</Cue>
<Cue start="01:14" voice="Burr Sutter">In many cases you cannot, even for our applications that we created, we had to create our data set, capture our data set, explore the data set, and of course, train a model accordingly. And we
also found there's another challenge to be overcome in this a AI/ML world, and that is access to certain types of hardware. If you think about an enterprise environment and the creation of an
enterprise application specifically for a AI/ML, end users need an inference engine to run on their hardware. Hardware that's available to them, to be effective for their application. Let's say
an application like Computer Vision, one that can detect anomalies and medical imaging or maybe on a factory floor. As those things are whizzing by on the factory line there, looking at them and
trying to determine if there is an error or not.</Cue>
<Cue start="01:56" voice="Burr Sutter">Well, how do you actually make it run on your hardware, your accessible technology that you have today? Well, there's a solution for this as an open toolkit called OpenVINO. And you might be
thinking, "Hey, wait a minute, don't you need a GPU for AI inferencing, a GPU for artificial intelligence, machine learning? Well, not according to Ryan Loney, product manager of OpenVINO
Developer Tools at Intel.</Cue>
<Cue start="02:20" voice="Ryan Loney">I guess I'll start with trying to maybe dispel a myth. I think that CPUs are widely used for inference today. So if we look at the data center segment, about 70% of the AI inference is happening
on Intel Xeon, on our data center CPUs. And so you don't need a GPU especially for running inference. And that's part of the value of OpenVINO, is that we're taking models that may have been
trained on a GPU using deep learning frameworks like PyTorch or TensorFlow, and then optimizing them to run on Intel hardware.</Cue>
<Cue start="02:57" voice="Burr Sutter">Ryan joined me to discuss AI/ML in the enterprise across various industries and exploring numerous use cases. Let's talk a little bit about the origin story behind OpenVINO. Tell us more about
it and how it came to be and why it came out of Intel.</Cue>
<Cue start="03:12" voice="Ryan Loney">Definitely. We had the first release of OpenVINO, was back in 2018, so still relatively new. And at that time, we were focused on Computer Vision and pretty tightly coupled with OpenCV, which is
another open source library with origins at Intel. It had its first release back in 1999, so it's been around a little bit longer. And many of the software engineers and architects at Intel that
were involved with and contributing to OpenCV are working on OpenVINO. So you can think of OpenVINO as complimentary software to OpenCV and we're providing an engine for executing inferences as
part of a Computer Vision pipeline, or at least that's how we started.</Cue>
<Cue start="03:58" voice="Ryan Loney">But since 2018, we've started to move beyond just Computer Vision inference. So when I say Computer Vision inference, I mean image classification, object detection, segmentation, and now we're
moving into natural language processing. Things like speech synthesis, speech recognition, knowledge graphs, time series forecasting and other use cases that don't involve Computer Vision and
don't involve inference on pixels. Our latest release, the 2022.1 that came out earlier this year, that was the most significant update that we've had to OpenVINO, since we started in 2018. And
the major focus of that release was optimizing for use cases that go beyond Computer Vision.</Cue>
<Cue start="04:41" voice="Burr Sutter">And I like that concept that you just mentioned right there, Computer Vision, and you said that you extended those use cases and went beyond that. Could you give us some more concrete examples
of Computer Vision?</Cue>
<Cue start="04:50" voice="Ryan Loney">Sure. When you think about manufacturing, quality control in factories, everything from arc welding, defect detection to inspecting BMW cars on assembly lines, they're using cameras or sensors
to collect data and usually it's cameras collecting images like RGB images that you and I can see and looks like something taken from a camera or video camera. But also, things like infrared or
computerized tomography scans used in healthcare, X-ray, different types of images where we can draw bounding boxes around regions of interest and say, "This is a defect," or, "This is not a
defect." And also, "Is this worker wearing a safety hat or did they forget to put it on?" And so, you can take this and integrate it into a pipeline where you're triggering an alert if somebody
forgets to wear their safety mask, or if there's a defect in a product on an assembly line, you can just use cameras and OpenVINO and OpenCV running these on Intel hardware and help to analyze.</Cue>
<Cue start="05:58" voice="Ryan Loney">And that's what a lot of the partners that we work with are doing, so these independent software vendors. And there's other use cases for things like retail. You think about going to a store and
using an automated checkout system. Sometimes people use those automated checkouts and they slide a few extra items into their bag that they don't scan and it's a huge loss for the retail
outlets that are providing this way to check out realtime shelf monitoring. We have a Vispera, one of our ISVs that helps keep store shelves stocked by just analyzing the cameras in the stores,
detecting when objects are missing from the shelves so that they can be restocked. We have Vistry, another ISV that works with quick service restaurants. When you think about automating the
process of, when do I drop the fries into the fryer so that they're warm when the car gets to the drive through window, there's quite a bit of industrial healthcare retail examples that we can
walk through.</Cue>
<Cue start="06:55" voice="Burr Sutter">And we should dig into some more of those, but I got to tell you, I have a personal experience in this category that I want to share with and you can tell me how silly you might think at this
point in time it is. We actually built a keynote demonstration for the Red Hat big stage back in 2015. And I really want to illustrate the concept of asset tracking. So we actually gave
everybody in the conference a little Bluetooth token with a little battery, a little watch battery, and a little Bluetooth emitter. And we basically tracked those things around the conference.
We basically put a raspberry pi in each of the meeting rooms and up in the lunch room and you could see how the tokens moved from room to room to room.</Cue>
<Cue start="07:28" voice="Burr Sutter">It was a relatively simple application, but it occurred to me, after we figured out how to do that with Bluetooth and triangulating Bluetooth signals by looking at relative signal strength from
one radio to another and putting that through an Apache Spark application at the time, we then realized, "You know what? This is easier done with cameras." And just simply looking at a camera
and having some form of a AI/ML model, a machine learning model, that would say, "There are people here now," or, "There are no people here now." What do you think about that?</Cue>
<Cue start="07:56" voice="Ryan Loney">What you just described is exactly the product that Pathr, one of our partners is offering, but they're doing it with Computer Vision and cameras. So when Pathr tries to help retail stores
analyze the foot traffic and understand, with heat maps, where are people spending the most time in stores, how many people are coming in, what size groups are coming into the store and trying
to help understand if there was a successful transaction from the people who entered the store and left the store, to help with the retail analytics and marketing sales and positioning of
products. And so, they're doing that in a way that also protects privacy. And that's something that's really important. So when you talked about those Bluetooth beacons, probably if everyone who walked into a
grocery store was asked to put a tracking device in their cart or on their person and say, "You're going to be tracked around the store," they probably wouldn't want to do that.</Cue>
<Cue start="08:53" voice="Ryan Loney">The way that you can do this with cameras, is you can detect people as they enter and remove their face. So you can ignore any biometric information and just track the person based on pixels
that are present in the detected region of interest. So they're able to analyze... Say a family walks in the door and they can group those people together with object detection and then they can
track their movement throughout the store without keeping track of their face, or any biometric, or any personal identifiable information, to avoid things like bias and to make sure that they're
protecting the privacy of the shoppers in the store, while still getting that really useful marketing analytics data. So that they can make better decisions about where to place their products.
That's one really good example of how Computer Vision, AI with OpenVINO is being used today.</Cue>
<Cue start="09:49" voice="Burr Sutter">And that is a great example, because you're definitely spot on. It is invasive when you hand someone a Bluetooth device and say, "Please, keep this with you as you go throughout our store, our
mall or throughout our hospital, wherever you might be." Now you mentioned another example earlier in the conversation which was related to worker safety. "Are they wearing a helmet?" I want to
talk more about that concept in a real industrial setting, a manufacturing setting, where there might be a factory floor and there's certain requirements. Or better yet there's like a quality
assurance requirement, let's say, when it comes to looking at a factory line. I've run that use case often with some of our customers. Can you talk more about those kinds of use cases?</Cue>
<Cue start="10:23" voice="Ryan Loney">One of our partners, Robotron, we published a case study, I think last year, where they were working with BMW at one of their factories. And they do quality control inspection, but they're also
doing things related to worker safety and analyzing. I use the safety hat example. There's a number of our ISVs and partners who have similar use cases and it comes down to, there's a few
reasons that are motivating this and some are related to insurance. It's important to make sure that if you want to have your factory insured, that your workers are protecting themselves and
wearing the gear regulatory compliance, you're being asked to properly protect from exposure to chemicals or potentially having something fall and hit someone on the head. So wearing a safety
vest, wearing goggles, wearing a helmet, these are things that you need to do inside the factory and you can really easily automate and detect and sometimes without bias.</Cue>
<Cue start="11:21" voice="Ryan Loney">I think that's one of the interesting things about the Robotron-BMW example is that they were also blurring, blacking out, so drawing a box to cover the face of the workers in the factory, so
that somebody who was analyzing the video footage and getting the alerts saying that, "Bay 21 has a worker without a hat on," that it's not sending their face and in the alert and potentially
invading or going against privacy laws or just the ethics of the company. They don't want to introduce bias or have people targeted because it's much better to blur the face and alert and have
somebody take care of it on the floor. And then, if you ever need to audit that information later, they have a way to do it where people who need to be able to see who the employee was and look
up their personal information, they can do that.</Cue>
<Cue start="12:17" voice="Ryan Loney">But then just for the purposes of maintaining safety, they don't need to have access to that personal information, or biometric information. Because that's one thing that when you hear about
Computer Vision or person tracking, object detection, there's a lot of concern, and rightfully so, about privacy being invaded and about tracking information, face re-identification, identifying
people who may have committed crimes through video footage. And that's just not something that a lot of companies want to... They want to protect privacy and they don't want to be in a situation
where they might be violating someone's rights.</Cue>
<Cue start="12:56" voice="Burr Sutter">Well, privacy is certainly opening up Pandora's box. There's a lot to be explored in that area, especially in a digital world that we now live in. But for now, let's move on and explore a
different area. I'm interested in how machines and computers offer advantages specifically in certain use cases like a quality control scenario. I asked Ryan to explain how a AI/ML and
specifically machines, computers, could augment that capability.</Cue>
<Cue start="13:20" voice="Ryan Loney">I can give a specific example where we have a partner that's doing defect detection, looking for anomalies in batteries. I'm sure you've heard there's a lot of interest right now in electric
vehicles, a lot of batteries being produced. And so, if you go into one of these factories, they have images that they collect of every battery that's going through this assembly line. And
through these images, people can look and see and visually inspect what their eyes and say, "This battery has a defect, send it back." And that's one step in the quality control process, there's
other steps I'm sure, like running diagnostic tests and measuring voltage and doing other types of non-visual inspection. But for the visual inspection piece, where you can really easily
identify some problems, it's much more efficient to introduce Computer Vision. And so, that's where we have this new library that we've introduced, called Anomalib.</Cue>
<Cue start="14:17" voice="Ryan Loney">So OpenVINO, while we're focused on inference, we're also thinking about the pipeline, or the funnel, that gets these models to OpenVINO. And so, we've invested in this anomaly segmentation,
anomaly detection library that we've recently open sourced and there's a great research paper about it, about Anomalib, but the idea is you can take just a few images and train a model and start
detecting these defects. And so, for this battery example, that's a more advanced example, but to make it simpler, take some bolts and... Take 10 bolts. You have one that has a scratch on it, or
one that is chipped, or has some damage to it, and you can easily get started in training to recognize the bolts that do not have an anomaly and the ones that do, which is a small data set. And
I think that's really one of the most important things today.</Cue>
<Cue start="15:11" voice="Ryan Loney">Challenges, one is access to data, but the other is needing a massive amount of data to do something meaningful. And so we're starting to try to change that dynamic with Anomalib. You may not
need a 100,000 images, you may need 100 images and you can start detecting anomalies in everything from batteries to bolts to, maybe even the wood varnish use case that you mentioned.</Cue>
<Cue start="15:37" voice="Burr Sutter">That is a very key point because often in that data scientist process, that data engineering data scientist process, the one key thing is, can you gather the data that you need for the input for
the model training? And we've often said, at least people I've worked with over the last couple years, "You need a lot of data, you need tens of thousands of correct images, so we can sort out
the difference between dogs versus cats," let's say. Or you need dozens and dozens of situations where if it's a natural language processing scenario, a good customer interaction, a good
customer conversation. And this case it sounds like what you're saying is, "Show us just the bad things, fewer images, fewer incorrect things, and then let us look for those kind of anomalies."
Can you tell us more about that? Because that is very interesting. The concept that I can use a much smaller data set as my input, as opposed to gathering terabytes of data in some cases, to just simply
get my model training underway.</Cue>
<Cue start="16:30" voice="Ryan Loney">Like you described, the idea is, if you have some good images and then you have some of the known defects, and you can just label, "Here's a set of good images and here's a few of the defects."
And you can right away start detecting those specific defects that you've identified. And then, also be able to determine when it doesn't match the expected appearance of a non defective item.
So if I have the undamaged screw and then I introduce one with some new anomaly that's never been seen before, I can say this one is not a valid screw. And so, that's the approach that we're
taking and it's really important because so often you need to have subject matter experts. Take the battery example, there's these workers who are on the floor, in a factory and they're the ones
who know best when they look at these images, which one's going to have an issue, which one's defective.</Cue>
<Cue start="17:31" voice="Ryan Loney">And then they also need to take that subject matter expertise and then use it to annotate data sets. And when you have these tens of thousands of images you need to annotate, it's asking those
people to stop working on the factory floor so they can come annotate some images. That's a tough business call to make, right? But if you only need them to annotate a handful of images, it's a
much easier ask to get the ball rolling and demonstrate value. And maybe over time you will want to annotate more and more images because you'll get even better accuracy in the model. Even
better, even if it's just small incremental improvements, that's something that if it generates value for the business, it's something the business will invest in over time. But you have to
convince the decision makers that it's worth the time of these subject matter experts to stop what they're doing and go and label some images of the things that they're working on in the
factory.</Cue>
<Cue start="18:27" voice="Burr Sutter">And that labeling process can be very labor intensive. If the annotation is basically saying what is correct, what's wrong, what is this, what is that. And therefore if we can minimize that
timeframe to get the value quicker, then there's something that's useful for the business, useful for the organization, long before we necessarily go through a whole huge model training phase.</Cue>
<Cue start="18:49" voice="Burr Sutter">So we talked about labeling and how that is labor intensive activity, but I love the idea of helping the human. And helping the human most specifically not get bored. Basically if the human is
eyeballing a bunch of widgets flying by, over time they make mistakes, they get bored and they don't pay as close attention as they should. That's why the constant of AI/ML, and specifically
Computer Vision augmenting that capability and really helping the human identify anomalies faster, more quickly, maybe with greater accuracy, could be a big win. We focused on manufacturing, but
let's actually go into healthcare and learn how these tools can be used in that sector and that industry. Ryan talked me about how OpenVINO's run time can be incorporated into medical imaging
equipment with Intel processors embedded in CT, MRI and ultrasound machines. While these inferences, this AI/ML workload, can be operating and executing right there in the same physical room as
the patient.</Cue>
<Cue start="19:44" voice="Ryan Loney">We did a presentation with GE last year, I think they said there's at least 80 countries that have their x-ray machines deployed. And they're doing things like helping doctors place breathing
tubes in patients. So during COVID, during the pandemic, that was a really important tool to help with nurses and doctors who were intubating patients, sometimes in a parking lot or a hallway of
a hospital. And when they had a statistic that GE said, I think one out of four breathing tubes gets placed incorrectly when you're doing it outside the operating room. Because when you're in an
operating room it's much more controlled and there's someone who's an expert at placing the tubes, it's something you have more of a controlled environment. But when you're out, in a parking
lot, in a tent, when the hospital's completely full and you're triaging patients with COVID, that's when they're more likely to make mistakes.And so, they had this endotracheal tube placement,
ETT, model that they trained and it helped to use an x-ray and give an alert and say, "This tube is placed wrong, pull it out and do it again." And so, things like that help doctors so that they
can avoid mistakes. And having a breathing tube placed incorrectly can cause collapsed lung and a number of other unwanted side effects. So it's really important to do it correctly. Another example
is Samsung Medison. They actually are estimating fetal angle of progression. So this is analyzing ultrasound of pregnant women being able to help take measurements that are usually hard to
calculate, but it can be done in an automated way. They're already taking an ultrasound scan and now they're executing this model that can take some of these measurements to help the doctor
avoid potentially more intrusive alternative methods. So the patient wins, it makes their life better and the doctor is getting help from this AI model. And those are just a few examples.</Cue>
<Cue start="21:42" voice="Burr Sutter">Those are some amazing examples when it comes to all these things, we're talking CT scans and x-rays, other examples of Computer Vision. One thing that's kind of interesting in this space, I
think, whenever I get a chance to work on, let's say an object detection model, and one of our workshops, by the way, is actually putting that out in front of people to say, "Look, you can use
your phone and it basically sends the image over to our OpenShift with our data science platform and then analyzes what you see." And even in my case, where I take a picture of my dog as an
example, it can't really decide, is it a dog or a cat? I have a very funny looking dog.</Cue>
<Cue start="22:15" voice="Burr Sutter">And so there's always a percentage outcome. In other words, "I think it's a dog, 52%." So I want to talk about that more. How important is it to get to that a hundred percent accuracy? How
important is it to really, depending on the use case, to allow for the gray area if you will, where it's an 80% accuracy or a 70% accuracy, and what are the trade offs there associated with the
application? Can you discuss that more?</Cue>
<Cue start="22:38" voice="Ryan Loney">Accuracy is definitely a touchy subject, because how you measure it makes a huge difference. I think what you were describing with the dog example, there's sort of a top five potential classes
that might maybe be identified. So let's say you're doing object detection and you detect a region of interest, and it says 65% confidence this is a dog. Well, the next potential label that
could be maybe 50% confidence or 20% confidence might be something similar to a dog. Or in the case of models that have been trained on the ImageNet dataset or on COCO dataset, they have actual
breeds of dogs. If I want to look at the top five labels for a dog, for my dog for example, she's a mix, mostly a Labrador retriever, but I may look at the top five labels and it may say 65%
confidence that she's a flat coated retriever.</Cue>
<Cue start="23:32" voice="Ryan Loney">And then confidence that she's a husky as 20%, and then 5% confidence that she's a greyhound or something. Those labels, all of them are dogs. So if I'm just trying to figure out, is this a dog?
I could probably find all of the classes within the data set and say, "Well, these all, class ID 65, 132, 92 and 158, all belong to a group of dogs." So if I want to just write an application to
tell me if this is a dog or not, I would probably use that to determine if it's a dog. But how you measure that as accuracy, well that's where it gets a little bit complicated. Because if you're
being really strict about the definition and you're trying to validate against the data set of labeled images, and I have specific dog breeds or some specific detail and it doesn't match, well
then, the accuracy's going to go down.</Cue>
<Cue start="24:25" voice="Ryan Loney">And that's especially important when we talk about things like compression and quantization, which historically, has been difficult to get adoption in some domains, like healthcare, where even
the hint of accuracy going down implies that we're not going to be able to help. In some small case, maybe if it's even half a percent of the time, we won't detect that that tube is placed
incorrectly or that that patient's lung has collapsed or something like that. And that's something that really prevents adoption of some of these methods that can really boost performance, like
quantization. But if you take that example of... Different from the dog example, and you think about segmentation of kidneys. If I'm doing kidney segmentation, which is taking a CT scan and then
trying to pick the pixels out of that scan that belong to a kidney, how I measure accuracy may be how many of those pixels I'm able to detect and how many did I miss?</Cue>
<Cue start="25:25" voice="Ryan Loney">Missing some of the pixels is maybe not a problem, depending on how you've built the application, because you still detect the kidney, and maybe you just need to apply padding around the region
of interest, so that you don't miss any of the actual kidney when you compress the model and when you quantize the model. But that requires a data scientist, an ML engineer, somebody to really,
they have to be able to go and apply that after the fact, after the inference happens, to make sure that you're not losing critical information. Because the next step from detecting the kidney,
may be detecting a tumor.</Cue>
<Cue start="26:04" voice="Ryan Loney">And so, maybe you can use the more optimized model to detect the kidney, but then you can use a slower model to detect the tumor. But that also requires somebody to architect and make that
decision or that trade off and say, "Well, I need to add padding," or, "I should only use the quantized model to detect the region of interest for the kidney." And then, use the model that takes
longer to do the inference just to find the tumor, which is going to be on a smaller size. The dimensions are going to be much smaller once we crop to the region of interest. But all of those
details, that's maybe not easy to explain in a few sentences and even the way I explained it is probably really confusing.</Cue>
<Cue start="26:45" voice="Burr Sutter">I do love that use case, like you mentioned, the cropping, even in one scenario that we worked on for another project, we specifically decided to pixelate the image that we had taken, because we
knew that we could get the outcome we wanted by even just using a smaller or having less resolution in our image. And therefore, as we transferred it from the mobile device, the edge device, up
into the cloud, we wanted that smaller image just for transfer purposes. And still, we could get the accuracy we needed by a lot of testing.</Cue>
<Cue start="27:11" voice="Burr Sutter">And one thing that's interesting about that, from my perspective, is, if you're doing image processing, sometimes it takes a while for this transaction to occur. I come from a traditional
application background, where I'm reading and writing things from a database, or a message broker, or moving data from one place to another. Those things happen sub-second normally, even with
great latency between your data centers, it's still sub-second in most cases. While a transaction like this one can actually take two seconds or four seconds, as it's doing its analysis and
actually coming back with its, "I think it's a dog, I think it's a kidney, I think it's whatever." And providing me that accuracy statement. That concept of optimization is very important in the
overall application architecture. Would you agree with that or how do you think about that concept?</Cue>
<Cue start="27:56" voice="Ryan Loney">Definitely. It depends too on the use case. So if you think about how important it is to reduce the latency and increase the number of frames per second that you can process when you're talking
about a loss prevention model that's running at a grocery store. You want to keep the lines moving, you don't want every person who's at the self checkout to have to wait five seconds for every
item they scan. You need it to happen as quickly as possible. And if sometimes the accuracy decreases slightly, or I'd say the accuracy of the whole pipeline, so not just looking at the
individual model or the individual inference, but let's say that the whole pipeline is not as successful at detecting when somebody steals one item from the self checkout, it's not going to be a
life threatening situation. Whereas being hooked up to the x-ray machine with the tube placement model, they might be willing to have the doctor or the nurse wait five seconds to get the result.</Cue>
<Cue start="28:55" voice="Ryan Loney">They don't need it to happen in 500 milliseconds. Their threshold for waiting is a little bit higher. That, I think, also drives some of the decision. You want to keep people moving through the
checkout line and you can afford to, potentially, if you lose a little bit of accuracy here and there, it's not going to cost the company that much money or it's not going to be life
threatening. It's going to be worth the trade off of keeping the line moving and not having people leave the store and not check out at all, to say, "I'm not going to shop today because the
line's too long."</Cue>
<Cue start="29:30" voice="Burr Sutter">There are so many trade-offs in enterprise AI/ML use cases, things like latency, accuracy and availability, and certainly complexities abound, especially in an obviously ever-evolving
technological landscape where we are still very early in the adoption of AI/ML. And to navigate that complexity, that direct feedback from real world end users is essential to Ryan and his team
at Intel. What would you say are some of the big hurdles or big outcomes, big opportunities in that space? And do you agree that we're still at the very beginning, in our infancy if you will, of
adopting these technologies and discovering what they can do for us?</Cue>
<Cue start="30:06" voice="Ryan Loney">Yeah, I think we're definitely in the infancy and I think that what we've seen is, our customers are evolving and the people who are deploying on Intel hardware, they're trying to run more
complicated models. They're the models that are doing object detection or detecting defects and doing segmentation. In the past you could say, "Here's a generic model that will do face
detection, or person detection, or vehicle detection, license plate detection." And those are general purpose models that you can just grab off the shelf and use them. But now we're moving into
the Anomalib scenarios, where I've got my own data and I'm trying to do something very specific and I'm the only one that has access to this data. You don't have that public data set that you can go
download that's under Creative Commons license for car batteries. It's just not something that's available.</Cue>
<Cue start="30:57" voice="Ryan Loney">And so, those use cases, the challenge with training those models and getting them optimized is the beginning of the pipeline. It's the data. You have to get the data, you have to annotate it
and the tools have to exist for you to do that. And that's part of the problem that we're trying to help solve. And then, the models are getting more complex. So if you think, just from working
with customers recently, they're no longer just trying to do image classification, "Is it a dog or a cat?" They've moved on to 3D point clouds and 3D segmentation models and things that are like the
speech synthesis example. These GPT models that are generating... You put a text input and it generates an image for you. It's just becoming much more advanced, much more sophisticated and on
larger images.</Cue>
<Cue start="31:50" voice="Ryan Loney">And so things like running super resolution and enhancing images, upscaling images, instead of just trying to take that 200 by 200 pixel image and classifying if it's a cat, now we're talking
about gigantic, huge images that we're processing and that all requires more resources or more optimized models. And every Computer Vision conference or AI conference, there's a new latest and
greatest architecture, there's new research paper, and things are getting adopted much faster. The lead time for a NeurIPS paper, CVPR, for a company to actually adopt and put those into
production, the time shortens every year.</Cue>
<Cue start="32:34" voice="Burr Sutter">Well Ryan, I got to tell you, I could talk to you, literally, all day about these topics, the various use cases, the various ways models are being optimized, how to put models into a pipeline
for average enterprise applications. I've enjoyed learning about OpenVINO and Anomalib. I'm fascinated by this, because I'll have a chance to go try this myself, taking advantage of Red Hat
OpenShift and taking advantage of our data science platform. On top of that, I will definitely go be poking at this myself. Thank you so much for your time today.</Cue>
<Cue start="33:00" voice="Ryan Loney">Thanks, Burr. This was a lot of fun. Thanks for having me.</Cue>
<Cue start="33:05" voice="Burr Sutter">You can check out the full transcript of our conversation and more resources, like a link to a white paper on OpenVINO and Anomalib at redhat.com/codecommentspodcast. This episode was produced
by Brent Simoneaux and Caroline Creaghead. Our sound designer is Christian Prohom. Our audio team includes Leigh Day, Stephanie Wonderlick, Mike Esser, Laura Barnes, Claire Allison, Nick Burns,
Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, Laura Walters, Alex Traboulsi, and Victoria Lawton. I'm your host, Burr Sutter. Thank you for joining me
today on Code Comments. I hope you enjoyed today's session and today's conversation, and I look forward to many more.</Cue>
</Transcript>
</AudioPlayer>
</rh-context-demo>
</section>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css" />
);Detailed Transcript
Edit element properties
import '@rhds/elements/rh-audio-player/rh-audio-player.js';rh-audio-player {
margin: var(--rh-space-xl, 24px);
}<rh-audio-player layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<rh-audio-player-about slot="about">
<h4 slot="heading">About the episode</h4>
<p>
There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.
</p>
<p>
Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.
</p>
<rh-avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools, <em>Intel®</em></span>
</rh-avatar>
</rh-audio-player-about>
<audio crossorigin="anonymous" slot="media" controls="">
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3">
</audio>
<rh-audio-player-subscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts">
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify">
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts">
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img class="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed">
</a>
</rh-audio-player-subscribe>
<rh-transcript slot="transcript">
<rh-cue start="00:02" voice="Burr Sutter"></rh-cue>
<rh-cue start="00:02" end="00:04">Hi, I'm Burr Sutter.</rh-cue>
<rh-cue start="00:04" end="00:05">I'm a Red Hatter</rh-cue>
<rh-cue start="00:05" end="00:08">who spends a lot of time talking to technologists about technologies.</rh-cue>
<rh-cue start="00:09" end="00:10">We say this a lot of Red Hat.</rh-cue>
<rh-cue start="00:10" end="00:14">No single technology provider holds the key to success, including us.</rh-cue>
<rh-cue start="00:15" end="00:17">And I would say the same thing about myself.</rh-cue>
<rh-cue start="00:17" end="00:18">I love to share ideas.</rh-cue>
<rh-cue start="00:18" end="00:19">So I thought it'd be awesome</rh-cue>
<rh-cue start="00:19" end="00:22">to talk to some brilliant technologists at Red Hat Partners.</rh-cue>
<rh-cue start="00:23" end="00:26">This is Code Comments, an original podcast</rh-cue>
<rh-cue start="00:26" end="00:29">from Red Hat.</rh-cue>
<rh-cue start="00:29" voice="Burr Sutter"></rh-cue>
<rh-cue start="00:29" end="00:32">I'm sure, like many of you here, you have been thinking about</rh-cue>
<rh-cue start="00:32" end="00:36">AI, ML, artificial intelligence and machine learning.</rh-cue>
<rh-cue start="00:36" end="00:38">I've been thinking about that for quite some time</rh-cue>
<rh-cue start="00:38" end="00:39">and actually had the opportunity</rh-cue>
<rh-cue start="00:39" end="00:43">to work on a few successful projects here at Red Hat using those technologies,</rh-cue>
<rh-cue start="00:43" end="00:46">actually enabling a dataset, gathering a dataset,</rh-cue>
<rh-cue start="00:46" end="00:49">working with data scientists and data engineering team,</rh-cue>
<rh-cue start="00:49" end="00:51">and then training a model and putting that model into production</rh-cue>
<rh-cue start="00:51" end="00:53">runtime environment.</rh-cue>
<rh-cue start="00:53" end="00:55">It was an exciting set of projects and you can kind of see</rh-cue>
<rh-cue start="00:55" end="00:58">those on numerous YouTube videos I have published out there before.</rh-cue>
<rh-cue start="00:59" end="01:01">But I want you to think about the problem space a little bit</rh-cue>
<rh-cue start="01:01" end="01:04">because there are some interesting challenges about AI/ML.</rh-cue>
<rh-cue start="01:04" end="01:06">One is simply just getting access to the data,</rh-cue>
<rh-cue start="01:06" end="01:09">and while there are numerous publicly available datasets</rh-cue>
<rh-cue start="01:09" end="01:12">when it comes to your specific enterprise use case, you might not be to find</rh-cue>
<rh-cue start="01:12" end="01:14">publicly available data.</rh-cue>
<rh-cue start="01:14" voice="Burr Sutter"></rh-cue>
<rh-cue start="01:14" end="01:17">In many cases, you cannot, even for our applications that we created,</rh-cue>
<rh-cue start="01:17" end="01:20">we had to create our dataset, capture our dataset,</rh-cue>
<rh-cue start="01:21" end="01:24">explore the dataset, and of course train a model accordingly.</rh-cue>
<rh-cue start="01:24" end="01:27">And we also found there's another challenge to be overcome</rh-cue>
<rh-cue start="01:27" end="01:30">in this AML world, and that is access to certain types of hardware.</rh-cue>
<rh-cue start="01:31" end="01:33">If you think about the enterprise environment</rh-cue>
<rh-cue start="01:33" end="01:36">and the creation of an enterprise application specifically for AML</rh-cue>
<rh-cue start="01:37" end="01:40">and users need an inference engine to run on their hardware,</rh-cue>
<rh-cue start="01:40" end="01:43">hardware that's available to them to be effective for their application.</rh-cue>
<rh-cue start="01:43" end="01:45">Let's say an application like computer vision,</rh-cue>
<rh-cue start="01:45" end="01:49">one that can detect anomalies in medical imaging or maybe on a factory floor,</rh-cue>
<rh-cue start="01:49" end="01:52">You know, those things are whizzing by on the factory line.</rh-cue>
<rh-cue start="01:52" end="01:55">They're looking at them and trying to determine if there is an error or not.</rh-cue>
<rh-cue start="01:56" voice="Burr Sutter"></rh-cue>
<rh-cue start="01:56" end="01:58">Well, how do you actually make it run on your hardware,</rh-cue>
<rh-cue start="01:58" end="02:01">your accessible technology that you have today?</rh-cue>
<rh-cue start="02:01" end="02:05">Well, there's a solution for this as an open toolkit called Open vino.</rh-cue>
<rh-cue start="02:05" end="02:07">And you might be thinking, hey, wait a minute,</rh-cue>
<rh-cue start="02:07" end="02:10">don't you need a GPU for a I inferencing a GPU</rh-cue>
<rh-cue start="02:10" end="02:12">for artificial intelligence machine learning?</rh-cue>
<rh-cue start="02:12" end="02:15">Well, not according to Ryan Loney, product manager of Open Vino Developer</rh-cue>
<rh-cue start="02:15" end="02:16">Tools at Intel.</rh-cue>
<rh-cue start="02:20" voice="Ryan Loney"></rh-cue>
<rh-cue start="02:20" end="02:20">I guess we'll</rh-cue>
<rh-cue start="02:20" end="02:23">start with trying to maybe dispel the myths, right?</rh-cue>
<rh-cue start="02:23" end="02:27">I think that CPUs are widely used for inference today.</rh-cue>
<rh-cue start="02:27" end="02:32">So and if we look at the data center segment, you know, about 70% of the A.I.</rh-cue>
<rh-cue start="02:32" end="02:36">inference is happening on Intel Xeon on our data center CPUs.</rh-cue>
<rh-cue start="02:36" end="02:40">And so you don't needed a GPU, especially for running inference.</rh-cue>
<rh-cue start="02:40" end="02:43">And that's part of the value of open vino, is that we're you know,</rh-cue>
<rh-cue start="02:43" end="02:47">we're taking models that may have been trained on a GPU</rh-cue>
<rh-cue start="02:47" end="02:50">using deep learning frameworks like PyTorch or TensorFlow</rh-cue>
<rh-cue start="02:51" end="02:54">and then optimizing them to run on Intel hardware.</rh-cue>
<rh-cue start="02:57" voice="Burr Sutter"></rh-cue>
<rh-cue start="02:56" end="03:00">Ryan joined me to discuss AI/ML and the enterprise</rh-cue>
<rh-cue start="03:00" end="03:03">across various industries and exploring numerous use cases.</rh-cue>
<rh-cue start="03:05" end="03:08">Let's talk a little bit about the origin story behind Open Vino.</rh-cue>
<rh-cue start="03:08" end="03:10">Tell us more about it and how it came to be</rh-cue>
<rh-cue start="03:10" end="03:13">and why it came out of Intel.</rh-cue>
<rh-cue start="03:12" voice="Ryan Loney"></rh-cue>
<rh-cue start="03:12" end="03:16">Definitely. So we had the first release of Open Vino</rh-cue>
<rh-cue start="03:16" end="03:20">was back in 2018, so still relatively new.</rh-cue>
<rh-cue start="03:20" end="03:25">And at that time we were focused on computer vision and pretty tightly coupled</rh-cue>
<rh-cue start="03:25" end="03:31">with open CV, which is another open source library with origins at Intel.</rh-cue>
<rh-cue start="03:31" end="03:31">You know, it</rh-cue>
<rh-cue start="03:31" end="03:36">had its first release back in 1999, so it's been around a little bit longer.</rh-cue>
<rh-cue start="03:36" end="03:40">And many of the software engineers and architects at Intel</rh-cue>
<rh-cue start="03:40" end="03:45">that were involved with and contributing to open CV are working on open Vino.</rh-cue>
<rh-cue start="03:45" end="03:49">So you can think of open vino as complementary software to open CV.</rh-cue>
<rh-cue start="03:50" end="03:53">And we're providing like an engine for executing inference</rh-cue>
<rh-cue start="03:53" end="03:57">as part of a computer vision pipeline, or at least that's how we started.</rh-cue>
<rh-cue start="03:58" voice="Ryan Loney"></rh-cue>
<rh-cue start="03:58" end="04:01">But since 2018, we've we've started to move beyond</rh-cue>
<rh-cue start="04:01" end="04:02">just computer vision inference.</rh-cue>
<rh-cue start="04:02" end="04:05">So when I say computer vision inference, I mean like image</rh-cue>
<rh-cue start="04:05" end="04:08">classification, object detection, segmentation.</rh-cue>
<rh-cue start="04:09" end="04:12">And now we're moving into natural language processing, things</rh-cue>
<rh-cue start="04:12" end="04:16">like speech synthesis, speech recognition, knowledge, graphs,</rh-cue>
<rh-cue start="04:17" end="04:21">time series forecasting, and other use cases that don't involve</rh-cue>
<rh-cue start="04:21" end="04:24">computer vision and don't involve inference on pixels.</rh-cue>
<rh-cue start="04:25" end="04:28">Our latest release, the 20 22.1 that came out earlier this year,</rh-cue>
<rh-cue start="04:29" end="04:32">there was a most significant update that we've had to open vino</rh-cue>
<rh-cue start="04:32" end="04:36">since we started in 2018, and the major focus of that release</rh-cue>
<rh-cue start="04:36" end="04:40">was optimizing for use cases that go beyond computer vision.</rh-cue>
<rh-cue start="04:41" voice="Burr Sutter"></rh-cue>
<rh-cue start="04:41" end="04:44">And I like that concept that you just mentioned right there, computer vision.</rh-cue>
<rh-cue start="04:44" end="04:47">And you said that you extended those use cases and went beyond that.</rh-cue>
<rh-cue start="04:47" end="04:50">So could you give us more concrete examples of computer vision?</rh-cue>
<rh-cue start="04:50" voice="Ryan Loney"></rh-cue>
<rh-cue start="04:50" end="04:50">Yeah, sure.</rh-cue>
<rh-cue start="04:50" end="04:55">So when you think about manufacturing quality control in factories, everything</rh-cue>
<rh-cue start="04:55" end="05:01">from ARC welding, defect detection to inspecting BMW cars on assembly lines,</rh-cue>
<rh-cue start="05:02" end="05:05">they're using cameras or sensors to collect data.</rh-cue>
<rh-cue start="05:05" end="05:11">And usually it's cameras collecting images like RGV images that you and I can see.</rh-cue>
<rh-cue start="05:11" end="05:14">And looks like something taken from a camera or video camera,</rh-cue>
<rh-cue start="05:15" end="05:19">but also things like infrared or computerized tomography</rh-cue>
<rh-cue start="05:19" end="05:24">scans used in health care, X-ray, different types of images where we can</rh-cue>
<rh-cue start="05:25" end="05:28">draw bounding boxes around regions of interest</rh-cue>
<rh-cue start="05:29" end="05:32">and say, you know, this is a defect or this is not a defect.</rh-cue>
<rh-cue start="05:32" end="05:37">And also, is this worker wearing a safety hat or did they forget to put it on?</rh-cue>
<rh-cue start="05:37" end="05:41">And so you can take this and integrate it into a pipeline</rh-cue>
<rh-cue start="05:41" end="05:44">where you're triggering an alert if somebody forgets</rh-cue>
<rh-cue start="05:44" end="05:49">to wear their safety mask or if there's a defect in a product</rh-cue>
<rh-cue start="05:49" end="05:53">on an assembly line, you can just use cameras and open</rh-cue>
<rh-cue start="05:53" end="05:58">vino and open CV running these on Intel hardware and help to analyze.</rh-cue>
<rh-cue start="05:58" voice="Ryan Loney"></rh-cue>
<rh-cue start="05:58" end="06:01">And that's what a lot of the partners that we work with are doing.</rh-cue>
<rh-cue start="06:01" end="06:03">So these independent software vendors</rh-cue>
<rh-cue start="06:03" end="06:06">and there's other use cases for things like retail.</rh-cue>
<rh-cue start="06:06" end="06:10">You think about going to a store and using an automated checkout system.</rh-cue>
<rh-cue start="06:11" end="06:13">You know, sometimes people use those automated checkouts</rh-cue>
<rh-cue start="06:13" end="06:17">and they they slide a few extra items into their bag that they don't scan.</rh-cue>
<rh-cue start="06:17" end="06:21">And it's a huge loss for the retail outlets</rh-cue>
<rh-cue start="06:21" end="06:25">that are providing this way to check out real time shelf monitoring.</rh-cue>
<rh-cue start="06:25" end="06:29">We have this bear on one of our is fees that helps keep store shelves</rh-cue>
<rh-cue start="06:29" end="06:33">stocked by just analyzing the cameras in the stores, detecting</rh-cue>
<rh-cue start="06:33" end="06:37">when objects are missing from the shelves so that they can be restocked.</rh-cue>
<rh-cue start="06:37" end="06:41">We have Vistry, another ISP that works with quick service restaurants.</rh-cue>
<rh-cue start="06:41" end="06:44">So when you think about automating the process of</rh-cue>
<rh-cue start="06:44" end="06:48">when do I drop the fries into the fryer so that they're warm</rh-cue>
<rh-cue start="06:48" end="06:50">when the car gets to the drive thru window,</rh-cue>
<rh-cue start="06:50" end="06:54">you know, there's quite a bit of industrial health care retail examples</rh-cue>
<rh-cue start="06:54" end="06:57">that we can walk through and we should dig into some more of those.</rh-cue>
<rh-cue start="06:57" voice="Burr Sutter"></rh-cue>
<rh-cue start="06:57" end="06:59">But I got to tell you, I have I have a personal experience</rh-cue>
<rh-cue start="06:59" end="06:59">in this category</rh-cue>
<rh-cue start="06:59" end="07:01">that I want to share with, and you can tell me how</rh-cue>
<rh-cue start="07:01" end="07:03">how silly you might think at this point in time.</rh-cue>
<rh-cue start="07:03" end="07:04">It is.</rh-cue>
<rh-cue start="07:04" end="07:08">We actually built an AI keynote demonstration for the Red Hat big stage</rh-cue>
<rh-cue start="07:08" end="07:12">back in 2015, and I really want to illustrate the concept of asset tracking.</rh-cue>
<rh-cue start="07:12" end="07:15">So we actually gave everybody in the conference a little Bluetooth token,</rh-cue>
<rh-cue start="07:16" end="07:19">but a little battery, a little watch battery and a little Bluetooth emitter.</rh-cue>
<rh-cue start="07:19" end="07:22">And we basically tracked those things around the conference.</rh-cue>
<rh-cue start="07:22" end="07:24">We basically put a Raspberry Pi in each of the meeting rooms</rh-cue>
<rh-cue start="07:24" end="07:26">and up in the lunch room, and you could see how the tokens</rh-cue>
<rh-cue start="07:26" end="07:30">moved from room to room to room as a relatively simple application.</rh-cue>
<rh-cue start="07:30" voice="Burr Sutter"></rh-cue>
<rh-cue start="07:30" end="07:32">But it occurred to me after we figured out,</rh-cue>
<rh-cue start="07:32" end="07:34">okay, how to do that with Bluetooth and triangulating</rh-cue>
<rh-cue start="07:34" end="07:39">Bluetooth signals by looking at relative signal strength from one radio to another</rh-cue>
<rh-cue start="07:39" end="07:42">and putting that through an Apache Spark application at the time,</rh-cue>
<rh-cue start="07:42" end="07:45">we then realized, you know what, this is easier done with cameras</rh-cue>
<rh-cue start="07:45" end="07:49">and just simply looking at a camera and having some form of animal</rh-cue>
<rh-cue start="07:49" end="07:51">or machine learning model that would say, Oh,</rh-cue>
<rh-cue start="07:51" end="07:53">there are people here now are there are no people here now.</rh-cue>
<rh-cue start="07:53" end="07:55">What do you think about that?</rh-cue>
<rh-cue start="07:55" voice="Ryan Loney"></rh-cue>
<rh-cue start="07:55" end="07:59">Yeah, I mean, what you just described is sort of exactly that the product</rh-cue>
<rh-cue start="07:59" end="08:02">that either one of our partners is offering,</rh-cue>
<rh-cue start="08:02" end="08:04">you know, that they're doing it with computer vision and cameras.</rh-cue>
<rh-cue start="08:04" end="08:08">So when partner tries to help retail stores</rh-cue>
<rh-cue start="08:08" end="08:12">analyze the foot traffic and understand with Heatmaps,</rh-cue>
<rh-cue start="08:12" end="08:16">where people are spending the most time in stores, how many people are coming</rh-cue>
<rh-cue start="08:16" end="08:19">in, what size groups are coming into the store,</rh-cue>
<rh-cue start="08:19" end="08:23">you know, and trying to help understand if there was a successful transaction</rh-cue>
<rh-cue start="08:23" end="08:27">from the people who entered the store and left the store so that you can,</rh-cue>
<rh-cue start="08:27" end="08:30">you know, to help with the, you know, retail analytics</rh-cue>
<rh-cue start="08:30" end="08:33">and marketing sales and positioning of products.</rh-cue>
<rh-cue start="08:34" end="08:37">And so they're doing that in a way that also protects privacy.</rh-cue>
<rh-cue start="08:37" end="08:38">And that's something that's really important.</rh-cue>
<rh-cue start="08:38" end="08:41">So when you talked about those Bluetooth beacons, probably,</rh-cue>
<rh-cue start="08:41" end="08:44">
you know, if everyone who walked into a grocery store was asked
</rh-cue>
<rh-cue start="08:44" end="08:49">
to put a tracking device in their cart or on their person and say, you know,
</rh-cue>
<rh-cue start="08:49" end="08:50">
you're going
</rh-cue>
<rh-cue start="08:50" end="08:53">
to be tracked around the store, they probably wouldn't want to do that.
</rh-cue>
<rh-cue start="08:53" end="08:56">
The way that you can do this with cameras is you can,
</rh-cue>
<rh-cue start="08:53" voice="Ryan Loney"></rh-cue>
<rh-cue start="08:56" end="09:01">
you know, detect people as they enter and, you know, remove their face.
</rh-cue>
<rh-cue start="09:01" end="09:01">
Right.
</rh-cue>
<rh-cue start="09:01" end="09:05">
So you can ignore any biometric information
</rh-cue>
<rh-cue start="09:05" end="09:08">
and and just track the person based on pixels
</rh-cue>
<rh-cue start="09:09" end="09:12">
that are present in the detected region of interest.
</rh-cue>
<rh-cue start="09:12" end="09:15">
So they're able to analyze, say, a family walks in the door
</rh-cue>
<rh-cue start="09:16" end="09:20">
and they can group those people together with object detection
</rh-cue>
<rh-cue start="09:20" end="09:23">
and then they can track their movement throughout the store
</rh-cue>
<rh-cue start="09:23" end="09:26">
without keeping track of their face or any biometric
</rh-cue>
<rh-cue start="09:26" end="09:30">
or any personal identifiable information to avoid things like bias
</rh-cue>
<rh-cue start="09:30" end="09:35">
and to make sure that they're protecting the privacy of the shoppers in the store
</rh-cue>
<rh-cue start="09:35" end="09:39">
while still getting that really useful marketing analytics data rate
</rh-cue>
<rh-cue start="09:39" end="09:42">
so that they can make better decisions about where to place their products.
</rh-cue>
<rh-cue start="09:42" end="09:45">
So that's one really good example of how
</rh-cue>
<rh-cue start="09:45" end="09:48">
computer vision AI with open vino is being used today.
</rh-cue>
<rh-cue start="09:48" voice="Burr Sutter"></rh-cue>
<rh-cue start="09:48" end="09:51">
And that is a great example because you're definitely spot on.
</rh-cue>
<rh-cue start="09:51" end="09:53">
It is invasive when you hand someone to Bluetooth devices,
</rh-cue>
<rh-cue start="09:53" end="09:56">
say, please keep this with you as you go throughout our our store
</rh-cue>
<rh-cue start="09:56" end="09:59">
or our mall or throughout our hospital, wherever you might be.
</rh-cue>
<rh-cue start="09:59" end="10:01">
Now, you mentioned another example earlier
</rh-cue>
<rh-cue start="10:01" end="10:03">
in the conversation which was related to like worker safety.
</rh-cue>
<rh-cue start="10:03" end="10:05">
Are they wearing a helmet?
</rh-cue>
<rh-cue start="10:05" end="10:08">
I want to talk more about that concept in a real industrial setting,
</rh-cue>
<rh-cue start="10:08" end="10:11">
a manufacturing setting where there might be a factory floor
</rh-cue>
<rh-cue start="10:11" end="10:13">
and there are certain requirements, or better yet, there's like a
</rh-cue>
<rh-cue start="10:13" end="10:16">
a quality assurance requirement, let's say, when it comes to looking
</rh-cue>
<rh-cue start="10:16" end="10:20">
at a factory line, I run to that use case often what some of our customers.
</rh-cue>
<rh-cue start="10:20" end="10:22">
Can you talk more about those kinds of use cases? Yeah.
</rh-cue>
<rh-cue start="10:22" voice="Ryan Loney"></rh-cue>
<rh-cue start="10:22" end="10:27">
So one of our partners, Robuchon and we you know, published a case study
</rh-cue>
<rh-cue start="10:27" end="10:31">
I think last year where they're working with BMW at one of their factories
</rh-cue>
<rh-cue start="10:32" end="10:35">
and they do quality control inspection, but they're also doing
</rh-cue>
<rh-cue start="10:35" end="10:38">
things related to worker safety and analyzing.
</rh-cue>
<rh-cue start="10:38" end="10:40">
You know, I used the safety had example.
</rh-cue>
<rh-cue start="10:40" end="10:45">
There's a number of of our ISP's and partners who have similar use cases.
</rh-cue>
<rh-cue start="10:45" end="10:48">
And it comes down to there's a few reasons
</rh-cue>
<rh-cue start="10:48" end="10:51">
that are motivating this and some are related to like insurance, right?
</rh-cue>
<rh-cue start="10:51" end="10:53">
It's important to make sure that
</rh-cue>
<rh-cue start="10:53" end="10:56">
if you want to have your factory insured and that your workers
</rh-cue>
<rh-cue start="10:56" end="10:58">
are protecting themselves and wearing the gear.
</rh-cue>
<rh-cue start="10:58" end="11:00">
Regulatory compliance. Right.
</rh-cue>
<rh-cue start="11:00" end="11:05">
You're you're being asked to properly protect from exposure to chemicals or,
</rh-cue>
<rh-cue start="11:05" end="11:09">
you know, potentially having something fall and and hit someone on the head.
</rh-cue>
<rh-cue start="11:09" end="11:13">
So wearing a safety vest, wearing goggles, wearing a helmet,
</rh-cue>
<rh-cue start="11:14" end="11:17">
these are things that you need to do inside the factory.
</rh-cue>
<rh-cue start="11:17" end="11:21">
And you can really easily automate and detect and sometimes without bias.
</rh-cue>
<rh-cue start="11:21" voice="Ryan Loney"></rh-cue>
<rh-cue start="11:21" end="11:26">
I think that's one of the interesting things about the robots on BMW example
</rh-cue>
<rh-cue start="11:26" end="11:31">
is that they were also blurring sort of blocking out and so drawing a box
</rh-cue>
<rh-cue start="11:31" end="11:35">
to cover the face of the workers in the factory
</rh-cue>
<rh-cue start="11:35" end="11:38">
so that somebody who was analyzing the video footage
</rh-cue>
<rh-cue start="11:38" end="11:43">
and getting the alerts saying that, hey, you know, Bay 21 has a worker
</rh-cue>
<rh-cue start="11:43" end="11:47">
without a hat on, that it's not sending their face
</rh-cue>
<rh-cue start="11:47" end="11:50">
and in the alert and potentially, you know, invading
</rh-cue>
<rh-cue start="11:50" end="11:54">
or going against privacy laws or just the ethics of the company.
</rh-cue>
<rh-cue start="11:54" end="11:54">
Right.
</rh-cue>
<rh-cue start="11:54" end="11:58">
They don't want to introduce bias or have people targeted because
</rh-cue>
<rh-cue start="11:58" end="12:02">
it's much better to to have it be, you know, blur the face
</rh-cue>
<rh-cue start="12:02" end="12:06">
and alert and have somebody take care of it on the floor.
</rh-cue>
<rh-cue start="12:06" end="12:09">
And then if you ever need to audit that information later,
</rh-cue>
<rh-cue start="12:09" end="12:12">
they have a way to do it where people who need to be able to see
</rh-cue>
<rh-cue start="12:12" end="12:17">
who the employee was and look up their personal information, they can do that.
</rh-cue>
<rh-cue start="12:17" voice="Ryan Loney"></rh-cue>
<rh-cue start="12:17" end="12:20">
But then just for the purposes of maintaining safety,
</rh-cue>
<rh-cue start="12:20" end="12:21">
they don't need to have access
</rh-cue>
<rh-cue start="12:21" end="12:24">
to that personal information or biometric information,
</rh-cue>
<rh-cue start="12:25" end="12:28">
because that's one thing that when you hear about computer vision
</rh-cue>
<rh-cue start="12:28" end="12:31">
or object person tracking, object detection,
</rh-cue>
<rh-cue start="12:32" end="12:36">
there's a lot of concern, and rightfully so, about privacy
</rh-cue>
<rh-cue start="12:36" end="12:40">
being invaded and about tracking information, face ID,
</rh-cue>
<rh-cue start="12:41" end="12:45">
identifying people who may have committed crimes through video footage.
</rh-cue>
<rh-cue start="12:45" end="12:48">
And that's just not something that a lot of companies want to
</rh-cue>
<rh-cue start="12:49" end="12:51">
you know, they want to protect privacy
</rh-cue>
<rh-cue start="12:51" end="12:52">
and they don't they don't want to be in a situation
</rh-cue>
<rh-cue start="12:52" end="12:55">
where they might be violating someone's rights.
</rh-cue>
<rh-cue start="12:56" voice="Burr Sutter"></rh-cue>
<rh-cue start="12:56" end="12:58">
Well, privacy is certainly opening up Pandora's box.
</rh-cue>
<rh-cue start="12:58" end="13:00">
There's a lot to be explored in that area,
</rh-cue>
<rh-cue start="13:00" end="13:02">
especially in a digital world that we now live in.
</rh-cue>
<rh-cue start="13:02" end="13:05">
But for now, let's move on and explore different area.
</rh-cue>
<rh-cue start="13:05" end="13:08">
I'm interested in how machines and computers offer advantages,
</rh-cue>
<rh-cue start="13:08" end="13:12">
specifically in certain use cases like a quality control scenario.
</rh-cue>
<rh-cue start="13:12" end="13:15">
I asked Ryan to explain how AML and specifically machines
</rh-cue>
<rh-cue start="13:15" end="13:18">
computers can augment that capability.
</rh-cue>
<rh-cue start="13:19" voice="Ryan Loney"></rh-cue>
<rh-cue start="13:19" end="13:22">
I can give a specific example where we have a partner
</rh-cue>
<rh-cue start="13:22" end="13:25">
that's there doing defect detection with
</rh-cue>
<rh-cue start="13:25" end="13:28">
and looking for anomalies in batteries.
</rh-cue>
<rh-cue start="13:28" end="13:31">
So, you know, sure, you've heard there's a lot of interest right now
</rh-cue>
<rh-cue start="13:31" end="13:34">
in electric vehicles, a lot of batteries being produced.
</rh-cue>
<rh-cue start="13:34" end="13:36">
And so if you go into one of these factories,
</rh-cue>
<rh-cue start="13:36" end="13:40">
they have images that they collect of every battery that's going through this
</rh-cue>
<rh-cue start="13:40" end="13:44">
assembly line and through these images, people
</rh-cue>
<rh-cue start="13:44" end="13:47">
can look and see and visually inspect with their eyes and say,
</rh-cue>
<rh-cue start="13:48" end="13:50">
this battery has a defect, send it back.
</rh-cue>
<rh-cue start="13:50" end="13:53">
And that's one step in the quality control process.
</rh-cue>
<rh-cue start="13:53" end="13:58">
And there's other steps, I'm sure, like running diagnostic tests and, you know,
</rh-cue>
<rh-cue start="13:58" end="14:02">
measuring voltage and doing other types of non-visual inspection.
</rh-cue>
<rh-cue start="14:02" end="14:06">
But for the visual inspection piece where you can really easily identify
</rh-cue>
<rh-cue start="14:06" end="14:10">
some problems, it's much more efficient to introduce computer vision.
</rh-cue>
<rh-cue start="14:11" end="14:14">
And so that's where we have this new library that we've introduced
</rh-cue>
<rh-cue start="14:14" end="14:17">
called Anomali, that's open vino.
</rh-cue>
<rh-cue start="14:17" voice="Ryan Loney"></rh-cue>
<rh-cue start="14:17" end="14:20">
While we're focused on inference, you know, we're also thinking
</rh-cue>
<rh-cue start="14:20" end="14:25">
about the pipeline or the funnel that gets these models to open vino.
</rh-cue>
<rh-cue start="14:25" end="14:28">
And so we've we've invested in this anomaly segmentation,
</rh-cue>
<rh-cue start="14:28" end="14:32">
anomaly detection library and that we've recently open source
</rh-cue>
<rh-cue start="14:32" end="14:35">
and there's a great research paper about it about Anomali.
</rh-cue>
<rh-cue start="14:36" end="14:39">
But the idea is you can take just a few images
</rh-cue>
<rh-cue start="14:39" end="14:43">
and train a model and start detecting these defects.
</rh-cue>
<rh-cue start="14:43" end="14:46">
And so for this battery example, that's a more advanced example.
</rh-cue>
<rh-cue start="14:46" end="14:52">
But to make it simpler, you know, take some bolts and, you know, take ten bolts.
</rh-cue>
<rh-cue start="14:52" end="14:55">
You have one that has a scratch on it or one that is chipped
</rh-cue>
<rh-cue start="14:56" end="14:58">
or has some damage to it.
</rh-cue>
<rh-cue start="14:58" end="15:00">
And you can easily get started in training
</rh-cue>
<rh-cue start="15:00" end="15:03">
to recognize the bolts that do not have an anomaly.
</rh-cue>
<rh-cue start="15:04" end="15:06">
And the ones that do, which is a small data set
</rh-cue>
<rh-cue start="15:06" end="15:10">
and I think that's really one of the most important things today.
</rh-cue>
<rh-cue start="15:11" voice="Ryan Loney"></rh-cue>
<rh-cue start="15:11" end="15:14">
Challenges is one is access to data, but the other is
</rh-cue>
<rh-cue start="15:14" end="15:17">
is needing a massive amount of data to do something meaningful.
</rh-cue>
<rh-cue start="15:18" end="15:22">
And so we're starting to try to change that dynamic with Anomali.
</rh-cue>
<rh-cue start="15:22" end="15:27">
So you may not need 100,000 images, you may need 100 images,
</rh-cue>
<rh-cue start="15:27" end="15:33">
and you can start detecting anomalies in everything from batteries to bolts to,
</rh-cue>
<rh-cue start="15:33" end="15:37">
you know, maybe even the wood varnish use case that you mentioned.
</rh-cue>
<rh-cue start="15:37" voice="Burr Sutter"></rh-cue>
<rh-cue start="15:37" end="15:40">
That is very key point because often in that data scientist
</rh-cue>
<rh-cue start="15:40" end="15:43">
process, that data engineer and data scientist process, right.
</rh-cue>
<rh-cue start="15:43" end="15:44">
The one key thing is can you gather
</rh-cue>
<rh-cue start="15:44" end="15:47">
the data that you need for the input for the model training?
</rh-cue>
<rh-cue start="15:47" end="15:49">
And we've often sat at least people I've worked
</rh-cue>
<rh-cue start="15:49" end="15:52">
with over the last couple of years, you know, you need a lot of data.
</rh-cue>
<rh-cue start="15:52" end="15:55">
You need tens of thousands of correct images
</rh-cue>
<rh-cue start="15:55" end="15:58">
so we can sort out the difference between dogs versus cats, let's say,
</rh-cue>
<rh-cue start="15:58" end="16:01">
or you need dozens and dozens of situations
</rh-cue>
<rh-cue start="16:01" end="16:03">
where if it's a natural language processing scenario,
</rh-cue>
<rh-cue start="16:03" end="16:06">
you know, a good customer interaction, a good customer conversation,
</rh-cue>
<rh-cue start="16:06" end="16:07">
and in this case,
</rh-cue>
<rh-cue start="16:07" end="16:11">
it sounds like what you're saying is show us just the bad things, right?
</rh-cue>
<rh-cue start="16:11" end="16:14">
Fewer images, fewer incorrect things,
</rh-cue>
<rh-cue start="16:14" end="16:17">
and then let us look for those kind of anomalies.
</rh-cue>
<rh-cue start="16:18" end="16:20">
Can tell us more about that because that is very interesting.
</rh-cue>
<rh-cue start="16:20" end="16:23">
The concept that I can use a much smaller dataset as my input
</rh-cue>
<rh-cue start="16:23" end="16:26">
as opposed to gathering terabytes of data in some cases
</rh-cue>
<rh-cue start="16:26" end="16:29">
to just simply get my model training underway.
</rh-cue>
<rh-cue start="16:30" voice="Ryan Loney"></rh-cue>
<rh-cue start="16:30" end="16:34">
You know, like you described, the idea is if you have some good images
</rh-cue>
<rh-cue start="16:34" end="16:37">
and then you have some of the the known defects
</rh-cue>
<rh-cue start="16:38" end="16:41">
and you can just label here's a set of good images
</rh-cue>
<rh-cue start="16:41" end="16:44">
and here's a few of the defects and you can right away
</rh-cue>
<rh-cue start="16:44" end="16:48">
start detecting those specific defects that you've identified.
</rh-cue>
<rh-cue start="16:48" end="16:49">
And then also, you know, be able to
</rh-cue>
<rh-cue start="16:50" end="16:53">
determine when it doesn't match
</rh-cue>
<rh-cue start="16:53" end="16:57">
the expected appearance of a non defective item.
</rh-cue>
<rh-cue start="16:57" end="17:00">
So if I have the undamaged screw and then I introduce
</rh-cue>
<rh-cue start="17:00" end="17:03">
one with some new anomaly that's never been seen before,
</rh-cue>
<rh-cue start="17:04" end="17:07">
I can say, you know, this one is not a valid screw.
</rh-cue>
<rh-cue start="17:07" end="17:11">
And so that's sort of the the approach that we're taking.
</rh-cue>
<rh-cue start="17:11" end="17:15">
And it's really important because so often you need to have
</rh-cue>
<rh-cue start="17:15" end="17:19">
subject matter experts often like if you think the take the battery example,
</rh-cue>
<rh-cue start="17:20" end="17:23">
there's these workers who are on the floor
</rh-cue>
<rh-cue start="17:23" end="17:27">
in a factory and they're the ones who know best when they look at these images,
</rh-cue>
<rh-cue start="17:28" end="17:31">
which one's going to have an issue, which one's defective?
</rh-cue>
<rh-cue start="17:31" voice="Ryan Loney"></rh-cue>
<rh-cue start="17:31" end="17:34">
And then they also need to take that subject matter, expertise
</rh-cue>
<rh-cue start="17:35" end="17:38">
and then use it to annotate data sets.
</rh-cue>
<rh-cue start="17:38" end="17:39">
And when you have these, you know,
</rh-cue>
<rh-cue start="17:39" end="17:43">
tens of thousands of images you need to annotate, it's asking those people
</rh-cue>
<rh-cue start="17:43" end="17:47">
to stop working on the factory floor so they can come annotate some images.
</rh-cue>
<rh-cue start="17:47" end="17:49">
That's a tough business call to make, right?
</rh-cue>
<rh-cue start="17:49" end="17:53">
But if you only need them to annotate a handful of images, it's a much easier
</rh-cue>
<rh-cue start="17:53" end="17:56">
ask to get the ball rolling and demonstrate value.
</rh-cue>
<rh-cue start="17:56" end="17:59">
And maybe over time you will want to annotate more
</rh-cue>
<rh-cue start="17:59" end="18:03">
and more images because you'll get even better accuracy in the model.
</rh-cue>
<rh-cue start="18:03" end="18:07">
Even better, even if it's just small incremental improvements.
</rh-cue>
<rh-cue start="18:08" end="18:11">
You know, that's something that if it generates value for the business,
</rh-cue>
<rh-cue start="18:11" end="18:14">
it's something the business will invest in over time.
</rh-cue>
<rh-cue start="18:14" end="18:17">
But you have to convince the decision makers that it's worth
</rh-cue>
<rh-cue start="18:17" end="18:22">
the time of these subject matter experts to stop what they're doing
</rh-cue>
<rh-cue start="18:22" end="18:26">
and go and label some images of the things that they're working on in the factory.
</rh-cue>
<rh-cue start="18:26" voice="Burr Sutter"></rh-cue>
<rh-cue start="18:26" end="18:30">
And that labeling process can be very labor intensive of the annotations,
</rh-cue>
<rh-cue start="18:30" end="18:33">
basically saying what is correct, what's wrong, what is this, what is that?
</rh-cue>
<rh-cue start="18:33" end="18:36">
And therefore, if we can minimize that time frame to get the value quicker,
</rh-cue>
<rh-cue start="18:36" end="18:40">
then there's something that's useful for the business, useful for the organization
</rh-cue>
<rh-cue start="18:40" end="18:41">
long before we necessarily good.
</rh-cue>
<rh-cue start="18:41" end="18:43">
There are huge model training based,
</rh-cue>
<rh-cue start="18:49" voice="Burr Sutter"></rh-cue>
<rh-cue start="18:49" end="18:52">
so we talk about labeling and how that is labor intensive activity.
</rh-cue>
<rh-cue start="18:52" end="18:54">
But I love the idea of helping the human
</rh-cue>
<rh-cue start="18:54" end="18:57">
and helping the human models specifically not get bored.
</rh-cue>
<rh-cue start="18:57" end="19:01">
Basically, if the human is eyeballing a bunch of widgets flying by over time,
</rh-cue>
<rh-cue start="19:01" end="19:03">
they make mistakes, they get bored
</rh-cue>
<rh-cue start="19:03" end="19:06">
and they don't pay as close attention as they should.
</rh-cue>
<rh-cue start="19:07" end="19:10">
That's why the concept of Amazon specifically computer vision, augmenting
</rh-cue>
<rh-cue start="19:10" end="19:14">
that capability and really helping the human identify anomalies faster,
</rh-cue>
<rh-cue start="19:14" end="19:17">
more quickly, maybe with greater accuracy could be a big win.
</rh-cue>
<rh-cue start="19:18" end="19:21">
We focused on manufacturing, but let's actually go into health care
</rh-cue>
<rh-cue start="19:21" end="19:24">
and learn how these tools can be used in that sector and that industry.
</rh-cue>
<rh-cue start="19:24" end="19:28">
Ryan talked to me about how Open Windows runtime can be incorporated into medical
</rh-cue>
<rh-cue start="19:28" end="19:32">
imaging equipment with intel processors and better than c.T.
</rh-cue>
<rh-cue start="19:32" end="19:34">
MRI and ultrasound machines.
</rh-cue>
<rh-cue start="19:34" end="19:37">
Well, these inferences, this AML workload can be operating
</rh-cue>
<rh-cue start="19:37" end="19:41">
and executing right there in the same physical room as the patient.
</rh-cue>
<rh-cue start="19:44" voice="Ryan Loney"></rh-cue>
<rh-cue start="19:44" end="19:46">
We did a presentation when she last year.
</rh-cue>
<rh-cue start="19:46" end="19:47">
I think they said
</rh-cue>
<rh-cue start="19:47" end="19:50">
there's at least 80 countries that have their X-ray machines deployed
</rh-cue>
<rh-cue start="19:51" end="19:56">
and they're doing things like helping doctors place breathing tubes in patients.
</rh-cue>
<rh-cue start="19:56" end="20:01">
So during COVID, during the pandemic, that was a really important tool
</rh-cue>
<rh-cue start="20:01" end="20:05">
to help with nurses and doctors who were intubating patients
</rh-cue>
<rh-cue start="20:05" end="20:09">
sometimes like in a parking lot or a hallway of the hospital.
</rh-cue>
<rh-cue start="20:09" end="20:14">
And, you know, when they had a statistic that you said, I think one out of four
</rh-cue>
<rh-cue start="20:14" end="20:17">
breathing tubes gets placed incorrectly
</rh-cue>
<rh-cue start="20:17" end="20:19">
when you're doing it outside the operating room,
</rh-cue>
<rh-cue start="20:19" end="20:22">
because when you're in an operating room, it's much more controlled
</rh-cue>
<rh-cue start="20:22" end="20:24">
and there's someone who's an expert at placing the tubes.
</rh-cue>
<rh-cue start="20:24" end="20:28">
It's something you have more of a controlled environment
</rh-cue>
<rh-cue start="20:28" end="20:31">
than when you're out in a parking lot, in a tent.
</rh-cue>
<rh-cue start="20:31" end="20:34">
You know, when the hospital's completely full and you're triaging patients
</rh-cue>
<rh-cue start="20:34" end="20:37">
with COVID, that's when they're more likely to make mistakes.
</rh-cue>
<rh-cue start="20:37" end="20:40">
And so they had this endotracheal tube placement
</rh-cue>
<rh-cue start="20:42" end="20:43">
model that they trained,
</rh-cue>
<rh-cue start="20:43" end="20:47">
and it helped to use an x ray and give an alert and say, hey,
</rh-cue>
<rh-cue start="20:47" end="20:50">
this tube is placed wrong, pull it out and do it again.
</rh-cue>
<rh-cue start="20:50" end="20:53">
And so things like that help doctors so that they can avoid mistakes.
</rh-cue>
<rh-cue start="20:54" end="20:57">
And, you know, having a breathing tube placed incorrectly
</rh-cue>
<rh-cue start="20:57" end="21:01">
can cause collapsed lung and a number of other unwanted side effects.
</rh-cue>
<rh-cue start="21:01" end="21:03">
So it's really important to do it correctly.
</rh-cue>
<rh-cue start="21:03" end="21:06">
Another example is Samsung Medicine.
</rh-cue>
<rh-cue start="21:06" end="21:10">
They actually are doing estimating fetal angle of progression.
</rh-cue>
<rh-cue start="21:10" end="21:13">
So this is analyzing ultrasound
</rh-cue>
<rh-cue start="21:14" end="21:18">
of pregnant women with that, being able to to help take measurements
</rh-cue>
<rh-cue start="21:18" end="21:22">
that are usually hard to calculate that can be done in an automated way.
</rh-cue>
<rh-cue start="21:22" end="21:26">
They're already taking the ultrasound scan and now they're executing this model.
</rh-cue>
<rh-cue start="21:26" end="21:31">
They can take some of these measurements to help the doctor avoid potentially more
</rh-cue>
<rh-cue start="21:31" end="21:34">
intrusive alternative methods so the patient wins.
</rh-cue>
<rh-cue start="21:35" end="21:36">
It makes their life better.
</rh-cue>
<rh-cue start="21:36" end="21:39">
And the doctors is getting help from this A.I.
</rh-cue>
<rh-cue start="21:39" end="21:40">
model.
</rh-cue>
<rh-cue start="21:40" end="21:42">
And those are, you know, just a few examples.
</rh-cue>
<rh-cue start="21:42" voice="Burr Sutter"></rh-cue>
<rh-cue start="21:42" end="21:45">
Those are some amazing examples when it comes to all these things.
</rh-cue>
<rh-cue start="21:45" end="21:49">
We're talking like CT scans, right, and x rays, other examples of computer vision.
</rh-cue>
<rh-cue start="21:49" end="21:52">
One thing that's kind of interesting in the space, I think
</rh-cue>
<rh-cue start="21:52" end="21:56">
whenever I get a chance to work on, let's say an object traction model
</rh-cue>
<rh-cue start="21:56" end="21:58">
and one of our workshops, by the way, is actually putting that out
</rh-cue>
<rh-cue start="21:58" end="22:01">
in front of people to say, Hey, look, you can use your phone.
</rh-cue>
<rh-cue start="22:01" end="22:04">
And it basically sends the image over to our OpenShift, right,
</rh-cue>
<rh-cue start="22:04" end="22:07">
with our data science platform and then analyzes what you see.
</rh-cue>
<rh-cue start="22:08" end="22:09">
And even in my case, where I take a picture of my dog
</rh-cue>
<rh-cue start="22:09" end="22:13">
as an example, it can't really decide is it a dog or a cat?
</rh-cue>
<rh-cue start="22:13" end="22:15">
I have a very funny looking dog,
</rh-cue>
<rh-cue start="22:15" voice="Burr Sutter"></rh-cue>
<rh-cue start="22:15" end="22:18">
and so there's always a percentage outcome, you know?
</rh-cue>
<rh-cue start="22:18" end="22:21">
In other words, I think it's a dog 52%.
</rh-cue>
<rh-cue start="22:21" end="22:22">
So I want to talk about that more.
</rh-cue>
<rh-cue start="22:22" end="22:25">
What how important is it to get to 100% accuracy?
</rh-cue>
<rh-cue start="22:25" end="22:29">
How important is it to really, depending on the use case, to allow
</rh-cue>
<rh-cue start="22:29" end="22:34">
for the gray area, if you will, where it's an 80% accuracy or 70% accuracy?
</rh-cue>
<rh-cue start="22:34" end="22:36">
And where are the trade offs there associated with the application?
</rh-cue>
<rh-cue start="22:36" end="22:38">
Can you can you discuss that more?
</rh-cue>
<rh-cue start="22:38" voice="Ryan Loney"></rh-cue>
<rh-cue start="22:38" end="22:40">
Accuracy is definitely, you know, a touchy subject
</rh-cue>
<rh-cue start="22:40" end="22:43">
because how you measure it makes a huge difference.
</rh-cue>
<rh-cue start="22:43" end="22:46">
And then I think with like what you were describing with the dog example, there's
</rh-cue>
<rh-cue start="22:46" end="22:51">
sort of a top five potential classes that might may be identified.
</rh-cue>
<rh-cue start="22:51" end="22:55">
So let's say you're doing object detection and you detect a region of interest
</rh-cue>
<rh-cue start="22:55" end="22:57">
and it says 65% confidence.
</rh-cue>
<rh-cue start="22:57" end="22:58">
This is a dog.
</rh-cue>
<rh-cue start="22:58" end="23:03">
Well, the next potential label that could be maybe 50% confidence
</rh-cue>
<rh-cue start="23:03" end="23:08">
or 20% confidence might be something similar to a dog or in the case of models
</rh-cue>
<rh-cue start="23:08" end="23:11">
that have been trained on like the image net dataset
</rh-cue>
<rh-cue start="23:11" end="23:15">
or on cocoa data set, they have like actual breeds of dogs.
</rh-cue>
<rh-cue start="23:15" end="23:20">
So if I want to look at the top five labels for a dog,
</rh-cue>
<rh-cue start="23:20" end="23:24">
for my dog, for example, she's a mixed mostly Labrador retriever.
</rh-cue>
<rh-cue start="23:24" voice="Ryan Loney"></rh-cue>
<rh-cue start="23:24" end="23:29">
But I may look at the top five labels and it may say 65% confidence that she's
</rh-cue>
<rh-cue start="23:29" end="23:34">
a flat coated retriever and then confidence that she's a husky,
</rh-cue>
<rh-cue start="23:34" end="23:39">
as you know, 20% and then 5% confidence that she's a greyhound or something.
</rh-cue>
<rh-cue start="23:40" end="23:42">
Those labels, all of them are dogs.
</rh-cue>
<rh-cue start="23:42" end="23:45">
So if I'm just trying to figure out is, is this a dog,
</rh-cue>
<rh-cue start="23:45" end="23:50">
I could probably find all of the, you know, classes within the data set
</rh-cue>
<rh-cue start="23:50" end="23:53">
and say, well, these are all, you know, class ID
</rh-cue>
<rh-cue start="23:53" end="24:00">
65, 132, 92 and 158 all belong to a group of dogs.
</rh-cue>
<rh-cue start="24:00" end="24:04">
So if I wanted to just write an application to tell me if this is a dog
</rh-cue>
<rh-cue start="24:04" end="24:07">
or not, I would probably use that to determine if it's a dog.
</rh-cue>
<rh-cue start="24:08" end="24:10">
But how you measure that is accuracy.
</rh-cue>
<rh-cue start="24:10" end="24:11">
Well, that's where it gets a little bit complicated,
</rh-cue>
<rh-cue start="24:11" end="24:15">
because if you're being really strict about the definition and you're
</rh-cue>
<rh-cue start="24:15" end="24:18">
trying to validate against the data set of labeled images
</rh-cue>
<rh-cue start="24:18" end="24:22">
and I have specific dog breeds or some specific detail
</rh-cue>
<rh-cue start="24:22" end="24:25">
and it doesn't match, well, then the accuracy is going to go down.
</rh-cue>
<rh-cue start="24:25" voice="Ryan Loney"></rh-cue>
<rh-cue start="24:25" end="24:29">
That's especially important when we talk about things like compression
</rh-cue>
<rh-cue start="24:29" end="24:30">
and quantization,
</rh-cue>
<rh-cue start="24:30" end="24:34">
which, you know, historically has been difficult for to get adoption
</rh-cue>
<rh-cue start="24:34" end="24:40">
in some domains like health care, where even the hint of accuracy going down
</rh-cue>
<rh-cue start="24:40" end="24:44">
implies that we're not going to be able to help in some small case,
</rh-cue>
<rh-cue start="24:44" end="24:47">
maybe if it's even half a percent of the time
</rh-cue>
<rh-cue start="24:47" end="24:51">
we want to take that that tube is placed incorrectly or that, you know,
</rh-cue>
<rh-cue start="24:51" end="24:54">
that patient's, you know, lung has collapsed or something like that.
</rh-cue>
<rh-cue start="24:54" end="24:58">
And that's something that really prevents adoption of some of these methods
</rh-cue>
<rh-cue start="24:58" end="25:01">
that can really boost performance like quantization.
</rh-cue>
<rh-cue start="25:01" end="25:05">
But if you take that example of sort of different from the dog example
</rh-cue>
<rh-cue start="25:05" end="25:07">
and you think about like segmentation of kidneys.
</rh-cue>
<rh-cue start="25:07" end="25:11">
So if I'm doing kidney segmentation, which is, you know, taking a CT scan
</rh-cue>
<rh-cue start="25:12" end="25:14">
and then trying to pick the pixels out of that
</rh-cue>
<rh-cue start="25:14" end="25:17">
scan that belong to a kidney,
</rh-cue>
<rh-cue start="25:17" end="25:20">
how I measure accuracy may be
</rh-cue>
<rh-cue start="25:20" end="25:24">
how many of those pixels I'm able to detect and how many did I miss?
</rh-cue>
<rh-cue start="25:25" voice="Ryan Loney"></rh-cue>
<rh-cue start="25:25" end="25:29">
Missing some of the pixels is maybe not a problem, right,
</rh-cue>
<rh-cue start="25:29" end="25:33">
depending on how you built the application because you still detect the kidney
</rh-cue>
<rh-cue start="25:34" end="25:38">
and maybe you just need to apply padding around the region of interest
</rh-cue>
<rh-cue start="25:38" end="25:41">
so that you don't miss any of the the actual kidney.
</rh-cue>
<rh-cue start="25:42" end="25:45">
When you compress the model and when you quantized the model. But
</rh-cue>
<rh-cue start="25:45" end="25:50">
that requires, you know, data scientist and email engineer somebody to really
</rh-cue>
<rh-cue start="25:51" end="25:52">
they have to be
</rh-cue>
<rh-cue start="25:52" end="25:55">
able to go and apply that after the fact, after the inference
</rh-cue>
<rh-cue start="25:55" end="25:59">
happens to make sure that you're not losing critical information,
</rh-cue>
<rh-cue start="25:59" end="26:02">
because the next step from detecting the kidney may be detecting a tumor.
</rh-cue>
<rh-cue start="26:03" voice="Ryan Loney"></rh-cue>
<rh-cue start="26:03" end="26:06">
And so maybe you can use the more optimized model
</rh-cue>
<rh-cue start="26:06" end="26:11">
to detect the kidney, but then you can use a slower model to detect the tumor.
</rh-cue>
<rh-cue start="26:11" end="26:15">
But that also requires somebody to architect and make that decision
</rh-cue>
<rh-cue start="26:15" end="26:16">
or that tradeoff and say,
</rh-cue>
<rh-cue start="26:16" end="26:20">
well, I need to add padding, or I should only use the quantized model
</rh-cue>
<rh-cue start="26:20" end="26:24">
to detect the region of interest for the kidney and then use the model
</rh-cue>
<rh-cue start="26:24" end="26:27">
that takes longer to do the inference
</rh-cue>
<rh-cue start="26:27" end="26:30">
just to find the tumor, which is going to be on a smaller size.
</rh-cue>
<rh-cue start="26:30" end="26:33">
Right. The dimensions are going to be much smaller
</rh-cue>
<rh-cue start="26:33" end="26:35">
once we crop to the region of interest.
</rh-cue>
<rh-cue start="26:35" end="26:40">
But all of those details, that's maybe not easy to explain in a few sentences.
</rh-cue>
<rh-cue start="26:40" end="26:43">
And even the way I explained it is probably really confusing.
</rh-cue>
<rh-cue start="26:45" voice="Burr Sutter"></rh-cue>
<rh-cue start="26:45" end="26:46">
I do love that use case.
</rh-cue>
<rh-cue start="26:46" end="26:47">
Like you mentioned, the cropping
</rh-cue>
<rh-cue start="26:47" end="26:50">
even in one such an area that we worked on for another project,
</rh-cue>
<rh-cue start="26:50" end="26:53">
we specifically decided to pix like the image that we had taken
</rh-cue>
<rh-cue start="26:53" end="26:57">
because we knew that we could get the outcome we wanted by even
</rh-cue>
<rh-cue start="26:57" end="27:01">
just using a smaller or less having less resolution in our image.
</rh-cue>
<rh-cue start="27:01" end="27:04">
And therefore, as we transferred it from the mobile device storage device
</rh-cue>
<rh-cue start="27:04" end="27:08">
up into the cloud, we wanted that smaller image just for transfer purposes
</rh-cue>
<rh-cue start="27:08" end="27:11">
and it still we could get the accuracy we needed by a lot of testing.
</rh-cue>
<rh-cue start="27:11" voice="Burr Sutter"></rh-cue>
<rh-cue start="27:11" end="27:14">
And one thing that's interesting about that from my perspective is
</rh-cue>
<rh-cue start="27:15" end="27:18">
if you're doing image processing, sometimes it takes a while
</rh-cue>
<rh-cue start="27:18" end="27:20">
for this transaction to occur.
</rh-cue>
<rh-cue start="27:20" end="27:20">
Like I,
</rh-cue>
<rh-cue start="27:20" end="27:24">
I come from a traditional application background, you know, where I'm reading
</rh-cue>
<rh-cue start="27:24" end="27:25">
and writing things from a database
</rh-cue>
<rh-cue start="27:25" end="27:28">
or a message broker or moving data from one place to another.
</rh-cue>
<rh-cue start="27:28" end="27:29">
Those things happen subsequent.
</rh-cue>
<rh-cue start="27:29" end="27:33">
Normally, even with great latency between your data centers, you know,
</rh-cue>
<rh-cue start="27:33" end="27:34">
it's still subsequent.
</rh-cue>
<rh-cue start="27:34" end="27:38">
In most cases, while on a transaction like this, one can actually take 2 seconds
</rh-cue>
<rh-cue start="27:38" end="27:42">
or 4 seconds as it's doing its analysis and actually coming back with, you know,
</rh-cue>
<rh-cue start="27:42" end="27:46">
I think it's a dog, I think it's a kidney, I think it's whatever, and provided me
</rh-cue>
<rh-cue start="27:46" end="27:48">
that accuracy statement.
</rh-cue>
<rh-cue start="27:48" end="27:51">
So that concept of optimization is very important
</rh-cue>
<rh-cue start="27:51" end="27:53">
in the overall application architecture.
</rh-cue>
<rh-cue start="27:53" end="27:56">
Would you agree with that or how do you think about that concept?
</rh-cue>
<rh-cue start="27:56" end="27:56">
Yeah, definitely.
</rh-cue>
<rh-cue start="27:56" voice="Ryan Loney"></rh-cue>
<rh-cue start="27:56" end="27:58">
It depends too on the use case.
</rh-cue>
<rh-cue start="27:58" end="28:02">
So if you think about how important it is to reduce the latency
</rh-cue>
<rh-cue start="28:02" end="28:06">
and increase the number of frames per second that you can process when you're
</rh-cue>
<rh-cue start="28:06" end="28:10">
talking about a loss prevention model that's running at a grocery store.
</rh-cue>
<rh-cue start="28:10" end="28:13">
So you want to keep the lines moving.
</rh-cue>
<rh-cue start="28:13" end="28:16">
You don't want every person who's at the self-checkout
</rh-cue>
<rh-cue start="28:16" end="28:19">
to have to wait 5 seconds for every item they scan.
</rh-cue>
<rh-cue start="28:19" end="28:22">
You need it to happen as quickly as possible.
</rh-cue>
<rh-cue start="28:22" end="28:25">
And if sometimes you, you know, the accuracy
</rh-cue>
<rh-cue start="28:25" end="28:28">
decreases slightly or the I'd say the accuracy of the whole pipeline.
</rh-cue>
<rh-cue start="28:28" end="28:32">
So not just looking at the individual model or the individual inference, but
</rh-cue>
<rh-cue start="28:32" end="28:36">
let's say that the the whole pipeline is not as successful at detecting
</rh-cue>
<rh-cue start="28:37" end="28:40">
when somebody steals one item from the self-checkout,
</rh-cue>
<rh-cue start="28:41" end="28:43">
it's not going to be a life threatening situation.
</rh-cue>
<rh-cue start="28:43" end="28:47">
Whereas, you know, being in the hooked up to the X-ray machine
</rh-cue>
<rh-cue start="28:47" end="28:51">
with the two placement model, they might be willing to have the doctor,
</rh-cue>
<rh-cue start="28:51" end="28:54">
the nurse wait 5 seconds to get the result.
</rh-cue>
<rh-cue start="28:55" voice="Ryan Loney"></rh-cue>
<rh-cue start="28:55" end="28:58">
They don't need it to happen in 500 milliseconds.
</rh-cue>
<rh-cue start="28:58" end="29:02">
So they're willing their threshold for waiting is a little bit higher.
</rh-cue>
<rh-cue start="29:02" end="29:05">
So that, I think, also drives some of the decision, like
</rh-cue>
<rh-cue start="29:06" end="29:09">
you want to keep people moving through the checkout line
</rh-cue>
<rh-cue start="29:09" end="29:13">
and you can afford to to potentially if you lose a little bit of accuracy here
</rh-cue>
<rh-cue start="29:13" end="29:14">
and there, it's not going to
</rh-cue>
<rh-cue start="29:14" end="29:18">
cost the company that much money or it's not going to be life threatening.
</rh-cue>
<rh-cue start="29:18" end="29:21">It's going to be worth the tradeoff of keeping the line moving</rh-cue>
<rh-cue start="29:21" end="29:24">and not having people leave the store and not check out at all.</rh-cue>
<rh-cue start="29:24" end="29:27">And to say, I'm not going to shop today because the line's too long.</rh-cue>
<rh-cue start="29:30" voice="Burr Sutter"></rh-cue>
<rh-cue start="29:30" end="29:32">There are so many trade offs and enterprise</rh-cue>
<rh-cue start="29:32" end="29:35">AML use cases, things like latency, accuracy and availability.</rh-cue>
<rh-cue start="29:35" end="29:40">And certainly complexities abound, especially in an obviously ever evolving</rh-cue>
<rh-cue start="29:40" end="29:43">technological landscape where we are still very early in the adoption of AML.</rh-cue>
<rh-cue start="29:44" end="29:47">And to navigate that complexity, the direct feedback from real world</rh-cue>
<rh-cue start="29:47" end="29:51">end users is essential to Ryan and his team at Intel.</rh-cue>
<rh-cue start="29:52" end="29:54">What would you say are some of the big hurdles or big</rh-cue>
<rh-cue start="29:54" end="29:57">outcomes, big opportunities in that space?</rh-cue>
<rh-cue start="29:57" end="30:01">And do you agree that we're kind of still at the very beginning in our infancy,</rh-cue>
<rh-cue start="30:01" end="30:01">if you will,</rh-cue>
<rh-cue start="30:01" end="30:05">of adopting these technologies and and discovering what they can do for us?</rh-cue>
<rh-cue start="30:05" voice="Ryan Loney"></rh-cue>
<rh-cue start="30:05" end="30:07">Yeah, I think we're definitely in the infancy</rh-cue>
<rh-cue start="30:07" end="30:10">and I think that what we've seen is our customers are evolving</rh-cue>
<rh-cue start="30:10" end="30:14">and the people who are deploying on Intel hardware, they're trying to run</rh-cue>
<rh-cue start="30:14" end="30:16">more complicated models.</rh-cue>
<rh-cue start="30:16" end="30:19">They're the models that are doing object detection or, you know,</rh-cue>
<rh-cue start="30:19" end="30:22">detecting defects and, you know, doing segmentation.</rh-cue>
<rh-cue start="30:23" end="30:27">You know, in the past you could say, oh, here's a generic model that will do face</rh-cue>
<rh-cue start="30:27" end="30:31">detection or person detection or vehicle detection and license plate detection.</rh-cue>
<rh-cue start="30:32" end="30:33">And those are sort of like</rh-cue>
<rh-cue start="30:33" end="30:36">general purpose models that you can just grab off the shelf and use them.</rh-cue>
<rh-cue start="30:37" end="30:40">But now we're moving into like the anomaly scenarios</rh-cue>
<rh-cue start="30:40" end="30:44">where I've got my own data and I'm trying to do something very specific</rh-cue>
<rh-cue start="30:45" end="30:47">and I'm the only one that has access to this data.</rh-cue>
<rh-cue start="30:47" end="30:51">And you don't have a public data set that you can go download</rh-cue>
<rh-cue start="30:51" end="30:54">that's under Creative Commons license for, you know, car batteries.</rh-cue>
<rh-cue start="30:54" end="30:57">It's, you know, it's just not something that's available.</rh-cue>
<rh-cue start="30:57" voice="Ryan Loney"></rh-cue>
<rh-cue start="30:57" end="31:02">And so those use cases, the challenge with with training those models</rh-cue>
<rh-cue start="31:02" end="31:06">and and getting them optimized is the beginning of the pipeline.</rh-cue>
<rh-cue start="31:06" end="31:10">It's the data you have to get the data you have to annotated</rh-cue>
<rh-cue start="31:10" end="31:12">and the tools have to exist for you to do that.</rh-cue>
<rh-cue start="31:12" end="31:15">And that's part of the problem that we're trying to help solve.</rh-cue>
<rh-cue start="31:16" end="31:17">And then the models are getting more complex.</rh-cue>
<rh-cue start="31:17" end="31:21">So if you think, you know, just from working with customers recently,</rh-cue>
<rh-cue start="31:21" end="31:22">you know, they're no longer</rh-cue>
<rh-cue start="31:22" end="31:26">just trying to do image classification and, you know, like is it a dog or a cat?</rh-cue>
<rh-cue start="31:26" end="31:29">They've moved on to like 3D point clouds</rh-cue>
<rh-cue start="31:29" end="31:34">and, you know, 3D segmentation models and things that are like the speech</rh-cue>
<rh-cue start="31:34" end="31:39">synthesis example, doing things these GPT models that are generating,</rh-cue>
<rh-cue start="31:40" end="31:44">you know, you, you put a text input and it generates an image for you.</rh-cue>
<rh-cue start="31:44" end="31:47">It's just becoming much more advanced, much more sophisticated</rh-cue>
<rh-cue start="31:48" end="31:50">and on larger images.</rh-cue>
<rh-cue start="31:50" voice="Ryan Loney"></rh-cue>
<rh-cue start="31:50" end="31:54">And so things like running super resolution enhancing images, upscaling</rh-cue>
<rh-cue start="31:54" end="31:59">images, instead of just trying to take that, you know, 200 by 200 pixel</rh-cue>
<rh-cue start="32:00" end="32:02">image and classifying if it's a cat.</rh-cue>
<rh-cue start="32:02" end="32:05">Now we're talking about gigantic</rh-cue>
<rh-cue start="32:05" end="32:09">huge images that we're processing and that all requires</rh-cue>
<rh-cue start="32:09" end="32:12">more resources or more optimized models.</rh-cue>
<rh-cue start="32:13" end="32:16">And, you know, every computer vision conference or A.I.</rh-cue>
<rh-cue start="32:16" end="32:19">conference, there's there's a new latest and greatest architecture.</rh-cue>
<rh-cue start="32:19" end="32:22">There's new research paper, and things are getting adopted much faster.</rh-cue>
<rh-cue start="32:23" end="32:27">The lead time for a nurse paper or CV PR</rh-cue>
<rh-cue start="32:27" end="32:30">for a company to actually adopt and put those into production.</rh-cue>
<rh-cue start="32:30" end="32:32">It's like the time shortens every year.</rh-cue>
<rh-cue start="32:33" voice="Burr Sutter"></rh-cue>
<rh-cue start="32:33" end="32:35">Well, Ryan, I got to tell you, I could talk to you</rh-cue>
<rh-cue start="32:35" end="32:39">literally all day about these topics, the various use cases, the various ways</rh-cue>
<rh-cue start="32:39" end="32:41">models are being optimized,</rh-cue>
<rh-cue start="32:41" end="32:44">how to put models into a pipeline for average enterprise applications.</rh-cue>
<rh-cue start="32:44" end="32:47">I've enjoyed learning about pop and vino and anomalies,</rh-cue>
<rh-cue start="32:47" end="32:50">but I'm fascinated by this because I will have a chance to go try this myself.</rh-cue>
<rh-cue start="32:51" end="32:52">Taking advantage of Red Hat OpenShift</rh-cue>
<rh-cue start="32:52" end="32:54">and taking advantage of our data science platform.</rh-cue>
<rh-cue start="32:54" end="32:58">On top of that, I will definitely go be poking at this myself.</rh-cue>
<rh-cue start="32:58" end="33:00">So thank you so much for your time today.</rh-cue>
<rh-cue start="33:00" voice="Ryan Loney"></rh-cue>
<rh-cue start="33:00" end="33:00">Thanks, Burr.</rh-cue>
<rh-cue start="33:00" end="33:01">This was a lot of fun.</rh-cue>
<rh-cue start="33:01" end="33:04">Thanks for having me.</rh-cue>
<rh-cue start="33:04" voice="Burr Sutter"></rh-cue>
<rh-cue start="33:04" end="33:06">And you can check out</rh-cue>
<rh-cue start="33:06" end="33:09">the full transcript of our conversation and more resources,</rh-cue>
<rh-cue start="33:09" end="33:12">like a link to a white paper on open vino and normal lib at Red Hat dot</rh-cue>
<rh-cue start="33:12" end="33:15">com slash code Comments Podcast.</rh-cue>
<rh-cue start="33:15" end="33:19">This episode was produced by Brant Seminole and Caroline Prickett.</rh-cue>
<rh-cue start="33:20" end="33:21">Our sound designer is Christian.</rh-cue>
<rh-cue start="33:21" end="33:26">From our audio team includes Lee Day, Stephanie Wunderlich, Mike Esser,</rh-cue>
<rh-cue start="33:27" end="33:32">Laura Barnes, Claire Allison, Nick Burns, Aaron Williamson, Karen King,</rh-cue>
<rh-cue start="33:32" end="33:36">Booboo House, Rachel Artell, Mike Compton, Ocean</rh-cue>
<rh-cue start="33:36" end="33:40">Mathews, Laura Walters, Alex Trabelsi and Victoria Lutton.</rh-cue>
<rh-cue start="33:41" end="33:43">I'm your host, Burt Sutter.</rh-cue>
<rh-cue start="33:43" end="33:45">Thank you for joining me today on Code Comments.</rh-cue>
<rh-cue start="33:45" end="33:48">I hope you enjoyed today's session and today's conversation, and I</rh-cue>
<rh-cue start="33:48" end="33:52">look forward to many more in.</rh-cue>
</rh-transcript>
</rh-audio-player>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css">import { AudioPlayer } from "@rhds/elements/react/rh-audio-player/rh-audio-player.js";
import { AudioPlayerAbout } from "@rhds/elements/react/rh-audio-player-about/rh-audio-player-about.js";
import { AudioPlayerSubscribe } from "@rhds/elements/react/rh-audio-player-subscribe/rh-audio-player-subscribe.js";
import { Avatar } from "@rhds/elements/react/rh-avatar/rh-avatar.js";
import { Cue } from "@rhds/elements/react/rh-cue/rh-cue.js";
import { Transcript } from "@rhds/elements/react/rh-transcript/rh-transcript.js";
// NOTE: React 19+ does not require these wrapper imports.
// You can use the custom elements directly as-is.
export const Demo = () => (
<AudioPlayer layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h3 slot="title">Bringing Deep Learning to Enterprise Applications</h3>
<AudioPlayerAbout slot="about">
<h4 slot="heading">About the episode</h4>
<p>There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.</p>
<p>Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.</p>
<Avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools,<em>Intel®</em></span>
</Avatar>
</AudioPlayerAbout>
<audio crossorigin="anonymous" slot="media" controls>
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3" />
</audio>
<AudioPlayerSubscribe slot="subscribe">
<h4 slot="heading">Subscribe</h4>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts" />
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify" />
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts" />
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img className="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed" />
</a>
</AudioPlayerSubscribe>
<Transcript slot="transcript">
<Cue start="00:02" voice="Burr Sutter" />
<Cue start="00:02" end="00:04">Hi, I'm Burr Sutter.</Cue>
<Cue start="00:04" end="00:05">I'm a Red Hatter</Cue>
<Cue start="00:05" end="00:08">who spends a lot of time talking to technologists about technologies.</Cue>
<Cue start="00:09" end="00:10">We say this a lot of Red Hat.</Cue>
<Cue start="00:10" end="00:14">No single technology provider holds the key to success, including us.</Cue>
<Cue start="00:15" end="00:17">And I would say the same thing about myself.</Cue>
<Cue start="00:17" end="00:18">I love to share ideas.</Cue>
<Cue start="00:18" end="00:19">So I thought it'd be awesome</Cue>
<Cue start="00:19" end="00:22">to talk to some brilliant technologists at Red Hat Partners.</Cue>
<Cue start="00:23" end="00:26">This is Code Comments, an original podcast</Cue>
<Cue start="00:26" end="00:29">from Red Hat.</Cue>
<Cue start="00:29" voice="Burr Sutter" />
<Cue start="00:29" end="00:32">I'm sure, like many of you here, you have been thinking about</Cue>
<Cue start="00:32" end="00:36">AI, ML, artificial intelligence and machine learning.</Cue>
<Cue start="00:36" end="00:38">I've been thinking about that for quite some time</Cue>
<Cue start="00:38" end="00:39">and actually had the opportunity</Cue>
<Cue start="00:39" end="00:43">to work on a few successful projects here at Red Hat using those technologies,</Cue>
<Cue start="00:43" end="00:46">actually enabling a dataset, gathering a dataset,</Cue>
<Cue start="00:46" end="00:49">working with data scientists and data engineering team,</Cue>
<Cue start="00:49" end="00:51">and then training a model and putting that model into production</Cue>
<Cue start="00:51" end="00:53">runtime environment.</Cue>
<Cue start="00:53" end="00:55">It was an exciting set of projects and you can kind of see</Cue>
<Cue start="00:55" end="00:58">those on numerous YouTube videos I have published out there before.</Cue>
<Cue start="00:59" end="01:01">But I want you to think about the problem space a little bit</Cue>
<Cue start="01:01" end="01:04">because there are some interesting challenges about AI/ML.</Cue>
<Cue start="01:04" end="01:06">One is simply just getting access to the data,</Cue>
<Cue start="01:06" end="01:09">and while there are numerous publicly available datasets</Cue>
<Cue start="01:09" end="01:12">when it comes to your specific enterprise use case, you might not be to find</Cue>
<Cue start="01:12" end="01:14">publicly available data.</Cue>
<Cue start="01:14" voice="Burr Sutter" />
<Cue start="01:14" end="01:17">In many cases, you cannot, even for our applications that we created,</Cue>
<Cue start="01:17" end="01:20">we had to create our dataset, capture our dataset,</Cue>
<Cue start="01:21" end="01:24">explore the dataset, and of course train a model accordingly.</Cue>
<Cue start="01:24" end="01:27">And we also found there's another challenge to be overcome</Cue>
<Cue start="01:27" end="01:30">in this AML world, and that is access to certain types of hardware.</Cue>
<Cue start="01:31" end="01:33">If you think about the enterprise environment</Cue>
<Cue start="01:33" end="01:36">and the creation of an enterprise application specifically for AML</Cue>
<Cue start="01:37" end="01:40">and users need an inference engine to run on their hardware,</Cue>
<Cue start="01:40" end="01:43">hardware that's available to them to be effective for their application.</Cue>
<Cue start="01:43" end="01:45">Let's say an application like computer vision,</Cue>
<Cue start="01:45" end="01:49">one that can detect anomalies in medical imaging or maybe on a factory floor,</Cue>
<Cue start="01:49" end="01:52">You know, those things are whizzing by on the factory line.</Cue>
<Cue start="01:52" end="01:55">They're looking at them and trying to determine if there is an error or not.</Cue>
<Cue start="01:56" voice="Burr Sutter" />
<Cue start="01:56" end="01:58">Well, how do you actually make it run on your hardware,</Cue>
<Cue start="01:58" end="02:01">your accessible technology that you have today?</Cue>
<Cue start="02:01" end="02:05">Well, there's a solution for this as an open toolkit called Open vino.</Cue>
<Cue start="02:05" end="02:07">And you might be thinking, hey, wait a minute,</Cue>
<Cue start="02:07" end="02:10">don't you need a GPU for a I inferencing a GPU</Cue>
<Cue start="02:10" end="02:12">for artificial intelligence machine learning?</Cue>
<Cue start="02:12" end="02:15">Well, not according to Ryan Loney, product manager of Open Vino Developer</Cue>
<Cue start="02:15" end="02:16">Tools at Intel.</Cue>
<Cue start="02:20" voice="Ryan Loney" />
<Cue start="02:20" end="02:20">I guess we'll</Cue>
<Cue start="02:20" end="02:23">start with trying to maybe dispel the myths, right?</Cue>
<Cue start="02:23" end="02:27">I think that CPUs are widely used for inference today.</Cue>
<Cue start="02:27" end="02:32">So and if we look at the data center segment, you know, about 70% of the A.I.</Cue>
<Cue start="02:32" end="02:36">inference is happening on Intel Xeon on our data center CPUs.</Cue>
<Cue start="02:36" end="02:40">And so you don't needed a GPU, especially for running inference.</Cue>
<Cue start="02:40" end="02:43">And that's part of the value of open vino, is that we're you know,</Cue>
<Cue start="02:43" end="02:47">we're taking models that may have been trained on a GPU</Cue>
<Cue start="02:47" end="02:50">using deep learning frameworks like PyTorch or TensorFlow</Cue>
<Cue start="02:51" end="02:54">and then optimizing them to run on Intel hardware.</Cue>
<Cue start="02:57" voice="Burr Sutter" />
<Cue start="02:56" end="03:00">Ryan joined me to discuss AI/ML and the enterprise</Cue>
<Cue start="03:00" end="03:03">across various industries and exploring numerous use cases.</Cue>
<Cue start="03:05" end="03:08">Let's talk a little bit about the origin story behind Open Vino.</Cue>
<Cue start="03:08" end="03:10">Tell us more about it and how it came to be</Cue>
<Cue start="03:10" end="03:13">and why it came out of Intel.</Cue>
<Cue start="03:12" voice="Ryan Loney" />
<Cue start="03:12" end="03:16">Definitely. So we had the first release of Open Vino</Cue>
<Cue start="03:16" end="03:20">was back in 2018, so still relatively new.</Cue>
<Cue start="03:20" end="03:25">And at that time we were focused on computer vision and pretty tightly coupled</Cue>
<Cue start="03:25" end="03:31">with open CV, which is another open source library with origins at Intel.</Cue>
<Cue start="03:31" end="03:31">You know, it</Cue>
<Cue start="03:31" end="03:36">had its first release back in 1999, so it's been around a little bit longer.</Cue>
<Cue start="03:36" end="03:40">And many of the software engineers and architects at Intel</Cue>
<Cue start="03:40" end="03:45">that were involved with and contributing to open CV are working on open Vino.</Cue>
<Cue start="03:45" end="03:49">So you can think of open vino as complementary software to open CV.</Cue>
<Cue start="03:50" end="03:53">And we're providing like an engine for executing inference</Cue>
<Cue start="03:53" end="03:57">as part of a computer vision pipeline, or at least that's how we started.</Cue>
<Cue start="03:58" voice="Ryan Loney" />
<Cue start="03:58" end="04:01">But since 2018, we've we've started to move beyond</Cue>
<Cue start="04:01" end="04:02">just computer vision inference.</Cue>
<Cue start="04:02" end="04:05">So when I say computer vision inference, I mean like image</Cue>
<Cue start="04:05" end="04:08">classification, object detection, segmentation.</Cue>
<Cue start="04:09" end="04:12">And now we're moving into natural language processing, things</Cue>
<Cue start="04:12" end="04:16">like speech synthesis, speech recognition, knowledge, graphs,</Cue>
<Cue start="04:17" end="04:21">time series forecasting, and other use cases that don't involve</Cue>
<Cue start="04:21" end="04:24">computer vision and don't involve inference on pixels.</Cue>
<Cue start="04:25" end="04:28">Our latest release, the 20 22.1 that came out earlier this year,</Cue>
<Cue start="04:29" end="04:32">there was a most significant update that we've had to open vino</Cue>
<Cue start="04:32" end="04:36">since we started in 2018, and the major focus of that release</Cue>
<Cue start="04:36" end="04:40">was optimizing for use cases that go beyond computer vision.</Cue>
<Cue start="04:41" voice="Burr Sutter" />
<Cue start="04:41" end="04:44">And I like that concept that you just mentioned right there, computer vision.</Cue>
<Cue start="04:44" end="04:47">And you said that you extended those use cases and went beyond that.</Cue>
<Cue start="04:47" end="04:50">So could you give us more concrete examples of computer vision?</Cue>
<Cue start="04:50" voice="Ryan Loney" />
<Cue start="04:50" end="04:50">Yeah, sure.</Cue>
<Cue start="04:50" end="04:55">So when you think about manufacturing quality control in factories, everything</Cue>
<Cue start="04:55" end="05:01">from ARC welding, defect detection to inspecting BMW cars on assembly lines,</Cue>
<Cue start="05:02" end="05:05">they're using cameras or sensors to collect data.</Cue>
<Cue start="05:05" end="05:11">And usually it's cameras collecting images like RGV images that you and I can see.</Cue>
<Cue start="05:11" end="05:14">And looks like something taken from a camera or video camera,</Cue>
<Cue start="05:15" end="05:19">but also things like infrared or computerized tomography</Cue>
<Cue start="05:19" end="05:24">scans used in health care, X-ray, different types of images where we can</Cue>
<Cue start="05:25" end="05:28">draw bounding boxes around regions of interest</Cue>
<Cue start="05:29" end="05:32">and say, you know, this is a defect or this is not a defect.</Cue>
<Cue start="05:32" end="05:37">And also, is this worker wearing a safety hat or did they forget to put it on?</Cue>
<Cue start="05:37" end="05:41">And so you can take this and integrate it into a pipeline</Cue>
<Cue start="05:41" end="05:44">where you're triggering an alert if somebody forgets</Cue>
<Cue start="05:44" end="05:49">to wear their safety mask or if there's a defect in a product</Cue>
<Cue start="05:49" end="05:53">on an assembly line, you can just use cameras and open</Cue>
<Cue start="05:53" end="05:58">vino and open CV running these on Intel hardware and help to analyze.</Cue>
<Cue start="05:58" voice="Ryan Loney" />
<Cue start="05:58" end="06:01">And that's what a lot of the partners that we work with are doing.</Cue>
<Cue start="06:01" end="06:03">So these independent software vendors</Cue>
<Cue start="06:03" end="06:06">and there's other use cases for things like retail.</Cue>
<Cue start="06:06" end="06:10">You think about going to a store and using an automated checkout system.</Cue>
<Cue start="06:11" end="06:13">You know, sometimes people use those automated checkouts</Cue>
<Cue start="06:13" end="06:17">and they they slide a few extra items into their bag that they don't scan.</Cue>
<Cue start="06:17" end="06:21">And it's a huge loss for the retail outlets</Cue>
<Cue start="06:21" end="06:25">that are providing this way to check out real time shelf monitoring.</Cue>
<Cue start="06:25" end="06:29">We have this bear on one of our is fees that helps keep store shelves</Cue>
<Cue start="06:29" end="06:33">stocked by just analyzing the cameras in the stores, detecting</Cue>
<Cue start="06:33" end="06:37">when objects are missing from the shelves so that they can be restocked.</Cue>
<Cue start="06:37" end="06:41">We have Vistry, another ISP that works with quick service restaurants.</Cue>
<Cue start="06:41" end="06:44">So when you think about automating the process of</Cue>
<Cue start="06:44" end="06:48">when do I drop the fries into the fryer so that they're warm</Cue>
<Cue start="06:48" end="06:50">when the car gets to the drive thru window,</Cue>
<Cue start="06:50" end="06:54">you know, there's quite a bit of industrial health care retail examples</Cue>
<Cue start="06:54" end="06:57">that we can walk through and we should dig into some more of those.</Cue>
<Cue start="06:57" voice="Burr Sutter" />
<Cue start="06:57" end="06:59">But I got to tell you, I have I have a personal experience</Cue>
<Cue start="06:59" end="06:59">in this category</Cue>
<Cue start="06:59" end="07:01">that I want to share with, and you can tell me how</Cue>
<Cue start="07:01" end="07:03">how silly you might think at this point in time.</Cue>
<Cue start="07:03" end="07:04">It is.</Cue>
<Cue start="07:04" end="07:08">We actually built an AI keynote demonstration for the Red Hat big stage</Cue>
<Cue start="07:08" end="07:12">back in 2015, and I really want to illustrate the concept of asset tracking.</Cue>
<Cue start="07:12" end="07:15">So we actually gave everybody in the conference a little Bluetooth token,</Cue>
<Cue start="07:16" end="07:19">but a little battery, a little watch battery and a little Bluetooth emitter.</Cue>
<Cue start="07:19" end="07:22">And we basically tracked those things around the conference.</Cue>
<Cue start="07:22" end="07:24">We basically put a Raspberry Pi in each of the meeting rooms</Cue>
<Cue start="07:24" end="07:26">and up in the lunch room, and you could see how the tokens</Cue>
<Cue start="07:26" end="07:30">moved from room to room to room as a relatively simple application.</Cue>
<Cue start="07:30" voice="Burr Sutter" />
<Cue start="07:30" end="07:32">But it occurred to me after we figured out,</Cue>
<Cue start="07:32" end="07:34">okay, how to do that with Bluetooth and triangulating</Cue>
<Cue start="07:34" end="07:39">Bluetooth signals by looking at relative signal strength from one radio to another</Cue>
<Cue start="07:39" end="07:42">and putting that through an Apache Spark application at the time,</Cue>
<Cue start="07:42" end="07:45">we then realized, you know what, this is easier done with cameras</Cue>
<Cue start="07:45" end="07:49">and just simply looking at a camera and having some form of animal</Cue>
<Cue start="07:49" end="07:51">or machine learning model that would say, Oh,</Cue>
<Cue start="07:51" end="07:53">there are people here now are there are no people here now.</Cue>
<Cue start="07:53" end="07:55">What do you think about that?</Cue>
<Cue start="07:55" voice="Ryan Loney" />
<Cue start="07:55" end="07:59">Yeah, I mean, what you just described is sort of exactly that the product</Cue>
<Cue start="07:59" end="08:02">that either one of our partners is offering,</Cue>
<Cue start="08:02" end="08:04">you know, that they're doing it with computer vision and cameras.</Cue>
<Cue start="08:04" end="08:08">So when partner tries to help retail stores</Cue>
<Cue start="08:08" end="08:12">analyze the foot traffic and understand with Heatmaps,</Cue>
<Cue start="08:12" end="08:16">where people are spending the most time in stores, how many people are coming</Cue>
<Cue start="08:16" end="08:19">in, what size groups are coming into the store,</Cue>
<Cue start="08:19" end="08:23">you know, and trying to help understand if there was a successful transaction</Cue>
<Cue start="08:23" end="08:27">from the people who entered the store and left the store so that you can,</Cue>
<Cue start="08:27" end="08:30">you know, to help with the, you know, retail analytics</Cue>
<Cue start="08:30" end="08:33">and marketing sales and positioning of products.</Cue>
<Cue start="08:34" end="08:37">And so they're doing that in a way that also protects privacy.</Cue>
<Cue start="08:37" end="08:38">And that's something that's really important.</Cue>
<Cue start="08:38" end="08:41">So when you talked about those Bluetooth beacons, probably,</Cue>
<Cue start="08:41" end="08:44">you know, if everyone who walked into a grocery store was asked</Cue>
<Cue start="08:44" end="08:49">to put a tracking device in their cart or on their person and say, you know,</Cue>
<Cue start="08:49" end="08:50">you're going</Cue>
<Cue start="08:50" end="08:53">to be tracked around the store, they probably wouldn't want to do that.</Cue>
<Cue start="08:53" end="08:56">The way that you can do this with cameras is you can,</Cue>
<Cue start="08:53" voice="Ryan Loney" />
<Cue start="08:56" end="09:01">you know, detect people as they enter and, you know, remove their face.</Cue>
<Cue start="09:01" end="09:01">Right.</Cue>
<Cue start="09:01" end="09:05">So you can ignore any biometric information</Cue>
<Cue start="09:05" end="09:08">and and just track the person based on pixels</Cue>
<Cue start="09:09" end="09:12">that are present in the detected region of interest.</Cue>
<Cue start="09:12" end="09:15">So they're able to analyze, say, a family walks in the door</Cue>
<Cue start="09:16" end="09:20">and they can group those people together with object detection</Cue>
<Cue start="09:20" end="09:23">and then they can track their movement throughout the store</Cue>
<Cue start="09:23" end="09:26">without keeping track of their face or any biometric</Cue>
<Cue start="09:26" end="09:30">or any personal identifiable information to avoid things like bias</Cue>
<Cue start="09:30" end="09:35">and to make sure that they're protecting the privacy of the shoppers in the store</Cue>
<Cue start="09:35" end="09:39">while still getting that really useful marketing analytics data rate</Cue>
<Cue start="09:39" end="09:42">so that they can make better decisions about where to place their products.</Cue>
<Cue start="09:42" end="09:45">So that's one really good example of how</Cue>
<Cue start="09:45" end="09:48">computer vision AI with open vino is being used today.</Cue>
<Cue start="09:48" voice="Burr Sutter" />
<Cue start="09:48" end="09:51">And that is a great example because you're definitely spot on.</Cue>
<Cue start="09:51" end="09:53">It is invasive when you hand someone to Bluetooth devices,</Cue>
<Cue start="09:53" end="09:56">say, please keep this with you as you go throughout our our store</Cue>
<Cue start="09:56" end="09:59">or our mall or throughout our hospital, wherever you might be.</Cue>
<Cue start="09:59" end="10:01">Now, you mentioned another example earlier</Cue>
<Cue start="10:01" end="10:03">in the conversation which was related to like worker safety.</Cue>
<Cue start="10:03" end="10:05">Are they wearing a helmet?</Cue>
<Cue start="10:05" end="10:08">I want to talk more about that concept in a real industrial setting,</Cue>
<Cue start="10:08" end="10:11">a manufacturing setting where there might be a factory floor</Cue>
<Cue start="10:11" end="10:13">and there are certain requirements, or better yet, there's like a</Cue>
<Cue start="10:13" end="10:16">a quality assurance requirement, let's say, when it comes to looking</Cue>
<Cue start="10:16" end="10:20">at a factory line, I run to that use case often what some of our customers.</Cue>
<Cue start="10:20" end="10:22">Can you talk more about those kinds of use cases? Yeah.</Cue>
<Cue start="10:22" voice="Ryan Loney" />
<Cue start="10:22" end="10:27">So one of our partners, Robuchon and we you know, published a case study</Cue>
<Cue start="10:27" end="10:31">I think last year where they're working with BMW at one of their factories</Cue>
<Cue start="10:32" end="10:35">and they do quality control inspection, but they're also doing</Cue>
<Cue start="10:35" end="10:38">things related to worker safety and analyzing.</Cue>
<Cue start="10:38" end="10:40">You know, I used the safety had example.</Cue>
<Cue start="10:40" end="10:45">There's a number of of our ISP's and partners who have similar use cases.</Cue>
<Cue start="10:45" end="10:48">And it comes down to there's a few reasons</Cue>
<Cue start="10:48" end="10:51">that are motivating this and some are related to like insurance, right?</Cue>
<Cue start="10:51" end="10:53">It's important to make sure that</Cue>
<Cue start="10:53" end="10:56">if you want to have your factory insured and that your workers</Cue>
<Cue start="10:56" end="10:58">are protecting themselves and wearing the gear.</Cue>
<Cue start="10:58" end="11:00">Regulatory compliance. Right.</Cue>
<Cue start="11:00" end="11:05">You're you're being asked to properly protect from exposure to chemicals or,</Cue>
<Cue start="11:05" end="11:09">you know, potentially having something fall and and hit someone on the head.</Cue>
<Cue start="11:09" end="11:13">So wearing a safety vest, wearing goggles, wearing a helmet,</Cue>
<Cue start="11:14" end="11:17">these are things that you need to do inside the factory.</Cue>
<Cue start="11:17" end="11:21">And you can really easily automate and detect and sometimes without bias.</Cue>
<Cue start="11:21" voice="Ryan Loney" />
<Cue start="11:21" end="11:26">I think that's one of the interesting things about the robots on BMW example</Cue>
<Cue start="11:26" end="11:31">is that they were also blurring sort of blocking out and so drawing a box</Cue>
<Cue start="11:31" end="11:35">to cover the face of the workers in the factory</Cue>
<Cue start="11:35" end="11:38">so that somebody who was analyzing the video footage</Cue>
<Cue start="11:38" end="11:43">and getting the alerts saying that, hey, you know, Bay 21 has a worker</Cue>
<Cue start="11:43" end="11:47">without a hat on, that it's not sending their face</Cue>
<Cue start="11:47" end="11:50">and in the alert and potentially, you know, invading</Cue>
<Cue start="11:50" end="11:54">or going against privacy laws or just the ethics of the company.</Cue>
<Cue start="11:54" end="11:54">Right.</Cue>
<Cue start="11:54" end="11:58">They don't want to introduce bias or have people targeted because</Cue>
<Cue start="11:58" end="12:02">it's much better to to have it be, you know, blur the face</Cue>
<Cue start="12:02" end="12:06">and alert and have somebody take care of it on the floor.</Cue>
<Cue start="12:06" end="12:09">And then if you ever need to audit that information later,</Cue>
<Cue start="12:09" end="12:12">they have a way to do it where people who need to be able to see</Cue>
<Cue start="12:12" end="12:17">who the employee was and look up their personal information, they can do that.</Cue>
<Cue start="12:17" voice="Ryan Loney" />
<Cue start="12:17" end="12:20">But then just for the purposes of maintaining safety,</Cue>
<Cue start="12:20" end="12:21">they don't need to have access</Cue>
<Cue start="12:21" end="12:24">to that personal information or biometric information,</Cue>
<Cue start="12:25" end="12:28">because that's one thing that when you hear about computer vision</Cue>
<Cue start="12:28" end="12:31">or object person tracking, object detection,</Cue>
<Cue start="12:32" end="12:36">there's a lot of concern, and rightfully so, about privacy</Cue>
<Cue start="12:36" end="12:40">being invaded and about tracking information, face ID,</Cue>
<Cue start="12:41" end="12:45">identifying people who may have committed crimes through video footage.</Cue>
<Cue start="12:45" end="12:48">And that's just not something that a lot of companies want to</Cue>
<Cue start="12:49" end="12:51">you know, they want to protect privacy</Cue>
<Cue start="12:51" end="12:52">and they don't they don't want to be in a situation</Cue>
<Cue start="12:52" end="12:55">where they might be violating someone's rights.</Cue>
<Cue start="12:56" voice="Burr Sutter" />
<Cue start="12:56" end="12:58">Well, privacy is certainly opening up Pandora's box.</Cue>
<Cue start="12:58" end="13:00">There's a lot to be explored in that area,</Cue>
<Cue start="13:00" end="13:02">especially in a digital world that we now live in.</Cue>
<Cue start="13:02" end="13:05">But for now, let's move on and explore different area.</Cue>
<Cue start="13:05" end="13:08">I'm interested in how machines and computers offer advantages,</Cue>
<Cue start="13:08" end="13:12">specifically in certain use cases like a quality control scenario.</Cue>
<Cue start="13:12" end="13:15">I asked Ryan to explain how AML and specifically machines</Cue>
<Cue start="13:15" end="13:18">computers can augment that capability.</Cue>
<Cue start="13:19" voice="Ryan Loney" />
<Cue start="13:19" end="13:22">I can give a specific example where we have a partner</Cue>
<Cue start="13:22" end="13:25">that's there doing defect detection with</Cue>
<Cue start="13:25" end="13:28">and looking for anomalies in batteries.</Cue>
<Cue start="13:28" end="13:31">So, you know, sure, you've heard there's a lot of interest right now</Cue>
<Cue start="13:31" end="13:34">in electric vehicles, a lot of batteries being produced.</Cue>
<Cue start="13:34" end="13:36">And so if you go into one of these factories,</Cue>
<Cue start="13:36" end="13:40">they have images that they collect of every battery that's going through this</Cue>
<Cue start="13:40" end="13:44">assembly line and through these images, people</Cue>
<Cue start="13:44" end="13:47">can look and see and visually inspect with their eyes and say,</Cue>
<Cue start="13:48" end="13:50">this battery has a defect, send it back.</Cue>
<Cue start="13:50" end="13:53">And that's one step in the quality control process.</Cue>
<Cue start="13:53" end="13:58">And there's other steps, I'm sure, like running diagnostic tests and, you know,</Cue>
<Cue start="13:58" end="14:02">measuring voltage and doing other types of non-visual inspection.</Cue>
<Cue start="14:02" end="14:06">But for the visual inspection piece where you can really easily identify</Cue>
<Cue start="14:06" end="14:10">some problems, it's much more efficient to introduce computer vision.</Cue>
<Cue start="14:11" end="14:14">And so that's where we have this new library that we've introduced</Cue>
<Cue start="14:14" end="14:17">called Anomali, that's open vino.</Cue>
<Cue start="14:17" voice="Ryan Loney" />
<Cue start="14:17" end="14:20">While we're focused on inference, you know, we're also thinking</Cue>
<Cue start="14:20" end="14:25">about the pipeline or the funnel that gets these models to open vino.</Cue>
<Cue start="14:25" end="14:28">And so we've we've invested in this anomaly segmentation,</Cue>
<Cue start="14:28" end="14:32">anomaly detection library and that we've recently open source</Cue>
<Cue start="14:32" end="14:35">and there's a great research paper about it about Anomali.</Cue>
<Cue start="14:36" end="14:39">But the idea is you can take just a few images</Cue>
<Cue start="14:39" end="14:43">and train a model and start detecting these defects.</Cue>
<Cue start="14:43" end="14:46">And so for this battery example, that's a more advanced example.</Cue>
<Cue start="14:46" end="14:52">But to make it simpler, you know, take some bolts and, you know, take ten bolts.</Cue>
<Cue start="14:52" end="14:55">You have one that has a scratch on it or one that is chipped</Cue>
<Cue start="14:56" end="14:58">or has some damage to it.</Cue>
<Cue start="14:58" end="15:00">And you can easily get started in training</Cue>
<Cue start="15:00" end="15:03">to recognize the bolts that do not have an anomaly.</Cue>
<Cue start="15:04" end="15:06">And the ones that do, which is a small data set</Cue>
<Cue start="15:06" end="15:10">and I think that's really one of the most important things today.</Cue>
<Cue start="15:11" voice="Ryan Loney" />
<Cue start="15:11" end="15:14">Challenges is one is access to data, but the other is</Cue>
<Cue start="15:14" end="15:17">is needing a massive amount of data to do something meaningful.</Cue>
<Cue start="15:18" end="15:22">And so we're starting to try to change that dynamic with Anomali.</Cue>
<Cue start="15:22" end="15:27">So you may not need 100,000 images, you may need 100 images,</Cue>
<Cue start="15:27" end="15:33">and you can start detecting anomalies in everything from batteries to bolts to,</Cue>
<Cue start="15:33" end="15:37">you know, maybe even the wood varnish use case that you mentioned.</Cue>
<Cue start="15:37" voice="Burr Sutter" />
<Cue start="15:37" end="15:40">That is very key point because often in that data scientist</Cue>
<Cue start="15:40" end="15:43">process, that data engineer and data scientist process, right.</Cue>
<Cue start="15:43" end="15:44">The one key thing is can you gather</Cue>
<Cue start="15:44" end="15:47">the data that you need for the input for the model training?</Cue>
<Cue start="15:47" end="15:49">And we've often sat at least people I've worked</Cue>
<Cue start="15:49" end="15:52">with over the last couple of years, you know, you need a lot of data.</Cue>
<Cue start="15:52" end="15:55">You need tens of thousands of correct images</Cue>
<Cue start="15:55" end="15:58">so we can sort out the difference between dogs versus cats, let's say,</Cue>
<Cue start="15:58" end="16:01">or you need dozens and dozens of situations</Cue>
<Cue start="16:01" end="16:03">where if it's a natural language processing scenario,</Cue>
<Cue start="16:03" end="16:06">you know, a good customer interaction, a good customer conversation,</Cue>
<Cue start="16:06" end="16:07">and in this case,</Cue>
<Cue start="16:07" end="16:11">it sounds like what you're saying is show us just the bad things, right?</Cue>
<Cue start="16:11" end="16:14">Fewer images, fewer incorrect things,</Cue>
<Cue start="16:14" end="16:17">and then let us look for those kind of anomalies.</Cue>
<Cue start="16:18" end="16:20">Can tell us more about that because that is very interesting.</Cue>
<Cue start="16:20" end="16:23">The concept that I can use a much smaller dataset as my input</Cue>
<Cue start="16:23" end="16:26">as opposed to gathering terabytes of data in some cases</Cue>
<Cue start="16:26" end="16:29">to just simply get my model training underway.</Cue>
<Cue start="16:30" voice="Ryan Loney" />
<Cue start="16:30" end="16:34">You know, like you described, the idea is if you have some good images</Cue>
<Cue start="16:34" end="16:37">and then you have some of the the known defects</Cue>
<Cue start="16:38" end="16:41">and you can just label here's a set of good images</Cue>
<Cue start="16:41" end="16:44">and here's a few of the defects and you can right away</Cue>
<Cue start="16:44" end="16:48">start detecting those specific defects that you've identified.</Cue>
<Cue start="16:48" end="16:49">And then also, you know, be able to</Cue>
<Cue start="16:50" end="16:53">determine when it doesn't match</Cue>
<Cue start="16:53" end="16:57">the expected appearance of a non defective item.</Cue>
<Cue start="16:57" end="17:00">So if I have the undamaged screw and then I introduce</Cue>
<Cue start="17:00" end="17:03">one with some new anomaly that's never been seen before,</Cue>
<Cue start="17:04" end="17:07">I can say, you know, this one is not a valid screw.</Cue>
<Cue start="17:07" end="17:11">And so that's sort of the the approach that we're taking.</Cue>
<Cue start="17:11" end="17:15">And it's really important because so often you need to have</Cue>
<Cue start="17:15" end="17:19">subject matter experts often like if you think the take the battery example,</Cue>
<Cue start="17:20" end="17:23">there's these workers who are on the floor</Cue>
<Cue start="17:23" end="17:27">in a factory and they're the ones who know best when they look at these images,</Cue>
<Cue start="17:28" end="17:31">which one's going to have an issue, which one's defective?</Cue>
<Cue start="17:31" voice="Ryan Loney" />
<Cue start="17:31" end="17:34">And then they also need to take that subject matter, expertise</Cue>
<Cue start="17:35" end="17:38">and then use it to annotate data sets.</Cue>
<Cue start="17:38" end="17:39">And when you have these, you know,</Cue>
<Cue start="17:39" end="17:43">tens of thousands of images you need to annotate, it's asking those people</Cue>
<Cue start="17:43" end="17:47">to stop working on the factory floor so they can come annotate some images.</Cue>
<Cue start="17:47" end="17:49">That's a tough business call to make, right?</Cue>
<Cue start="17:49" end="17:53">But if you only need them to annotate a handful of images, it's a much easier</Cue>
<Cue start="17:53" end="17:56">ask to get the ball rolling and demonstrate value.</Cue>
<Cue start="17:56" end="17:59">And maybe over time you will want to annotate more</Cue>
<Cue start="17:59" end="18:03">and more images because you'll get even better accuracy in the model.</Cue>
<Cue start="18:03" end="18:07">Even better, even if it's just small incremental improvements.</Cue>
<Cue start="18:08" end="18:11">You know, that's something that if it generates value for the business,</Cue>
<Cue start="18:11" end="18:14">it's something the business will invest in over time.</Cue>
<Cue start="18:14" end="18:17">But you have to convince the decision makers that it's worth</Cue>
<Cue start="18:17" end="18:22">the time of these subject matter experts to stop what they're doing</Cue>
<Cue start="18:22" end="18:26">and go and label some images of the things that they're working on in the factory.</Cue>
<Cue start="18:26" voice="Burr Sutter" />
<Cue start="18:26" end="18:30">And that labeling process can be very labor intensive of the annotations,</Cue>
<Cue start="18:30" end="18:33">basically saying what is correct, what's wrong, what is this, what is that?</Cue>
<Cue start="18:33" end="18:36">And therefore, if we can minimize that time frame to get the value quicker,</Cue>
<Cue start="18:36" end="18:40">then there's something that's useful for the business, useful for the organization</Cue>
<Cue start="18:40" end="18:41">long before we necessarily good.</Cue>
<Cue start="18:41" end="18:43">There are huge model training based,</Cue>
<Cue start="18:49" voice="Burr Sutter" />
<Cue start="18:49" end="18:52">so we talk about labeling and how that is labor intensive activity.</Cue>
<Cue start="18:52" end="18:54">But I love the idea of helping the human</Cue>
<Cue start="18:54" end="18:57">and helping the human models specifically not get bored.</Cue>
<Cue start="18:57" end="19:01">Basically, if the human is eyeballing a bunch of widgets flying by over time,</Cue>
<Cue start="19:01" end="19:03">they make mistakes, they get bored</Cue>
<Cue start="19:03" end="19:06">and they don't pay as close attention as they should.</Cue>
<Cue start="19:07" end="19:10">That's why the concept of Amazon specifically computer vision, augmenting</Cue>
<Cue start="19:10" end="19:14">that capability and really helping the human identify anomalies faster,</Cue>
<Cue start="19:14" end="19:17">more quickly, maybe with greater accuracy could be a big win.</Cue>
<Cue start="19:18" end="19:21">We focused on manufacturing, but let's actually go into health care</Cue>
<Cue start="19:21" end="19:24">and learn how these tools can be used in that sector and that industry.</Cue>
<Cue start="19:24" end="19:28">Ryan talked to me about how Open Windows runtime can be incorporated into medical</Cue>
<Cue start="19:28" end="19:32">imaging equipment with intel processors and better than c.T.</Cue>
<Cue start="19:32" end="19:34">MRI and ultrasound machines.</Cue>
<Cue start="19:34" end="19:37">Well, these inferences, this AML workload can be operating</Cue>
<Cue start="19:37" end="19:41">and executing right there in the same physical room as the patient.</Cue>
<Cue start="19:44" voice="Ryan Loney" />
<Cue start="19:44" end="19:46">We did a presentation when she last year.</Cue>
<Cue start="19:46" end="19:47">I think they said</Cue>
<Cue start="19:47" end="19:50">there's at least 80 countries that have their X-ray machines deployed</Cue>
<Cue start="19:51" end="19:56">and they're doing things like helping doctors place breathing tubes in patients.</Cue>
<Cue start="19:56" end="20:01">So during COVID, during the pandemic, that was a really important tool</Cue>
<Cue start="20:01" end="20:05">to help with nurses and doctors who were intubating patients</Cue>
<Cue start="20:05" end="20:09">sometimes like in a parking lot or a hallway of the hospital.</Cue>
<Cue start="20:09" end="20:14">And, you know, when they had a statistic that you said, I think one out of four</Cue>
<Cue start="20:14" end="20:17">breathing tubes gets placed incorrectly</Cue>
<Cue start="20:17" end="20:19">when you're doing it outside the operating room,</Cue>
<Cue start="20:19" end="20:22">because when you're in an operating room, it's much more controlled</Cue>
<Cue start="20:22" end="20:24">and there's someone who's an expert at placing the tubes.</Cue>
<Cue start="20:24" end="20:28">It's something you have more of a controlled environment</Cue>
<Cue start="20:28" end="20:31">than when you're out in a parking lot, in a tent.</Cue>
<Cue start="20:31" end="20:34">You know, when the hospital's completely full and you're triaging patients</Cue>
<Cue start="20:34" end="20:37">with COVID, that's when they're more likely to make mistakes.</Cue>
<Cue start="20:37" end="20:40">And so they had this endotracheal tube placement</Cue>
<Cue start="20:42" end="20:43">model that they trained,</Cue>
<Cue start="20:43" end="20:47">and it helped to use an x ray and give an alert and say, hey,</Cue>
<Cue start="20:47" end="20:50">this tube is placed wrong, pull it out and do it again.</Cue>
<Cue start="20:50" end="20:53">And so things like that help doctors so that they can avoid mistakes.</Cue>
<Cue start="20:54" end="20:57">And, you know, having a breathing tube placed incorrectly</Cue>
<Cue start="20:57" end="21:01">can cause collapsed lung and a number of other unwanted side effects.</Cue>
<Cue start="21:01" end="21:03">So it's really important to do it correctly.</Cue>
<Cue start="21:03" end="21:06">Another example is Samsung Medicine.</Cue>
<Cue start="21:06" end="21:10">They actually are doing estimating fetal angle of progression.</Cue>
<Cue start="21:10" end="21:13">So this is analyzing ultrasound</Cue>
<Cue start="21:14" end="21:18">of pregnant women with that, being able to to help take measurements</Cue>
<Cue start="21:18" end="21:22">that are usually hard to calculate that can be done in an automated way.</Cue>
<Cue start="21:22" end="21:26">They're already taking the ultrasound scan and now they're executing this model.</Cue>
<Cue start="21:26" end="21:31">They can take some of these measurements to help the doctor avoid potentially more</Cue>
<Cue start="21:31" end="21:34">intrusive alternative methods so the patient wins.</Cue>
<Cue start="21:35" end="21:36">It makes their life better.</Cue>
<Cue start="21:36" end="21:39">And the doctors is getting help from this A.I.</Cue>
<Cue start="21:39" end="21:40">model.</Cue>
<Cue start="21:40" end="21:42">And those are, you know, just a few examples.</Cue>
<Cue start="21:42" voice="Burr Sutter" />
<Cue start="21:42" end="21:45">Those are some amazing examples when it comes to all these things.</Cue>
<Cue start="21:45" end="21:49">We're talking like CT scans, right, and x rays, other examples of computer vision.</Cue>
<Cue start="21:49" end="21:52">One thing that's kind of interesting in the space, I think</Cue>
<Cue start="21:52" end="21:56">whenever I get a chance to work on, let's say an object traction model</Cue>
<Cue start="21:56" end="21:58">and one of our workshops, by the way, is actually putting that out</Cue>
<Cue start="21:58" end="22:01">in front of people to say, Hey, look, you can use your phone.</Cue>
<Cue start="22:01" end="22:04">And it basically sends the image over to our OpenShift, right,</Cue>
<Cue start="22:04" end="22:07">with our data science platform and then analyzes what you see.</Cue>
<Cue start="22:08" end="22:09">And even in my case, where I take a picture of my dog</Cue>
<Cue start="22:09" end="22:13">as an example, it can't really decide is it a dog or a cat?</Cue>
<Cue start="22:13" end="22:15">I have a very funny looking dog,</Cue>
<Cue start="22:15" voice="Burr Sutter" />
<Cue start="22:15" end="22:18">and so there's always a percentage outcome, you know?</Cue>
<Cue start="22:18" end="22:21">In other words, I think it's a dog 52%.</Cue>
<Cue start="22:21" end="22:22">So I want to talk about that more.</Cue>
<Cue start="22:22" end="22:25">What how important is it to get to 100% accuracy?</Cue>
<Cue start="22:25" end="22:29">How important is it to really, depending on the use case, to allow</Cue>
<Cue start="22:29" end="22:34">for the gray area, if you will, where it's an 80% accuracy or 70% accuracy?</Cue>
<Cue start="22:34" end="22:36">And where are the trade offs there associated with the application?</Cue>
<Cue start="22:36" end="22:38">Can you can you discuss that more?</Cue>
<Cue start="22:38" voice="Ryan Loney" />
<Cue start="22:38" end="22:40">Accuracy is definitely, you know, a touchy subject</Cue>
<Cue start="22:40" end="22:43">because how you measure it makes a huge difference.</Cue>
<Cue start="22:43" end="22:46">And then I think with like what you were describing with the dog example, there's</Cue>
<Cue start="22:46" end="22:51">sort of a top five potential classes that might may be identified.</Cue>
<Cue start="22:51" end="22:55">So let's say you're doing object detection and you detect a region of interest</Cue>
<Cue start="22:55" end="22:57">and it says 65% confidence.</Cue>
<Cue start="22:57" end="22:58">This is a dog.</Cue>
<Cue start="22:58" end="23:03">Well, the next potential label that could be maybe 50% confidence</Cue>
<Cue start="23:03" end="23:08">or 20% confidence might be something similar to a dog or in the case of models</Cue>
<Cue start="23:08" end="23:11">that have been trained on like the image net dataset</Cue>
<Cue start="23:11" end="23:15">or on cocoa data set, they have like actual breeds of dogs.</Cue>
<Cue start="23:15" end="23:20">So if I want to look at the top five labels for a dog,</Cue>
<Cue start="23:20" end="23:24">for my dog, for example, she's a mixed mostly Labrador retriever.</Cue>
<Cue start="23:24" voice="Ryan Loney" />
<Cue start="23:24" end="23:29">But I may look at the top five labels and it may say 65% confidence that she's</Cue>
<Cue start="23:29" end="23:34">a flat coated retriever and then confidence that she's a husky,</Cue>
<Cue start="23:34" end="23:39">as you know, 20% and then 5% confidence that she's a greyhound or something.</Cue>
<Cue start="23:40" end="23:42">Those labels, all of them are dogs.</Cue>
<Cue start="23:42" end="23:45">So if I'm just trying to figure out is, is this a dog,</Cue>
<Cue start="23:45" end="23:50">I could probably find all of the, you know, classes within the data set</Cue>
<Cue start="23:50" end="23:53">and say, well, these are all, you know, class ID</Cue>
<Cue start="23:53" end="24:00">65, 132, 92 and 158 all belong to a group of dogs.</Cue>
<Cue start="24:00" end="24:04">So if I wanted to just write an application to tell me if this is a dog</Cue>
<Cue start="24:04" end="24:07">or not, I would probably use that to determine if it's a dog.</Cue>
<Cue start="24:08" end="24:10">But how you measure that is accuracy.</Cue>
<Cue start="24:10" end="24:11">Well, that's where it gets a little bit complicated,</Cue>
<Cue start="24:11" end="24:15">because if you're being really strict about the definition and you're</Cue>
<Cue start="24:15" end="24:18">trying to validate against the data set of labeled images</Cue>
<Cue start="24:18" end="24:22">and I have specific dog breeds or some specific detail</Cue>
<Cue start="24:22" end="24:25">and it doesn't match, well, then the accuracy is going to go down.</Cue>
<Cue start="24:25" voice="Ryan Loney" />
<Cue start="24:25" end="24:29">That's especially important when we talk about things like compression</Cue>
<Cue start="24:29" end="24:30">and quantization,</Cue>
<Cue start="24:30" end="24:34">which, you know, historically has been difficult for to get adoption</Cue>
<Cue start="24:34" end="24:40">in some domains like health care, where even the hint of accuracy going down</Cue>
<Cue start="24:40" end="24:44">implies that we're not going to be able to help in some small case,</Cue>
<Cue start="24:44" end="24:47">maybe if it's even half a percent of the time</Cue>
<Cue start="24:47" end="24:51">we want to take that that tube is placed incorrectly or that, you know,</Cue>
<Cue start="24:51" end="24:54">that patient's, you know, lung has collapsed or something like that.</Cue>
<Cue start="24:54" end="24:58">And that's something that really prevents adoption of some of these methods</Cue>
<Cue start="24:58" end="25:01">that can really boost performance like quantization.</Cue>
<Cue start="25:01" end="25:05">But if you take that example of sort of different from the dog example</Cue>
<Cue start="25:05" end="25:07">and you think about like segmentation of kidneys.</Cue>
<Cue start="25:07" end="25:11">So if I'm doing kidney segmentation, which is, you know, taking a CT scan</Cue>
<Cue start="25:12" end="25:14">and then trying to pick the pixels out of that</Cue>
<Cue start="25:14" end="25:17">scan that belong to a kidney,</Cue>
<Cue start="25:17" end="25:20">how I measure accuracy may be</Cue>
<Cue start="25:20" end="25:24">how many of those pixels I'm able to detect and how many did I miss?</Cue>
<Cue start="25:25" voice="Ryan Loney" />
<Cue start="25:25" end="25:29">Missing some of the pixels is maybe not a problem, right,</Cue>
<Cue start="25:29" end="25:33">depending on how you built the application because you still detect the kidney</Cue>
<Cue start="25:34" end="25:38">and maybe you just need to apply padding around the region of interest</Cue>
<Cue start="25:38" end="25:41">so that you don't miss any of the the actual kidney.</Cue>
<Cue start="25:42" end="25:45">When you compress the model and when you quantized the model. But</Cue>
<Cue start="25:45" end="25:50">that requires, you know, data scientist and email engineer somebody to really</Cue>
<Cue start="25:51" end="25:52">they have to be</Cue>
<Cue start="25:52" end="25:55">able to go and apply that after the fact, after the inference</Cue>
<Cue start="25:55" end="25:59">happens to make sure that you're not losing critical information,</Cue>
<Cue start="25:59" end="26:02">because the next step from detecting the kidney may be detecting a tumor.</Cue>
<Cue start="26:03" voice="Ryan Loney" />
<Cue start="26:03" end="26:06">And so maybe you can use the more optimized model</Cue>
<Cue start="26:06" end="26:11">to detect the kidney, but then you can use a slower model to detect the tumor.</Cue>
<Cue start="26:11" end="26:15">But that also requires somebody to architect and make that decision</Cue>
<Cue start="26:15" end="26:16">or that tradeoff and say,</Cue>
<Cue start="26:16" end="26:20">well, I need to add padding, or I should only use the quantized model</Cue>
<Cue start="26:20" end="26:24">to detect the region of interest for the kidney and then use the model</Cue>
<Cue start="26:24" end="26:27">that takes longer to do the inference</Cue>
<Cue start="26:27" end="26:30">just to find the tumor, which is going to be on a smaller size.</Cue>
<Cue start="26:30" end="26:33">Right. The dimensions are going to be much smaller</Cue>
<Cue start="26:33" end="26:35">once we crop to the region of interest.</Cue>
<Cue start="26:35" end="26:40">But all of those details, that's maybe not easy to explain in a few sentences.</Cue>
<Cue start="26:40" end="26:43">And even the way I explained it is probably really confusing.</Cue>
<Cue start="26:45" voice="Burr Sutter" />
<Cue start="26:45" end="26:46">I do love that use case.</Cue>
<Cue start="26:46" end="26:47">Like you mentioned, the cropping</Cue>
<Cue start="26:47" end="26:50">even in one such an area that we worked on for another project,</Cue>
<Cue start="26:50" end="26:53">we specifically decided to pix like the image that we had taken</Cue>
<Cue start="26:53" end="26:57">because we knew that we could get the outcome we wanted by even</Cue>
<Cue start="26:57" end="27:01">just using a smaller or less having less resolution in our image.</Cue>
<Cue start="27:01" end="27:04">And therefore, as we transferred it from the mobile device storage device</Cue>
<Cue start="27:04" end="27:08">up into the cloud, we wanted that smaller image just for transfer purposes</Cue>
<Cue start="27:08" end="27:11">and it still we could get the accuracy we needed by a lot of testing.</Cue>
<Cue start="27:11" voice="Burr Sutter" />
<Cue start="27:11" end="27:14">And one thing that's interesting about that from my perspective is</Cue>
<Cue start="27:15" end="27:18">if you're doing image processing, sometimes it takes a while</Cue>
<Cue start="27:18" end="27:20">for this transaction to occur.</Cue>
<Cue start="27:20" end="27:20">Like I,</Cue>
<Cue start="27:20" end="27:24">I come from a traditional application background, you know, where I'm reading</Cue>
<Cue start="27:24" end="27:25">and writing things from a database</Cue>
<Cue start="27:25" end="27:28">or a message broker or moving data from one place to another.</Cue>
<Cue start="27:28" end="27:29">Those things happen subsequent.</Cue>
<Cue start="27:29" end="27:33">Normally, even with great latency between your data centers, you know,</Cue>
<Cue start="27:33" end="27:34">it's still subsequent.</Cue>
<Cue start="27:34" end="27:38">In most cases, while on a transaction like this, one can actually take 2 seconds</Cue>
<Cue start="27:38" end="27:42">or 4 seconds as it's doing its analysis and actually coming back with, you know,</Cue>
<Cue start="27:42" end="27:46">I think it's a dog, I think it's a kidney, I think it's whatever, and provided me</Cue>
<Cue start="27:46" end="27:48">that accuracy statement.</Cue>
<Cue start="27:48" end="27:51">So that concept of optimization is very important</Cue>
<Cue start="27:51" end="27:53">in the overall application architecture.</Cue>
<Cue start="27:53" end="27:56">Would you agree with that or how do you think about that concept?</Cue>
<Cue start="27:56" end="27:56">Yeah, definitely.</Cue>
<Cue start="27:56" voice="Ryan Loney" />
<Cue start="27:56" end="27:58">It depends too on the use case.</Cue>
<Cue start="27:58" end="28:02">So if you think about how important it is to reduce the latency</Cue>
<Cue start="28:02" end="28:06">and increase the number of frames per second that you can process when you're</Cue>
<Cue start="28:06" end="28:10">talking about a loss prevention model that's running at a grocery store.</Cue>
<Cue start="28:10" end="28:13">So you want to keep the lines moving.</Cue>
<Cue start="28:13" end="28:16">You don't want every person who's at the self-checkout</Cue>
<Cue start="28:16" end="28:19">to have to wait 5 seconds for every item they scan.</Cue>
<Cue start="28:19" end="28:22">You need it to happen as quickly as possible.</Cue>
<Cue start="28:22" end="28:25">And if sometimes you, you know, the accuracy</Cue>
<Cue start="28:25" end="28:28">decreases slightly or the I'd say the accuracy of the whole pipeline.</Cue>
<Cue start="28:28" end="28:32">So not just looking at the individual model or the individual inference, but</Cue>
<Cue start="28:32" end="28:36">let's say that the the whole pipeline is not as successful at detecting</Cue>
<Cue start="28:37" end="28:40">when somebody steals one item from the self-checkout,</Cue>
<Cue start="28:41" end="28:43">it's not going to be a life threatening situation.</Cue>
<Cue start="28:43" end="28:47">Whereas, you know, being in the hooked up to the X-ray machine</Cue>
<Cue start="28:47" end="28:51">with the two placement model, they might be willing to have the doctor,</Cue>
<Cue start="28:51" end="28:54">the nurse wait 5 seconds to get the result.</Cue>
<Cue start="28:55" voice="Ryan Loney" />
<Cue start="28:55" end="28:58">They don't need it to happen in 500 milliseconds.</Cue>
<Cue start="28:58" end="29:02">So they're willing their threshold for waiting is a little bit higher.</Cue>
<Cue start="29:02" end="29:05">So that, I think, also drives some of the decision, like</Cue>
<Cue start="29:06" end="29:09">you want to keep people moving through the checkout line</Cue>
<Cue start="29:09" end="29:13">and you can afford to to potentially if you lose a little bit of accuracy here</Cue>
<Cue start="29:13" end="29:14">and there, it's not going to</Cue>
<Cue start="29:14" end="29:18">cost the company that much money or it's not going to be life threatening.</Cue>
<Cue start="29:18" end="29:21">It's going to be worth the tradeoff of keeping the line moving</Cue>
<Cue start="29:21" end="29:24">and not having people leave the store and not check out at all.</Cue>
<Cue start="29:24" end="29:27">And to say, I'm not going to shop today because the line's too long.</Cue>
<Cue start="29:30" voice="Burr Sutter" />
<Cue start="29:30" end="29:32">There are so many trade offs and enterprise</Cue>
<Cue start="29:32" end="29:35">AML use cases, things like latency, accuracy and availability.</Cue>
<Cue start="29:35" end="29:40">And certainly complexities abound, especially in an obviously ever evolving</Cue>
<Cue start="29:40" end="29:43">technological landscape where we are still very early in the adoption of AML.</Cue>
<Cue start="29:44" end="29:47">And to navigate that complexity, the direct feedback from real world</Cue>
<Cue start="29:47" end="29:51">end users is essential to Ryan and his team at Intel.</Cue>
<Cue start="29:52" end="29:54">What would you say are some of the big hurdles or big</Cue>
<Cue start="29:54" end="29:57">outcomes, big opportunities in that space?</Cue>
<Cue start="29:57" end="30:01">And do you agree that we're kind of still at the very beginning in our infancy,</Cue>
<Cue start="30:01" end="30:01">if you will,</Cue>
<Cue start="30:01" end="30:05">of adopting these technologies and and discovering what they can do for us?</Cue>
<Cue start="30:05" voice="Ryan Loney" />
<Cue start="30:05" end="30:07">Yeah, I think we're definitely in the infancy</Cue>
<Cue start="30:07" end="30:10">and I think that what we've seen is our customers are evolving</Cue>
<Cue start="30:10" end="30:14">and the people who are deploying on Intel hardware, they're trying to run</Cue>
<Cue start="30:14" end="30:16">more complicated models.</Cue>
<Cue start="30:16" end="30:19">They're the models that are doing object detection or, you know,</Cue>
<Cue start="30:19" end="30:22">detecting defects and, you know, doing segmentation.</Cue>
<Cue start="30:23" end="30:27">You know, in the past you could say, oh, here's a generic model that will do face</Cue>
<Cue start="30:27" end="30:31">detection or person detection or vehicle detection and license plate detection.</Cue>
<Cue start="30:32" end="30:33">And those are sort of like</Cue>
<Cue start="30:33" end="30:36">general purpose models that you can just grab off the shelf and use them.</Cue>
<Cue start="30:37" end="30:40">But now we're moving into like the anomaly scenarios</Cue>
<Cue start="30:40" end="30:44">where I've got my own data and I'm trying to do something very specific</Cue>
<Cue start="30:45" end="30:47">and I'm the only one that has access to this data.</Cue>
<Cue start="30:47" end="30:51">And you don't have a public data set that you can go download</Cue>
<Cue start="30:51" end="30:54">that's under Creative Commons license for, you know, car batteries.</Cue>
<Cue start="30:54" end="30:57">It's, you know, it's just not something that's available.</Cue>
<Cue start="30:57" voice="Ryan Loney" />
<Cue start="30:57" end="31:02">And so those use cases, the challenge with with training those models</Cue>
<Cue start="31:02" end="31:06">and and getting them optimized is the beginning of the pipeline.</Cue>
<Cue start="31:06" end="31:10">It's the data you have to get the data you have to annotated</Cue>
<Cue start="31:10" end="31:12">and the tools have to exist for you to do that.</Cue>
<Cue start="31:12" end="31:15">And that's part of the problem that we're trying to help solve.</Cue>
<Cue start="31:16" end="31:17">And then the models are getting more complex.</Cue>
<Cue start="31:17" end="31:21">So if you think, you know, just from working with customers recently,</Cue>
<Cue start="31:21" end="31:22">you know, they're no longer</Cue>
<Cue start="31:22" end="31:26">just trying to do image classification and, you know, like is it a dog or a cat?</Cue>
<Cue start="31:26" end="31:29">They've moved on to like 3D point clouds</Cue>
<Cue start="31:29" end="31:34">and, you know, 3D segmentation models and things that are like the speech</Cue>
<Cue start="31:34" end="31:39">synthesis example, doing things these GPT models that are generating,</Cue>
<Cue start="31:40" end="31:44">you know, you, you put a text input and it generates an image for you.</Cue>
<Cue start="31:44" end="31:47">It's just becoming much more advanced, much more sophisticated</Cue>
<Cue start="31:48" end="31:50">and on larger images.</Cue>
<Cue start="31:50" voice="Ryan Loney" />
<Cue start="31:50" end="31:54">And so things like running super resolution enhancing images, upscaling</Cue>
<Cue start="31:54" end="31:59">images, instead of just trying to take that, you know, 200 by 200 pixel</Cue>
<Cue start="32:00" end="32:02">image and classifying if it's a cat.</Cue>
<Cue start="32:02" end="32:05">Now we're talking about gigantic</Cue>
<Cue start="32:05" end="32:09">huge images that we're processing and that all requires</Cue>
<Cue start="32:09" end="32:12">more resources or more optimized models.</Cue>
<Cue start="32:13" end="32:16">And, you know, every computer vision conference or A.I.</Cue>
<Cue start="32:16" end="32:19">conference, there's there's a new latest and greatest architecture.</Cue>
<Cue start="32:19" end="32:22">There's new research paper, and things are getting adopted much faster.</Cue>
<Cue start="32:23" end="32:27">The lead time for a nurse paper or CV PR</Cue>
<Cue start="32:27" end="32:30">for a company to actually adopt and put those into production.</Cue>
<Cue start="32:30" end="32:32">It's like the time shortens every year.</Cue>
<Cue start="32:33" voice="Burr Sutter" />
<Cue start="32:33" end="32:35">Well, Ryan, I got to tell you, I could talk to you</Cue>
<Cue start="32:35" end="32:39">literally all day about these topics, the various use cases, the various ways</Cue>
<Cue start="32:39" end="32:41">models are being optimized,</Cue>
<Cue start="32:41" end="32:44">how to put models into a pipeline for average enterprise applications.</Cue>
<Cue start="32:44" end="32:47">I've enjoyed learning about pop and vino and anomalies,</Cue>
<Cue start="32:47" end="32:50">but I'm fascinated by this because I will have a chance to go try this myself.</Cue>
<Cue start="32:51" end="32:52">Taking advantage of Red Hat OpenShift</Cue>
<Cue start="32:52" end="32:54">and taking advantage of our data science platform.</Cue>
<Cue start="32:54" end="32:58">On top of that, I will definitely go be poking at this myself.</Cue>
<Cue start="32:58" end="33:00">So thank you so much for your time today.</Cue>
<Cue start="33:00" voice="Ryan Loney" />
<Cue start="33:00" end="33:00">Thanks, Burr.</Cue>
<Cue start="33:00" end="33:01">This was a lot of fun.</Cue>
<Cue start="33:01" end="33:04">Thanks for having me.</Cue>
<Cue start="33:04" voice="Burr Sutter" />
<Cue start="33:04" end="33:06">And you can check out</Cue>
<Cue start="33:06" end="33:09">the full transcript of our conversation and more resources,</Cue>
<Cue start="33:09" end="33:12">like a link to a white paper on open vino and normal lib at Red Hat dot</Cue>
<Cue start="33:12" end="33:15">com slash code Comments Podcast.</Cue>
<Cue start="33:15" end="33:19">This episode was produced by Brant Seminole and Caroline Prickett.</Cue>
<Cue start="33:20" end="33:21">Our sound designer is Christian.</Cue>
<Cue start="33:21" end="33:26">From our audio team includes Lee Day, Stephanie Wunderlich, Mike Esser,</Cue>
<Cue start="33:27" end="33:32">Laura Barnes, Claire Allison, Nick Burns, Aaron Williamson, Karen King,</Cue>
<Cue start="33:32" end="33:36">Booboo House, Rachel Artell, Mike Compton, Ocean</Cue>
<Cue start="33:36" end="33:40">Mathews, Laura Walters, Alex Trabelsi and Victoria Lutton.</Cue>
<Cue start="33:41" end="33:43">I'm your host, Burt Sutter.</Cue>
<Cue start="33:43" end="33:45">Thank you for joining me today on Code Comments.</Cue>
<Cue start="33:45" end="33:48">I hope you enjoyed today's session and today's conversation, and I</Cue>
<Cue start="33:48" end="33:52">look forward to many more in.</Cue>
</Transcript>
</AudioPlayer>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css" />
);Heading Levels
Edit element properties
import '@rhds/elements/rh-audio-player/rh-audio-player.js';#heading-levels {
padding: var(--rh-space-xl, 24px);
}<section id="heading-levels">
<p>Audio player should automatically calculate it's heading levels</p>
<h3>Root Level h3</h3>
<p>Transcript should be <code>h5</code>, cues should be <code>h6</code></p>
<rh-audio-player layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h4 slot="title">Bringing Deep Learning to Enterprise Applications</h4>
<rh-audio-player-about slot="about">
<h5 slot="heading">About the episode</h5>
<p>
There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.
</p>
<p>
Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.
</p>
<rh-avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools, <em>Intel®</em></span>
</rh-avatar>
</rh-audio-player-about>
<audio crossorigin="anonymous" slot="media" controls="">
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3">
</audio>
<rh-audio-player-subscribe slot="subscribe">
<h5 slot="heading">Subscribe</h5>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts">
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify">
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts">
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img class="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed">
</a>
</rh-audio-player-subscribe>
<rh-transcript slot="transcript">
<rh-cue start="00:02" voice="Burr Sutter"></rh-cue>
<rh-cue start="00:02" end="00:04">Hi, I'm Burr Sutter.</rh-cue>
<rh-cue start="00:04" end="00:05">I'm a Red Hatter</rh-cue>
<rh-cue start="00:05" end="00:08">who spends a lot of time talking to technologists about technologies.</rh-cue>
<rh-cue start="00:09" end="00:10">We say this a lot of Red Hat.</rh-cue>
<rh-cue start="00:10" end="00:14">No single technology provider holds the key to success, including us.</rh-cue>
<rh-cue start="00:15" end="00:17">And I would say the same thing about myself.</rh-cue>
<rh-cue start="00:17" end="00:18">I love to share ideas.</rh-cue>
<rh-cue start="00:18" end="00:19">So I thought it'd be awesome</rh-cue>
<rh-cue start="00:19" end="00:22">to talk to some brilliant technologists at Red Hat Partners.</rh-cue>
<rh-cue start="00:23" end="00:26">This is Code Comments, an original podcast</rh-cue>
<rh-cue start="00:26" end="00:29">from Red Hat.</rh-cue>
<rh-cue start="00:29" voice="Burr Sutter"></rh-cue>
<rh-cue start="00:29" end="00:32">I'm sure, like many of you here, you have been thinking about</rh-cue>
<rh-cue start="00:32" end="00:36">AI, ML, artificial intelligence and machine learning.</rh-cue>
<rh-cue start="00:36" end="00:38">I've been thinking about that for quite some time</rh-cue>
<rh-cue start="00:38" end="00:39">and actually had the opportunity</rh-cue>
<rh-cue start="00:39" end="00:43">to work on a few successful projects here at Red Hat using those technologies,</rh-cue>
<rh-cue start="00:43" end="00:46">actually enabling a dataset, gathering a dataset,</rh-cue>
<rh-cue start="00:46" end="00:49">working with data scientists and data engineering team,</rh-cue>
<rh-cue start="00:49" end="00:51">and then training a model and putting that model into production</rh-cue>
<rh-cue start="00:51" end="00:53">runtime environment.</rh-cue>
<rh-cue start="00:53" end="00:55">It was an exciting set of projects and you can kind of see</rh-cue>
<rh-cue start="00:55" end="00:58">those on numerous YouTube videos I have published out there before.</rh-cue>
<rh-cue start="00:59" end="01:01">But I want you to think about the problem space a little bit</rh-cue>
<rh-cue start="01:01" end="01:04">because there are some interesting challenges about AI/ML.</rh-cue>
<rh-cue start="01:04" end="01:06">One is simply just getting access to the data,</rh-cue>
<rh-cue start="01:06" end="01:09">and while there are numerous publicly available datasets</rh-cue>
<rh-cue start="01:09" end="01:12">when it comes to your specific enterprise use case, you might not be to find</rh-cue>
<rh-cue start="01:12" end="01:14">publicly available data.</rh-cue>
<rh-cue start="01:14" voice="Burr Sutter"></rh-cue>
<rh-cue start="01:14" end="01:17">In many cases, you cannot, even for our applications that we created,</rh-cue>
<rh-cue start="01:17" end="01:20">we had to create our dataset, capture our dataset,</rh-cue>
<rh-cue start="01:21" end="01:24">explore the dataset, and of course train a model accordingly.</rh-cue>
<rh-cue start="01:24" end="01:27">And we also found there's another challenge to be overcome</rh-cue>
<rh-cue start="01:27" end="01:30">in this AML world, and that is access to certain types of hardware.</rh-cue>
<rh-cue start="01:31" end="01:33">If you think about the enterprise environment</rh-cue>
<rh-cue start="01:33" end="01:36">and the creation of an enterprise application specifically for AML</rh-cue>
<rh-cue start="01:37" end="01:40">and users need an inference engine to run on their hardware,</rh-cue>
<rh-cue start="01:40" end="01:43">hardware that's available to them to be effective for their application.</rh-cue>
<rh-cue start="01:43" end="01:45">Let's say an application like computer vision,</rh-cue>
<rh-cue start="01:45" end="01:49">one that can detect anomalies in medical imaging or maybe on a factory floor,</rh-cue>
<rh-cue start="01:49" end="01:52">You know, those things are whizzing by on the factory line.</rh-cue>
<rh-cue start="01:52" end="01:55">They're looking at them and trying to determine if there is an error or not.</rh-cue>
<rh-cue start="01:56" voice="Burr Sutter"></rh-cue>
<rh-cue start="01:56" end="01:58">Well, how do you actually make it run on your hardware,</rh-cue>
<rh-cue start="01:58" end="02:01">your accessible technology that you have today?</rh-cue>
<rh-cue start="02:01" end="02:05">Well, there's a solution for this as an open toolkit called Open vino.</rh-cue>
<rh-cue start="02:05" end="02:07">And you might be thinking, hey, wait a minute,</rh-cue>
<rh-cue start="02:07" end="02:10">don't you need a GPU for a I inferencing a GPU</rh-cue>
<rh-cue start="02:10" end="02:12">for artificial intelligence machine learning?</rh-cue>
<rh-cue start="02:12" end="02:15">Well, not according to Ryan Loney, product manager of Open Vino Developer</rh-cue>
<rh-cue start="02:15" end="02:16">Tools at Intel.</rh-cue>
<rh-cue start="02:20" voice="Ryan Loney"></rh-cue>
<rh-cue start="02:20" end="02:20">I guess we'll</rh-cue>
<rh-cue start="02:20" end="02:23">start with trying to maybe dispel the myths, right?</rh-cue>
<rh-cue start="02:23" end="02:27">I think that CPUs are widely used for inference today.</rh-cue>
<rh-cue start="02:27" end="02:32">So and if we look at the data center segment, you know, about 70% of the A.I.</rh-cue>
<rh-cue start="02:32" end="02:36">inference is happening on Intel Xeon on our data center CPUs.</rh-cue>
<rh-cue start="02:36" end="02:40">And so you don't needed a GPU, especially for running inference.</rh-cue>
<rh-cue start="02:40" end="02:43">And that's part of the value of open vino, is that we're you know,</rh-cue>
<rh-cue start="02:43" end="02:47">we're taking models that may have been trained on a GPU</rh-cue>
<rh-cue start="02:47" end="02:50">using deep learning frameworks like PyTorch or TensorFlow</rh-cue>
<rh-cue start="02:51" end="02:54">and then optimizing them to run on Intel hardware.</rh-cue>
<rh-cue start="02:57" voice="Burr Sutter"></rh-cue>
<rh-cue start="02:56" end="03:00">Ryan joined me to discuss AI/ML and the enterprise</rh-cue>
<rh-cue start="03:00" end="03:03">across various industries and exploring numerous use cases.</rh-cue>
<rh-cue start="03:05" end="03:08">Let's talk a little bit about the origin story behind Open Vino.</rh-cue>
<rh-cue start="03:08" end="03:10">Tell us more about it and how it came to be</rh-cue>
<rh-cue start="03:10" end="03:13">and why it came out of Intel.</rh-cue>
<rh-cue start="03:12" voice="Ryan Loney"></rh-cue>
<rh-cue start="03:12" end="03:16">Definitely. So we had the first release of Open Vino</rh-cue>
<rh-cue start="03:16" end="03:20">was back in 2018, so still relatively new.</rh-cue>
<rh-cue start="03:20" end="03:25">And at that time we were focused on computer vision and pretty tightly coupled</rh-cue>
<rh-cue start="03:25" end="03:31">with open CV, which is another open source library with origins at Intel.</rh-cue>
<rh-cue start="03:31" end="03:31">You know, it</rh-cue>
<rh-cue start="03:31" end="03:36">had its first release back in 1999, so it's been around a little bit longer.</rh-cue>
<rh-cue start="03:36" end="03:40">And many of the software engineers and architects at Intel</rh-cue>
<rh-cue start="03:40" end="03:45">that were involved with and contributing to open CV are working on open Vino.</rh-cue>
<rh-cue start="03:45" end="03:49">So you can think of open vino as complementary software to open CV.</rh-cue>
<rh-cue start="03:50" end="03:53">And we're providing like an engine for executing inference</rh-cue>
<rh-cue start="03:53" end="03:57">as part of a computer vision pipeline, or at least that's how we started.</rh-cue>
<rh-cue start="03:58" voice="Ryan Loney"></rh-cue>
<rh-cue start="03:58" end="04:01">But since 2018, we've we've started to move beyond</rh-cue>
<rh-cue start="04:01" end="04:02">just computer vision inference.</rh-cue>
<rh-cue start="04:02" end="04:05">So when I say computer vision inference, I mean like image</rh-cue>
<rh-cue start="04:05" end="04:08">classification, object detection, segmentation.</rh-cue>
<rh-cue start="04:09" end="04:12">And now we're moving into natural language processing, things</rh-cue>
<rh-cue start="04:12" end="04:16">like speech synthesis, speech recognition, knowledge, graphs,</rh-cue>
<rh-cue start="04:17" end="04:21">time series forecasting, and other use cases that don't involve</rh-cue>
<rh-cue start="04:21" end="04:24">computer vision and don't involve inference on pixels.</rh-cue>
<rh-cue start="04:25" end="04:28">Our latest release, the 20 22.1 that came out earlier this year,</rh-cue>
<rh-cue start="04:29" end="04:32">there was a most significant update that we've had to open vino</rh-cue>
<rh-cue start="04:32" end="04:36">since we started in 2018, and the major focus of that release</rh-cue>
<rh-cue start="04:36" end="04:40">was optimizing for use cases that go beyond computer vision.</rh-cue>
<rh-cue start="04:41" voice="Burr Sutter"></rh-cue>
<rh-cue start="04:41" end="04:44">And I like that concept that you just mentioned right there, computer vision.</rh-cue>
<rh-cue start="04:44" end="04:47">And you said that you extended those use cases and went beyond that.</rh-cue>
<rh-cue start="04:47" end="04:50">So could you give us more concrete examples of computer vision?</rh-cue>
<rh-cue start="04:50" voice="Ryan Loney"></rh-cue>
<rh-cue start="04:50" end="04:50">Yeah, sure.</rh-cue>
<rh-cue start="04:50" end="04:55">So when you think about manufacturing quality control in factories, everything</rh-cue>
<rh-cue start="04:55" end="05:01">from ARC welding, defect detection to inspecting BMW cars on assembly lines,</rh-cue>
<rh-cue start="05:02" end="05:05">they're using cameras or sensors to collect data.</rh-cue>
<rh-cue start="05:05" end="05:11">And usually it's cameras collecting images like RGV images that you and I can see.</rh-cue>
<rh-cue start="05:11" end="05:14">And looks like something taken from a camera or video camera,</rh-cue>
<rh-cue start="05:15" end="05:19">but also things like infrared or computerized tomography</rh-cue>
<rh-cue start="05:19" end="05:24">scans used in health care, X-ray, different types of images where we can</rh-cue>
<rh-cue start="05:25" end="05:28">draw bounding boxes around regions of interest</rh-cue>
<rh-cue start="05:29" end="05:32">and say, you know, this is a defect or this is not a defect.</rh-cue>
<rh-cue start="05:32" end="05:37">And also, is this worker wearing a safety hat or did they forget to put it on?</rh-cue>
<rh-cue start="05:37" end="05:41">And so you can take this and integrate it into a pipeline</rh-cue>
<rh-cue start="05:41" end="05:44">where you're triggering an alert if somebody forgets</rh-cue>
<rh-cue start="05:44" end="05:49">to wear their safety mask or if there's a defect in a product</rh-cue>
<rh-cue start="05:49" end="05:53">on an assembly line, you can just use cameras and open</rh-cue>
<rh-cue start="05:53" end="05:58">vino and open CV running these on Intel hardware and help to analyze.</rh-cue>
<rh-cue start="05:58" voice="Ryan Loney"></rh-cue>
<rh-cue start="05:58" end="06:01">And that's what a lot of the partners that we work with are doing.</rh-cue>
<rh-cue start="06:01" end="06:03">So these independent software vendors</rh-cue>
<rh-cue start="06:03" end="06:06">and there's other use cases for things like retail.</rh-cue>
<rh-cue start="06:06" end="06:10">You think about going to a store and using an automated checkout system.</rh-cue>
<rh-cue start="06:11" end="06:13">You know, sometimes people use those automated checkouts</rh-cue>
<rh-cue start="06:13" end="06:17">and they they slide a few extra items into their bag that they don't scan.</rh-cue>
<rh-cue start="06:17" end="06:21">And it's a huge loss for the retail outlets</rh-cue>
<rh-cue start="06:21" end="06:25">that are providing this way to check out real time shelf monitoring.</rh-cue>
<rh-cue start="06:25" end="06:29">We have this bear on one of our is fees that helps keep store shelves</rh-cue>
<rh-cue start="06:29" end="06:33">stocked by just analyzing the cameras in the stores, detecting</rh-cue>
<rh-cue start="06:33" end="06:37">when objects are missing from the shelves so that they can be restocked.</rh-cue>
<rh-cue start="06:37" end="06:41">We have Vistry, another ISP that works with quick service restaurants.</rh-cue>
<rh-cue start="06:41" end="06:44">So when you think about automating the process of</rh-cue>
<rh-cue start="06:44" end="06:48">when do I drop the fries into the fryer so that they're warm</rh-cue>
<rh-cue start="06:48" end="06:50">when the car gets to the drive thru window,</rh-cue>
<rh-cue start="06:50" end="06:54">you know, there's quite a bit of industrial health care retail examples</rh-cue>
<rh-cue start="06:54" end="06:57">that we can walk through and we should dig into some more of those.</rh-cue>
<rh-cue start="06:57" voice="Burr Sutter"></rh-cue>
<rh-cue start="06:57" end="06:59">But I got to tell you, I have I have a personal experience</rh-cue>
<rh-cue start="06:59" end="06:59">in this category</rh-cue>
<rh-cue start="06:59" end="07:01">that I want to share with, and you can tell me how</rh-cue>
<rh-cue start="07:01" end="07:03">how silly you might think at this point in time.</rh-cue>
<rh-cue start="07:03" end="07:04">It is.</rh-cue>
<rh-cue start="07:04" end="07:08">We actually built an AI keynote demonstration for the Red Hat big stage</rh-cue>
<rh-cue start="07:08" end="07:12">back in 2015, and I really want to illustrate the concept of asset tracking.</rh-cue>
<rh-cue start="07:12" end="07:15">So we actually gave everybody in the conference a little Bluetooth token,</rh-cue>
<rh-cue start="07:16" end="07:19">but a little battery, a little watch battery and a little Bluetooth emitter.</rh-cue>
<rh-cue start="07:19" end="07:22">And we basically tracked those things around the conference.</rh-cue>
<rh-cue start="07:22" end="07:24">We basically put a Raspberry Pi in each of the meeting rooms</rh-cue>
<rh-cue start="07:24" end="07:26">and up in the lunch room, and you could see how the tokens</rh-cue>
<rh-cue start="07:26" end="07:30">moved from room to room to room as a relatively simple application.</rh-cue>
<rh-cue start="07:30" voice="Burr Sutter"></rh-cue>
<rh-cue start="07:30" end="07:32">But it occurred to me after we figured out,</rh-cue>
<rh-cue start="07:32" end="07:34">okay, how to do that with Bluetooth and triangulating</rh-cue>
<rh-cue start="07:34" end="07:39">Bluetooth signals by looking at relative signal strength from one radio to another</rh-cue>
<rh-cue start="07:39" end="07:42">and putting that through an Apache Spark application at the time,</rh-cue>
<rh-cue start="07:42" end="07:45">we then realized, you know what, this is easier done with cameras</rh-cue>
<rh-cue start="07:45" end="07:49">and just simply looking at a camera and having some form of animal</rh-cue>
<rh-cue start="07:49" end="07:51">or machine learning model that would say, Oh,</rh-cue>
<rh-cue start="07:51" end="07:53">there are people here now are there are no people here now.</rh-cue>
<rh-cue start="07:53" end="07:55">What do you think about that?</rh-cue>
<rh-cue start="07:55" voice="Ryan Loney"></rh-cue>
<rh-cue start="07:55" end="07:59">Yeah, I mean, what you just described is sort of exactly that the product</rh-cue>
<rh-cue start="07:59" end="08:02">that either one of our partners is offering,</rh-cue>
<rh-cue start="08:02" end="08:04">you know, that they're doing it with computer vision and cameras.</rh-cue>
<rh-cue start="08:04" end="08:08">So when partner tries to help retail stores</rh-cue>
<rh-cue start="08:08" end="08:12">analyze the foot traffic and understand with Heatmaps,</rh-cue>
<rh-cue start="08:12" end="08:16">where people are spending the most time in stores, how many people are coming</rh-cue>
<rh-cue start="08:16" end="08:19">in, what size groups are coming into the store,</rh-cue>
<rh-cue start="08:19" end="08:23">you know, and trying to help understand if there was a successful transaction</rh-cue>
<rh-cue start="08:23" end="08:27">from the people who entered the store and left the store so that you can,</rh-cue>
<rh-cue start="08:27" end="08:30">you know, to help with the, you know, retail analytics</rh-cue>
<rh-cue start="08:30" end="08:33">and marketing sales and positioning of products.</rh-cue>
<rh-cue start="08:34" end="08:37">And so they're doing that in a way that also protects privacy.</rh-cue>
<rh-cue start="08:37" end="08:38">And that's something that's really important.</rh-cue>
<rh-cue start="08:38" end="08:41">So when you talked about those Bluetooth beacons, probably,</rh-cue>
<rh-cue start="08:41" end="08:44">
you know, if everyone who walked into a grocery store was asked
</rh-cue>
<rh-cue start="08:44" end="08:49">
to put a tracking device in their cart or on their person and say, you know,
</rh-cue>
<rh-cue start="08:49" end="08:50">
you're going
</rh-cue>
<rh-cue start="08:50" end="08:53">
to be tracked around the store, they probably wouldn't want to do that.
</rh-cue>
<rh-cue start="08:53" end="08:56">
The way that you can do this with cameras is you can,
</rh-cue>
<rh-cue start="08:53" voice="Ryan Loney"></rh-cue>
<rh-cue start="08:56" end="09:01">
you know, detect people as they enter and, you know, remove their face.
</rh-cue>
<rh-cue start="09:01" end="09:01">
Right.
</rh-cue>
<rh-cue start="09:01" end="09:05">
So you can ignore any biometric information
</rh-cue>
<rh-cue start="09:05" end="09:08">
and and just track the person based on pixels
</rh-cue>
<rh-cue start="09:09" end="09:12">
that are present in the detected region of interest.
</rh-cue>
<rh-cue start="09:12" end="09:15">
So they're able to analyze, say, a family walks in the door
</rh-cue>
<rh-cue start="09:16" end="09:20">
and they can group those people together with object detection
</rh-cue>
<rh-cue start="09:20" end="09:23">
and then they can track their movement throughout the store
</rh-cue>
<rh-cue start="09:23" end="09:26">
without keeping track of their face or any biometric
</rh-cue>
<rh-cue start="09:26" end="09:30">
or any personal identifiable information to avoid things like bias
</rh-cue>
<rh-cue start="09:30" end="09:35">
and to make sure that they're protecting the privacy of the shoppers in the store
</rh-cue>
<rh-cue start="09:35" end="09:39">
while still getting that really useful marketing analytics data rate
</rh-cue>
<rh-cue start="09:39" end="09:42">
so that they can make better decisions about where to place their products.
</rh-cue>
<rh-cue start="09:42" end="09:45">
So that's one really good example of how
</rh-cue>
<rh-cue start="09:45" end="09:48">
computer vision AI with open vino is being used today.
</rh-cue>
<rh-cue start="09:48" voice="Burr Sutter"></rh-cue>
<rh-cue start="09:48" end="09:51">
And that is a great example because you're definitely spot on.
</rh-cue>
<rh-cue start="09:51" end="09:53">
It is invasive when you hand someone to Bluetooth devices,
</rh-cue>
<rh-cue start="09:53" end="09:56">
say, please keep this with you as you go throughout our our store
</rh-cue>
<rh-cue start="09:56" end="09:59">
or our mall or throughout our hospital, wherever you might be.
</rh-cue>
<rh-cue start="09:59" end="10:01">
Now, you mentioned another example earlier
</rh-cue>
<rh-cue start="10:01" end="10:03">
in the conversation which was related to like worker safety.
</rh-cue>
<rh-cue start="10:03" end="10:05">
Are they wearing a helmet?
</rh-cue>
<rh-cue start="10:05" end="10:08">
I want to talk more about that concept in a real industrial setting,
</rh-cue>
<rh-cue start="10:08" end="10:11">
a manufacturing setting where there might be a factory floor
</rh-cue>
<rh-cue start="10:11" end="10:13">
and there are certain requirements, or better yet, there's like a
</rh-cue>
<rh-cue start="10:13" end="10:16">
a quality assurance requirement, let's say, when it comes to looking
</rh-cue>
<rh-cue start="10:16" end="10:20">
at a factory line, I run to that use case often what some of our customers.
</rh-cue>
<rh-cue start="10:20" end="10:22">
Can you talk more about those kinds of use cases? Yeah.
</rh-cue>
<rh-cue start="10:22" voice="Ryan Loney"></rh-cue>
<rh-cue start="10:22" end="10:27">
So one of our partners, Robuchon and we you know, published a case study
</rh-cue>
<rh-cue start="10:27" end="10:31">
I think last year where they're working with BMW at one of their factories
</rh-cue>
<rh-cue start="10:32" end="10:35">
and they do quality control inspection, but they're also doing
</rh-cue>
<rh-cue start="10:35" end="10:38">
things related to worker safety and analyzing.
</rh-cue>
<rh-cue start="10:38" end="10:40">
You know, I used the safety had example.
</rh-cue>
<rh-cue start="10:40" end="10:45">
There's a number of of our ISP's and partners who have similar use cases.
</rh-cue>
<rh-cue start="10:45" end="10:48">
And it comes down to there's a few reasons
</rh-cue>
<rh-cue start="10:48" end="10:51">
that are motivating this and some are related to like insurance, right?
</rh-cue>
<rh-cue start="10:51" end="10:53">
It's important to make sure that
</rh-cue>
<rh-cue start="10:53" end="10:56">
if you want to have your factory insured and that your workers
</rh-cue>
<rh-cue start="10:56" end="10:58">
are protecting themselves and wearing the gear.
</rh-cue>
<rh-cue start="10:58" end="11:00">
Regulatory compliance. Right.
</rh-cue>
<rh-cue start="11:00" end="11:05">
You're you're being asked to properly protect from exposure to chemicals or,
</rh-cue>
<rh-cue start="11:05" end="11:09">
you know, potentially having something fall and and hit someone on the head.
</rh-cue>
<rh-cue start="11:09" end="11:13">
So wearing a safety vest, wearing goggles, wearing a helmet,
</rh-cue>
<rh-cue start="11:14" end="11:17">
these are things that you need to do inside the factory.
</rh-cue>
<rh-cue start="11:17" end="11:21">
And you can really easily automate and detect and sometimes without bias.
</rh-cue>
<rh-cue start="11:21" voice="Ryan Loney"></rh-cue>
<rh-cue start="11:21" end="11:26">
I think that's one of the interesting things about the robots on BMW example
</rh-cue>
<rh-cue start="11:26" end="11:31">
is that they were also blurring sort of blocking out and so drawing a box
</rh-cue>
<rh-cue start="11:31" end="11:35">
to cover the face of the workers in the factory
</rh-cue>
<rh-cue start="11:35" end="11:38">
so that somebody who was analyzing the video footage
</rh-cue>
<rh-cue start="11:38" end="11:43">
and getting the alerts saying that, hey, you know, Bay 21 has a worker
</rh-cue>
<rh-cue start="11:43" end="11:47">
without a hat on, that it's not sending their face
</rh-cue>
<rh-cue start="11:47" end="11:50">
and in the alert and potentially, you know, invading
</rh-cue>
<rh-cue start="11:50" end="11:54">
or going against privacy laws or just the ethics of the company.
</rh-cue>
<rh-cue start="11:54" end="11:54">
Right.
</rh-cue>
<rh-cue start="11:54" end="11:58">
They don't want to introduce bias or have people targeted because
</rh-cue>
<rh-cue start="11:58" end="12:02">
it's much better to to have it be, you know, blur the face
</rh-cue>
<rh-cue start="12:02" end="12:06">
and alert and have somebody take care of it on the floor.
</rh-cue>
<rh-cue start="12:06" end="12:09">
And then if you ever need to audit that information later,
</rh-cue>
<rh-cue start="12:09" end="12:12">
they have a way to do it where people who need to be able to see
</rh-cue>
<rh-cue start="12:12" end="12:17">
who the employee was and look up their personal information, they can do that.
</rh-cue>
<rh-cue start="12:17" voice="Ryan Loney"></rh-cue>
<rh-cue start="12:17" end="12:20">
But then just for the purposes of maintaining safety,
</rh-cue>
<rh-cue start="12:20" end="12:21">
they don't need to have access
</rh-cue>
<rh-cue start="12:21" end="12:24">
to that personal information or biometric information,
</rh-cue>
<rh-cue start="12:25" end="12:28">
because that's one thing that when you hear about computer vision
</rh-cue>
<rh-cue start="12:28" end="12:31">
or object person tracking, object detection,
</rh-cue>
<rh-cue start="12:32" end="12:36">
there's a lot of concern, and rightfully so, about privacy
</rh-cue>
<rh-cue start="12:36" end="12:40">
being invaded and about tracking information, face ID,
</rh-cue>
<rh-cue start="12:41" end="12:45">
identifying people who may have committed crimes through video footage.
</rh-cue>
<rh-cue start="12:45" end="12:48">
And that's just not something that a lot of companies want to
</rh-cue>
<rh-cue start="12:49" end="12:51">
you know, they want to protect privacy
</rh-cue>
<rh-cue start="12:51" end="12:52">
and they don't they don't want to be in a situation
</rh-cue>
<rh-cue start="12:52" end="12:55">
where they might be violating someone's rights.
</rh-cue>
<rh-cue start="12:56" voice="Burr Sutter"></rh-cue>
<rh-cue start="12:56" end="12:58">
Well, privacy is certainly opening up Pandora's box.
</rh-cue>
<rh-cue start="12:58" end="13:00">
There's a lot to be explored in that area,
</rh-cue>
<rh-cue start="13:00" end="13:02">
especially in a digital world that we now live in.
</rh-cue>
<rh-cue start="13:02" end="13:05">
But for now, let's move on and explore different area.
</rh-cue>
<rh-cue start="13:05" end="13:08">
I'm interested in how machines and computers offer advantages,
</rh-cue>
<rh-cue start="13:08" end="13:12">
specifically in certain use cases like a quality control scenario.
</rh-cue>
<rh-cue start="13:12" end="13:15">
I asked Ryan to explain how AML and specifically machines
</rh-cue>
<rh-cue start="13:15" end="13:18">
computers can augment that capability.
</rh-cue>
<rh-cue start="13:19" voice="Ryan Loney"></rh-cue>
<rh-cue start="13:19" end="13:22">
I can give a specific example where we have a partner
</rh-cue>
<rh-cue start="13:22" end="13:25">
that's there doing defect detection with
</rh-cue>
<rh-cue start="13:25" end="13:28">
and looking for anomalies in batteries.
</rh-cue>
<rh-cue start="13:28" end="13:31">
So, you know, sure, you've heard there's a lot of interest right now
</rh-cue>
<rh-cue start="13:31" end="13:34">
in electric vehicles, a lot of batteries being produced.
</rh-cue>
<rh-cue start="13:34" end="13:36">
And so if you go into one of these factories,
</rh-cue>
<rh-cue start="13:36" end="13:40">
they have images that they collect of every battery that's going through this
</rh-cue>
<rh-cue start="13:40" end="13:44">
assembly line and through these images, people
</rh-cue>
<rh-cue start="13:44" end="13:47">
can look and see and visually inspect with their eyes and say,
</rh-cue>
<rh-cue start="13:48" end="13:50">
this battery has a defect, send it back.
</rh-cue>
<rh-cue start="13:50" end="13:53">
And that's one step in the quality control process.
</rh-cue>
<rh-cue start="13:53" end="13:58">
And there's other steps, I'm sure, like running diagnostic tests and, you know,
</rh-cue>
<rh-cue start="13:58" end="14:02">
measuring voltage and doing other types of non-visual inspection.
</rh-cue>
<rh-cue start="14:02" end="14:06">
But for the visual inspection piece where you can really easily identify
</rh-cue>
<rh-cue start="14:06" end="14:10">
some problems, it's much more efficient to introduce computer vision.
</rh-cue>
<rh-cue start="14:11" end="14:14">
And so that's where we have this new library that we've introduced
</rh-cue>
<rh-cue start="14:14" end="14:17">
called Anomali, that's open vino.
</rh-cue>
<rh-cue start="14:17" voice="Ryan Loney"></rh-cue>
<rh-cue start="14:17" end="14:20">
While we're focused on inference, you know, we're also thinking
</rh-cue>
<rh-cue start="14:20" end="14:25">
about the pipeline or the funnel that gets these models to open vino.
</rh-cue>
<rh-cue start="14:25" end="14:28">
And so we've we've invested in this anomaly segmentation,
</rh-cue>
<rh-cue start="14:28" end="14:32">
anomaly detection library and that we've recently open source
</rh-cue>
<rh-cue start="14:32" end="14:35">
and there's a great research paper about it about Anomali.
</rh-cue>
<rh-cue start="14:36" end="14:39">
But the idea is you can take just a few images
</rh-cue>
<rh-cue start="14:39" end="14:43">
and train a model and start detecting these defects.
</rh-cue>
<rh-cue start="14:43" end="14:46">
And so for this battery example, that's a more advanced example.
</rh-cue>
<rh-cue start="14:46" end="14:52">
But to make it simpler, you know, take some bolts and, you know, take ten bolts.
</rh-cue>
<rh-cue start="14:52" end="14:55">
You have one that has a scratch on it or one that is chipped
</rh-cue>
<rh-cue start="14:56" end="14:58">
or has some damage to it.
</rh-cue>
<rh-cue start="14:58" end="15:00">
And you can easily get started in training
</rh-cue>
<rh-cue start="15:00" end="15:03">
to recognize the bolts that do not have an anomaly.
</rh-cue>
<rh-cue start="15:04" end="15:06">
And the ones that do, which is a small data set
</rh-cue>
<rh-cue start="15:06" end="15:10">
and I think that's really one of the most important things today.
</rh-cue>
<rh-cue start="15:11" voice="Ryan Loney"></rh-cue>
<rh-cue start="15:11" end="15:14">
Challenges is one is access to data, but the other is
</rh-cue>
<rh-cue start="15:14" end="15:17">
is needing a massive amount of data to do something meaningful.
</rh-cue>
<rh-cue start="15:18" end="15:22">
And so we're starting to try to change that dynamic with Anomali.
</rh-cue>
<rh-cue start="15:22" end="15:27">
So you may not need 100,000 images, you may need 100 images,
</rh-cue>
<rh-cue start="15:27" end="15:33">
and you can start detecting anomalies in everything from batteries to bolts to,
</rh-cue>
<rh-cue start="15:33" end="15:37">
you know, maybe even the wood varnish use case that you mentioned.
</rh-cue>
<rh-cue start="15:37" voice="Burr Sutter"></rh-cue>
<rh-cue start="15:37" end="15:40">
That is very key point because often in that data scientist
</rh-cue>
<rh-cue start="15:40" end="15:43">
process, that data engineer and data scientist process, right.
</rh-cue>
<rh-cue start="15:43" end="15:44">
The one key thing is can you gather
</rh-cue>
<rh-cue start="15:44" end="15:47">
the data that you need for the input for the model training?
</rh-cue>
<rh-cue start="15:47" end="15:49">
And we've often sat at least people I've worked
</rh-cue>
<rh-cue start="15:49" end="15:52">
with over the last couple of years, you know, you need a lot of data.
</rh-cue>
<rh-cue start="15:52" end="15:55">
You need tens of thousands of correct images
</rh-cue>
<rh-cue start="15:55" end="15:58">
so we can sort out the difference between dogs versus cats, let's say,
</rh-cue>
<rh-cue start="15:58" end="16:01">
or you need dozens and dozens of situations
</rh-cue>
<rh-cue start="16:01" end="16:03">
where if it's a natural language processing scenario,
</rh-cue>
<rh-cue start="16:03" end="16:06">
you know, a good customer interaction, a good customer conversation,
</rh-cue>
<rh-cue start="16:06" end="16:07">
and in this case,
</rh-cue>
<rh-cue start="16:07" end="16:11">
it sounds like what you're saying is show us just the bad things, right?
</rh-cue>
<rh-cue start="16:11" end="16:14">
Fewer images, fewer incorrect things,
</rh-cue>
<rh-cue start="16:14" end="16:17">
and then let us look for those kind of anomalies.
</rh-cue>
<rh-cue start="16:18" end="16:20">
Can tell us more about that because that is very interesting.
</rh-cue>
<rh-cue start="16:20" end="16:23">
The concept that I can use a much smaller dataset as my input
</rh-cue>
<rh-cue start="16:23" end="16:26">
as opposed to gathering terabytes of data in some cases
</rh-cue>
<rh-cue start="16:26" end="16:29">
to just simply get my model training underway.
</rh-cue>
<rh-cue start="16:30" voice="Ryan Loney"></rh-cue>
<rh-cue start="16:30" end="16:34">
You know, like you described, the idea is if you have some good images
</rh-cue>
<rh-cue start="16:34" end="16:37">
and then you have some of the the known defects
</rh-cue>
<rh-cue start="16:38" end="16:41">
and you can just label here's a set of good images
</rh-cue>
<rh-cue start="16:41" end="16:44">
and here's a few of the defects and you can right away
</rh-cue>
<rh-cue start="16:44" end="16:48">
start detecting those specific defects that you've identified.
</rh-cue>
<rh-cue start="16:48" end="16:49">
And then also, you know, be able to
</rh-cue>
<rh-cue start="16:50" end="16:53">
determine when it doesn't match
</rh-cue>
<rh-cue start="16:53" end="16:57">
the expected appearance of a non defective item.
</rh-cue>
<rh-cue start="16:57" end="17:00">
So if I have the undamaged screw and then I introduce
</rh-cue>
<rh-cue start="17:00" end="17:03">
one with some new anomaly that's never been seen before,
</rh-cue>
<rh-cue start="17:04" end="17:07">
I can say, you know, this one is not a valid screw.
</rh-cue>
<rh-cue start="17:07" end="17:11">
And so that's sort of the the approach that we're taking.
</rh-cue>
<rh-cue start="17:11" end="17:15">
And it's really important because so often you need to have
</rh-cue>
<rh-cue start="17:15" end="17:19">
subject matter experts often like if you think the take the battery example,
</rh-cue>
<rh-cue start="17:20" end="17:23">
there's these workers who are on the floor
</rh-cue>
<rh-cue start="17:23" end="17:27">
in a factory and they're the ones who know best when they look at these images,
</rh-cue>
<rh-cue start="17:28" end="17:31">
which one's going to have an issue, which one's defective?
</rh-cue>
<rh-cue start="17:31" voice="Ryan Loney"></rh-cue>
<rh-cue start="17:31" end="17:34">
And then they also need to take that subject matter, expertise
</rh-cue>
<rh-cue start="17:35" end="17:38">
and then use it to annotate data sets.
</rh-cue>
<rh-cue start="17:38" end="17:39">
And when you have these, you know,
</rh-cue>
<rh-cue start="17:39" end="17:43">
tens of thousands of images you need to annotate, it's asking those people
</rh-cue>
<rh-cue start="17:43" end="17:47">
to stop working on the factory floor so they can come annotate some images.
</rh-cue>
<rh-cue start="17:47" end="17:49">
That's a tough business call to make, right?
</rh-cue>
<rh-cue start="17:49" end="17:53">
But if you only need them to annotate a handful of images, it's a much easier
</rh-cue>
<rh-cue start="17:53" end="17:56">
ask to get the ball rolling and demonstrate value.
</rh-cue>
<rh-cue start="17:56" end="17:59">
And maybe over time you will want to annotate more
</rh-cue>
<rh-cue start="17:59" end="18:03">
and more images because you'll get even better accuracy in the model.
</rh-cue>
<rh-cue start="18:03" end="18:07">
Even better, even if it's just small incremental improvements.
</rh-cue>
<rh-cue start="18:08" end="18:11">
You know, that's something that if it generates value for the business,
</rh-cue>
<rh-cue start="18:11" end="18:14">
it's something the business will invest in over time.
</rh-cue>
<rh-cue start="18:14" end="18:17">
But you have to convince the decision makers that it's worth
</rh-cue>
<rh-cue start="18:17" end="18:22">
the time of these subject matter experts to stop what they're doing
</rh-cue>
<rh-cue start="18:22" end="18:26">
and go and label some images of the things that they're working on in the factory.
</rh-cue>
<rh-cue start="18:26" voice="Burr Sutter"></rh-cue>
<rh-cue start="18:26" end="18:30">
And that labeling process can be very labor intensive of the annotations,
</rh-cue>
<rh-cue start="18:30" end="18:33">
basically saying what is correct, what's wrong, what is this, what is that?
</rh-cue>
<rh-cue start="18:33" end="18:36">
And therefore, if we can minimize that time frame to get the value quicker,
</rh-cue>
<rh-cue start="18:36" end="18:40">
then there's something that's useful for the business, useful for the organization
</rh-cue>
<rh-cue start="18:40" end="18:41">
long before we necessarily good.
</rh-cue>
<rh-cue start="18:41" end="18:43">
There are huge model training based,
</rh-cue>
<rh-cue start="18:49" voice="Burr Sutter"></rh-cue>
<rh-cue start="18:49" end="18:52">
so we talk about labeling and how that is labor intensive activity.
</rh-cue>
<rh-cue start="18:52" end="18:54">
But I love the idea of helping the human
</rh-cue>
<rh-cue start="18:54" end="18:57">
and helping the human models specifically not get bored.
</rh-cue>
<rh-cue start="18:57" end="19:01">
Basically, if the human is eyeballing a bunch of widgets flying by over time,
</rh-cue>
<rh-cue start="19:01" end="19:03">
they make mistakes, they get bored
</rh-cue>
<rh-cue start="19:03" end="19:06">
and they don't pay as close attention as they should.
</rh-cue>
<rh-cue start="19:07" end="19:10">
That's why the concept of Amazon specifically computer vision, augmenting
</rh-cue>
<rh-cue start="19:10" end="19:14">
that capability and really helping the human identify anomalies faster,
</rh-cue>
<rh-cue start="19:14" end="19:17">
more quickly, maybe with greater accuracy could be a big win.
</rh-cue>
<rh-cue start="19:18" end="19:21">
We focused on manufacturing, but let's actually go into health care
</rh-cue>
<rh-cue start="19:21" end="19:24">
and learn how these tools can be used in that sector and that industry.
</rh-cue>
<rh-cue start="19:24" end="19:28">
Ryan talked to me about how Open Windows runtime can be incorporated into medical
</rh-cue>
<rh-cue start="19:28" end="19:32">
imaging equipment with intel processors and better than c.T.
</rh-cue>
<rh-cue start="19:32" end="19:34">
MRI and ultrasound machines.
</rh-cue>
<rh-cue start="19:34" end="19:37">
Well, these inferences, this AML workload can be operating
</rh-cue>
<rh-cue start="19:37" end="19:41">
and executing right there in the same physical room as the patient.
</rh-cue>
<rh-cue start="19:44" voice="Ryan Loney"></rh-cue>
<rh-cue start="19:44" end="19:46">
We did a presentation when she last year.
</rh-cue>
<rh-cue start="19:46" end="19:47">
I think they said
</rh-cue>
<rh-cue start="19:47" end="19:50">
there's at least 80 countries that have their X-ray machines deployed
</rh-cue>
<rh-cue start="19:51" end="19:56">
and they're doing things like helping doctors place breathing tubes in patients.
</rh-cue>
<rh-cue start="19:56" end="20:01">
So during COVID, during the pandemic, that was a really important tool
</rh-cue>
<rh-cue start="20:01" end="20:05">
to help with nurses and doctors who were intubating patients
</rh-cue>
<rh-cue start="20:05" end="20:09">
sometimes like in a parking lot or a hallway of the hospital.
</rh-cue>
<rh-cue start="20:09" end="20:14">
And, you know, when they had a statistic that you said, I think one out of four
</rh-cue>
<rh-cue start="20:14" end="20:17">
breathing tubes gets placed incorrectly
</rh-cue>
<rh-cue start="20:17" end="20:19">
when you're doing it outside the operating room,
</rh-cue>
<rh-cue start="20:19" end="20:22">
because when you're in an operating room, it's much more controlled
</rh-cue>
<rh-cue start="20:22" end="20:24">
and there's someone who's an expert at placing the tubes.
</rh-cue>
<rh-cue start="20:24" end="20:28">
It's something you have more of a controlled environment
</rh-cue>
<rh-cue start="20:28" end="20:31">
than when you're out in a parking lot, in a tent.
</rh-cue>
<rh-cue start="20:31" end="20:34">
You know, when the hospital's completely full and you're triaging patients
</rh-cue>
<rh-cue start="20:34" end="20:37">
with COVID, that's when they're more likely to make mistakes.
</rh-cue>
<rh-cue start="20:37" end="20:40">
And so they had this endotracheal tube placement
</rh-cue>
<rh-cue start="20:42" end="20:43">
model that they trained,
</rh-cue>
<rh-cue start="20:43" end="20:47">
and it helped to use an x ray and give an alert and say, hey,
</rh-cue>
<rh-cue start="20:47" end="20:50">
this tube is placed wrong, pull it out and do it again.
</rh-cue>
<rh-cue start="20:50" end="20:53">
And so things like that help doctors so that they can avoid mistakes.
</rh-cue>
<rh-cue start="20:54" end="20:57">
And, you know, having a breathing tube placed incorrectly
</rh-cue>
<rh-cue start="20:57" end="21:01">
can cause collapsed lung and a number of other unwanted side effects.
</rh-cue>
<rh-cue start="21:01" end="21:03">
So it's really important to do it correctly.
</rh-cue>
<rh-cue start="21:03" end="21:06">
Another example is Samsung Medicine.
</rh-cue>
<rh-cue start="21:06" end="21:10">
They actually are doing estimating fetal angle of progression.
</rh-cue>
<rh-cue start="21:10" end="21:13">
So this is analyzing ultrasound
</rh-cue>
<rh-cue start="21:14" end="21:18">
of pregnant women with that, being able to to help take measurements
</rh-cue>
<rh-cue start="21:18" end="21:22">
that are usually hard to calculate that can be done in an automated way.
</rh-cue>
<rh-cue start="21:22" end="21:26">
They're already taking the ultrasound scan and now they're executing this model.
</rh-cue>
<rh-cue start="21:26" end="21:31">
They can take some of these measurements to help the doctor avoid potentially more
</rh-cue>
<rh-cue start="21:31" end="21:34">
intrusive alternative methods so the patient wins.
</rh-cue>
<rh-cue start="21:35" end="21:36">
It makes their life better.
</rh-cue>
<rh-cue start="21:36" end="21:39">
And the doctors is getting help from this A.I.
</rh-cue>
<rh-cue start="21:39" end="21:40">
model.
</rh-cue>
<rh-cue start="21:40" end="21:42">
And those are, you know, just a few examples.
</rh-cue>
<rh-cue start="21:42" voice="Burr Sutter"></rh-cue>
<rh-cue start="21:42" end="21:45">
Those are some amazing examples when it comes to all these things.
</rh-cue>
<rh-cue start="21:45" end="21:49">
We're talking like CT scans, right, and x rays, other examples of computer vision.
</rh-cue>
<rh-cue start="21:49" end="21:52">
One thing that's kind of interesting in the space, I think
</rh-cue>
<rh-cue start="21:52" end="21:56">
whenever I get a chance to work on, let's say an object traction model
</rh-cue>
<rh-cue start="21:56" end="21:58">
and one of our workshops, by the way, is actually putting that out
</rh-cue>
<rh-cue start="21:58" end="22:01">
in front of people to say, Hey, look, you can use your phone.
</rh-cue>
<rh-cue start="22:01" end="22:04">
And it basically sends the image over to our OpenShift, right,
</rh-cue>
<rh-cue start="22:04" end="22:07">
with our data science platform and then analyzes what you see.
</rh-cue>
<rh-cue start="22:08" end="22:09">
And even in my case, where I take a picture of my dog
</rh-cue>
<rh-cue start="22:09" end="22:13">
as an example, it can't really decide is it a dog or a cat?
</rh-cue>
<rh-cue start="22:13" end="22:15">
I have a very funny looking dog,
</rh-cue>
<rh-cue start="22:15" voice="Burr Sutter"></rh-cue>
<rh-cue start="22:15" end="22:18">
and so there's always a percentage outcome, you know?
</rh-cue>
<rh-cue start="22:18" end="22:21">
In other words, I think it's a dog 52%.
</rh-cue>
<rh-cue start="22:21" end="22:22">
So I want to talk about that more.
</rh-cue>
<rh-cue start="22:22" end="22:25">
What how important is it to get to 100% accuracy?
</rh-cue>
<rh-cue start="22:25" end="22:29">
How important is it to really, depending on the use case, to allow
</rh-cue>
<rh-cue start="22:29" end="22:34">
for the gray area, if you will, where it's an 80% accuracy or 70% accuracy?
</rh-cue>
<rh-cue start="22:34" end="22:36">
And where are the trade offs there associated with the application?
</rh-cue>
<rh-cue start="22:36" end="22:38">
Can you can you discuss that more?
</rh-cue>
<rh-cue start="22:38" voice="Ryan Loney"></rh-cue>
<rh-cue start="22:38" end="22:40">
Accuracy is definitely, you know, a touchy subject
</rh-cue>
<rh-cue start="22:40" end="22:43">
because how you measure it makes a huge difference.
</rh-cue>
<rh-cue start="22:43" end="22:46">
And then I think with like what you were describing with the dog example, there's
</rh-cue>
<rh-cue start="22:46" end="22:51">
sort of a top five potential classes that might may be identified.
</rh-cue>
<rh-cue start="22:51" end="22:55">
So let's say you're doing object detection and you detect a region of interest
</rh-cue>
<rh-cue start="22:55" end="22:57">
and it says 65% confidence.
</rh-cue>
<rh-cue start="22:57" end="22:58">
This is a dog.
</rh-cue>
<rh-cue start="22:58" end="23:03">
Well, the next potential label that could be maybe 50% confidence
</rh-cue>
<rh-cue start="23:03" end="23:08">
or 20% confidence might be something similar to a dog or in the case of models
</rh-cue>
<rh-cue start="23:08" end="23:11">
that have been trained on like the image net dataset
</rh-cue>
<rh-cue start="23:11" end="23:15">
or on cocoa data set, they have like actual breeds of dogs.
</rh-cue>
<rh-cue start="23:15" end="23:20">
So if I want to look at the top five labels for a dog,
</rh-cue>
<rh-cue start="23:20" end="23:24">
for my dog, for example, she's a mixed mostly Labrador retriever.
</rh-cue>
<rh-cue start="23:24" voice="Ryan Loney"></rh-cue>
<rh-cue start="23:24" end="23:29">
But I may look at the top five labels and it may say 65% confidence that she's
</rh-cue>
<rh-cue start="23:29" end="23:34">
a flat coated retriever and then confidence that she's a husky,
</rh-cue>
<rh-cue start="23:34" end="23:39">
as you know, 20% and then 5% confidence that she's a greyhound or something.
</rh-cue>
<rh-cue start="23:40" end="23:42">
Those labels, all of them are dogs.
</rh-cue>
<rh-cue start="23:42" end="23:45">
So if I'm just trying to figure out is, is this a dog,
</rh-cue>
<rh-cue start="23:45" end="23:50">
I could probably find all of the, you know, classes within the data set
</rh-cue>
<rh-cue start="23:50" end="23:53">
and say, well, these are all, you know, class ID
</rh-cue>
<rh-cue start="23:53" end="24:00">
65, 132, 92 and 158 all belong to a group of dogs.
</rh-cue>
<rh-cue start="24:00" end="24:04">
So if I wanted to just write an application to tell me if this is a dog
</rh-cue>
<rh-cue start="24:04" end="24:07">
or not, I would probably use that to determine if it's a dog.
</rh-cue>
<rh-cue start="24:08" end="24:10">
But how you measure that is accuracy.
</rh-cue>
<rh-cue start="24:10" end="24:11">
Well, that's where it gets a little bit complicated,
</rh-cue>
<rh-cue start="24:11" end="24:15">
because if you're being really strict about the definition and you're
</rh-cue>
<rh-cue start="24:15" end="24:18">
trying to validate against the data set of labeled images
</rh-cue>
<rh-cue start="24:18" end="24:22">
and I have specific dog breeds or some specific detail
</rh-cue>
<rh-cue start="24:22" end="24:25">
and it doesn't match, well, then the accuracy is going to go down.
</rh-cue>
<rh-cue start="24:25" voice="Ryan Loney"></rh-cue>
<rh-cue start="24:25" end="24:29">
That's especially important when we talk about things like compression
</rh-cue>
<rh-cue start="24:29" end="24:30">
and quantization,
</rh-cue>
<rh-cue start="24:30" end="24:34">
which, you know, historically has been difficult for to get adoption
</rh-cue>
<rh-cue start="24:34" end="24:40">
in some domains like health care, where even the hint of accuracy going down
</rh-cue>
<rh-cue start="24:40" end="24:44">
implies that we're not going to be able to help in some small case,
</rh-cue>
<rh-cue start="24:44" end="24:47">
maybe if it's even half a percent of the time
</rh-cue>
<rh-cue start="24:47" end="24:51">
we want to take that that tube is placed incorrectly or that, you know,
</rh-cue>
<rh-cue start="24:51" end="24:54">
that patient's, you know, lung has collapsed or something like that.
</rh-cue>
<rh-cue start="24:54" end="24:58">
And that's something that really prevents adoption of some of these methods
</rh-cue>
<rh-cue start="24:58" end="25:01">
that can really boost performance like quantization.
</rh-cue>
<rh-cue start="25:01" end="25:05">
But if you take that example of sort of different from the dog example
</rh-cue>
<rh-cue start="25:05" end="25:07">
and you think about like segmentation of kidneys.
</rh-cue>
<rh-cue start="25:07" end="25:11">
So if I'm doing kidney segmentation, which is, you know, taking a CT scan
</rh-cue>
<rh-cue start="25:12" end="25:14">
and then trying to pick the pixels out of that
</rh-cue>
<rh-cue start="25:14" end="25:17">
scan that belong to a kidney,
</rh-cue>
<rh-cue start="25:17" end="25:20">
how I measure accuracy may be
</rh-cue>
<rh-cue start="25:20" end="25:24">
how many of those pixels I'm able to detect and how many did I miss?
</rh-cue>
<rh-cue start="25:25" voice="Ryan Loney"></rh-cue>
<rh-cue start="25:25" end="25:29">
Missing some of the pixels is maybe not a problem, right,
</rh-cue>
<rh-cue start="25:29" end="25:33">
depending on how you built the application because you still detect the kidney
</rh-cue>
<rh-cue start="25:34" end="25:38">
and maybe you just need to apply padding around the region of interest
</rh-cue>
<rh-cue start="25:38" end="25:41">
so that you don't miss any of the the actual kidney.
</rh-cue>
<rh-cue start="25:42" end="25:45">
When you compress the model and when you quantized the model. But
</rh-cue>
<rh-cue start="25:45" end="25:50">
that requires, you know, data scientist and email engineer somebody to really
</rh-cue>
<rh-cue start="25:51" end="25:52">
they have to be
</rh-cue>
<rh-cue start="25:52" end="25:55">
able to go and apply that after the fact, after the inference
</rh-cue>
<rh-cue start="25:55" end="25:59">
happens to make sure that you're not losing critical information,
</rh-cue>
<rh-cue start="25:59" end="26:02">
because the next step from detecting the kidney may be detecting a tumor.
</rh-cue>
<rh-cue start="26:03" voice="Ryan Loney"></rh-cue>
<rh-cue start="26:03" end="26:06">
And so maybe you can use the more optimized model
</rh-cue>
<rh-cue start="26:06" end="26:11">
to detect the kidney, but then you can use a slower model to detect the tumor.
</rh-cue>
<rh-cue start="26:11" end="26:15">
But that also requires somebody to architect and make that decision
</rh-cue>
<rh-cue start="26:15" end="26:16">
or that tradeoff and say,
</rh-cue>
<rh-cue start="26:16" end="26:20">
well, I need to add padding, or I should only use the quantized model
</rh-cue>
<rh-cue start="26:20" end="26:24">
to detect the region of interest for the kidney and then use the model
</rh-cue>
<rh-cue start="26:24" end="26:27">
that takes longer to do the inference
</rh-cue>
<rh-cue start="26:27" end="26:30">
just to find the tumor, which is going to be on a smaller size.
</rh-cue>
<rh-cue start="26:30" end="26:33">
Right. The dimensions are going to be much smaller
</rh-cue>
<rh-cue start="26:33" end="26:35">
once we crop to the region of interest.
</rh-cue>
<rh-cue start="26:35" end="26:40">
But all of those details, that's maybe not easy to explain in a few sentences.
</rh-cue>
<rh-cue start="26:40" end="26:43">
And even the way I explained it is probably really confusing.
</rh-cue>
<rh-cue start="26:45" voice="Burr Sutter"></rh-cue>
<rh-cue start="26:45" end="26:46">
I do love that use case.
</rh-cue>
<rh-cue start="26:46" end="26:47">
Like you mentioned, the cropping
</rh-cue>
<rh-cue start="26:47" end="26:50">
even in one such an area that we worked on for another project,
</rh-cue>
<rh-cue start="26:50" end="26:53">
we specifically decided to pix like the image that we had taken
</rh-cue>
<rh-cue start="26:53" end="26:57">
because we knew that we could get the outcome we wanted by even
</rh-cue>
<rh-cue start="26:57" end="27:01">
just using a smaller or less having less resolution in our image.
</rh-cue>
<rh-cue start="27:01" end="27:04">
And therefore, as we transferred it from the mobile device storage device
</rh-cue>
<rh-cue start="27:04" end="27:08">
up into the cloud, we wanted that smaller image just for transfer purposes
</rh-cue>
<rh-cue start="27:08" end="27:11">
and it still we could get the accuracy we needed by a lot of testing.
</rh-cue>
<rh-cue start="27:11" voice="Burr Sutter"></rh-cue>
<rh-cue start="27:11" end="27:14">
And one thing that's interesting about that from my perspective is
</rh-cue>
<rh-cue start="27:15" end="27:18">
if you're doing image processing, sometimes it takes a while
</rh-cue>
<rh-cue start="27:18" end="27:20">
for this transaction to occur.
</rh-cue>
<rh-cue start="27:20" end="27:20">
Like I,
</rh-cue>
<rh-cue start="27:20" end="27:24">
I come from a traditional application background, you know, where I'm reading
</rh-cue>
<rh-cue start="27:24" end="27:25">
and writing things from a database
</rh-cue>
<rh-cue start="27:25" end="27:28">
or a message broker or moving data from one place to another.
</rh-cue>
<rh-cue start="27:28" end="27:29">
Those things happen subsequent.
</rh-cue>
<rh-cue start="27:29" end="27:33">
Normally, even with great latency between your data centers, you know,
</rh-cue>
<rh-cue start="27:33" end="27:34">
it's still subsequent.
</rh-cue>
<rh-cue start="27:34" end="27:38">
In most cases, while on a transaction like this, one can actually take 2 seconds
</rh-cue>
<rh-cue start="27:38" end="27:42">
or 4 seconds as it's doing its analysis and actually coming back with, you know,
</rh-cue>
<rh-cue start="27:42" end="27:46">
I think it's a dog, I think it's a kidney, I think it's whatever, and provided me
</rh-cue>
<rh-cue start="27:46" end="27:48">
that accuracy statement.
</rh-cue>
<rh-cue start="27:48" end="27:51">
So that concept of optimization is very important
</rh-cue>
<rh-cue start="27:51" end="27:53">
in the overall application architecture.
</rh-cue>
<rh-cue start="27:53" end="27:56">
Would you agree with that or how do you think about that concept?
</rh-cue>
<rh-cue start="27:56" end="27:56">
Yeah, definitely.
</rh-cue>
<rh-cue start="27:56" voice="Ryan Loney"></rh-cue>
<rh-cue start="27:56" end="27:58">
It depends too on the use case.
</rh-cue>
<rh-cue start="27:58" end="28:02">
So if you think about how important it is to reduce the latency
</rh-cue>
<rh-cue start="28:02" end="28:06">
and increase the number of frames per second that you can process when you're
</rh-cue>
<rh-cue start="28:06" end="28:10">
talking about a loss prevention model that's running at a grocery store.
</rh-cue>
<rh-cue start="28:10" end="28:13">
So you want to keep the lines moving.
</rh-cue>
<rh-cue start="28:13" end="28:16">
You don't want every person who's at the self-checkout
</rh-cue>
<rh-cue start="28:16" end="28:19">
to have to wait 5 seconds for every item they scan.
</rh-cue>
<rh-cue start="28:19" end="28:22">
You need it to happen as quickly as possible.
</rh-cue>
<rh-cue start="28:22" end="28:25">
And if sometimes you, you know, the accuracy
</rh-cue>
<rh-cue start="28:25" end="28:28">
decreases slightly or the I'd say the accuracy of the whole pipeline.
</rh-cue>
<rh-cue start="28:28" end="28:32">
So not just looking at the individual model or the individual inference, but
</rh-cue>
<rh-cue start="28:32" end="28:36">
let's say that the the whole pipeline is not as successful at detecting
</rh-cue>
<rh-cue start="28:37" end="28:40">
when somebody steals one item from the self-checkout,
</rh-cue>
<rh-cue start="28:41" end="28:43">
it's not going to be a life threatening situation.
</rh-cue>
<rh-cue start="28:43" end="28:47">
Whereas, you know, being in the hooked up to the X-ray machine
</rh-cue>
<rh-cue start="28:47" end="28:51">
with the two placement model, they might be willing to have the doctor,
</rh-cue>
<rh-cue start="28:51" end="28:54">
the nurse wait 5 seconds to get the result.
</rh-cue>
<rh-cue start="28:55" voice="Ryan Loney"></rh-cue>
<rh-cue start="28:55" end="28:58">
They don't need it to happen in 500 milliseconds.
</rh-cue>
<rh-cue start="28:58" end="29:02">
So they're willing their threshold for waiting is a little bit higher.
</rh-cue>
<rh-cue start="29:02" end="29:05">
So that, I think, also drives some of the decision, like
</rh-cue>
<rh-cue start="29:06" end="29:09">
you want to keep people moving through the checkout line
</rh-cue>
<rh-cue start="29:09" end="29:13">
and you can afford to to potentially if you lose a little bit of accuracy here
</rh-cue>
<rh-cue start="29:13" end="29:14">
and there, it's not going to
</rh-cue>
<rh-cue start="29:14" end="29:18">
cost the company that much money or it's not going to be life threatening.
</rh-cue>
<rh-cue start="29:18" end="29:21">It's going to be worth the tradeoff of keeping the line moving</rh-cue>
<rh-cue start="29:21" end="29:24">and not having people leave the store and not check out at all.</rh-cue>
<rh-cue start="29:24" end="29:27">And to say, I'm not going to shop today because the line's too long.</rh-cue>
<rh-cue start="29:30" voice="Burr Sutter"></rh-cue>
<rh-cue start="29:30" end="29:32">There are so many trade offs and enterprise</rh-cue>
<rh-cue start="29:32" end="29:35">AML use cases, things like latency, accuracy and availability.</rh-cue>
<rh-cue start="29:35" end="29:40">And certainly complexities abound, especially in an obviously ever evolving</rh-cue>
<rh-cue start="29:40" end="29:43">technological landscape where we are still very early in the adoption of AML.</rh-cue>
<rh-cue start="29:44" end="29:47">And to navigate that complexity, the direct feedback from real world</rh-cue>
<rh-cue start="29:47" end="29:51">end users is essential to Ryan and his team at Intel.</rh-cue>
<rh-cue start="29:52" end="29:54">What would you say are some of the big hurdles or big</rh-cue>
<rh-cue start="29:54" end="29:57">outcomes, big opportunities in that space?</rh-cue>
<rh-cue start="29:57" end="30:01">And do you agree that we're kind of still at the very beginning in our infancy,</rh-cue>
<rh-cue start="30:01" end="30:01">if you will,</rh-cue>
<rh-cue start="30:01" end="30:05">of adopting these technologies and and discovering what they can do for us?</rh-cue>
<rh-cue start="30:05" voice="Ryan Loney"></rh-cue>
<rh-cue start="30:05" end="30:07">Yeah, I think we're definitely in the infancy</rh-cue>
<rh-cue start="30:07" end="30:10">and I think that what we've seen is our customers are evolving</rh-cue>
<rh-cue start="30:10" end="30:14">and the people who are deploying on Intel hardware, they're trying to run</rh-cue>
<rh-cue start="30:14" end="30:16">more complicated models.</rh-cue>
<rh-cue start="30:16" end="30:19">They're the models that are doing object detection or, you know,</rh-cue>
<rh-cue start="30:19" end="30:22">detecting defects and, you know, doing segmentation.</rh-cue>
<rh-cue start="30:23" end="30:27">You know, in the past you could say, oh, here's a generic model that will do face</rh-cue>
<rh-cue start="30:27" end="30:31">detection or person detection or vehicle detection and license plate detection.</rh-cue>
<rh-cue start="30:32" end="30:33">And those are sort of like</rh-cue>
<rh-cue start="30:33" end="30:36">general purpose models that you can just grab off the shelf and use them.</rh-cue>
<rh-cue start="30:37" end="30:40">But now we're moving into like the anomaly scenarios</rh-cue>
<rh-cue start="30:40" end="30:44">where I've got my own data and I'm trying to do something very specific</rh-cue>
<rh-cue start="30:45" end="30:47">and I'm the only one that has access to this data.</rh-cue>
<rh-cue start="30:47" end="30:51">And you don't have a public data set that you can go download</rh-cue>
<rh-cue start="30:51" end="30:54">that's under Creative Commons license for, you know, car batteries.</rh-cue>
<rh-cue start="30:54" end="30:57">It's, you know, it's just not something that's available.</rh-cue>
<rh-cue start="30:57" voice="Ryan Loney"></rh-cue>
<rh-cue start="30:57" end="31:02">And so those use cases, the challenge with with training those models</rh-cue>
<rh-cue start="31:02" end="31:06">and and getting them optimized is the beginning of the pipeline.</rh-cue>
<rh-cue start="31:06" end="31:10">It's the data you have to get the data you have to annotated</rh-cue>
<rh-cue start="31:10" end="31:12">and the tools have to exist for you to do that.</rh-cue>
<rh-cue start="31:12" end="31:15">And that's part of the problem that we're trying to help solve.</rh-cue>
<rh-cue start="31:16" end="31:17">And then the models are getting more complex.</rh-cue>
<rh-cue start="31:17" end="31:21">So if you think, you know, just from working with customers recently,</rh-cue>
<rh-cue start="31:21" end="31:22">you know, they're no longer</rh-cue>
<rh-cue start="31:22" end="31:26">just trying to do image classification and, you know, like is it a dog or a cat?</rh-cue>
<rh-cue start="31:26" end="31:29">They've moved on to like 3D point clouds</rh-cue>
<rh-cue start="31:29" end="31:34">and, you know, 3D segmentation models and things that are like the speech</rh-cue>
<rh-cue start="31:34" end="31:39">synthesis example, doing things these GPT models that are generating,</rh-cue>
<rh-cue start="31:40" end="31:44">you know, you, you put a text input and it generates an image for you.</rh-cue>
<rh-cue start="31:44" end="31:47">It's just becoming much more advanced, much more sophisticated</rh-cue>
<rh-cue start="31:48" end="31:50">and on larger images.</rh-cue>
<rh-cue start="31:50" voice="Ryan Loney"></rh-cue>
<rh-cue start="31:50" end="31:54">And so things like running super resolution enhancing images, upscaling</rh-cue>
<rh-cue start="31:54" end="31:59">images, instead of just trying to take that, you know, 200 by 200 pixel</rh-cue>
<rh-cue start="32:00" end="32:02">image and classifying if it's a cat.</rh-cue>
<rh-cue start="32:02" end="32:05">Now we're talking about gigantic</rh-cue>
<rh-cue start="32:05" end="32:09">huge images that we're processing and that all requires</rh-cue>
<rh-cue start="32:09" end="32:12">more resources or more optimized models.</rh-cue>
<rh-cue start="32:13" end="32:16">And, you know, every computer vision conference or A.I.</rh-cue>
<rh-cue start="32:16" end="32:19">conference, there's there's a new latest and greatest architecture.</rh-cue>
<rh-cue start="32:19" end="32:22">There's new research paper, and things are getting adopted much faster.</rh-cue>
<rh-cue start="32:23" end="32:27">The lead time for a nurse paper or CV PR</rh-cue>
<rh-cue start="32:27" end="32:30">for a company to actually adopt and put those into production.</rh-cue>
<rh-cue start="32:30" end="32:32">It's like the time shortens every year.</rh-cue>
<rh-cue start="32:33" voice="Burr Sutter"></rh-cue>
<rh-cue start="32:33" end="32:35">Well, Ryan, I got to tell you, I could talk to you</rh-cue>
<rh-cue start="32:35" end="32:39">literally all day about these topics, the various use cases, the various ways</rh-cue>
<rh-cue start="32:39" end="32:41">models are being optimized,</rh-cue>
<rh-cue start="32:41" end="32:44">how to put models into a pipeline for average enterprise applications.</rh-cue>
<rh-cue start="32:44" end="32:47">I've enjoyed learning about pop and vino and anomalies,</rh-cue>
<rh-cue start="32:47" end="32:50">but I'm fascinated by this because I will have a chance to go try this myself.</rh-cue>
<rh-cue start="32:51" end="32:52">Taking advantage of Red Hat OpenShift</rh-cue>
<rh-cue start="32:52" end="32:54">and taking advantage of our data science platform.</rh-cue>
<rh-cue start="32:54" end="32:58">On top of that, I will definitely go be poking at this myself.</rh-cue>
<rh-cue start="32:58" end="33:00">So thank you so much for your time today.</rh-cue>
<rh-cue start="33:00" voice="Ryan Loney"></rh-cue>
<rh-cue start="33:00" end="33:00">Thanks, Burr.</rh-cue>
<rh-cue start="33:00" end="33:01">This was a lot of fun.</rh-cue>
<rh-cue start="33:01" end="33:04">Thanks for having me.</rh-cue>
<rh-cue start="33:04" voice="Burr Sutter"></rh-cue>
<rh-cue start="33:04" end="33:06">And you can check out</rh-cue>
<rh-cue start="33:06" end="33:09">the full transcript of our conversation and more resources,</rh-cue>
<rh-cue start="33:09" end="33:12">like a link to a white paper on open vino and normal lib at Red Hat dot</rh-cue>
<rh-cue start="33:12" end="33:15">com slash code Comments Podcast.</rh-cue>
<rh-cue start="33:15" end="33:19">This episode was produced by Brant Seminole and Caroline Prickett.</rh-cue>
<rh-cue start="33:20" end="33:21">Our sound designer is Christian.</rh-cue>
<rh-cue start="33:21" end="33:26">From our audio team includes Lee Day, Stephanie Wunderlich, Mike Esser,</rh-cue>
<rh-cue start="33:27" end="33:32">Laura Barnes, Claire Allison, Nick Burns, Aaron Williamson, Karen King,</rh-cue>
<rh-cue start="33:32" end="33:36">Booboo House, Rachel Artell, Mike Compton, Ocean</rh-cue>
<rh-cue start="33:36" end="33:40">Mathews, Laura Walters, Alex Trabelsi and Victoria Lutton.</rh-cue>
<rh-cue start="33:41" end="33:43">I'm your host, Burt Sutter.</rh-cue>
<rh-cue start="33:43" end="33:45">Thank you for joining me today on Code Comments.</rh-cue>
<rh-cue start="33:45" end="33:48">I hope you enjoyed today's session and today's conversation, and I</rh-cue>
<rh-cue start="33:48" end="33:52">look forward to many more in.</rh-cue>
</rh-transcript>
</rh-audio-player>
<h2>Even with more headings</h2>
<p>This last heading is allowed to go back up to h2, but the player should still take h3 as its root heading level.</p>
</section>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css">import { AudioPlayer } from "@rhds/elements/react/rh-audio-player/rh-audio-player.js";
import { AudioPlayerAbout } from "@rhds/elements/react/rh-audio-player-about/rh-audio-player-about.js";
import { AudioPlayerSubscribe } from "@rhds/elements/react/rh-audio-player-subscribe/rh-audio-player-subscribe.js";
import { Avatar } from "@rhds/elements/react/rh-avatar/rh-avatar.js";
import { Cue } from "@rhds/elements/react/rh-cue/rh-cue.js";
import { Transcript } from "@rhds/elements/react/rh-transcript/rh-transcript.js";
// NOTE: React 19+ does not require these wrapper imports.
// You can use the custom elements directly as-is.
export const Demo = () => (
<section id="heading-levels">
<p>Audio player should automatically calculate it's heading levels</p>
<h3>Root Level h3</h3>
<p>
Transcript should be
<code>h5</code>
, cues should be
<code>h6</code>
</p>
<AudioPlayer layout="full" poster="https://www.redhat.com/cms/managed-files/CLH-S7-ep1.png">
<p slot="series">Code Comments</p>
<h4 slot="title">Bringing Deep Learning to Enterprise Applications</h4>
<AudioPlayerAbout slot="about">
<h5 slot="heading">About the episode</h5>
<p>There are a lot of publicly available data sets out there. But when it
comes to specific enterprise use cases, you're not necessarily going to
able to find one to train your models. To realize the power of AI/ML in
enterprise environments, end users need an inference engine to run on
their hardware. Ryan Loney takes us through OpenVINO and Anomalib, open
toolkits from Intel that do precisely that. He looks specifically at
anomaly detection in use cases as varied as medical imaging and
manufacturing.</p>
<p>Want to learn more about Anomalib? Check out the research paper that
introduces the deep learning library.</p>
<Avatar slot="profile" src="https://www.redhat.com/cms/managed-files/ryan-loney.png">
Ryan Loney
<span slot="subtitle">Product manager, OpenVINO Developer Tools,<em>Intel®</em></span>
</Avatar>
</AudioPlayerAbout>
<audio crossorigin="anonymous" slot="media" controls>
<source type="audio/mp3" srclang="en" src="https://cdn.simplecast.com/audio/28d037d3-7d17-42d4-a8e2-2e00fd8b602b/episodes/bd38190e-516f-49c0-b47e-6cf663d80986/audio/dc570fd1-7a5e-41e2-b9a4-96deb346c20f/default_tc.mp3" />
</audio>
<AudioPlayerSubscribe slot="subscribe">
<h5 slot="heading">Subscribe</h5>
<p>Subscribe here:</p>
<a slot="link" href="https://podcasts.apple.com/us/podcast/code-comments/id1649848507" target="_blank" title="Listen on Apple Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Apple Podcasts" data-analytics-category="Hero|Listen on Apple Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_apple-podcast-white.svg" alt="Listen on Apple Podcasts" />
</a>
<a slot="link" href="https://open.spotify.com/show/6eJc62sKckHs4uEQ8eoKzD" target="_blank" title="Listen on Spotify" data-analytics-linktype="cta" data-analytics-text="Listen on Spotify" data-analytics-category="Hero|Listen on Spotify">
<img src="https://www.redhat.com/cms/managed-files/badge_spotify.svg" alt="Listen on Spotify" />
</a>
<a slot="link" href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5wYWNpZmljLWNvbnRlbnQuY29tL2NvZGVjb21tZW50cw" target="_blank" title="Listen on Google Podcasts" data-analytics-linktype="cta" data-analytics-text="Listen on Google Podcasts" data-analytics-category="Hero|Listen on Google Podcasts">
<img src="https://www.redhat.com/cms/managed-files/badge_google-podcast.svg" alt="Listen on Google Podcasts" />
</a>
<a slot="link" href="https://feeds.pacific-content.com/codecomments" target="_blank" title="Subscribe via RSS Feed" data-analytics-linktype="cta" data-analytics-text="Subscribe via RSS Feed" data-analytics-category="Hero|Subscribe via RSS Feed">
<img className="img-fluid" src="https://www.redhat.com/cms/managed-files/badge_RSS-feed.svg" alt="Subscribe via RSS Feed" />
</a>
</AudioPlayerSubscribe>
<Transcript slot="transcript">
<Cue start="00:02" voice="Burr Sutter" />
<Cue start="00:02" end="00:04">Hi, I'm Burr Sutter.</Cue>
<Cue start="00:04" end="00:05">I'm a Red Hatter</Cue>
<Cue start="00:05" end="00:08">who spends a lot of time talking to technologists about technologies.</Cue>
<Cue start="00:09" end="00:10">We say this a lot of Red Hat.</Cue>
<Cue start="00:10" end="00:14">No single technology provider holds the key to success, including us.</Cue>
<Cue start="00:15" end="00:17">And I would say the same thing about myself.</Cue>
<Cue start="00:17" end="00:18">I love to share ideas.</Cue>
<Cue start="00:18" end="00:19">So I thought it'd be awesome</Cue>
<Cue start="00:19" end="00:22">to talk to some brilliant technologists at Red Hat Partners.</Cue>
<Cue start="00:23" end="00:26">This is Code Comments, an original podcast</Cue>
<Cue start="00:26" end="00:29">from Red Hat.</Cue>
<Cue start="00:29" voice="Burr Sutter" />
<Cue start="00:29" end="00:32">I'm sure, like many of you here, you have been thinking about</Cue>
<Cue start="00:32" end="00:36">AI, ML, artificial intelligence and machine learning.</Cue>
<Cue start="00:36" end="00:38">I've been thinking about that for quite some time</Cue>
<Cue start="00:38" end="00:39">and actually had the opportunity</Cue>
<Cue start="00:39" end="00:43">to work on a few successful projects here at Red Hat using those technologies,</Cue>
<Cue start="00:43" end="00:46">actually enabling a dataset, gathering a dataset,</Cue>
<Cue start="00:46" end="00:49">working with data scientists and data engineering team,</Cue>
<Cue start="00:49" end="00:51">and then training a model and putting that model into production</Cue>
<Cue start="00:51" end="00:53">runtime environment.</Cue>
<Cue start="00:53" end="00:55">It was an exciting set of projects and you can kind of see</Cue>
<Cue start="00:55" end="00:58">those on numerous YouTube videos I have published out there before.</Cue>
<Cue start="00:59" end="01:01">But I want you to think about the problem space a little bit</Cue>
<Cue start="01:01" end="01:04">because there are some interesting challenges about AI/ML.</Cue>
<Cue start="01:04" end="01:06">One is simply just getting access to the data,</Cue>
<Cue start="01:06" end="01:09">and while there are numerous publicly available datasets</Cue>
<Cue start="01:09" end="01:12">when it comes to your specific enterprise use case, you might not be to find</Cue>
<Cue start="01:12" end="01:14">publicly available data.</Cue>
<Cue start="01:14" voice="Burr Sutter" />
<Cue start="01:14" end="01:17">In many cases, you cannot, even for our applications that we created,</Cue>
<Cue start="01:17" end="01:20">we had to create our dataset, capture our dataset,</Cue>
<Cue start="01:21" end="01:24">explore the dataset, and of course train a model accordingly.</Cue>
<Cue start="01:24" end="01:27">And we also found there's another challenge to be overcome</Cue>
<Cue start="01:27" end="01:30">in this AML world, and that is access to certain types of hardware.</Cue>
<Cue start="01:31" end="01:33">If you think about the enterprise environment</Cue>
<Cue start="01:33" end="01:36">and the creation of an enterprise application specifically for AML</Cue>
<Cue start="01:37" end="01:40">and users need an inference engine to run on their hardware,</Cue>
<Cue start="01:40" end="01:43">hardware that's available to them to be effective for their application.</Cue>
<Cue start="01:43" end="01:45">Let's say an application like computer vision,</Cue>
<Cue start="01:45" end="01:49">one that can detect anomalies in medical imaging or maybe on a factory floor,</Cue>
<Cue start="01:49" end="01:52">You know, those things are whizzing by on the factory line.</Cue>
<Cue start="01:52" end="01:55">They're looking at them and trying to determine if there is an error or not.</Cue>
<Cue start="01:56" voice="Burr Sutter" />
<Cue start="01:56" end="01:58">Well, how do you actually make it run on your hardware,</Cue>
<Cue start="01:58" end="02:01">your accessible technology that you have today?</Cue>
<Cue start="02:01" end="02:05">Well, there's a solution for this as an open toolkit called Open vino.</Cue>
<Cue start="02:05" end="02:07">And you might be thinking, hey, wait a minute,</Cue>
<Cue start="02:07" end="02:10">don't you need a GPU for a I inferencing a GPU</Cue>
<Cue start="02:10" end="02:12">for artificial intelligence machine learning?</Cue>
<Cue start="02:12" end="02:15">Well, not according to Ryan Loney, product manager of Open Vino Developer</Cue>
<Cue start="02:15" end="02:16">Tools at Intel.</Cue>
<Cue start="02:20" voice="Ryan Loney" />
<Cue start="02:20" end="02:20">I guess we'll</Cue>
<Cue start="02:20" end="02:23">start with trying to maybe dispel the myths, right?</Cue>
<Cue start="02:23" end="02:27">I think that CPUs are widely used for inference today.</Cue>
<Cue start="02:27" end="02:32">So and if we look at the data center segment, you know, about 70% of the A.I.</Cue>
<Cue start="02:32" end="02:36">inference is happening on Intel Xeon on our data center CPUs.</Cue>
<Cue start="02:36" end="02:40">And so you don't needed a GPU, especially for running inference.</Cue>
<Cue start="02:40" end="02:43">And that's part of the value of open vino, is that we're you know,</Cue>
<Cue start="02:43" end="02:47">we're taking models that may have been trained on a GPU</Cue>
<Cue start="02:47" end="02:50">using deep learning frameworks like PyTorch or TensorFlow</Cue>
<Cue start="02:51" end="02:54">and then optimizing them to run on Intel hardware.</Cue>
<Cue start="02:57" voice="Burr Sutter" />
<Cue start="02:56" end="03:00">Ryan joined me to discuss AI/ML and the enterprise</Cue>
<Cue start="03:00" end="03:03">across various industries and exploring numerous use cases.</Cue>
<Cue start="03:05" end="03:08">Let's talk a little bit about the origin story behind Open Vino.</Cue>
<Cue start="03:08" end="03:10">Tell us more about it and how it came to be</Cue>
<Cue start="03:10" end="03:13">and why it came out of Intel.</Cue>
<Cue start="03:12" voice="Ryan Loney" />
<Cue start="03:12" end="03:16">Definitely. So we had the first release of Open Vino</Cue>
<Cue start="03:16" end="03:20">was back in 2018, so still relatively new.</Cue>
<Cue start="03:20" end="03:25">And at that time we were focused on computer vision and pretty tightly coupled</Cue>
<Cue start="03:25" end="03:31">with open CV, which is another open source library with origins at Intel.</Cue>
<Cue start="03:31" end="03:31">You know, it</Cue>
<Cue start="03:31" end="03:36">had its first release back in 1999, so it's been around a little bit longer.</Cue>
<Cue start="03:36" end="03:40">And many of the software engineers and architects at Intel</Cue>
<Cue start="03:40" end="03:45">that were involved with and contributing to open CV are working on open Vino.</Cue>
<Cue start="03:45" end="03:49">So you can think of open vino as complementary software to open CV.</Cue>
<Cue start="03:50" end="03:53">And we're providing like an engine for executing inference</Cue>
<Cue start="03:53" end="03:57">as part of a computer vision pipeline, or at least that's how we started.</Cue>
<Cue start="03:58" voice="Ryan Loney" />
<Cue start="03:58" end="04:01">But since 2018, we've we've started to move beyond</Cue>
<Cue start="04:01" end="04:02">just computer vision inference.</Cue>
<Cue start="04:02" end="04:05">So when I say computer vision inference, I mean like image</Cue>
<Cue start="04:05" end="04:08">classification, object detection, segmentation.</Cue>
<Cue start="04:09" end="04:12">And now we're moving into natural language processing, things</Cue>
<Cue start="04:12" end="04:16">like speech synthesis, speech recognition, knowledge, graphs,</Cue>
<Cue start="04:17" end="04:21">time series forecasting, and other use cases that don't involve</Cue>
<Cue start="04:21" end="04:24">computer vision and don't involve inference on pixels.</Cue>
<Cue start="04:25" end="04:28">Our latest release, the 20 22.1 that came out earlier this year,</Cue>
<Cue start="04:29" end="04:32">there was a most significant update that we've had to open vino</Cue>
<Cue start="04:32" end="04:36">since we started in 2018, and the major focus of that release</Cue>
<Cue start="04:36" end="04:40">was optimizing for use cases that go beyond computer vision.</Cue>
<Cue start="04:41" voice="Burr Sutter" />
<Cue start="04:41" end="04:44">And I like that concept that you just mentioned right there, computer vision.</Cue>
<Cue start="04:44" end="04:47">And you said that you extended those use cases and went beyond that.</Cue>
<Cue start="04:47" end="04:50">So could you give us more concrete examples of computer vision?</Cue>
<Cue start="04:50" voice="Ryan Loney" />
<Cue start="04:50" end="04:50">Yeah, sure.</Cue>
<Cue start="04:50" end="04:55">So when you think about manufacturing quality control in factories, everything</Cue>
<Cue start="04:55" end="05:01">from ARC welding, defect detection to inspecting BMW cars on assembly lines,</Cue>
<Cue start="05:02" end="05:05">they're using cameras or sensors to collect data.</Cue>
<Cue start="05:05" end="05:11">And usually it's cameras collecting images like RGV images that you and I can see.</Cue>
<Cue start="05:11" end="05:14">And looks like something taken from a camera or video camera,</Cue>
<Cue start="05:15" end="05:19">but also things like infrared or computerized tomography</Cue>
<Cue start="05:19" end="05:24">scans used in health care, X-ray, different types of images where we can</Cue>
<Cue start="05:25" end="05:28">draw bounding boxes around regions of interest</Cue>
<Cue start="05:29" end="05:32">and say, you know, this is a defect or this is not a defect.</Cue>
<Cue start="05:32" end="05:37">And also, is this worker wearing a safety hat or did they forget to put it on?</Cue>
<Cue start="05:37" end="05:41">And so you can take this and integrate it into a pipeline</Cue>
<Cue start="05:41" end="05:44">where you're triggering an alert if somebody forgets</Cue>
<Cue start="05:44" end="05:49">to wear their safety mask or if there's a defect in a product</Cue>
<Cue start="05:49" end="05:53">on an assembly line, you can just use cameras and open</Cue>
<Cue start="05:53" end="05:58">vino and open CV running these on Intel hardware and help to analyze.</Cue>
<Cue start="05:58" voice="Ryan Loney" />
<Cue start="05:58" end="06:01">And that's what a lot of the partners that we work with are doing.</Cue>
<Cue start="06:01" end="06:03">So these independent software vendors</Cue>
<Cue start="06:03" end="06:06">and there's other use cases for things like retail.</Cue>
<Cue start="06:06" end="06:10">You think about going to a store and using an automated checkout system.</Cue>
<Cue start="06:11" end="06:13">You know, sometimes people use those automated checkouts</Cue>
<Cue start="06:13" end="06:17">and they they slide a few extra items into their bag that they don't scan.</Cue>
<Cue start="06:17" end="06:21">And it's a huge loss for the retail outlets</Cue>
<Cue start="06:21" end="06:25">that are providing this way to check out real time shelf monitoring.</Cue>
<Cue start="06:25" end="06:29">We have this bear on one of our is fees that helps keep store shelves</Cue>
<Cue start="06:29" end="06:33">stocked by just analyzing the cameras in the stores, detecting</Cue>
<Cue start="06:33" end="06:37">when objects are missing from the shelves so that they can be restocked.</Cue>
<Cue start="06:37" end="06:41">We have Vistry, another ISP that works with quick service restaurants.</Cue>
<Cue start="06:41" end="06:44">So when you think about automating the process of</Cue>
<Cue start="06:44" end="06:48">when do I drop the fries into the fryer so that they're warm</Cue>
<Cue start="06:48" end="06:50">when the car gets to the drive thru window,</Cue>
<Cue start="06:50" end="06:54">you know, there's quite a bit of industrial health care retail examples</Cue>
<Cue start="06:54" end="06:57">that we can walk through and we should dig into some more of those.</Cue>
<Cue start="06:57" voice="Burr Sutter" />
<Cue start="06:57" end="06:59">But I got to tell you, I have I have a personal experience</Cue>
<Cue start="06:59" end="06:59">in this category</Cue>
<Cue start="06:59" end="07:01">that I want to share with, and you can tell me how</Cue>
<Cue start="07:01" end="07:03">how silly you might think at this point in time.</Cue>
<Cue start="07:03" end="07:04">It is.</Cue>
<Cue start="07:04" end="07:08">We actually built an AI keynote demonstration for the Red Hat big stage</Cue>
<Cue start="07:08" end="07:12">back in 2015, and I really want to illustrate the concept of asset tracking.</Cue>
<Cue start="07:12" end="07:15">So we actually gave everybody in the conference a little Bluetooth token,</Cue>
<Cue start="07:16" end="07:19">but a little battery, a little watch battery and a little Bluetooth emitter.</Cue>
<Cue start="07:19" end="07:22">And we basically tracked those things around the conference.</Cue>
<Cue start="07:22" end="07:24">We basically put a Raspberry Pi in each of the meeting rooms</Cue>
<Cue start="07:24" end="07:26">and up in the lunch room, and you could see how the tokens</Cue>
<Cue start="07:26" end="07:30">moved from room to room to room as a relatively simple application.</Cue>
<Cue start="07:30" voice="Burr Sutter" />
<Cue start="07:30" end="07:32">But it occurred to me after we figured out,</Cue>
<Cue start="07:32" end="07:34">okay, how to do that with Bluetooth and triangulating</Cue>
<Cue start="07:34" end="07:39">Bluetooth signals by looking at relative signal strength from one radio to another</Cue>
<Cue start="07:39" end="07:42">and putting that through an Apache Spark application at the time,</Cue>
<Cue start="07:42" end="07:45">we then realized, you know what, this is easier done with cameras</Cue>
<Cue start="07:45" end="07:49">and just simply looking at a camera and having some form of animal</Cue>
<Cue start="07:49" end="07:51">or machine learning model that would say, Oh,</Cue>
<Cue start="07:51" end="07:53">there are people here now are there are no people here now.</Cue>
<Cue start="07:53" end="07:55">What do you think about that?</Cue>
<Cue start="07:55" voice="Ryan Loney" />
<Cue start="07:55" end="07:59">Yeah, I mean, what you just described is sort of exactly that the product</Cue>
<Cue start="07:59" end="08:02">that either one of our partners is offering,</Cue>
<Cue start="08:02" end="08:04">you know, that they're doing it with computer vision and cameras.</Cue>
<Cue start="08:04" end="08:08">So when partner tries to help retail stores</Cue>
<Cue start="08:08" end="08:12">analyze the foot traffic and understand with Heatmaps,</Cue>
<Cue start="08:12" end="08:16">where people are spending the most time in stores, how many people are coming</Cue>
<Cue start="08:16" end="08:19">in, what size groups are coming into the store,</Cue>
<Cue start="08:19" end="08:23">you know, and trying to help understand if there was a successful transaction</Cue>
<Cue start="08:23" end="08:27">from the people who entered the store and left the store so that you can,</Cue>
<Cue start="08:27" end="08:30">you know, to help with the, you know, retail analytics</Cue>
<Cue start="08:30" end="08:33">and marketing sales and positioning of products.</Cue>
<Cue start="08:34" end="08:37">And so they're doing that in a way that also protects privacy.</Cue>
<Cue start="08:37" end="08:38">And that's something that's really important.</Cue>
<Cue start="08:38" end="08:41">So when you talked about those Bluetooth beacons, probably,</Cue>
<Cue start="08:41" end="08:44">you know, if everyone who walked into a grocery store was asked</Cue>
<Cue start="08:44" end="08:49">to put a tracking device in their cart or on their person and say, you know,</Cue>
<Cue start="08:49" end="08:50">you're going</Cue>
<Cue start="08:50" end="08:53">to be tracked around the store, they probably wouldn't want to do that.</Cue>
<Cue start="08:53" end="08:56">The way that you can do this with cameras is you can,</Cue>
<Cue start="08:53" voice="Ryan Loney" />
<Cue start="08:56" end="09:01">you know, detect people as they enter and, you know, remove their face.</Cue>
<Cue start="09:01" end="09:01">Right.</Cue>
<Cue start="09:01" end="09:05">So you can ignore any biometric information</Cue>
<Cue start="09:05" end="09:08">and and just track the person based on pixels</Cue>
<Cue start="09:09" end="09:12">that are present in the detected region of interest.</Cue>
<Cue start="09:12" end="09:15">So they're able to analyze, say, a family walks in the door</Cue>
<Cue start="09:16" end="09:20">and they can group those people together with object detection</Cue>
<Cue start="09:20" end="09:23">and then they can track their movement throughout the store</Cue>
<Cue start="09:23" end="09:26">without keeping track of their face or any biometric</Cue>
<Cue start="09:26" end="09:30">or any personal identifiable information to avoid things like bias</Cue>
<Cue start="09:30" end="09:35">and to make sure that they're protecting the privacy of the shoppers in the store</Cue>
<Cue start="09:35" end="09:39">while still getting that really useful marketing analytics data rate</Cue>
<Cue start="09:39" end="09:42">so that they can make better decisions about where to place their products.</Cue>
<Cue start="09:42" end="09:45">So that's one really good example of how</Cue>
<Cue start="09:45" end="09:48">computer vision AI with open vino is being used today.</Cue>
<Cue start="09:48" voice="Burr Sutter" />
<Cue start="09:48" end="09:51">And that is a great example because you're definitely spot on.</Cue>
<Cue start="09:51" end="09:53">It is invasive when you hand someone to Bluetooth devices,</Cue>
<Cue start="09:53" end="09:56">say, please keep this with you as you go throughout our our store</Cue>
<Cue start="09:56" end="09:59">or our mall or throughout our hospital, wherever you might be.</Cue>
<Cue start="09:59" end="10:01">Now, you mentioned another example earlier</Cue>
<Cue start="10:01" end="10:03">in the conversation which was related to like worker safety.</Cue>
<Cue start="10:03" end="10:05">Are they wearing a helmet?</Cue>
<Cue start="10:05" end="10:08">I want to talk more about that concept in a real industrial setting,</Cue>
<Cue start="10:08" end="10:11">a manufacturing setting where there might be a factory floor</Cue>
<Cue start="10:11" end="10:13">and there are certain requirements, or better yet, there's like a</Cue>
<Cue start="10:13" end="10:16">a quality assurance requirement, let's say, when it comes to looking</Cue>
<Cue start="10:16" end="10:20">at a factory line, I run to that use case often what some of our customers.</Cue>
<Cue start="10:20" end="10:22">Can you talk more about those kinds of use cases? Yeah.</Cue>
<Cue start="10:22" voice="Ryan Loney" />
<Cue start="10:22" end="10:27">So one of our partners, Robuchon and we you know, published a case study</Cue>
<Cue start="10:27" end="10:31">I think last year where they're working with BMW at one of their factories</Cue>
<Cue start="10:32" end="10:35">and they do quality control inspection, but they're also doing</Cue>
<Cue start="10:35" end="10:38">things related to worker safety and analyzing.</Cue>
<Cue start="10:38" end="10:40">You know, I used the safety had example.</Cue>
<Cue start="10:40" end="10:45">There's a number of of our ISP's and partners who have similar use cases.</Cue>
<Cue start="10:45" end="10:48">And it comes down to there's a few reasons</Cue>
<Cue start="10:48" end="10:51">that are motivating this and some are related to like insurance, right?</Cue>
<Cue start="10:51" end="10:53">It's important to make sure that</Cue>
<Cue start="10:53" end="10:56">if you want to have your factory insured and that your workers</Cue>
<Cue start="10:56" end="10:58">are protecting themselves and wearing the gear.</Cue>
<Cue start="10:58" end="11:00">Regulatory compliance. Right.</Cue>
<Cue start="11:00" end="11:05">You're you're being asked to properly protect from exposure to chemicals or,</Cue>
<Cue start="11:05" end="11:09">you know, potentially having something fall and and hit someone on the head.</Cue>
<Cue start="11:09" end="11:13">So wearing a safety vest, wearing goggles, wearing a helmet,</Cue>
<Cue start="11:14" end="11:17">these are things that you need to do inside the factory.</Cue>
<Cue start="11:17" end="11:21">And you can really easily automate and detect and sometimes without bias.</Cue>
<Cue start="11:21" voice="Ryan Loney" />
<Cue start="11:21" end="11:26">I think that's one of the interesting things about the robots on BMW example</Cue>
<Cue start="11:26" end="11:31">is that they were also blurring sort of blocking out and so drawing a box</Cue>
<Cue start="11:31" end="11:35">to cover the face of the workers in the factory</Cue>
<Cue start="11:35" end="11:38">so that somebody who was analyzing the video footage</Cue>
<Cue start="11:38" end="11:43">and getting the alerts saying that, hey, you know, Bay 21 has a worker</Cue>
<Cue start="11:43" end="11:47">without a hat on, that it's not sending their face</Cue>
<Cue start="11:47" end="11:50">and in the alert and potentially, you know, invading</Cue>
<Cue start="11:50" end="11:54">or going against privacy laws or just the ethics of the company.</Cue>
<Cue start="11:54" end="11:54">Right.</Cue>
<Cue start="11:54" end="11:58">They don't want to introduce bias or have people targeted because</Cue>
<Cue start="11:58" end="12:02">it's much better to to have it be, you know, blur the face</Cue>
<Cue start="12:02" end="12:06">and alert and have somebody take care of it on the floor.</Cue>
<Cue start="12:06" end="12:09">And then if you ever need to audit that information later,</Cue>
<Cue start="12:09" end="12:12">they have a way to do it where people who need to be able to see</Cue>
<Cue start="12:12" end="12:17">who the employee was and look up their personal information, they can do that.</Cue>
<Cue start="12:17" voice="Ryan Loney" />
<Cue start="12:17" end="12:20">But then just for the purposes of maintaining safety,</Cue>
<Cue start="12:20" end="12:21">they don't need to have access</Cue>
<Cue start="12:21" end="12:24">to that personal information or biometric information,</Cue>
<Cue start="12:25" end="12:28">because that's one thing that when you hear about computer vision</Cue>
<Cue start="12:28" end="12:31">or object person tracking, object detection,</Cue>
<Cue start="12:32" end="12:36">there's a lot of concern, and rightfully so, about privacy</Cue>
<Cue start="12:36" end="12:40">being invaded and about tracking information, face ID,</Cue>
<Cue start="12:41" end="12:45">identifying people who may have committed crimes through video footage.</Cue>
<Cue start="12:45" end="12:48">And that's just not something that a lot of companies want to</Cue>
<Cue start="12:49" end="12:51">you know, they want to protect privacy</Cue>
<Cue start="12:51" end="12:52">and they don't they don't want to be in a situation</Cue>
<Cue start="12:52" end="12:55">where they might be violating someone's rights.</Cue>
<Cue start="12:56" voice="Burr Sutter" />
<Cue start="12:56" end="12:58">Well, privacy is certainly opening up Pandora's box.</Cue>
<Cue start="12:58" end="13:00">There's a lot to be explored in that area,</Cue>
<Cue start="13:00" end="13:02">especially in a digital world that we now live in.</Cue>
<Cue start="13:02" end="13:05">But for now, let's move on and explore different area.</Cue>
<Cue start="13:05" end="13:08">I'm interested in how machines and computers offer advantages,</Cue>
<Cue start="13:08" end="13:12">specifically in certain use cases like a quality control scenario.</Cue>
<Cue start="13:12" end="13:15">I asked Ryan to explain how AML and specifically machines</Cue>
<Cue start="13:15" end="13:18">computers can augment that capability.</Cue>
<Cue start="13:19" voice="Ryan Loney" />
<Cue start="13:19" end="13:22">I can give a specific example where we have a partner</Cue>
<Cue start="13:22" end="13:25">that's there doing defect detection with</Cue>
<Cue start="13:25" end="13:28">and looking for anomalies in batteries.</Cue>
<Cue start="13:28" end="13:31">So, you know, sure, you've heard there's a lot of interest right now</Cue>
<Cue start="13:31" end="13:34">in electric vehicles, a lot of batteries being produced.</Cue>
<Cue start="13:34" end="13:36">And so if you go into one of these factories,</Cue>
<Cue start="13:36" end="13:40">they have images that they collect of every battery that's going through this</Cue>
<Cue start="13:40" end="13:44">assembly line and through these images, people</Cue>
<Cue start="13:44" end="13:47">can look and see and visually inspect with their eyes and say,</Cue>
<Cue start="13:48" end="13:50">this battery has a defect, send it back.</Cue>
<Cue start="13:50" end="13:53">And that's one step in the quality control process.</Cue>
<Cue start="13:53" end="13:58">And there's other steps, I'm sure, like running diagnostic tests and, you know,</Cue>
<Cue start="13:58" end="14:02">measuring voltage and doing other types of non-visual inspection.</Cue>
<Cue start="14:02" end="14:06">But for the visual inspection piece where you can really easily identify</Cue>
<Cue start="14:06" end="14:10">some problems, it's much more efficient to introduce computer vision.</Cue>
<Cue start="14:11" end="14:14">And so that's where we have this new library that we've introduced</Cue>
<Cue start="14:14" end="14:17">called Anomali, that's open vino.</Cue>
<Cue start="14:17" voice="Ryan Loney" />
<Cue start="14:17" end="14:20">While we're focused on inference, you know, we're also thinking</Cue>
<Cue start="14:20" end="14:25">about the pipeline or the funnel that gets these models to open vino.</Cue>
<Cue start="14:25" end="14:28">And so we've we've invested in this anomaly segmentation,</Cue>
<Cue start="14:28" end="14:32">anomaly detection library and that we've recently open source</Cue>
<Cue start="14:32" end="14:35">and there's a great research paper about it about Anomali.</Cue>
<Cue start="14:36" end="14:39">But the idea is you can take just a few images</Cue>
<Cue start="14:39" end="14:43">and train a model and start detecting these defects.</Cue>
<Cue start="14:43" end="14:46">And so for this battery example, that's a more advanced example.</Cue>
<Cue start="14:46" end="14:52">But to make it simpler, you know, take some bolts and, you know, take ten bolts.</Cue>
<Cue start="14:52" end="14:55">You have one that has a scratch on it or one that is chipped</Cue>
<Cue start="14:56" end="14:58">or has some damage to it.</Cue>
<Cue start="14:58" end="15:00">And you can easily get started in training</Cue>
<Cue start="15:00" end="15:03">to recognize the bolts that do not have an anomaly.</Cue>
<Cue start="15:04" end="15:06">And the ones that do, which is a small data set</Cue>
<Cue start="15:06" end="15:10">and I think that's really one of the most important things today.</Cue>
<Cue start="15:11" voice="Ryan Loney" />
<Cue start="15:11" end="15:14">Challenges is one is access to data, but the other is</Cue>
<Cue start="15:14" end="15:17">is needing a massive amount of data to do something meaningful.</Cue>
<Cue start="15:18" end="15:22">And so we're starting to try to change that dynamic with Anomali.</Cue>
<Cue start="15:22" end="15:27">So you may not need 100,000 images, you may need 100 images,</Cue>
<Cue start="15:27" end="15:33">and you can start detecting anomalies in everything from batteries to bolts to,</Cue>
<Cue start="15:33" end="15:37">you know, maybe even the wood varnish use case that you mentioned.</Cue>
<Cue start="15:37" voice="Burr Sutter" />
<Cue start="15:37" end="15:40">That is very key point because often in that data scientist</Cue>
<Cue start="15:40" end="15:43">process, that data engineer and data scientist process, right.</Cue>
<Cue start="15:43" end="15:44">The one key thing is can you gather</Cue>
<Cue start="15:44" end="15:47">the data that you need for the input for the model training?</Cue>
<Cue start="15:47" end="15:49">And we've often sat at least people I've worked</Cue>
<Cue start="15:49" end="15:52">with over the last couple of years, you know, you need a lot of data.</Cue>
<Cue start="15:52" end="15:55">You need tens of thousands of correct images</Cue>
<Cue start="15:55" end="15:58">so we can sort out the difference between dogs versus cats, let's say,</Cue>
<Cue start="15:58" end="16:01">or you need dozens and dozens of situations</Cue>
<Cue start="16:01" end="16:03">where if it's a natural language processing scenario,</Cue>
<Cue start="16:03" end="16:06">you know, a good customer interaction, a good customer conversation,</Cue>
<Cue start="16:06" end="16:07">and in this case,</Cue>
<Cue start="16:07" end="16:11">it sounds like what you're saying is show us just the bad things, right?</Cue>
<Cue start="16:11" end="16:14">Fewer images, fewer incorrect things,</Cue>
<Cue start="16:14" end="16:17">and then let us look for those kind of anomalies.</Cue>
<Cue start="16:18" end="16:20">Can tell us more about that because that is very interesting.</Cue>
<Cue start="16:20" end="16:23">The concept that I can use a much smaller dataset as my input</Cue>
<Cue start="16:23" end="16:26">as opposed to gathering terabytes of data in some cases</Cue>
<Cue start="16:26" end="16:29">to just simply get my model training underway.</Cue>
<Cue start="16:30" voice="Ryan Loney" />
<Cue start="16:30" end="16:34">You know, like you described, the idea is if you have some good images</Cue>
<Cue start="16:34" end="16:37">and then you have some of the the known defects</Cue>
<Cue start="16:38" end="16:41">and you can just label here's a set of good images</Cue>
<Cue start="16:41" end="16:44">and here's a few of the defects and you can right away</Cue>
<Cue start="16:44" end="16:48">start detecting those specific defects that you've identified.</Cue>
<Cue start="16:48" end="16:49">And then also, you know, be able to</Cue>
<Cue start="16:50" end="16:53">determine when it doesn't match</Cue>
<Cue start="16:53" end="16:57">the expected appearance of a non defective item.</Cue>
<Cue start="16:57" end="17:00">So if I have the undamaged screw and then I introduce</Cue>
<Cue start="17:00" end="17:03">one with some new anomaly that's never been seen before,</Cue>
<Cue start="17:04" end="17:07">I can say, you know, this one is not a valid screw.</Cue>
<Cue start="17:07" end="17:11">And so that's sort of the the approach that we're taking.</Cue>
<Cue start="17:11" end="17:15">And it's really important because so often you need to have</Cue>
<Cue start="17:15" end="17:19">subject matter experts often like if you think the take the battery example,</Cue>
<Cue start="17:20" end="17:23">there's these workers who are on the floor</Cue>
<Cue start="17:23" end="17:27">in a factory and they're the ones who know best when they look at these images,</Cue>
<Cue start="17:28" end="17:31">which one's going to have an issue, which one's defective?</Cue>
<Cue start="17:31" voice="Ryan Loney" />
<Cue start="17:31" end="17:34">And then they also need to take that subject matter, expertise</Cue>
<Cue start="17:35" end="17:38">and then use it to annotate data sets.</Cue>
<Cue start="17:38" end="17:39">And when you have these, you know,</Cue>
<Cue start="17:39" end="17:43">tens of thousands of images you need to annotate, it's asking those people</Cue>
<Cue start="17:43" end="17:47">to stop working on the factory floor so they can come annotate some images.</Cue>
<Cue start="17:47" end="17:49">That's a tough business call to make, right?</Cue>
<Cue start="17:49" end="17:53">But if you only need them to annotate a handful of images, it's a much easier</Cue>
<Cue start="17:53" end="17:56">ask to get the ball rolling and demonstrate value.</Cue>
<Cue start="17:56" end="17:59">And maybe over time you will want to annotate more</Cue>
<Cue start="17:59" end="18:03">and more images because you'll get even better accuracy in the model.</Cue>
<Cue start="18:03" end="18:07">Even better, even if it's just small incremental improvements.</Cue>
<Cue start="18:08" end="18:11">You know, that's something that if it generates value for the business,</Cue>
<Cue start="18:11" end="18:14">it's something the business will invest in over time.</Cue>
<Cue start="18:14" end="18:17">But you have to convince the decision makers that it's worth</Cue>
<Cue start="18:17" end="18:22">the time of these subject matter experts to stop what they're doing</Cue>
<Cue start="18:22" end="18:26">and go and label some images of the things that they're working on in the factory.</Cue>
<Cue start="18:26" voice="Burr Sutter" />
<Cue start="18:26" end="18:30">And that labeling process can be very labor intensive of the annotations,</Cue>
<Cue start="18:30" end="18:33">basically saying what is correct, what's wrong, what is this, what is that?</Cue>
<Cue start="18:33" end="18:36">And therefore, if we can minimize that time frame to get the value quicker,</Cue>
<Cue start="18:36" end="18:40">then there's something that's useful for the business, useful for the organization</Cue>
<Cue start="18:40" end="18:41">long before we necessarily good.</Cue>
<Cue start="18:41" end="18:43">There are huge model training based,</Cue>
<Cue start="18:49" voice="Burr Sutter" />
<Cue start="18:49" end="18:52">so we talk about labeling and how that is labor intensive activity.</Cue>
<Cue start="18:52" end="18:54">But I love the idea of helping the human</Cue>
<Cue start="18:54" end="18:57">and helping the human models specifically not get bored.</Cue>
<Cue start="18:57" end="19:01">Basically, if the human is eyeballing a bunch of widgets flying by over time,</Cue>
<Cue start="19:01" end="19:03">they make mistakes, they get bored</Cue>
<Cue start="19:03" end="19:06">and they don't pay as close attention as they should.</Cue>
<Cue start="19:07" end="19:10">That's why the concept of Amazon specifically computer vision, augmenting</Cue>
<Cue start="19:10" end="19:14">that capability and really helping the human identify anomalies faster,</Cue>
<Cue start="19:14" end="19:17">more quickly, maybe with greater accuracy could be a big win.</Cue>
<Cue start="19:18" end="19:21">We focused on manufacturing, but let's actually go into health care</Cue>
<Cue start="19:21" end="19:24">and learn how these tools can be used in that sector and that industry.</Cue>
<Cue start="19:24" end="19:28">Ryan talked to me about how Open Windows runtime can be incorporated into medical</Cue>
<Cue start="19:28" end="19:32">imaging equipment with intel processors and better than c.T.</Cue>
<Cue start="19:32" end="19:34">MRI and ultrasound machines.</Cue>
<Cue start="19:34" end="19:37">Well, these inferences, this AML workload can be operating</Cue>
<Cue start="19:37" end="19:41">and executing right there in the same physical room as the patient.</Cue>
<Cue start="19:44" voice="Ryan Loney" />
<Cue start="19:44" end="19:46">We did a presentation when she last year.</Cue>
<Cue start="19:46" end="19:47">I think they said</Cue>
<Cue start="19:47" end="19:50">there's at least 80 countries that have their X-ray machines deployed</Cue>
<Cue start="19:51" end="19:56">and they're doing things like helping doctors place breathing tubes in patients.</Cue>
<Cue start="19:56" end="20:01">So during COVID, during the pandemic, that was a really important tool</Cue>
<Cue start="20:01" end="20:05">to help with nurses and doctors who were intubating patients</Cue>
<Cue start="20:05" end="20:09">sometimes like in a parking lot or a hallway of the hospital.</Cue>
<Cue start="20:09" end="20:14">And, you know, when they had a statistic that you said, I think one out of four</Cue>
<Cue start="20:14" end="20:17">breathing tubes gets placed incorrectly</Cue>
<Cue start="20:17" end="20:19">when you're doing it outside the operating room,</Cue>
<Cue start="20:19" end="20:22">because when you're in an operating room, it's much more controlled</Cue>
<Cue start="20:22" end="20:24">and there's someone who's an expert at placing the tubes.</Cue>
<Cue start="20:24" end="20:28">It's something you have more of a controlled environment</Cue>
<Cue start="20:28" end="20:31">than when you're out in a parking lot, in a tent.</Cue>
<Cue start="20:31" end="20:34">You know, when the hospital's completely full and you're triaging patients</Cue>
<Cue start="20:34" end="20:37">with COVID, that's when they're more likely to make mistakes.</Cue>
<Cue start="20:37" end="20:40">And so they had this endotracheal tube placement</Cue>
<Cue start="20:42" end="20:43">model that they trained,</Cue>
<Cue start="20:43" end="20:47">and it helped to use an x ray and give an alert and say, hey,</Cue>
<Cue start="20:47" end="20:50">this tube is placed wrong, pull it out and do it again.</Cue>
<Cue start="20:50" end="20:53">And so things like that help doctors so that they can avoid mistakes.</Cue>
<Cue start="20:54" end="20:57">And, you know, having a breathing tube placed incorrectly</Cue>
<Cue start="20:57" end="21:01">can cause collapsed lung and a number of other unwanted side effects.</Cue>
<Cue start="21:01" end="21:03">So it's really important to do it correctly.</Cue>
<Cue start="21:03" end="21:06">Another example is Samsung Medicine.</Cue>
<Cue start="21:06" end="21:10">They actually are doing estimating fetal angle of progression.</Cue>
<Cue start="21:10" end="21:13">So this is analyzing ultrasound</Cue>
<Cue start="21:14" end="21:18">of pregnant women with that, being able to to help take measurements</Cue>
<Cue start="21:18" end="21:22">that are usually hard to calculate that can be done in an automated way.</Cue>
<Cue start="21:22" end="21:26">They're already taking the ultrasound scan and now they're executing this model.</Cue>
<Cue start="21:26" end="21:31">They can take some of these measurements to help the doctor avoid potentially more</Cue>
<Cue start="21:31" end="21:34">intrusive alternative methods so the patient wins.</Cue>
<Cue start="21:35" end="21:36">It makes their life better.</Cue>
<Cue start="21:36" end="21:39">And the doctors is getting help from this A.I.</Cue>
<Cue start="21:39" end="21:40">model.</Cue>
<Cue start="21:40" end="21:42">And those are, you know, just a few examples.</Cue>
<Cue start="21:42" voice="Burr Sutter" />
<Cue start="21:42" end="21:45">Those are some amazing examples when it comes to all these things.</Cue>
<Cue start="21:45" end="21:49">We're talking like CT scans, right, and x rays, other examples of computer vision.</Cue>
<Cue start="21:49" end="21:52">One thing that's kind of interesting in the space, I think</Cue>
<Cue start="21:52" end="21:56">whenever I get a chance to work on, let's say an object traction model</Cue>
<Cue start="21:56" end="21:58">and one of our workshops, by the way, is actually putting that out</Cue>
<Cue start="21:58" end="22:01">in front of people to say, Hey, look, you can use your phone.</Cue>
<Cue start="22:01" end="22:04">And it basically sends the image over to our OpenShift, right,</Cue>
<Cue start="22:04" end="22:07">with our data science platform and then analyzes what you see.</Cue>
<Cue start="22:08" end="22:09">And even in my case, where I take a picture of my dog</Cue>
<Cue start="22:09" end="22:13">as an example, it can't really decide is it a dog or a cat?</Cue>
<Cue start="22:13" end="22:15">I have a very funny looking dog,</Cue>
<Cue start="22:15" voice="Burr Sutter" />
<Cue start="22:15" end="22:18">and so there's always a percentage outcome, you know?</Cue>
<Cue start="22:18" end="22:21">In other words, I think it's a dog 52%.</Cue>
<Cue start="22:21" end="22:22">So I want to talk about that more.</Cue>
<Cue start="22:22" end="22:25">What how important is it to get to 100% accuracy?</Cue>
<Cue start="22:25" end="22:29">How important is it to really, depending on the use case, to allow</Cue>
<Cue start="22:29" end="22:34">for the gray area, if you will, where it's an 80% accuracy or 70% accuracy?</Cue>
<Cue start="22:34" end="22:36">And where are the trade offs there associated with the application?</Cue>
<Cue start="22:36" end="22:38">Can you can you discuss that more?</Cue>
<Cue start="22:38" voice="Ryan Loney" />
<Cue start="22:38" end="22:40">Accuracy is definitely, you know, a touchy subject</Cue>
<Cue start="22:40" end="22:43">because how you measure it makes a huge difference.</Cue>
<Cue start="22:43" end="22:46">And then I think with like what you were describing with the dog example, there's</Cue>
<Cue start="22:46" end="22:51">sort of a top five potential classes that might may be identified.</Cue>
<Cue start="22:51" end="22:55">So let's say you're doing object detection and you detect a region of interest</Cue>
<Cue start="22:55" end="22:57">and it says 65% confidence.</Cue>
<Cue start="22:57" end="22:58">This is a dog.</Cue>
<Cue start="22:58" end="23:03">Well, the next potential label that could be maybe 50% confidence</Cue>
<Cue start="23:03" end="23:08">or 20% confidence might be something similar to a dog or in the case of models</Cue>
<Cue start="23:08" end="23:11">that have been trained on like the image net dataset</Cue>
<Cue start="23:11" end="23:15">or on cocoa data set, they have like actual breeds of dogs.</Cue>
<Cue start="23:15" end="23:20">So if I want to look at the top five labels for a dog,</Cue>
<Cue start="23:20" end="23:24">for my dog, for example, she's a mixed mostly Labrador retriever.</Cue>
<Cue start="23:24" voice="Ryan Loney" />
<Cue start="23:24" end="23:29">But I may look at the top five labels and it may say 65% confidence that she's</Cue>
<Cue start="23:29" end="23:34">a flat coated retriever and then confidence that she's a husky,</Cue>
<Cue start="23:34" end="23:39">as you know, 20% and then 5% confidence that she's a greyhound or something.</Cue>
<Cue start="23:40" end="23:42">Those labels, all of them are dogs.</Cue>
<Cue start="23:42" end="23:45">So if I'm just trying to figure out is, is this a dog,</Cue>
<Cue start="23:45" end="23:50">I could probably find all of the, you know, classes within the data set</Cue>
<Cue start="23:50" end="23:53">and say, well, these are all, you know, class ID</Cue>
<Cue start="23:53" end="24:00">65, 132, 92 and 158 all belong to a group of dogs.</Cue>
<Cue start="24:00" end="24:04">So if I wanted to just write an application to tell me if this is a dog</Cue>
<Cue start="24:04" end="24:07">or not, I would probably use that to determine if it's a dog.</Cue>
<Cue start="24:08" end="24:10">But how you measure that is accuracy.</Cue>
<Cue start="24:10" end="24:11">Well, that's where it gets a little bit complicated,</Cue>
<Cue start="24:11" end="24:15">because if you're being really strict about the definition and you're</Cue>
<Cue start="24:15" end="24:18">trying to validate against the data set of labeled images</Cue>
<Cue start="24:18" end="24:22">and I have specific dog breeds or some specific detail</Cue>
<Cue start="24:22" end="24:25">and it doesn't match, well, then the accuracy is going to go down.</Cue>
<Cue start="24:25" voice="Ryan Loney" />
<Cue start="24:25" end="24:29">That's especially important when we talk about things like compression</Cue>
<Cue start="24:29" end="24:30">and quantization,</Cue>
<Cue start="24:30" end="24:34">which, you know, historically has been difficult for to get adoption</Cue>
<Cue start="24:34" end="24:40">in some domains like health care, where even the hint of accuracy going down</Cue>
<Cue start="24:40" end="24:44">implies that we're not going to be able to help in some small case,</Cue>
<Cue start="24:44" end="24:47">maybe if it's even half a percent of the time</Cue>
<Cue start="24:47" end="24:51">we want to take that that tube is placed incorrectly or that, you know,</Cue>
<Cue start="24:51" end="24:54">that patient's, you know, lung has collapsed or something like that.</Cue>
<Cue start="24:54" end="24:58">And that's something that really prevents adoption of some of these methods</Cue>
<Cue start="24:58" end="25:01">that can really boost performance like quantization.</Cue>
<Cue start="25:01" end="25:05">But if you take that example of sort of different from the dog example</Cue>
<Cue start="25:05" end="25:07">and you think about like segmentation of kidneys.</Cue>
<Cue start="25:07" end="25:11">So if I'm doing kidney segmentation, which is, you know, taking a CT scan</Cue>
<Cue start="25:12" end="25:14">and then trying to pick the pixels out of that</Cue>
<Cue start="25:14" end="25:17">scan that belong to a kidney,</Cue>
<Cue start="25:17" end="25:20">how I measure accuracy may be</Cue>
<Cue start="25:20" end="25:24">how many of those pixels I'm able to detect and how many did I miss?</Cue>
<Cue start="25:25" voice="Ryan Loney" />
<Cue start="25:25" end="25:29">Missing some of the pixels is maybe not a problem, right,</Cue>
<Cue start="25:29" end="25:33">depending on how you built the application because you still detect the kidney</Cue>
<Cue start="25:34" end="25:38">and maybe you just need to apply padding around the region of interest</Cue>
<Cue start="25:38" end="25:41">so that you don't miss any of the the actual kidney.</Cue>
<Cue start="25:42" end="25:45">When you compress the model and when you quantized the model. But</Cue>
<Cue start="25:45" end="25:50">that requires, you know, data scientist and email engineer somebody to really</Cue>
<Cue start="25:51" end="25:52">they have to be</Cue>
<Cue start="25:52" end="25:55">able to go and apply that after the fact, after the inference</Cue>
<Cue start="25:55" end="25:59">happens to make sure that you're not losing critical information,</Cue>
<Cue start="25:59" end="26:02">because the next step from detecting the kidney may be detecting a tumor.</Cue>
<Cue start="26:03" voice="Ryan Loney" />
<Cue start="26:03" end="26:06">And so maybe you can use the more optimized model</Cue>
<Cue start="26:06" end="26:11">to detect the kidney, but then you can use a slower model to detect the tumor.</Cue>
<Cue start="26:11" end="26:15">But that also requires somebody to architect and make that decision</Cue>
<Cue start="26:15" end="26:16">or that tradeoff and say,</Cue>
<Cue start="26:16" end="26:20">well, I need to add padding, or I should only use the quantized model</Cue>
<Cue start="26:20" end="26:24">to detect the region of interest for the kidney and then use the model</Cue>
<Cue start="26:24" end="26:27">that takes longer to do the inference</Cue>
<Cue start="26:27" end="26:30">just to find the tumor, which is going to be on a smaller size.</Cue>
<Cue start="26:30" end="26:33">Right. The dimensions are going to be much smaller</Cue>
<Cue start="26:33" end="26:35">once we crop to the region of interest.</Cue>
<Cue start="26:35" end="26:40">But all of those details, that's maybe not easy to explain in a few sentences.</Cue>
<Cue start="26:40" end="26:43">And even the way I explained it is probably really confusing.</Cue>
<Cue start="26:45" voice="Burr Sutter" />
<Cue start="26:45" end="26:46">I do love that use case.</Cue>
<Cue start="26:46" end="26:47">Like you mentioned, the cropping</Cue>
<Cue start="26:47" end="26:50">even in one such an area that we worked on for another project,</Cue>
<Cue start="26:50" end="26:53">we specifically decided to pix like the image that we had taken</Cue>
<Cue start="26:53" end="26:57">because we knew that we could get the outcome we wanted by even</Cue>
<Cue start="26:57" end="27:01">just using a smaller or less having less resolution in our image.</Cue>
<Cue start="27:01" end="27:04">And therefore, as we transferred it from the mobile device storage device</Cue>
<Cue start="27:04" end="27:08">up into the cloud, we wanted that smaller image just for transfer purposes</Cue>
<Cue start="27:08" end="27:11">and it still we could get the accuracy we needed by a lot of testing.</Cue>
<Cue start="27:11" voice="Burr Sutter" />
<Cue start="27:11" end="27:14">And one thing that's interesting about that from my perspective is</Cue>
<Cue start="27:15" end="27:18">if you're doing image processing, sometimes it takes a while</Cue>
<Cue start="27:18" end="27:20">for this transaction to occur.</Cue>
<Cue start="27:20" end="27:20">Like I,</Cue>
<Cue start="27:20" end="27:24">I come from a traditional application background, you know, where I'm reading</Cue>
<Cue start="27:24" end="27:25">and writing things from a database</Cue>
<Cue start="27:25" end="27:28">or a message broker or moving data from one place to another.</Cue>
<Cue start="27:28" end="27:29">Those things happen subsequent.</Cue>
<Cue start="27:29" end="27:33">Normally, even with great latency between your data centers, you know,</Cue>
<Cue start="27:33" end="27:34">it's still subsequent.</Cue>
<Cue start="27:34" end="27:38">In most cases, while on a transaction like this, one can actually take 2 seconds</Cue>
<Cue start="27:38" end="27:42">or 4 seconds as it's doing its analysis and actually coming back with, you know,</Cue>
<Cue start="27:42" end="27:46">I think it's a dog, I think it's a kidney, I think it's whatever, and provided me</Cue>
<Cue start="27:46" end="27:48">that accuracy statement.</Cue>
<Cue start="27:48" end="27:51">So that concept of optimization is very important</Cue>
<Cue start="27:51" end="27:53">in the overall application architecture.</Cue>
<Cue start="27:53" end="27:56">Would you agree with that or how do you think about that concept?</Cue>
<Cue start="27:56" end="27:56">Yeah, definitely.</Cue>
<Cue start="27:56" voice="Ryan Loney" />
<Cue start="27:56" end="27:58">It depends too on the use case.</Cue>
<Cue start="27:58" end="28:02">So if you think about how important it is to reduce the latency</Cue>
<Cue start="28:02" end="28:06">and increase the number of frames per second that you can process when you're</Cue>
<Cue start="28:06" end="28:10">talking about a loss prevention model that's running at a grocery store.</Cue>
<Cue start="28:10" end="28:13">So you want to keep the lines moving.</Cue>
<Cue start="28:13" end="28:16">You don't want every person who's at the self-checkout</Cue>
<Cue start="28:16" end="28:19">to have to wait 5 seconds for every item they scan.</Cue>
<Cue start="28:19" end="28:22">You need it to happen as quickly as possible.</Cue>
<Cue start="28:22" end="28:25">And if sometimes you, you know, the accuracy</Cue>
<Cue start="28:25" end="28:28">decreases slightly or the I'd say the accuracy of the whole pipeline.</Cue>
<Cue start="28:28" end="28:32">So not just looking at the individual model or the individual inference, but</Cue>
<Cue start="28:32" end="28:36">let's say that the the whole pipeline is not as successful at detecting</Cue>
<Cue start="28:37" end="28:40">when somebody steals one item from the self-checkout,</Cue>
<Cue start="28:41" end="28:43">it's not going to be a life threatening situation.</Cue>
<Cue start="28:43" end="28:47">Whereas, you know, being in the hooked up to the X-ray machine</Cue>
<Cue start="28:47" end="28:51">with the two placement model, they might be willing to have the doctor,</Cue>
<Cue start="28:51" end="28:54">the nurse wait 5 seconds to get the result.</Cue>
<Cue start="28:55" voice="Ryan Loney" />
<Cue start="28:55" end="28:58">They don't need it to happen in 500 milliseconds.</Cue>
<Cue start="28:58" end="29:02">So they're willing their threshold for waiting is a little bit higher.</Cue>
<Cue start="29:02" end="29:05">So that, I think, also drives some of the decision, like</Cue>
<Cue start="29:06" end="29:09">you want to keep people moving through the checkout line</Cue>
<Cue start="29:09" end="29:13">and you can afford to to potentially if you lose a little bit of accuracy here</Cue>
<Cue start="29:13" end="29:14">and there, it's not going to</Cue>
<Cue start="29:14" end="29:18">cost the company that much money or it's not going to be life threatening.</Cue>
<Cue start="29:18" end="29:21">It's going to be worth the tradeoff of keeping the line moving</Cue>
<Cue start="29:21" end="29:24">and not having people leave the store and not check out at all.</Cue>
<Cue start="29:24" end="29:27">And to say, I'm not going to shop today because the line's too long.</Cue>
<Cue start="29:30" voice="Burr Sutter" />
<Cue start="29:30" end="29:32">There are so many trade offs and enterprise</Cue>
<Cue start="29:32" end="29:35">AML use cases, things like latency, accuracy and availability.</Cue>
<Cue start="29:35" end="29:40">And certainly complexities abound, especially in an obviously ever evolving</Cue>
<Cue start="29:40" end="29:43">technological landscape where we are still very early in the adoption of AML.</Cue>
<Cue start="29:44" end="29:47">And to navigate that complexity, the direct feedback from real world</Cue>
<Cue start="29:47" end="29:51">end users is essential to Ryan and his team at Intel.</Cue>
<Cue start="29:52" end="29:54">What would you say are some of the big hurdles or big</Cue>
<Cue start="29:54" end="29:57">outcomes, big opportunities in that space?</Cue>
<Cue start="29:57" end="30:01">And do you agree that we're kind of still at the very beginning in our infancy,</Cue>
<Cue start="30:01" end="30:01">if you will,</Cue>
<Cue start="30:01" end="30:05">of adopting these technologies and and discovering what they can do for us?</Cue>
<Cue start="30:05" voice="Ryan Loney" />
<Cue start="30:05" end="30:07">Yeah, I think we're definitely in the infancy</Cue>
<Cue start="30:07" end="30:10">and I think that what we've seen is our customers are evolving</Cue>
<Cue start="30:10" end="30:14">and the people who are deploying on Intel hardware, they're trying to run</Cue>
<Cue start="30:14" end="30:16">more complicated models.</Cue>
<Cue start="30:16" end="30:19">They're the models that are doing object detection or, you know,</Cue>
<Cue start="30:19" end="30:22">detecting defects and, you know, doing segmentation.</Cue>
<Cue start="30:23" end="30:27">You know, in the past you could say, oh, here's a generic model that will do face</Cue>
<Cue start="30:27" end="30:31">detection or person detection or vehicle detection and license plate detection.</Cue>
<Cue start="30:32" end="30:33">And those are sort of like</Cue>
<Cue start="30:33" end="30:36">general purpose models that you can just grab off the shelf and use them.</Cue>
<Cue start="30:37" end="30:40">But now we're moving into like the anomaly scenarios</Cue>
<Cue start="30:40" end="30:44">where I've got my own data and I'm trying to do something very specific</Cue>
<Cue start="30:45" end="30:47">and I'm the only one that has access to this data.</Cue>
<Cue start="30:47" end="30:51">And you don't have a public data set that you can go download</Cue>
<Cue start="30:51" end="30:54">that's under Creative Commons license for, you know, car batteries.</Cue>
<Cue start="30:54" end="30:57">It's, you know, it's just not something that's available.</Cue>
<Cue start="30:57" voice="Ryan Loney" />
<Cue start="30:57" end="31:02">And so those use cases, the challenge with with training those models</Cue>
<Cue start="31:02" end="31:06">and and getting them optimized is the beginning of the pipeline.</Cue>
<Cue start="31:06" end="31:10">It's the data you have to get the data you have to annotated</Cue>
<Cue start="31:10" end="31:12">and the tools have to exist for you to do that.</Cue>
<Cue start="31:12" end="31:15">And that's part of the problem that we're trying to help solve.</Cue>
<Cue start="31:16" end="31:17">And then the models are getting more complex.</Cue>
<Cue start="31:17" end="31:21">So if you think, you know, just from working with customers recently,</Cue>
<Cue start="31:21" end="31:22">you know, they're no longer</Cue>
<Cue start="31:22" end="31:26">just trying to do image classification and, you know, like is it a dog or a cat?</Cue>
<Cue start="31:26" end="31:29">They've moved on to like 3D point clouds</Cue>
<Cue start="31:29" end="31:34">and, you know, 3D segmentation models and things that are like the speech</Cue>
<Cue start="31:34" end="31:39">synthesis example, doing things these GPT models that are generating,</Cue>
<Cue start="31:40" end="31:44">you know, you, you put a text input and it generates an image for you.</Cue>
<Cue start="31:44" end="31:47">It's just becoming much more advanced, much more sophisticated</Cue>
<Cue start="31:48" end="31:50">and on larger images.</Cue>
<Cue start="31:50" voice="Ryan Loney" />
<Cue start="31:50" end="31:54">And so things like running super resolution enhancing images, upscaling</Cue>
<Cue start="31:54" end="31:59">images, instead of just trying to take that, you know, 200 by 200 pixel</Cue>
<Cue start="32:00" end="32:02">image and classifying if it's a cat.</Cue>
<Cue start="32:02" end="32:05">Now we're talking about gigantic</Cue>
<Cue start="32:05" end="32:09">huge images that we're processing and that all requires</Cue>
<Cue start="32:09" end="32:12">more resources or more optimized models.</Cue>
<Cue start="32:13" end="32:16">And, you know, every computer vision conference or A.I.</Cue>
<Cue start="32:16" end="32:19">conference, there's there's a new latest and greatest architecture.</Cue>
<Cue start="32:19" end="32:22">There's new research paper, and things are getting adopted much faster.</Cue>
<Cue start="32:23" end="32:27">The lead time for a nurse paper or CV PR</Cue>
<Cue start="32:27" end="32:30">for a company to actually adopt and put those into production.</Cue>
<Cue start="32:30" end="32:32">It's like the time shortens every year.</Cue>
<Cue start="32:33" voice="Burr Sutter" />
<Cue start="32:33" end="32:35">Well, Ryan, I got to tell you, I could talk to you</Cue>
<Cue start="32:35" end="32:39">literally all day about these topics, the various use cases, the various ways</Cue>
<Cue start="32:39" end="32:41">models are being optimized,</Cue>
<Cue start="32:41" end="32:44">how to put models into a pipeline for average enterprise applications.</Cue>
<Cue start="32:44" end="32:47">I've enjoyed learning about pop and vino and anomalies,</Cue>
<Cue start="32:47" end="32:50">but I'm fascinated by this because I will have a chance to go try this myself.</Cue>
<Cue start="32:51" end="32:52">Taking advantage of Red Hat OpenShift</Cue>
<Cue start="32:52" end="32:54">and taking advantage of our data science platform.</Cue>
<Cue start="32:54" end="32:58">On top of that, I will definitely go be poking at this myself.</Cue>
<Cue start="32:58" end="33:00">So thank you so much for your time today.</Cue>
<Cue start="33:00" voice="Ryan Loney" />
<Cue start="33:00" end="33:00">Thanks, Burr.</Cue>
<Cue start="33:00" end="33:01">This was a lot of fun.</Cue>
<Cue start="33:01" end="33:04">Thanks for having me.</Cue>
<Cue start="33:04" voice="Burr Sutter" />
<Cue start="33:04" end="33:06">And you can check out</Cue>
<Cue start="33:06" end="33:09">the full transcript of our conversation and more resources,</Cue>
<Cue start="33:09" end="33:12">like a link to a white paper on open vino and normal lib at Red Hat dot</Cue>
<Cue start="33:12" end="33:15">com slash code Comments Podcast.</Cue>
<Cue start="33:15" end="33:19">This episode was produced by Brant Seminole and Caroline Prickett.</Cue>
<Cue start="33:20" end="33:21">Our sound designer is Christian.</Cue>
<Cue start="33:21" end="33:26">From our audio team includes Lee Day, Stephanie Wunderlich, Mike Esser,</Cue>
<Cue start="33:27" end="33:32">Laura Barnes, Claire Allison, Nick Burns, Aaron Williamson, Karen King,</Cue>
<Cue start="33:32" end="33:36">Booboo House, Rachel Artell, Mike Compton, Ocean</Cue>
<Cue start="33:36" end="33:40">Mathews, Laura Walters, Alex Trabelsi and Victoria Lutton.</Cue>
<Cue start="33:41" end="33:43">I'm your host, Burt Sutter.</Cue>
<Cue start="33:43" end="33:45">Thank you for joining me today on Code Comments.</Cue>
<Cue start="33:45" end="33:48">I hope you enjoyed today's session and today's conversation, and I</Cue>
<Cue start="33:48" end="33:52">look forward to many more in.</Cue>
</Transcript>
</AudioPlayer>
<h2>Even with more headings</h2>
<p>This last heading is allowed to go back up to h2, but the player should still take h3 as its root heading level.</p>
</section>
<link rel="stylesheet" href="../rh-audio-player-lightdom.css" />
);