Aug. 14, 2024

164 - Experiences with AI with Xinyan Huang

164 - Experiences with AI with Xinyan Huang
Apple Podcasts podcast player badge
Spotify podcast player badge
Apple Podcasts podcast player icon Spotify podcast player icon

The last time I had Xinyan on the show was in 2021, and we were all excited about the possibilities that AI could bring to Fire Safety Engineering and Smart Firefighting. Three years have passed, and while we are still excited, we can now talk about experiences. What worked and what did not? Where were the challenges, and what was simple? You can only learn that from brainstorming, you learn this by doing. Xinyan's team implemented dozens of algorithms for various projects, and it is this experience we try to explore today.
 
The episode is bitter-sweet. Even though considerable progress was made in the AI layer, it is still not possible to implement this in firefighting. The barriers that always separated fire science from firefighting are still in place, and it is even harder to cross them with such a novel approach. As always, communication is the key. However, in the midst of the research, a realization was made. AI does not work that great with humans, but works perfectly well with robots. This gives a beginning to a new chapter - AI-powered robotic firefighting, and hell, this is really exciting stuff.

Besides smart firefighting, we spend good time discussing use of AI in Fire Safety Engineering itself. Xinyan's team is developing practical tools to assist the designers and engineers, and they look promising. What is most interesteing is that the implementation of those tools reasembles  how CFD was implemented back in the day - I have huge hopes for this technology.

If you want to read more about AI in PBD FSE, this is the paper you look for: https://www.sciencedirect.com/science/article/pii/S2352710221003867#appsec1

If you want to learn more about the work of the PolyU X Fire Lab, learn more on their up-to-date webpage:  https://www.firelabxy.com/

----
The Fire Science Show is produced by the Fire Science Media in collaboration with OFR Consultants. Thank you to the podcast sponsor for their continuous support towards our mission.

Chapters

00:00 - AI in Fire Safety Engineering

13:26 - AI in Fire Engineering

18:57 - AI for Fire Size Prediction

26:31 - Advancing Fire Safety With AI

35:02 - Challenges in Firefighter AI Communication

44:52 - Advancing AI in Fire Safety

Transcript
WEBVTT

00:00:00.180 --> 00:00:02.028
Hello everybody, welcome to the Fire Science Show.

00:00:02.450 --> 00:00:11.320
Today we're going to talk AI in fire safety engineering and I am very excited because we're not going to hypothesize what the use of AI will look like.

00:00:11.320 --> 00:00:16.452
We're going to talk about experiences in doing that and that's something very unique.

00:00:16.452 --> 00:00:28.126
With my guest Professor Sinian Huang from Hong Kong Polytechnic University, we've hypothesized how it could look like and talked about his early experiences three years ago in episode seven.

00:00:28.126 --> 00:00:40.905
Actually, that was one of the first episodes of the Fire Science Show and today, three years fast forward, we can talk about a lot more experiences that Simeon and his group has gained over those years.

00:00:40.905 --> 00:00:46.615
They're on the forefront of implementing AI in various kinds of fire science.

00:00:46.615 --> 00:00:49.546
And we're not talking chatbot AI.

00:00:49.546 --> 00:00:59.591
We're talking neural networks and using it to predict fire behaviors, to predict fire phenomena, to measure fire and to help in engineering design.

00:00:59.591 --> 00:01:21.376
It all started with smart firefighting, so the theme of episode seven and the discussion back then was how we can use AI to assist firefighters and, if you're curious how this ended, it's at the same time interesting, to some extent disappointing and, at the same time, exciting.

00:01:21.376 --> 00:01:37.793
Some pathways did not lead anywhere, but some pathways lead to extremely exciting places and we're also going to talk about that later in the episode, and if you want to learn about that, well, first intro and then let's go with the AI in fire safety engineering.

00:01:43.600 --> 00:01:45.168
Welcome to the Fireiresize Show.

00:01:45.168 --> 00:01:48.670
My name is Wojciech Wigrzyński and I will be your host.

00:01:48.670 --> 00:02:04.510
This podcast is brought to you in collaboration with OFR Consultants.

00:02:04.510 --> 00:02:07.468
Ofr is the UK's leading fire risk consultancy.

00:02:07.468 --> 00:02:18.312
Its globally established team has developed a reputation for preeminent fire engineering expertise, with colleagues working across the world to help protect people, property and environment.

00:02:18.312 --> 00:02:34.116
Established in the UK in 2016 as a startup business of two highly experienced fire engineering consultants, the business has grown phenomenally in just seven years, with offices across the country in seven locations, from Edinburgh to Bath, and now employing more than 100 professionals.

00:02:34.116 --> 00:02:45.760
Colleagues are on a mission to continually explore the challenges that fire creates for clients and society, applying the best research, experience and diligence for effective, tailored fire safety solutions.

00:02:45.760 --> 00:02:56.849
In 2024, ofr will grow its team once more and is always keen to hear from industry professionals who would like to collaborate on fire safety futures this year.

00:02:56.849 --> 00:02:59.743
Get in touch at OFRConsultantscom.

00:03:00.185 --> 00:03:01.990
Hello everybody, welcome to the Fire Science Show.

00:03:01.990 --> 00:03:06.109
I am here today with Professor Sinan Huang from Hong Kong Polytechnic University.

00:03:06.109 --> 00:03:09.647
Hey, sinan Hi Bozsik, good to see you again.

00:03:09.647 --> 00:03:12.288
Very happy to have you back in the podcast.

00:03:12.288 --> 00:03:15.389
You were one of the first 10 episodes.

00:03:15.389 --> 00:03:18.188
I can call you the OG of the Fire Science Show.

00:03:18.188 --> 00:03:21.352
Yeah, I'm F-7.

00:03:21.352 --> 00:03:25.430
Yeah, nice 007, licensed to do AI in fire safety engineering.

00:03:25.430 --> 00:03:30.411
Good, good, and we're going to continue the discussion that stopped in episode seven.

00:03:30.411 --> 00:03:41.068
Gosh, that's a long time ago, but in that episode we've discussed smart firefighting and different ways of using AI to assist firefighters.

00:03:41.068 --> 00:03:48.562
I remember you were very happy back then by a large grant that your unit was given on this topic.

00:03:48.562 --> 00:03:51.330
I know a lot of papers came out of your office.

00:03:51.330 --> 00:03:52.893
So now, fast forward.

00:03:52.893 --> 00:03:54.122
Three years have passed.

00:03:54.122 --> 00:03:57.310
Let's see where we are on smart firefighting today.

00:03:57.310 --> 00:04:06.495
So if you can summarize, what's the biggest change between 21 and 24 in terms of using AI in assisting firefighters?

00:04:07.240 --> 00:04:20.014
Yeah, I think the last time when we first talked about the smart firefighting back 2021, and we just get that grant and I just recruit a few students doing this project.

00:04:20.014 --> 00:04:21.745
Also, I'm new to AI.

00:04:21.745 --> 00:04:24.906
Right now I think I'm still new to AI.

00:04:24.906 --> 00:04:42.310
I haven't got a chance to really run AI as all the students doing the hard works, but I think I know more about the AI application and how it works and what problem AI can solve to help us, no matter it's to support firefighters or support 5G news.

00:04:42.310 --> 00:04:45.769
So I think I know more about the tool.

00:04:46.420 --> 00:04:54.624
The last time we talked, you also mentioned that the use of AI comes from patches of code that are implementing real packages.

00:04:54.624 --> 00:04:57.668
You don't have to be an AI scientist in implementing AI.

00:04:57.668 --> 00:05:05.166
Now, working with this for three years together with your students, was it very hard to enter the world of AI?

00:05:05.166 --> 00:05:08.512
I mean, three years have passed and you've shown some success.

00:05:08.512 --> 00:05:12.343
I wonder if that can inspire others to try out AI.

00:05:12.343 --> 00:05:14.648
Was it very hard to implement a lot of challenges?

00:05:15.209 --> 00:05:18.942
I think it's very simple to use the AI algorithm.

00:05:18.942 --> 00:05:40.975
So most of my students who have most of them have never used AI in their research before, or maybe they haven't done any research before, so when they start to do the AI-related research, I think it takes less than one month to be able to run some simple AI program or reproduce some previous paper.

00:05:40.975 --> 00:05:46.012
So I think running the AI algorithm itself is also a challenge.

00:05:46.012 --> 00:05:59.391
The most challenging thing is to identify the problem that is worth solving by AI, and that requires a lot of knowledge about the file as well as the capacity of AI.

00:06:00.021 --> 00:06:02.290
And how about choosing the correct algorithm?

00:06:02.290 --> 00:06:08.173
Because with my understanding of AI, I understand that there are supervised and unsupervised models.

00:06:08.173 --> 00:06:11.629
You have neural networks, but you have also classification tools.

00:06:11.629 --> 00:06:14.586
There is so much like when you start digging.

00:06:14.586 --> 00:06:16.331
There are so many choices.

00:06:16.331 --> 00:06:22.312
Have you figured out the way how to assign correct algorithm or model to a correct problem?

00:06:22.312 --> 00:06:25.761
Or is it the other way you know an algorithm and you find a problem for it?

00:06:26.062 --> 00:06:37.451
Yes, that's also something we are learning during the process of this project, and overall feeling is I still think the algorithm is not so important.

00:06:37.451 --> 00:06:39.581
First, it can be solved.

00:06:39.581 --> 00:06:48.074
Most of the algorithm problem people are facing can be solved by increasing the size of the database or the number of useful data.

00:06:48.074 --> 00:06:55.687
Sometimes you have a very large database but most of the data could be not valuable, so not really helping training AI.

00:06:55.687 --> 00:07:03.752
But if you have a good database, even if it's small, it can basically solve most of the training problems.

00:07:03.752 --> 00:07:04.694
That's my feeling.

00:07:04.694 --> 00:07:07.559
It can basically solve most of the training problems.

00:07:07.559 --> 00:07:10.882
That's my feeling In some aspect.

00:07:10.942 --> 00:07:12.389
For example, we are doing a lot of file simulation.

00:07:12.408 --> 00:07:14.779
We are predicting the file development showing the smoke movement.

00:07:15.480 --> 00:07:35.833
So if you want to use AI to generate very nice or very real CFD file images, then the algorithm is quite important and from my experience, diffusion model is definitely the best to generate very detailed flow motions, smoke motions.

00:07:36.319 --> 00:07:45.269
But the problem is the training of the diffusion model is very, very long time and even when you use it for prediction, the rendering time of these images the AI prediction images also very long time.

00:07:45.269 --> 00:07:49.045
And even when you use it for prediction, the rendering time of these images the AI prediction images also vary in long time.

00:07:49.045 --> 00:07:57.607
So unless you really want to achieve that detailed structures, usually you don't need a diffusion model.

00:07:57.607 --> 00:08:13.408
In my experience, some models like GAN model or GL model they all solve pretty good problems and, for example, if you just want to predict the ASET, you just want to know when the smoke layer will drop to two meter high.

00:08:13.408 --> 00:08:21.805
Then you don't need to know the detailed flow structure of the smoke, you just need to know when the smoke layer touch the critical line.

00:08:21.805 --> 00:08:26.552
So in that sense there's really no need of using advanced AI model.

00:08:27.074 --> 00:08:34.188
It's really interesting because your group was able to use AI in a way like many of us would use CFD.

00:08:34.188 --> 00:08:41.203
I see so much resemblance, by the way, how you are using AI with how many engineers would be using CFD.

00:08:41.203 --> 00:08:48.347
Also, you know, in the way that we don't really comprehend CFD that well as engineers like, and you don't need to because there are already made packages that you apply.

00:08:48.347 --> 00:08:52.245
You also have to understand the problem definition and set the boundary conditions.

00:08:52.245 --> 00:08:58.563
Like you said here, you choose the appropriate model or appropriate tools for the problem you solve Now in CFD.

00:08:58.563 --> 00:09:06.200
I would say one of the reasons it is such a popular tool in fire safety engineering is because of the realism of output.

00:09:06.200 --> 00:09:10.950
You get those really beautifully looking plots that look like fire.

00:09:11.530 --> 00:09:14.904
People use CFD because they get those lovely images and everything.

00:09:14.904 --> 00:09:21.272
You just said that you can use AI very quickly to just get the ACID value of two meters and yes, I agree you can do that.

00:09:21.272 --> 00:09:24.222
But the question is the perceived value of the tool.

00:09:24.222 --> 00:09:31.549
If, if you lose the beautiful images generated by the diffusion model, will that tool be believed that it truly is two meters?

00:09:31.549 --> 00:09:48.923
You know, without the layer of the graphics, it's hard to convince someone that the result really is the two meters, and it's all a matter of trusting the tool which, let's be honest, the trust to AI generated results is, in general, quite low, I would say.

00:09:49.706 --> 00:09:50.942
Yes, that's the reason.

00:09:50.942 --> 00:10:23.549
A lot of FDS simulations can cheat the public because they look real, and I'm sure the software companies or SmokeView or other rendering tools, they have tried a lot to make these images look real and so far what we can do is first, of course, we can prove that even a rough smoke layer without all these small eddies, they basically have the same smoke height as the one with detailed eddies.

00:10:23.549 --> 00:10:25.030
And that's one way.

00:10:25.030 --> 00:10:33.437
The other way is we can also use AI tools to generate these eddies to make it more real If it's required to convince people.

00:10:33.557 --> 00:10:37.241
Okay, it's just a matter of cost and time, right?

00:10:37.241 --> 00:10:44.327
I am disturbed by the amount of similarities with AI and CFD as a tool, and I wonder how the future will look like.

00:10:44.327 --> 00:10:47.089
Will we be using one or another, or both?

00:10:47.340 --> 00:10:53.307
Yeah, if you print that in paper, probably you cannot tell the difference whether it's AI generated or it's CFD generated.

00:10:53.460 --> 00:10:58.370
It's disturbing because I know at least cell biology and genetics.

00:10:58.370 --> 00:11:16.164
There were hundreds of studies that were retracted with very serious accusations that you know the genome sequencing is like a line with some lines in it, so it's very easy to fire up Adobe Photoshop and just cheat a part of the image.

00:11:16.164 --> 00:11:22.043
Serious scientists would face serious accusations that the images in there these are falsified.

00:11:22.184 --> 00:11:23.808
They cannot blame that for AI.

00:11:23.808 --> 00:11:25.613
That's actually a real human cheating.

00:11:25.960 --> 00:11:34.067
Yeah, I know, I know, I know, but I'm stressed because the ease of this tool and the ease will increase in the future.

00:11:34.067 --> 00:11:36.744
And what if the AI is wrong?

00:11:36.744 --> 00:11:42.164
What if it gives us incorrect output because someone did choose the train set as a too small one?

00:11:42.164 --> 00:11:45.106
How sensitive actually was it to data?

00:11:45.106 --> 00:11:48.267
You said the biggest challenges were with getting data correct.

00:11:48.267 --> 00:11:56.347
Was it truly one of the biggest challenges in your project to get the data and how much of the data you actually needed to get reasonable outcomes?

00:11:56.860 --> 00:11:59.028
Depending on the problems you're trying to solve.

00:11:59.028 --> 00:12:05.971
For example, recently we are trying to use AI to forecast smoke flow in very complex shape atrium.

00:12:05.971 --> 00:12:11.899
In that sense, we need a lot of simulation CFD simulation to form the database.

00:12:11.899 --> 00:12:16.072
But even so, I don't think that database is that big.

00:12:16.072 --> 00:12:19.811
We only have a few hundred case with complex shapes.

00:12:19.811 --> 00:12:24.311
We have another few thousand case with relatively simple shape.

00:12:24.311 --> 00:12:27.769
So I don't think that's large enough.

00:12:27.769 --> 00:12:41.009
Because essentially what we want to do is I mean, nowadays so many consulting companies, they are running CFD simulations for different buildings, different structures, but all these data are not fully used.

00:12:41.399 --> 00:12:43.788
After they finish the project it's in the hard drive.

00:12:43.788 --> 00:12:45.826
Nobody is really using it.

00:12:45.826 --> 00:12:51.068
But in fact, all this data can be trained for improving the AI capacity.

00:12:51.068 --> 00:12:57.788
But if we have this database to train AI, that will be amazing.

00:12:57.788 --> 00:13:04.890
We have a very large database and we are not asking extra input, we're just using what's already there.

00:13:04.890 --> 00:13:15.931
But of course, the pre-processing for these data will take a lot of time because every company, every engineer, they have their own habit of making the model to run the simulation.

00:13:15.931 --> 00:13:25.808
So that's also what we see is that in fact, a lot of time is spent on pre-processing the database rather than creating database itself.

00:13:26.460 --> 00:13:32.065
If you wanted to use this data like the way you said, I think there would be so many human variables with what you just said.

00:13:32.065 --> 00:13:33.446
Different people would do it differently.

00:13:33.446 --> 00:13:38.542
I wonder if it's even possible to quantify all the choices that people do Like.

00:13:38.542 --> 00:13:42.063
There must be doses of choices Like what design fire did you put?

00:13:42.063 --> 00:13:43.065
How do you place it?

00:13:43.065 --> 00:13:44.086
Was the suit healed?

00:13:44.086 --> 00:13:45.289
Was the heat of combustion?

00:13:45.289 --> 00:13:47.413
Was the makeup moisture?

00:13:49.200 --> 00:13:52.571
That's actually the good thing, because everyone chooses different parameters.

00:13:52.571 --> 00:13:55.649
That just makes the database become richer.

00:13:55.649 --> 00:13:57.899
Ah, okay, not just a few settings.

00:13:57.899 --> 00:14:02.369
So everyone has different settings, so the database becomes very good, very large?

00:14:03.019 --> 00:14:06.350
And how about training or integrating experimental data?

00:14:06.350 --> 00:14:11.673
Because I know that you use CFD and you have a good reason for it, which I hope you will reveal.

00:14:11.673 --> 00:14:14.086
But how about using experimental data?

00:14:14.086 --> 00:14:14.909
Let's start with CFD.

00:14:14.909 --> 00:14:19.730
Why do you train more on CFD than on experiments, from what I understand?

00:14:20.231 --> 00:14:20.393
Yes.

00:14:20.393 --> 00:14:24.870
So first of all, we still use some of the experiment data.

00:14:24.870 --> 00:14:34.294
I would say, before we do a large amount of CFD simulation, we always calibrate the model with the experiment data.

00:14:34.294 --> 00:14:46.900
So in that sense I consider we already include some of the experiment into the database, because some parameters used for the boundary condition may come from the experiment.

00:14:46.900 --> 00:14:51.149
I wouldn't say it's 100% numerical input.

00:14:51.149 --> 00:14:53.660
It also has a lot of input from the experiment.

00:14:53.922 --> 00:14:58.211
The problem is, even for the experiment it's very difficult to quantify the result.

00:14:58.211 --> 00:15:01.024
For example, we all have limited sensors.

00:15:01.024 --> 00:15:04.291
For example, even if you have some couple of trees, you have a few points.

00:15:04.291 --> 00:15:09.405
Even you have cameras, you have only a limited view of the smoke motion.

00:15:09.405 --> 00:15:18.982
Compared to the CFD simulations, the data you get from the experiment is extremely limited and have a large uncertainty.

00:15:19.585 --> 00:15:24.740
For example, the fire you used in the experiment may not be so well controlled.

00:15:24.740 --> 00:15:31.394
If you are burning, for example, a wood crib, who knows what kind of large fire, how large is the fire it is, and there's a smoke.

00:15:31.394 --> 00:15:33.727
I mean, every wood burns different smokes.

00:15:33.727 --> 00:15:35.647
It's difficult to quantify that.

00:15:35.647 --> 00:15:41.873
So in that sense I feel it's quite difficult to directly use experimental data.

00:15:41.873 --> 00:15:52.725
And I think, most importantly, for file engineering design is you only consider certain representative scenarios rather than the so-called real scenario.

00:15:52.725 --> 00:15:55.166
There's no such thing as a real scenario.

00:15:55.166 --> 00:16:03.386
Even the same building have the same furniture burning for a hundred times, every time it's completely different.

00:16:03.386 --> 00:16:06.129
So in that sense, we cannot forget.

00:16:06.129 --> 00:16:13.785
Doing design is just following certain framework and test some possible file scenario to give certain confidence.

00:16:13.785 --> 00:16:17.673
We are not trying to simulate a potential real file.

00:16:17.995 --> 00:16:33.067
I would summarize what you've just said is that it's hard to capture all the uncertainties in the learning process, like, if you learn based on CFD, you, if you input it one megawatt, you're certain you've inputted one megawatt.

00:16:33.067 --> 00:16:43.408
And here, if you had a crib that was supposed to give you a megawatt one day it was very hot and dry and the lab was well ventilated, you had 1.1.

00:16:43.408 --> 00:16:45.541
Other day you've done a repeat.

00:16:45.541 --> 00:16:46.841
It was a moist after rain.

00:16:46.841 --> 00:16:50.884
You had 0.95, right, and yet you put something into training.

00:16:50.884 --> 00:16:57.908
You tell the trained model it was one megawatt there's an uncertainty in the input that you've not accounted for.

00:16:57.927 --> 00:16:58.575
So there are a few aspects.

00:16:58.575 --> 00:17:04.428
First, from AI training point of view, the experiment data have their own format.

00:17:04.428 --> 00:17:19.647
So you may have some temperature sensors done one experiment, you have some other group of sensors done in different locations in a different experiment, and these data formats don't match with each other, so it's quite difficult to train them.

00:17:19.647 --> 00:17:24.287
If you run the CFD simulation, you can collect the data in a consistent way.

00:17:24.287 --> 00:17:27.603
Then it's much easier for AI to train them.

00:17:27.603 --> 00:17:38.885
That's one aspect, but I think the second aspect which is most important is when we do the current state-of-the-art practice, we never ask the guys who run CFD.

00:17:38.885 --> 00:17:43.612
We don't question if their model represents the real file or not.

00:17:43.612 --> 00:17:47.665
We just assume okay, your simulation is reasonable and correct.

00:17:47.665 --> 00:17:51.586
So in that sense we only need to compare with the CFD simulation.

00:17:51.586 --> 00:17:55.286
We don't have to compare with the real experiment, because this is a design practice.

00:17:55.807 --> 00:18:04.548
So, basically, assuming that the CFD is the state of the art tool, you basically create a tool that is at the same confidence level as the CFD.

00:18:04.548 --> 00:18:06.317
Yes, okay, that makes sense.

00:18:06.317 --> 00:18:12.017
Out of all the AI implementations you've done, let's pick one and go deeper.

00:18:12.017 --> 00:18:13.722
How about the fire prediction?

00:18:13.722 --> 00:18:15.678
I love the fire prediction, so.

00:18:15.678 --> 00:18:33.969
So your group has built those tools that are able to predict the size of the fire based on images, I believe, and I I found it really interesting, especially that there are videos online that showcase the real, uh, real-time capability of this prediction software, and it's just magical.

00:18:33.969 --> 00:18:40.403
Are the videos fake or it really works like that, like real-time, showing the hit-release rate?

00:18:41.038 --> 00:18:54.224
Yes, we're actually having a latest paper will come out very soon, that we have an online link Everyone can upload their video and we were exporting the real-time hit rate.

00:18:54.546 --> 00:18:57.346
That's good, so I confirm, this is really amazing.

00:18:57.346 --> 00:19:01.740
So tell me, what was the big idea behind starting this and how did it go?

00:19:01.740 --> 00:19:04.040
Actually, what was the point of doing this study?

00:19:04.462 --> 00:19:08.820
So I have to say the idea come from when I was teaching the fire dynamics class.

00:19:09.135 --> 00:19:20.487
So there's one session I have to teach the students what's the definition of the fire heat release rate and then I have to go to the only two methods that we can measure the fire heat release rate.

00:19:20.855 --> 00:19:26.364
One is to measure the mass loss rate of the fuel and the other is oxygen calorimetry.

00:19:26.364 --> 00:19:37.464
You measure the oxygen depletion based on the smoke measurement and eventually the students questioning okay, both methods can only be used in labs.

00:19:37.464 --> 00:19:40.555
Can any method can help us to measure the real fire.

00:19:40.555 --> 00:19:43.441
So I think that's a really a good question.

00:19:43.441 --> 00:20:05.028
Some students I don't really remember the name of the student, but someone asked me about that so I think that's something we have to think about, because if, of course, you can put a big hood above a house or above a burning car, but everything is done in the lab, you cannot put a big hood where you have a fire incident and you put it about there and measure the heat rate.

00:20:05.028 --> 00:20:11.689
So none of the methods that we have so far can actually measure the power of a real fire.

00:20:11.689 --> 00:20:20.561
And that just inspired me to think about AI method and I think during that time we have a lot of advancement.

00:20:20.561 --> 00:20:28.845
For example, using the mobile phone, we can use a facial ID to unlock our phone and we have a lot of facial recognition everywhere.

00:20:28.845 --> 00:20:34.362
In China you can use a face ID to pay, actually Okay, so the image is really powerful.

00:20:34.362 --> 00:20:36.060
That's what I feel.

00:20:36.255 --> 00:20:40.926
And doing experiments and all these fire experiments, we have a very rough view.

00:20:40.926 --> 00:20:46.788
So if the fire size is an area, the volume is larger, of course it's more powerful.

00:20:46.788 --> 00:20:57.079
So I think there is a certain correlation between the size of the fire as well as its power, correlation between the size of the fire as well as its power.

00:20:57.079 --> 00:21:08.547
And if you really look into the details of the fundamental flame sheet and that definitely makes sense because flame is essentially like a coating, it only has a small sheet and all the reactions happen in that sheet.

00:21:08.768 --> 00:21:24.068
So if you can get to the area of that sheet, definitely you are able to quantify the file release, heat release rate, so, and that area of the sheet is proportioned to a certain degree to the image can captured by the camera.

00:21:24.068 --> 00:21:32.404
So that's the original idea, but of course we know it's very challenging to actually train the database Then we are just super lucky.

00:21:32.404 --> 00:21:37.066
I would say super lucky because NIST had such a wonderful database.

00:21:37.066 --> 00:21:54.364
So they are burning all different kinds of things I think they have more than 2,000 different material things burning in the lab and as they record all the heat release rate by oxygen calorimetry, they also have all the images, videos, you can just download from the website.

00:21:54.364 --> 00:21:59.585
So that's just amazing and you can use this database to train.

00:22:00.145 --> 00:22:00.988
I'll quickly plug in.

00:22:00.988 --> 00:22:02.798
I had an interview with Matt Bundy.

00:22:02.798 --> 00:22:10.040
That's episode 110 of the Fire Science Show where we've just discussed what you've just said the NIST fire calorimetry database.

00:22:10.040 --> 00:22:16.782
So Matt told us all the tricks they have for recording cameras, automated storage, processing.

00:22:16.782 --> 00:22:27.244
Like a lot of effort goes into building a database like that and we are very grateful to NIST for developing and maintaining this database.

00:22:27.244 --> 00:22:31.501
So you had images from, or videos from, the database.

00:22:31.501 --> 00:22:39.243
You had the heat release rate plots, what goes from these points to having a trained model that can predict fire size.

00:22:39.243 --> 00:22:45.124
But because I assume it's not a simple like press enter, here's the images and you robot learn.

00:22:45.424 --> 00:22:54.249
But it must be quite a process so basic for all the ai model, you need to identify the input and output and you pair them in the training.

00:22:54.249 --> 00:23:03.931
So for this specific case, the input is the image of that moment and the output is the heat release rate measured by the oxygen calorimetry.

00:23:03.931 --> 00:23:04.934
So you pair them.

00:23:04.934 --> 00:23:07.263
So every second you have a pair.

00:23:07.263 --> 00:23:17.528
If you burn something for 20 minutes let's just take one point per second you have 1,200 pairs of heat release rate as well as images.

00:23:17.528 --> 00:23:28.586
Then you put all of them into the training database and now you have 1,000 different fire burning and each test you have 1,200 images.

00:23:28.586 --> 00:23:32.979
So together you have a million of data pairs for the training.

00:23:32.979 --> 00:23:44.111
So together you have a million of data pairs for the training and that results in a very amazing trained AI model that can basically give you a hit-release rate if you input any image Okay, but the image is a collection of pixels.

00:23:46.414 --> 00:23:47.237
It doesn't reflect the real world.

00:23:47.237 --> 00:23:50.683
If you put a matchstick right next to the camera, it's going to appear huge on the image.

00:23:50.683 --> 00:23:56.115
So how did you solve the dimensionality of the fires at NIST?

00:23:56.115 --> 00:23:58.362
Or were the cameras conveniently positioned?

00:23:58.362 --> 00:23:59.105
Always the same way?

00:23:59.516 --> 00:24:16.704
Yeah, first we removed those cases that clearly the camera is putting a different location and later on we added some additional data from our lab to measure the fire from different distance and use that to calibrate the fire image.

00:24:16.704 --> 00:24:21.346
So we rescale the image to be the same as our database.

00:24:21.346 --> 00:24:29.941
So in the database all the images are rescaled under a certain scale and for any practical applications.

00:24:29.941 --> 00:24:37.545
I think there are three methods you can approach to solve the distance or the scale problem.

00:24:37.545 --> 00:24:39.958
First, you can use the reference lens.

00:24:40.138 --> 00:24:52.019
For example, if you see some fire is burning in a car passenger car and you know roughly how long the passenger car, how tall it is, you can use that as a reference scale to help you to scale that fire image.

00:24:52.019 --> 00:24:54.522
Use that as a reference scale to help you to scale that fire image.

00:24:54.522 --> 00:24:55.364
That's one thing.

00:24:55.364 --> 00:24:59.710
The other is you can use a bimolecular camera.

00:24:59.710 --> 00:25:06.903
You have basically two cameras that can measure the distance between the camera and the fire and that can also give you a reference scale.

00:25:06.903 --> 00:25:18.982
And as a third option we provide is if you put that in UAV and the UAV can measure the height between the ground and a UAV, that actually give you a reference lens as well.

00:25:18.982 --> 00:25:26.027
So, depending on the application, you can always find a good reference lens to help you solve the distance issue.

00:25:26.674 --> 00:25:29.304
So, so this is probably the challenging part of modeling.

00:25:29.304 --> 00:25:31.538
And do you see any?

00:25:31.538 --> 00:25:38.377
Okay, because, fueling the curiosity, you see any practical outputs.

00:25:38.377 --> 00:25:43.154
How helpful do you believe this could be more to scientists, more to firefighters?

00:25:44.076 --> 00:25:47.461
I think there are potential applications.

00:25:47.461 --> 00:25:54.391
For example, initially we make this system trying to help the firefighters.

00:25:54.391 --> 00:26:03.644
For example, if one fire happens and someone may be passing by the fire and they can just use their phone to record.

00:26:03.644 --> 00:26:10.744
In fact a lot of people when they see the fire they will start to record, they will do streaming in the cloud server so people can see it.

00:26:10.744 --> 00:26:27.262
So if the firefighters can get access of this data in the fire engine on their way to the fire engine, they can know the initial fire development, they can understand what's the original condition of the fire or what's the original fire source.

00:26:27.795 --> 00:26:31.226
I think that helps the firefighting operation to a certain degree.

00:26:31.226 --> 00:26:45.787
I think it also can help the fire scientists to do some research, although I haven't really used it yet, but I think in some cases not everyone has a nice oxygen calorimetry in the lab.

00:26:45.787 --> 00:26:51.304
So in a random past we burn something, but sometimes it's difficult to quantify their heat rates.

00:26:51.304 --> 00:27:00.190
And if we just record the fire videos and using our algorithm you can have a rough idea about the evolution of the heat release rate.

00:27:00.190 --> 00:27:07.128
And that is much cheaper compared to install a big hood to measure the heat release rate.

00:27:07.734 --> 00:27:10.998
Even though it would be uncertain and some rough estimate.

00:27:10.998 --> 00:27:16.804
I think also for some field experiments it would be uncertain and some rough estimate, I think also for some field experiments.

00:27:16.804 --> 00:27:19.145
It's often a difficult variable to get a hold of, even approximate.

00:27:19.145 --> 00:27:21.728
What was the heat release rate during an experiment?

00:27:21.728 --> 00:27:25.592
Or you could perhaps have a footage from a real world fire incident.

00:27:25.592 --> 00:27:31.718
You know how far the smoke penetrated the building, you know where it ended up.

00:27:31.718 --> 00:27:34.082
You want to do some forensic analysis and all you have is a video from the scene.

00:27:34.082 --> 00:27:39.997
Perhaps that can give you a data point you know, to match your simulation with the incident itself.

00:27:39.997 --> 00:27:43.885
I think there could be a lot of places where this could be used.

00:27:43.885 --> 00:27:49.490
I also know you were trying to figure out the sizes of fires based on temperature measurements.

00:27:49.490 --> 00:27:51.538
I recall a paper related to tunnels.

00:27:51.538 --> 00:27:54.926
So how did that differentiate from the images?

00:27:55.434 --> 00:27:56.699
So inside the tunnel.

00:27:56.699 --> 00:28:02.055
Essentially it's very challenging to get a full image of the tunnel fire.

00:28:02.055 --> 00:28:12.626
For example, your CCTV camera is installed a certain distance away from the fire source so of course if you are lucky you can capture the initial development of the fire.

00:28:12.626 --> 00:28:21.304
But most of the tunnel fire are in very confined space so it generates very heavy smoke so your camera doesn't work quite very quickly.

00:28:21.304 --> 00:28:31.462
Instead you always have the thermocouple, sometimes the optical fibers, to measure the temperature, so linear heat detector.

00:28:31.462 --> 00:28:36.507
So we can assume you always have good temperature measurement in the tunnel.

00:28:36.507 --> 00:28:44.320
Then with this temperature sensor you are able to predict the evolution of the fire, essentially the fire size.

00:28:44.320 --> 00:28:49.847
I'm not talking about the location of the fire, because everyone knows where the location it is.

00:28:49.847 --> 00:28:53.346
It's just near the sensor which has the highest temperature.

00:28:53.346 --> 00:28:56.803
This is also related to some question.

00:28:57.244 --> 00:29:02.666
A lot of people ask what kind of problem in fire is worth to be solved by fire.

00:29:02.666 --> 00:29:04.823
Because I see a lot of papers.

00:29:04.823 --> 00:29:10.123
They use temperature sensor inside a tunnel to predict the location of the fire.

00:29:10.123 --> 00:29:25.262
A lot of paper on this topic which I feel is just meaningless because we all know the fire is just right next to the thermocouples which has the highest temperature measurement, even if you don't use any AI method.

00:29:25.262 --> 00:29:36.525
You know it's near there and if you use the AI method to improve the position, maybe one meter or half meter more accurate, it's meaningless, but still a lot of people are doing that.

00:29:36.525 --> 00:29:44.121
So I think AI is a good tool, but you have to use it to solve the right problem, not abuse it.

00:29:44.121 --> 00:29:47.862
There's a lot of questions you don't, a lot of problems you don't need AI to solve.

00:29:48.316 --> 00:29:49.701
I think that's an important statement.

00:29:49.701 --> 00:30:05.047
I also see that in the world of general science, engineering sciences and AI, that people are applying AI for trivial problems and claim that it's a new solution, whereas a really good solution existed and there was everything fine with that.

00:30:05.047 --> 00:30:06.857
Ai doesn't bring you any novelty.

00:30:06.857 --> 00:30:12.616
Sometimes it would be put into papers or research just because it's, you know, innovative.

00:30:12.616 --> 00:30:28.450
It gives you this novelty factor and for many years already I've in my reviews and I see that from other reviewers that the tendency is that just using AI in your paper is not yet enough to claim the novelty.

00:30:28.450 --> 00:30:29.877
You know that's not enough.

00:30:29.877 --> 00:30:34.777
You have to solve something important with the use of it, has to bring the new value.

00:30:34.777 --> 00:30:39.948
It has to bring a new how to say it gain over the existing methods.

00:30:39.948 --> 00:30:41.798
Where do you see those gains?

00:30:41.798 --> 00:30:47.218
Like you do a lot of AI, where do you see the real benefits of employing those methods?

00:30:47.218 --> 00:30:52.087
Let's say, the finding the fire in tunnel is a bad application.

00:30:52.087 --> 00:30:53.557
Where do you see the good applications?

00:30:54.097 --> 00:31:04.425
Some problem I think it is worth using AI to solve is transient fire problem, so things related to time or complex space.

00:31:04.425 --> 00:31:18.518
So because all the conventional fire dynamics textbook or the lectures we are given is using analytical solutions, but the analytical solutions can only solve low-dimensional problems.

00:31:18.518 --> 00:31:30.945
I have looked at all the classical equations we have in our community, for example Cargill's correlation, arbert's correlation or the ignition temperature, flame spread rate.

00:31:30.945 --> 00:31:40.192
All these classical equations at most have two-dimensional, one-dimensional in time, one dimensional in space, or two space dimensions.

00:31:40.192 --> 00:31:48.419
There's no equations can include more than three.

00:31:48.419 --> 00:31:50.563
If it include more than three, the equation looks extremely ugly.

00:31:50.563 --> 00:31:53.909
It has a lot of coefficient trying to fit it into a certain special cases.

00:31:53.909 --> 00:31:56.317
In fact, that's a lot of people are doing.

00:31:56.317 --> 00:32:07.403
They do a certain test and are trying to modify these classical correlations to make it explain some special cases, but all of them just make that equation so ugly.

00:32:07.403 --> 00:32:11.365
In fact, when I think more about it, it's a fundamental problem.

00:32:11.365 --> 00:32:15.365
Yes, these kind of polynomial expressions are not good to describe a high-dimensional problem.

00:32:15.365 --> 00:32:16.167
It's just not possible.

00:32:16.167 --> 00:32:17.270
For example, we solved the CFD simulation.

00:32:17.270 --> 00:32:18.012
It's a high-dimensional problem.

00:32:18.012 --> 00:32:18.654
It's just not possible.

00:32:18.654 --> 00:32:21.724
For example, we solved the CFD simulation.

00:32:21.724 --> 00:32:24.904
It's essentially four-dimensional, at least four-dimensional.

00:32:24.904 --> 00:32:28.685
So you have time one-dimensional, time three-dimensional scale.

00:32:28.685 --> 00:32:36.295
You cannot write the equation of a temperature distribution, even you know the solution, because the solution is in numerical.

00:32:36.295 --> 00:32:40.961
You cannot use a polynomial to write down the temperature distribution.

00:32:40.961 --> 00:32:41.743
You can fit it.

00:32:41.743 --> 00:32:49.305
You can fit it in a super ugly way because the polynomial is not designed to describe high dimensional problems.

00:32:49.305 --> 00:32:52.999
So instead, how can we describe the high dimensional problem?

00:32:52.999 --> 00:32:55.104
We actually use a neural network.

00:32:55.104 --> 00:32:58.962
The neural network is essentially a kind of expression.

00:32:58.962 --> 00:33:09.810
It's in parallel to the polynomial just to describe a high dimensional problem and with that tools we are able to consider additional dimension, for example transient problem.

00:33:10.432 --> 00:33:19.740
When I first working on the AI, I start with a tunnel because I feel a tunnel is relatively simple One dimension right, one dimension yes.

00:33:19.740 --> 00:33:22.582
And I searched all the literature.

00:33:22.582 --> 00:33:24.182
I tried to find the data.

00:33:24.182 --> 00:33:33.367
If the data helps me to do the prediction of the tunnel fire, essentially no, because there is no transient data in the literature.

00:33:33.367 --> 00:33:38.431
No one will plot the time evolution of the fire.

00:33:38.431 --> 00:33:41.093
They always pick up the steady state point.

00:33:41.093 --> 00:33:44.479
They just ignore all the transient point.

00:33:44.499 --> 00:33:49.845
Because I already have so many datas, even the steady state point is already a lot to plot.

00:33:49.845 --> 00:33:56.205
Same even you're trying to plot something, you can only include low dimensional information.

00:33:56.205 --> 00:33:59.243
So for high dimensional information, you cannot plot it.

00:33:59.243 --> 00:34:03.320
So ignore the time dimension is an automatic choice.

00:34:03.320 --> 00:34:10.583
But if you don't have the time information, how can you predict, how can you forecast the time evolution of the file?

00:34:10.583 --> 00:34:12.041
So that's basically.

00:34:12.041 --> 00:34:18.960
After searching all the literature on the tunnel file, I found none of this data is useful for the AI.

00:34:18.960 --> 00:34:27.485
That's the reason I started to run the CFD simulation to create my own database to include the time evolution data for the training.

00:34:27.485 --> 00:34:29.762
Otherwise it's just using steady state.

00:34:29.762 --> 00:34:32.643
You cannot predict a varying fire, right?

00:34:33.255 --> 00:34:41.208
I think you're very right in here, and especially that you would always, or very often, consider fire safety as a factor of time.

00:34:41.208 --> 00:34:45.666
A timeline approach is a very fundamental to fire safety.

00:34:45.666 --> 00:34:47.119
You know ACID also.

00:34:47.119 --> 00:34:49.786
That's the thing that engineers would mostly do.

00:34:49.786 --> 00:35:01.557
I think you're quite correct in your assessment that this is a space where those new approaches can actually shine and where the existing approaches are perhaps unsufficient.

00:35:01.557 --> 00:35:10.507
One more thing I wanted to ask you, because we've started this talking about firefighters and you know it was smart firefighting as the theme of your research.

00:35:10.507 --> 00:35:24.322
I wonder how that went, the connection of these new tools and the firefighting, because from our discussions, there's much less firefighter context in what we just discussed than I would have expected.

00:35:24.322 --> 00:35:25.646
I assume it was challenging.

00:35:25.646 --> 00:35:27.320
Yeah, it is super challenging.

00:35:27.996 --> 00:35:38.027
Initially, when we started this project, we went to the firefighting training centers and we worked with firefighters to do some tests together.

00:35:38.027 --> 00:36:00.835
It all started very well, but later on, when we are trying to do something or give some advice about the firefighting operation, then that conversation went to the dead end, because it seems like we don't know much about what firefighters do and the firefighters think we are not giving them anything useful in their daily practice.

00:36:00.835 --> 00:36:03.242
So it's quite a challenge.

00:36:03.242 --> 00:36:06.431
In fact, I feel a lot of fire scientists.

00:36:06.431 --> 00:36:18.358
They don't really understand the firefighters' work or they don't talk to the firefighters that much, and it seems like there are two different communities and it's difficult to break the boundaries.

00:36:18.358 --> 00:36:30.146
And once, after one or two years, I realized that the problem may be lies in the data, because we don't have the data sensors in the buildings.

00:36:30.146 --> 00:36:33.407
So even our algorithm is very powerful.

00:36:33.407 --> 00:36:39.992
If we don't have the real time data feeding these AI algorithms, there's no way you can do fire forecasting.

00:36:39.992 --> 00:36:44.099
So that's the first challenge we found.

00:36:44.099 --> 00:36:45.865
And then I look at the building.

00:36:45.865 --> 00:36:47.882
Oh, we have so many smoke detectors.

00:36:47.882 --> 00:36:50.143
Sometimes we have temperature sensors.

00:36:50.143 --> 00:36:52.161
Can we get these sensor data?

00:36:52.161 --> 00:36:54.764
And that's another challenge we met.

00:36:55.034 --> 00:37:00.807
Basically, it's so difficult to get these sensor data, for example the smoke detectors.

00:37:00.807 --> 00:37:04.202
They only give you yes and no, so zero and one information.

00:37:04.202 --> 00:37:10.284
Even you can get these information, you cannot extract the data from sensor directly.

00:37:10.284 --> 00:37:19.327
They all go to a control panel and the control panel data can only access by the software developed by that company.

00:37:19.327 --> 00:37:24.407
Every company has their own barriers to preventing other companies to accessing the data.

00:37:24.407 --> 00:37:29.427
From the firefighting point of view, from the data point of view, that's a disaster.

00:37:29.427 --> 00:37:31.121
Basically you cannot get any data.

00:37:31.121 --> 00:37:36.824
So in the end we just install our own sensor and create our own system.

00:37:36.824 --> 00:37:40.750
That unfortunately cannot be accessed by other groups either.

00:37:40.750 --> 00:37:43.342
So there's some challenges.

00:37:43.815 --> 00:38:11.405
I think, and thank you for sharing that very openly, but I think you hit the nail on the head with the issues communicating our societies and there's definitely a gap between the fire science as understood by us and the fire science as understood by fire scientists, who are fighter fighters and they also do their own fire science, you know, and that is not necessarily the exactly same science, even though we're talking about the exact same phenomenon of fire in buildings.

00:38:11.405 --> 00:38:17.596
Indeed, it is something that I find very intriguing to nail down why.

00:38:17.596 --> 00:38:18.478
Why is that?

00:38:18.478 --> 00:38:18.759
Why?

00:38:18.759 --> 00:38:20.786
Why cannot we find a common language?

00:38:20.786 --> 00:38:23.623
Why cannot we find the solutions?

00:38:23.623 --> 00:38:29.014
And I also see that we don't have the background and experience of firefighters.

00:38:29.014 --> 00:38:40.268
We don't really understand how firefighting works and for firefighters, they perhaps don't see our view on the understanding of fires.

00:38:40.268 --> 00:38:51.054
I've noticed they speak different language, they focus on different phenomena, they pay attention to other things that we would pay attention to, like we would pay a lot of attention to heat release rate.

00:38:51.918 --> 00:39:00.782
Your algorithm is one example of how much effort we can put into knowing the heat release rate, because, from my perspective, that's the most important variable I can learn.

00:39:00.782 --> 00:39:04.516
I wonder what value would a heat release rate have to firefighter.

00:39:04.516 --> 00:39:12.385
Like if a firefighter knew there's like seven and a half megawatts in front of me, what true value would it give to them?

00:39:12.385 --> 00:39:20.407
I know there are approaches that allow you to quantify the amount of water you need to extinguish based on approximation of heat release rate, but that would be it.

00:39:20.407 --> 00:39:23.264
I don't know any bigger achievements.

00:39:23.264 --> 00:39:26.900
If you've shown them those tools, what was the reaction?

00:39:26.900 --> 00:39:28.119
Yeah, it's cool and that's it.

00:39:28.119 --> 00:39:31.023
Or they've seen a practical use for that.

00:39:31.403 --> 00:39:32.045
It's useless.

00:39:32.045 --> 00:39:35.184
I have to say it's essentially useless to firefighters.

00:39:35.184 --> 00:39:43.664
Sometimes the students ask me okay, so my AI predicts the temperature is 10 degree lower than the experimental measurement.

00:39:43.664 --> 00:39:45.088
So what's the problem?

00:39:45.088 --> 00:39:52.840
If you tell the firefighter the smoke temperature is 240 degrees Celsius and the real temperature 250, what's the difference?

00:39:52.840 --> 00:39:54.422
There's no difference to them.

00:39:54.422 --> 00:39:59.525
They only need to know whether it's safe to enter or it's not safe to enter.

00:39:59.525 --> 00:40:01.181
That's the information they need.

00:40:01.181 --> 00:40:03.081
They don't need numerical values.

00:40:03.081 --> 00:40:05.242
The value is meaningless to them.

00:40:06.257 --> 00:40:08.278
And they also have their own diagnostics.

00:40:08.278 --> 00:40:10.639
There's a parallel world that's developing.

00:40:10.639 --> 00:40:13.896
At least in Poland, they would use thermal cameras a lot, right?

00:40:13.896 --> 00:40:23.005
So perhaps they are less reliant on external sources of knowledge and more reliant on what they can hold in their hand than they use, right?

00:40:23.286 --> 00:40:26.416
Yes, so the IR camera is definitely a good example.

00:40:26.416 --> 00:40:34.737
Showing exact number is meaningless because we all know during the fire test if you're using some images to measure the smoke temperature, you will get the wrong data.

00:40:34.737 --> 00:40:35.318
But it doesn't matter.

00:40:35.318 --> 00:40:37.081
Well, the firefighters they only need to know which part is hot.

00:40:37.081 --> 00:40:38.123
See some images to measure the smoke temperature.

00:40:38.123 --> 00:40:40.947
You will get the wrong data, but it doesn't matter For the firefighters.

00:40:40.947 --> 00:40:52.601
They only need to know which part is hot, which part is relatively cooler, and that information is already sufficient for them to judge where to go, whether they can evacuate safely.

00:40:52.601 --> 00:41:00.844
And that kind of information is that kind of inaccurate information are very useful and actually are what the firefighters need.

00:41:01.454 --> 00:41:05.105
And sometimes we need to translate this information.

00:41:05.105 --> 00:41:08.894
No matter it's coming from the raw data or it's generated by the AI.

00:41:08.894 --> 00:41:12.681
We need to translate that into the language or the information.

00:41:12.681 --> 00:41:17.690
The firefighters actually need it, because they are already overloaded in the operation.

00:41:17.690 --> 00:41:19.722
They are receiving massive information.

00:41:19.722 --> 00:41:23.324
They don't want you to give them a number how much megawatt.

00:41:23.324 --> 00:41:23.985
They don't need that.

00:41:23.985 --> 00:41:28.106
They need something simple that can help them to make decisions quickly.

00:41:28.106 --> 00:41:33.965
That's the reason they like IR cameras, although the IR camera does not measure the correct temperature.

00:41:34.574 --> 00:41:38.085
I think it's also a matter of trust and having power over something.

00:41:38.085 --> 00:41:47.563
If you hold an IR camera in your hands, you have the power to do the measurement yourself, interpret it yourself and take decisions yourself.

00:41:47.563 --> 00:41:55.070
When you're reliant on an external system or a person, you're taking information from the other person and that person may be wrong.

00:41:55.070 --> 00:41:57.731
It's about consequences of being mistaken.

00:41:57.731 --> 00:42:10.300
I think people are much more accepting that they can be wrong and accept the consequences of that choice, rather than accepting the fact that someone else can be wrong and having to live with the consequences of that person being wrong.

00:42:10.855 --> 00:42:17.233
In fact, a lot of our effort is now focusing on the digital twin technology.

00:42:17.233 --> 00:42:22.606
Okay, so the digital twin essentially is used to compress information.

00:42:22.606 --> 00:42:32.375
So, for example, if you want to have a digital twin of the building fire, you project that in a big screen that helps the fire commanders to make decisions.

00:42:32.375 --> 00:42:35.905
That is basically a demonstration.

00:42:35.905 --> 00:42:44.969
You collect hundreds, thousands of data points every second but you transport that numerical information into colorful images.

00:42:44.969 --> 00:43:01.291
Simply some dangerous area, you put a red color, some safe area, you put a ring there and you compress this massive information into something vivid and something animated can be easily understood by the file commander.

00:43:01.291 --> 00:43:05.405
So that's actually a lot of our effort is doing.

00:43:05.405 --> 00:43:11.614
So we try to use AI to compress information, compress that into something human can easily understand.

00:43:12.117 --> 00:43:23.876
You also can gather data from different interfaces and compress it into one value so you can take observations from outside, from inside, from sensors and process.

00:43:23.876 --> 00:43:32.505
Where a person's standing is limited by the location where they are, they can only see what they see and not see what's in the back.

00:43:32.505 --> 00:43:39.005
With my limited knowledge of firefighting process, I know the importance of assessing the full perimeter of a building.

00:43:39.005 --> 00:43:46.760
For example, they do this 360 check around the building to not miss the information coming from behind the building.

00:43:46.760 --> 00:43:51.282
You had UAV that would do the 360 while people are entering inside.

00:43:51.282 --> 00:43:53.817
They perhaps do the action quicker.

00:43:53.817 --> 00:44:01.438
But again, we're brainstorming things that perhaps could be useful for them and we need to learn from firefighters what they want.

00:44:01.798 --> 00:44:11.949
And after working on this project for almost five years, I feel like AI is not really good to work with humans or firefighters.

00:44:11.949 --> 00:44:14.891
Ai is perfectly working with robots.

00:44:14.891 --> 00:44:18.804
Okay, because the robot can just adopt the AI algorithm.

00:44:18.804 --> 00:44:24.983
They collect all the information and they process automatically with their powerful CPU GPU.

00:44:24.983 --> 00:44:27.663
But the human brain actually are quite limited.

00:44:27.663 --> 00:44:31.000
We cannot handle so much information at the same time.

00:44:31.000 --> 00:44:36.039
We can only accept a few key information to do judgment, otherwise we overload it.

00:44:36.039 --> 00:44:48.505
So in that sense, I feel all the digital training, all the AI, all these things, they're best to work with robotic firefighter rather than the real firefighter.

00:44:49.217 --> 00:44:51.764
That's definitely a trajectory for a future.

00:44:51.764 --> 00:45:14.025
I think it was like 10 years ago when I've read the piece that was covering development of humanoidal robots and the first use that they've predicted was something carrying loads, like, you know, a companion to carry whether we're talking about military setting and you know, carrying stuff with soldiers, but just as a carrier.

00:45:14.025 --> 00:45:23.788
And the second thing that they foresaw was firefighting, and I found it very interesting and I remember that time a friend from Italy, Fabio Limo Ponciani.

00:45:23.788 --> 00:45:27.097
He was developing interesting firefighting robots.

00:45:27.097 --> 00:45:45.807
I see that as potential future direction, though, knowing how devastating fire conditions are to my quite robust scientific apparatus that I put inside the fires and how fragile robots and drones are, I'm not sure if that's the place where I want to have my robots.

00:45:46.315 --> 00:45:52.617
If our goal is to protect the firefighters, then letting the robots to do the job can solve everything.

00:45:52.938 --> 00:45:55.909
So, sinian, wrapping it up, what are the next steps?

00:45:55.909 --> 00:45:57.976
What should we talk about in three years?

00:45:57.976 --> 00:46:03.449
What do you expect to happen in the use of ai, fire safety engineering and smart firefighting?

00:46:03.891 --> 00:46:04.572
I, I think it's.

00:46:04.572 --> 00:46:07.900
Currently we are trying to do a few things.

00:46:07.900 --> 00:46:13.710
First we are still exploring the ai driven fire safety design.

00:46:13.710 --> 00:46:19.188
So my students is further developing the database of the building.

00:46:19.188 --> 00:46:35.885
So every time we have a very complex shape of the atrium or warehouse we are able to give prediction of ASAT very quickly and we hope that tools can be implemented into some software, some mature commercial software.

00:46:35.885 --> 00:46:38.590
They cannot generate the final result.

00:46:38.590 --> 00:46:43.842
They can give you a very quick early identification of what kind of case it runs.

00:46:44.416 --> 00:46:50.666
If I recall correctly, the first instances of those AI tools for HVAC were available online.

00:46:50.666 --> 00:46:52.079
Can I link them in the show notes?

00:46:52.661 --> 00:46:54.398
Yes, please yes we have.

00:46:55.119 --> 00:46:55.742
It's just open.

00:46:55.742 --> 00:46:57.501
Everyone can play with that.

00:46:57.501 --> 00:47:15.726
It's only for a cubic box, it cannot cover a complex shape.

00:47:15.726 --> 00:47:41.068
And the other thing is input using AI to do drawing, and our recent tests are showing that the design made by AI can have a lower number of speaker heads, so it can actually save the material you need, compared to some engineers' design, because we're trying to ask a few engineers you do this design, then we let AI to do the design, then we compare which one is doing better.

00:47:41.454 --> 00:47:55.402
So hopefully we can achieve certain automation in this area, because I heard some engineers say, okay, they have to pinpoint the sprinkler head for this drawing, so it's kind of like a boring task.

00:47:55.402 --> 00:47:59.286
So right now we can use AI to just automatically generate that layout.

00:47:59.286 --> 00:48:01.260
So that's from design point of view.

00:48:01.260 --> 00:48:02.525
I think it can be.

00:48:02.525 --> 00:48:06.260
A lot of things can be improved in three or five years.

00:48:06.260 --> 00:48:08.266
That's exciting, yeah.

00:48:08.594 --> 00:48:27.902
And the other area I'm working on right now is essentially the robotic firefighting, because I feel this is essentially the final goal of the AI, because the this is essentially the final goal of the AI, because the robotic is essentially use AI to do all the measurement, to do the decision-making and essentially stop the fire.

00:48:27.902 --> 00:48:45.847
If you use the AI to process information and pass that information to firefighters, then the efficiency is really low because we don't know if the firefighters understand what AI provides and there is also certain moral risk whether they should trust the AI information or not.

00:48:45.847 --> 00:48:51.347
But if AI is coupled with robots, the UAVs, then you don't have to worry about that.

00:48:51.347 --> 00:48:59.139
They just pair so perfectly and they can do the job based on the information they get from the building or maybe from the wireless.

00:48:59.179 --> 00:49:03.989
So I guess in the future we do robotic firefighting instead of smart firefighting.

00:49:11.175 --> 00:49:13.815
It's still very challenging because you see, nowadays what AI replacing is not the conventionally hard labor work.

00:49:13.815 --> 00:49:15.742
They are not replacing firefighters.

00:49:15.742 --> 00:49:18.864
They are basically replacing researchers like us.

00:49:18.864 --> 00:49:28.949
They can generate papers, they can generate reviews, these kind of things humans used to think this is so unique, only humans can do.

00:49:28.949 --> 00:49:30.621
But right now AI can do that.

00:49:30.621 --> 00:49:42.248
But instead, if you're carrying something, lifting something, these kind of things are very difficult to be replaced by robots, because our humans, we have evolved for millions of years.

00:49:42.248 --> 00:49:43.568
Just look at our hands.

00:49:43.568 --> 00:49:45.130
It's so elegant.

00:49:45.130 --> 00:49:53.219
There's no, basically no robots can achieve the function of the hand, but our brain only developed for a few thousand years.

00:49:53.219 --> 00:49:56.224
So they are actually kind of replaced by AI now.

00:49:56.224 --> 00:50:03.943
But for the other part of the human human as a machine is actually very good it's very difficult to be replaced by robots.

00:50:03.943 --> 00:50:08.983
I think firefighters don't have to worry about being replaced by robots Anytime soon.

00:50:08.983 --> 00:50:09.826
It's not that easy.

00:50:09.826 --> 00:50:11.467
Not that easy, okay, thank you.

00:50:11.467 --> 00:50:13.960
Thank you, scientists have to be worried about that.

00:50:14.543 --> 00:50:28.429
Scientists, yes, and we are very well aware of the competition from AI-powered colleagues, who I'm not sure have the same level of morality as there should be for being a scientist.

00:50:28.429 --> 00:50:30.260
Sinan, thank you so much.

00:50:30.260 --> 00:50:42.219
It was a pleasure talking with you again in the Fire Science Show and, as always, you have the most exciting topics, so I hope the audience enjoyed this as well.

00:50:42.219 --> 00:50:44.465
Thank you very much for the invitation and that's it.

00:50:44.465 --> 00:50:48.561
It's quite odd that something can be at the same time exciting and disappointing, right?

00:50:48.561 --> 00:50:52.458
I mean the interface between fire science and firefighting.

00:50:52.458 --> 00:51:04.307
The fire scientists people like me who learn about compartment fires, discover physics and so on, and the firefighting fire scientists who do the stuff that's important for a fire brigade.

00:51:04.307 --> 00:51:15.844
We don't have a common language and even if you have the best intentions, it is real challenging to find the connections, and I know that there are people who want those connections.

00:51:15.844 --> 00:51:17.356
I know that there are people who want those connections.

00:51:17.356 --> 00:51:18.297
I know that there are people looking for that.

00:51:18.297 --> 00:51:26.951
There are people working really hard, like I am, about building the bridges and closing the gap between us, because it makes no sense that there is a gap right.

00:51:26.951 --> 00:51:30.626
But it truly is a challenge and it needs good communication.

00:51:30.626 --> 00:51:35.945
I've said it so many times in the podcast Good communication is absolutely necessary to close the gap.

00:51:35.945 --> 00:51:38.021
Institutions like FSRI are necessary to close the gap.

00:51:38.021 --> 00:51:40.010
Institutions like FSRI are necessary to close this gap.

00:51:40.010 --> 00:51:44.481
Open-minded firefighters who listen to Fire Science Show are needed to close this gap.

00:51:44.481 --> 00:51:51.824
Open-minded fire scientists who first ask firefighters and then start their research are needed to close this gap.

00:51:51.824 --> 00:51:57.143
And I hope together we will be able to close this gap because it's really needed in the world.

00:51:57.143 --> 00:52:04.840
And from the exciting things wow, ai-powered autonomous firefighting robots where do I sign in?

00:52:04.840 --> 00:52:09.862
That's a crazy interesting idea, like a science fiction level idea.

00:52:09.862 --> 00:52:10.164
I love it.

00:52:10.164 --> 00:52:16.119
And now we can also deploy them in space or in Mars habitats to make it even more exciting.

00:52:16.119 --> 00:52:20.536
The next thing use of AI to support fire safety engineering.

00:52:20.536 --> 00:52:23.284
Like truly, I know the guys from HK Poly.

00:52:23.284 --> 00:52:26.695
I had my students stay with them for many months.

00:52:26.695 --> 00:52:34.228
We work together with HK Poly and the way how those guys use AI like really is crazy.

00:52:34.228 --> 00:52:40.056
Like it's really like applicating CFD in fire safety engineering looked like 15, 20 years ago.

00:52:40.056 --> 00:52:42.360
There's basically no difference.

00:52:42.360 --> 00:52:44.045
You take a package, you implement that.

00:52:44.045 --> 00:52:45.467
It gives you results.

00:52:45.467 --> 00:52:47.481
It's next level.

00:52:47.481 --> 00:52:55.344
And looking at those guys, I know how the future of fire safety engineering will look like, and I hope this discussion gave you an insight to that as well.

00:52:55.344 --> 00:53:01.179
So that will be it for the AI experiences with AI in fire safety engineering episode.

00:53:01.179 --> 00:53:03.407
I hope you've enjoyed those experiences.

00:53:03.407 --> 00:53:10.373
If we find some novelty in the research of Sinian and I'm sure we will I'll bring him back again to the podcast.

00:53:10.373 --> 00:53:21.380
Sinian is the top one scientist of my generation and I admire him so much so I would love to have him more in the show and I hope you would like that For the next week.

00:53:21.440 --> 00:53:23.686
Another interesting topic in the fire science show.

00:53:23.686 --> 00:53:25.938
So make sure you tune in on Wednesdays.

00:53:25.938 --> 00:53:40.295
And I have to tell you that my season two of Uncovered Witness another four episodes in the other podcast, uncovered Witness, fire Science Revelations is also live and we're covering human behavior in fires in that series.

00:53:40.295 --> 00:53:47.661
I think it's also very exciting a little different format than the fire science show, narrated, scripted, more in-depth.

00:53:47.661 --> 00:53:52.614
Look into one specific part of fire science, this case human behavior in fires.

00:53:52.614 --> 00:54:04.291
I am sure that if you like fire science show and if you like the Fundamentals of Fire Science series that we present in here Uncovered Witnesses, fire Fundamentals on Steroids and you'll love it.

00:54:04.291 --> 00:54:06.135
Thank you for being here with me.

00:54:06.135 --> 00:54:07.135
See you here next Wednesday.

00:54:07.135 --> 00:54:21.445
Bye, this was the Fire Science Show.

00:54:21.445 --> 00:54:23.726
Thank you for listening and see you soon.