Transcript
WEBVTT
00:00:00.221 --> 00:00:02.126
Hello everybody, welcome to the Fire Science Show.
00:00:02.126 --> 00:00:09.252
This is Fire Science Fundamentals, episode 9, and I know that you'll really enjoy this series.
00:00:09.252 --> 00:00:16.390
I know it because the first episode of Fire Fundamentals, with Rory Haddon on ignition has just reached 2000 downloads.
00:00:16.390 --> 00:00:18.353
That is incredible.
00:00:18.353 --> 00:00:22.109
You, the audience, were paramount in coming up with this series.
00:00:22.208 --> 00:00:30.653
I was asked over and over again to do some basic physics episodes in a kind of approachable way and it kind of took off and I really enjoyed doing it.
00:00:30.653 --> 00:00:33.588
So let's continue doing fire fundamentals.
00:00:33.588 --> 00:00:46.790
The last time I did it solo was on compartment fires and previously, before that, we talked about CFD, and the CFD episode was one that many people really enjoyed and yeah, unfortunately for me, you have asked for more.
00:00:46.790 --> 00:00:50.130
I was not really sure what's going to happen after that episode.
00:00:50.130 --> 00:01:00.088
I was pretty sure that I'm going to get a lot of rage emails that I am not covering fluid dynamics in a way that I should, not in a scientific way.
00:01:00.088 --> 00:01:01.771
But actually people have enjoyed that.
00:01:01.771 --> 00:01:03.134
There were no complaints.
00:01:03.134 --> 00:01:04.585
There were questions for more.
00:01:04.585 --> 00:01:05.701
So here we are.
00:01:05.701 --> 00:01:24.631
I'm going to do another episode on the fundamentals of CFD modeling and today we will be discussing boundary conditions and, as boring as it sounds, I'll try to make it exciting and interesting for you that even such a simple thing can be taught in a way that is fun and that really highlights the importance of the subject.
00:01:24.631 --> 00:01:32.200
For the goodness of your models, it's critical to know your boundary conditions, so let's spin the intro and learn our boundaries.
00:01:37.503 --> 00:01:39.144
Welcome to the Firesize Show.
00:01:39.144 --> 00:01:42.605
My name is Wojciech Wigrzyński and I will be your host.
00:01:42.605 --> 00:02:00.656
This podcast is brought to you in collaboration with OFR Consultants.
00:02:00.656 --> 00:02:03.597
Ofr is the UK's leading fire risk consultancy.
00:02:03.597 --> 00:02:14.448
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:14.448 --> 00:02:30.245
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 a hundred professionals.
00:02:30.245 --> 00:02:41.905
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:41.905 --> 00:02:52.550
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.
00:02:52.550 --> 00:02:55.865
This year, get in touch at ofrconsultantscom.
00:02:57.168 --> 00:03:06.520
I wonder if you have this feeling that you wake up and you realize that what you have planned is perhaps a really bad idea and you should not be pursuing that.
00:03:06.520 --> 00:03:15.467
I go through that every second podcast episode, but I'm very bad at listening to my voice of consciousness, or perhaps my imposter.
00:03:15.467 --> 00:03:19.760
And here I am talking on podcasts about boundary conditions.
00:03:19.760 --> 00:03:34.419
You could claim perhaps one of most boring topics one could pick, but I really see some funny and interesting things related to boundary conditions, on a very fundamental level of their use actually, which can make or break your simulation.
00:03:34.419 --> 00:03:48.275
And actually every now and then I see some people posting on LinkedIn their simulations and you immediately realize that their boundaries are not really the ones they should use or they're perhaps misused in a way.
00:03:48.560 --> 00:03:53.733
So let's try and talk about boundary conditions in fluid dynamics, in simulations.
00:03:53.733 --> 00:03:59.372
And note, before we start, you have to understand that I am ANSYS fluent person.
00:03:59.372 --> 00:04:00.765
I am an ANSYS fluent user.
00:04:00.765 --> 00:04:08.663
I'm trained and, let's say, skilled at FDS, but it's not my daily software that I would be using for everything.
00:04:08.663 --> 00:04:16.273
So if I confuse the name of a boundary condition in FDS, please feel free to correct me and I'll try to fix it.
00:04:16.273 --> 00:04:17.377
I'm learning every day.
00:04:17.377 --> 00:04:21.769
Hopefully I'll get my boundaries done in Ansys and correct If I mess that one.
00:04:21.769 --> 00:04:22.711
That's going to be hilarious.
00:04:23.199 --> 00:04:26.009
Anyway, if we talk about boundaries, what are boundary conditions?
00:04:26.009 --> 00:04:28.168
Why do we need them in our simulations?
00:04:28.168 --> 00:04:35.005
If you would like to attempt a fluid, dynamic simulation of an endless space, let's think planet Earth.
00:04:35.005 --> 00:04:41.466
You swim to the east, you eventually reach the point from where you've started An endless continuity.
00:04:41.466 --> 00:04:44.279
If you look down, well, there's a boundary condition.
00:04:44.279 --> 00:04:46.086
There's a solid surface or an ocean.
00:04:46.086 --> 00:04:51.002
If you look up, it ends in with a vacuum of space, also something you could call a boundary condition.
00:04:51.002 --> 00:04:55.982
So even in an endless space of Earth, you are still constrained by something.
00:04:55.982 --> 00:05:04.687
And obviously, when we simulate our fire cases, it's not that we're going to simulate an endless atmosphere around our buildings.
00:05:04.687 --> 00:05:08.274
I mean time is money and resources are everything.
00:05:08.274 --> 00:05:11.187
They dictate what we can and what we cannot do.
00:05:11.329 --> 00:05:34.089
In our simulations we have to narrow the field of what we're investigating into a part of the space and, as you remember from the previous CFD episode of the Far Fundamentals, cfd works basically on solving multiple equations momentum transfer, heat transfer, species conservation and so on, so on in a confined space.
00:05:34.089 --> 00:05:42.170
And for it to work, it must understand what's happening when it reaches the end of that space.
00:05:42.170 --> 00:05:44.206
Does it magically disappear?
00:05:44.206 --> 00:05:47.387
Does it bounce back from a solid obstacle?
00:05:47.387 --> 00:05:48.591
These are your boundaries.
00:05:48.591 --> 00:05:58.632
These are the elements that constrain your fluid, that constrain your model and through which you can actually act and define your model.
00:05:58.632 --> 00:06:06.761
These are critical parts of your model where you have the ability to interact with the fluid that you are modeling.
00:06:06.761 --> 00:06:18.072
Actually, if you think about fluid itself, you can define fluid as a substance that continuously deforms under the application of sheer stress and adapts its shape to the constraints.
00:06:18.072 --> 00:06:19.221
So here you are.
00:06:19.221 --> 00:06:22.550
That's your boundary conditions, things that act on your fluid.
00:06:22.750 --> 00:06:29.192
Now, if we want to narrow the discussion into particular types of boundary conditions I'm not going to list them, that's pointless.
00:06:29.192 --> 00:06:34.007
I would say I would define two major categories of the boundaries.
00:06:34.007 --> 00:06:43.012
One would be the boundaries that actually interact with your fluid, so I would call them the flow boundaries or the fluid boundaries.
00:06:43.012 --> 00:06:48.651
It's a very unprofessional way to call them, but it kind of delivers the message.
00:06:48.651 --> 00:06:55.952
It's the boundaries that interact with your fluid and act on it, and boundaries that are pretty much solid walls, like solid boundaries of your model.
00:06:55.952 --> 00:06:59.105
And there are some special boundaries which we'll talk in the end.
00:06:59.105 --> 00:07:04.605
So stay tuned for a surprise hopefully interesting For fluid boundaries.
00:07:05.307 --> 00:07:13.701
Into this big bucket I put all the boundaries that you use as a CFD user to interact with the fluid you have in your model.
00:07:13.701 --> 00:07:17.987
That most likely is air or some mixture of air and smoke.
00:07:17.987 --> 00:07:35.069
I often call the smoke spoiled air because in CFD modeling the smoke properties are actually quite same as the air has, and the only difference being that there are species in it, like soot and other products of combustion, and due to that it has different emissivity.
00:07:35.069 --> 00:07:41.408
However, for most cases the smoke and air are pretty much the same thing from the fluid dynamics perspective.
00:07:41.408 --> 00:07:47.108
Anyway, from my perspective, the first, most basic boundary condition I would always have in my model.
00:07:47.108 --> 00:07:51.584
It's hard for me to figure out a single model in which I would never use that boundary condition.
00:07:52.125 --> 00:07:58.461
These are conditions that simulate an open end to your numerical domain.
00:07:58.461 --> 00:08:02.805
In ANSYS we call them pressure boundaries, pressure inlets, pressure outlets.
00:08:02.805 --> 00:08:05.629
We call them pressure boundaries, pressure inlets, pressure outlets.
00:08:05.629 --> 00:08:12.196
In FTS I think we commonly refer to them open, and those are types of vents that are used in FTS.
00:08:12.196 --> 00:08:27.480
Regardless of the name, the point of this open or pressure boundary is to define space through which the fluid can flow freely and there's a defined pressure dynamic pressure on that boundary condition.
00:08:27.480 --> 00:08:28.983
Now, what does it mean?
00:08:28.983 --> 00:08:38.100
If the dynamic pressure on that boundary is positive, then the flow is coming from that boundary into your model, unless the pressure in your model is higher than that one.
00:08:38.100 --> 00:08:41.610
If the pressure is negative, there's going to be a suction effect.
00:08:41.610 --> 00:08:47.684
If it's zero, then the flow will be an outcome of the pressure value inside your domain.
00:08:47.684 --> 00:08:48.787
Pretty simple, isn't it?
00:08:48.787 --> 00:08:58.062
But there are some issues that you can easily incorporate into your model by simply applying these boundary conditions without thinking.
00:08:58.863 --> 00:09:06.541
If you think about pressure in your domain, well, it's not that the pressure in every point of your domain is exactly same.
00:09:06.541 --> 00:09:08.585
There's hydrostatic pressure.
00:09:08.585 --> 00:09:13.313
That is simply an outcome of your fluid having some weight.
00:09:13.313 --> 00:09:17.068
It just weights and you'll have a hydrostatic pressure buildup.
00:09:17.068 --> 00:09:20.625
In normal conditions that would be roughly 12 pascals per meter of height.
00:09:20.625 --> 00:09:22.610
So that's quite a significant pressure.
00:09:22.610 --> 00:09:32.562
Now imagine, on your other side of your boundary condition you always have zero and on the domain in which you are simulating your fluid flow, the pressure is growing.
00:09:32.562 --> 00:09:46.354
With every meter down, it simply increases, which means that you could end up with artificial pressure difference between your domain and exterior just because you've defined the pressure on the other side as zero.
00:09:46.354 --> 00:09:51.671
For the CFD software, along the height of your pressure boundary, the pressure is zero.
00:09:51.671 --> 00:09:53.062
It's not hydrostatic.
00:09:53.062 --> 00:09:59.923
Perhaps in other softwares than ANSYS it's predefined as hydrostatic, being included automatically.
00:09:59.923 --> 00:10:04.802
For us, there's actually a necessity to consider that and include that in our pressure boundaries.
00:10:04.802 --> 00:10:08.631
So here, even the most simple condition has a challenge for you.
00:10:09.139 --> 00:10:17.010
Now another thing that's interesting in pressure boundaries or open boundaries, sometimes we would be only interested in modeling the interior of our building.
00:10:17.010 --> 00:10:24.211
Let's say you're modeling a warehouse and you want to put some sort of inlets, outlets, to that warehouse.
00:10:24.211 --> 00:10:31.011
You're working with a natural smoke control, so you're obviously using things like natural smoke extraction ventilators.
00:10:31.011 --> 00:10:34.971
You're using doors as your makeup air sources.
00:10:34.971 --> 00:10:38.390
We've talked about that in previous Fire Fundamentals episodes.
00:10:38.390 --> 00:10:45.250
Now you would like to model them, and there is an urge that the simplest way to model them was a natural opening.
00:10:45.250 --> 00:10:49.054
That's like literally something that connects your interior to the exterior, right?
00:10:49.054 --> 00:10:52.504
So perhaps a pressure boundary is a perfect way to simulate that.
00:10:52.904 --> 00:11:08.282
Now the thing is that when you have natural ventilators, especially smaller or ones that do not open fully, there are different types of natural ventilators that are less efficient In those devices.
00:11:08.282 --> 00:11:13.113
It's not that the air flows freely through the entire cross-section of the device.
00:11:13.113 --> 00:11:15.368
It may be blocking the pathway for the air.
00:11:15.368 --> 00:11:18.669
It will definitely include some resistance for air to go.
00:11:18.669 --> 00:11:40.591
So if you have, let's say, a square meter of a natural ventilator on your roof and in that space you put a square meter of a natural ventilator on your roof and in that space you put a square meter of a pressure boundary, the effects of pressure boundary will be more pronounced, more significant than the effects of your natural ventilator, because the natural ventilator is less efficient than an idealized hole.
00:11:40.591 --> 00:11:43.402
Another thing outside you would have different temperatures.
00:11:43.402 --> 00:11:51.645
So you also have to define this temperature on the other side of your open boundary to really capture the chimney effects and all the buoyancy effects that will come in play.
00:11:51.966 --> 00:11:57.969
So just dropping your open boundaries, because they are not openings, they're pressure boundaries.
00:11:57.969 --> 00:12:03.028
You have to understand how you use them and be conscious in where you place them.
00:12:03.028 --> 00:12:06.662
If you want to simulate natural ventilators, they're not the way to go.
00:12:06.662 --> 00:12:15.898
You need to simulate some sort of a roof structure and some sort of openings in that roof that at least try to mimic the effectiveness of natural ventilators.
00:12:15.898 --> 00:12:23.524
Perhaps you can go away in the most simplistic case by using smaller, but I'm not going to give you a recommendation of how small you should make them.
00:12:23.524 --> 00:12:30.583
If you want to play like that, you need to do your own validation and figure out values that would work for yourself.
00:12:30.583 --> 00:12:34.775
Now we've briefly talked about the pressure boundaries.
00:12:35.378 --> 00:12:41.350
Another boundary that I would very, very commonly use in my models would be velocity boundaries.
00:12:41.350 --> 00:12:44.764
So here we are talking about mechanical vents.
00:12:44.764 --> 00:12:47.581
In ANSYS we would call them velocity inlets.
00:12:47.581 --> 00:13:00.994
In this case, instead of a pressure on my boundary, which again is something that fluid can flow through, I define velocity of the flow and I define a vector which way the flow goes.
00:13:00.994 --> 00:13:12.869
So I am capable of defining a fixed suction or inlet point in my model through which air will come or be extracted through with a specified velocity.
00:13:12.869 --> 00:13:15.701
I also define stuff like temperatures.
00:13:15.701 --> 00:13:22.082
I also define in Ansys stuff like turbulent intensity and other important parameters for my simulation.
00:13:22.504 --> 00:13:26.461
But the most important thing, what's the velocity at the boundary condition?
00:13:26.461 --> 00:13:29.327
Now, again, we're talking about boundary condition.
00:13:29.327 --> 00:13:34.649
You have a patch of your model that this boundary condition is applied to.
00:13:34.649 --> 00:13:57.472
When I say that the boundary condition of velocity is three meters per second, every single cell, that's a part of this patch that I called my velocity inlet now will have three meters of velocity introduced into my model, exactly this value, and the model will make sure that this value is the value introduced to my model.
00:13:57.980 --> 00:13:59.626
Now there's an issue with that.
00:13:59.626 --> 00:14:06.010
It's pretty robust and simple and in most cases it works without playing too much with it.
00:14:06.010 --> 00:14:19.725
But if you would like to be really, really precise in modeling your vents, it's not that the entire ventilator has the same velocity at its surface, whatever the surface is.
00:14:19.725 --> 00:14:22.509
It's actually a virtual concept the surface of a ventilator.
00:14:22.509 --> 00:14:41.532
Anyway, through the cross-section from which the air enters your domain, in a real case, in a real building, you will have some sort of velocity profile, whereas in your CFD model you will have idealized averaged flow over the entirety of the velocity patch that you put into your model.
00:14:42.261 --> 00:14:43.419
How big is the issue?
00:14:43.419 --> 00:14:59.850
So if you have a very narrow duct work, you have we call them pancake ducts very flat ducts in which one dimension is pretty long and the other is pretty narrow and you have a very big vent on such a pancake duct.
00:14:59.850 --> 00:15:05.130
You usually end up with extremely uneven flow through that duct.
00:15:05.130 --> 00:15:19.552
So you could have 2 m per second average on such an opening, which could sound acceptable in some sort of cases for smoke control, whereas in reality you would have no flow on most of the opening and 5 m at the bottom.
00:15:19.552 --> 00:15:32.654
Now those 5 m will cause you trouble with your smoke control system because that's a lot of kinetic energy introduced into your building and a good chance that this flow will mix something in a place that you don't want it to be mixed.
00:15:32.654 --> 00:15:56.620
And especially if you're modeling stuff like corridors or some narrow, tight spaces, this error can occur, lead to a system which works perfectly in simulations by applying this averaged velocity over your inlet, whereas in reality the velocity is skewed and you get much higher velocities and the system actually does not work.
00:15:56.620 --> 00:16:00.028
We've seen that happen and that's a pretty big challenge.
00:16:00.934 --> 00:16:19.043
The ways to overcome that we usually try to model the ductwork and so the the profile on the inlet is actually some sort of an outcome of the calculations of the model, and my velocity inlet is actually where my extraction or inlet fans are physically.
00:16:19.043 --> 00:16:26.917
So instead of simulating just grills that are in my compartment, I would would simulate the ductwork For the more challenging projects.
00:16:26.917 --> 00:16:30.376
I wouldn't say that we did it every single time, but when we need to pay attention.
00:16:30.376 --> 00:16:31.299
We do it like that.
00:16:31.299 --> 00:16:34.572
Another way you can define profiles.
00:16:34.572 --> 00:16:37.519
This is a very interesting way to work with those boundary conditions.
00:16:37.519 --> 00:16:48.441
So you can actually force CFD software to apply a specific profile to the velocity introduced so it's no longer even but actually conforms to however you define it.
00:16:48.441 --> 00:16:50.565
So yeah that, that that's the way.
00:16:51.226 --> 00:17:07.556
Another thing interesting with velocity boundaries is that when you think you introduce flow from a mechanical ventilator into your compartment, you would most likely think about your horizontal velocity component from that fan.
00:17:07.556 --> 00:17:11.328
Right, because it's just blowing air straight in front right.
00:17:11.328 --> 00:17:22.018
But in fact, because the fan is a rotating machine, it actually introduces quite a significant tangential component to velocity.
00:17:22.018 --> 00:17:31.403
It swirls and in some cases, in some aspects of modeling, this swirl may be actually quite important to the outcomes of your simulation.
00:17:31.403 --> 00:17:31.875
Here.
00:17:31.875 --> 00:17:34.765
I wouldn't say it's something we would use commonly.
00:17:34.765 --> 00:17:37.022
I would say it's very rarely used.
00:17:37.022 --> 00:17:48.105
But especially in tunneling projects when you're modeling big jet fans, you're not usually doing that with velocity inlets, but other flow conditions also can apply as well.
00:17:48.105 --> 00:17:56.343
This could actually make a big difference in the outcomes of your modeling of the flow profile of your jet fan.
00:17:56.343 --> 00:18:05.780
So yeah, sometimes you have to go in your understanding beyond just the basic characteristic that you're pushing air forward.
00:18:05.780 --> 00:18:08.135
I know some cases.
00:18:08.135 --> 00:18:12.965
There's a gentleman, fahd Itrada, who is doing amazing modeling of chat fans.
00:18:12.965 --> 00:18:27.598
They've developed a fan called Mojet and truly the modeling they do to model their fans is remarkable and the level of details they go into to actually capture the behavior of that chat fan is stunning.
00:18:27.598 --> 00:18:36.746
So, as with most of the things you do in fire safety science and fire safety engineering, when you go deep inside it becomes pretty complicated.
00:18:37.326 --> 00:18:42.503
Another aspect of velocity boundary conditions is when we try to apply wind.
00:18:42.503 --> 00:18:43.325
That's a big trap.
00:18:43.325 --> 00:18:44.748
A lot of people fall into that.
00:18:44.748 --> 00:18:50.324
So wind is not just a boundary condition that blows air at a constant speed.
00:18:50.324 --> 00:18:58.366
Wind is a complicated phenomenon, physical phenomenon, and you really have to introduce wind first with a profile.
00:18:58.366 --> 00:19:00.623
So it has to follow some profile.
00:19:00.623 --> 00:19:06.942
The wind at the ground level will be weaker than the wind at some height.
00:19:06.942 --> 00:19:11.228
There are logarithmic profiles that define the velocity of wind.
00:19:11.228 --> 00:19:15.500
With the height, wind will introduce turbulence, so you have to capture the turbulence.
00:19:15.500 --> 00:19:32.333
If you're modeling it with large eddy simulation, you may be even in need to get some sort of periodic boundary condition that increases, decreases velocity continuously so you capture the formation of large eddies or large vortices that come with winds.
00:19:32.333 --> 00:19:34.317
So you get the spikes in velocity correct.
00:19:34.317 --> 00:19:43.300
It's actually quite challenging, but just dropping a massive velocity inlet boundary condition in front of your model, it it's not really cutting.
00:19:43.300 --> 00:19:55.724
That that's not wind, that's a big chunk of velocity, not a physical phenomenon of wind, which is beautiful and complex, and I have many other podcast episodes that go deeper into that.
00:19:55.924 --> 00:19:57.127
There's another thing about velocity.
00:19:57.127 --> 00:19:58.660
I mean velocity inlets.
00:19:58.660 --> 00:20:06.981
This is very simple but it could be a very problematic boundary condition or it can have a very far-reaching consequences for your models.
00:20:06.981 --> 00:20:25.240
So if you define the velocity inlet boundary condition, you define the speed at which the air is put into your model or extracted from your model, which basically defines the exact value of volumetric flow that's flowing through that space, and this will be constrained by the model.
00:20:25.240 --> 00:20:28.460
Now imagine you have your model.
00:20:28.460 --> 00:20:30.727
It's a cube, it's a compartment.
00:20:30.727 --> 00:20:33.935
You have one velocity inlet that brings air into the room.
00:20:33.935 --> 00:20:37.304
You have velocity outlet that extract the air from the room.
00:20:37.304 --> 00:20:54.821
You've defined both velocities to match each other and now you introduce the fire into the room and what will happen is that you will observe a pressure increase into the room, perhaps even up to some unphysical levels of pressure and your CFD model will crash.
00:20:54.821 --> 00:20:57.242
It will give you very odd results.
00:20:57.242 --> 00:20:57.564
Why?
00:20:57.564 --> 00:21:04.923
Because the system is not able to blow more air through the velocity inlet, which has a defined velocity.
00:21:04.923 --> 00:21:10.484
It has to extract or input exact the number you've put into it.
00:21:10.484 --> 00:21:18.665
If there's a pressure increase around that boundary condition, it's not changing the outcomes, so the pressure increases, decreases.
00:21:18.705 --> 00:21:31.944
You can get into big trouble in your models if you only define very fixed values on those types of boundary conditions, and that's why I said I use pressure boundaries in almost every single model.
00:21:31.944 --> 00:21:42.684
You almost always need a pressure boundary somewhere to improve the convergence of your simulation, to have a way to manage the decrease, increase of pressures.
00:21:42.684 --> 00:21:46.598
Of course this has to represent some physical leakage in your building.
00:21:46.598 --> 00:21:57.669
If you're designing a, the most sealed building in the planet, you perhaps should do velocity boundaries, but then again the fans don't work like that and they would adjust.
00:21:57.669 --> 00:21:59.398
Oh yeah, let's go to fans.
00:21:59.901 --> 00:22:06.281
Actually, that's accidentally a very good segue to the next boundary condition I wanted to talk about which, which is fan boundary condition.
00:22:06.281 --> 00:22:13.240
And this is a boundary condition in which we have a slice of space through which the air can flow through.
00:22:13.240 --> 00:22:20.637
So it's a boundary condition that does not mark the outer regions of our simulation.
00:22:20.637 --> 00:22:24.942
It's placed inside the fluid and it accelerates the fluid.
00:22:24.942 --> 00:22:28.164
It acts as a fan, as a ventilator would.
00:22:28.164 --> 00:22:33.990
Now there are so many ways you can design this boundary condition.
00:22:33.990 --> 00:22:51.103
Actually, my friends from Silesian University of Technology, alexander and Gosia Kurl, have wrote a really nice paper on all the different ways you can use to model fan boundary condition to capture the behavior of a fan, especially jet fans, in your simulation better.
00:22:51.103 --> 00:22:55.840
And yeah, I really like to use this, this boundary condition in ansys.
00:22:55.840 --> 00:23:08.637
It gives me very good, uh, first, it gives me very good control over the flow of my fan and secondly, because it's based on decades of answers being used to model fans for fan manufacturers.
00:23:08.637 --> 00:23:15.057
They actually got very convenient and good and accurate models of fans built within the software.
00:23:15.057 --> 00:23:26.190
So for me it's just convenient and if you think about it, it's kind of funny because it's a very simple answer to a problem that have been quite complicated in the past.
00:23:26.692 --> 00:23:41.195
So if I remember correctly, the first times we tried to do jet fans we were mostly using velocity inlets and you know, having air sucked into the velocity inlet on one end of the jet fan, having it released on the other end.
00:23:41.195 --> 00:23:48.240
The issue was it was a different air because it kind of disappeared when it reached the other end of the boundary condition.
00:23:48.240 --> 00:23:49.684
It was not modeled anymore.
00:23:49.684 --> 00:24:03.243
Then we went into recirculation inlets, outlets, which were velocity inlets connected with, let's say, a magical duct that connects one end to another and that allowed us to transfer air from one side to another.
00:24:03.243 --> 00:24:13.537
But this did not allow us to model the behavior of the ventilator where it receives different pressures on the inlet or the losses change on the outlet side.
00:24:13.958 --> 00:24:15.942
The fan, of course, is a mechanical device.
00:24:15.942 --> 00:24:19.558
It has its power curve, it has its fan curve.
00:24:19.558 --> 00:24:24.999
Those are the things you can actually model with a good fan model and by introducing that.
00:24:24.999 --> 00:24:40.128
It takes a lot of work actually to introduce that correctly, but when you introduce that you are actually modeling a real ventilation device in your system and I think in some projects it's absolutely necessary, just like capturing the profiles on your velocity inlets.
00:24:40.128 --> 00:24:58.175
This is sometimes also critical to get your smoke control system modeled in a way that you can be fairly sure that what you've done is accurate and in the building, when they finally build the building and they finally do the smoke control system in it, it's going to work like you've simulated.
00:24:58.175 --> 00:25:07.317
It's a very stressful situation when reality validates or verifies your numerical modeling and you really want to be on the safe side.
00:25:07.317 --> 00:25:13.040
And you get on the safe side by knowing your boundaries, knowing your boundary conditions and applying them correctly.
00:25:13.842 --> 00:25:22.146
An interesting thing for modeling fans and, in general, smoke control systems or ventilation systems is the hvc model in fds.
00:25:22.146 --> 00:25:28.459
Massive shout out to jason floyd who was spearheading the efforts to write this model.
00:25:28.459 --> 00:25:44.876
I think it's a brilliant addition to FDS and it's simply a nodal model where you can basically build a network of nodes that interconnect to each other and simulate the ductworks, but instead of physically simulating the ducts, you know the shape and the flows inside.
00:25:44.876 --> 00:26:01.624
There are physical relations that describe the flow of air within the ducts, through ventilation devices into your rooms and so on, and this network is modeled along your CFD model and the boundary conditions are defined by that network.
00:26:01.624 --> 00:26:11.642
So it takes a lot of hard work from you onto the network and it actually calculates what are the flows, what are the pressure points on your fans and so on.
00:26:11.642 --> 00:26:16.128
A brilliant way to actually make the lives of fire engineers simpler.
00:26:16.128 --> 00:26:19.022
So highly appreciate that this was included in FDS.
00:26:19.022 --> 00:26:26.898
I actually wish we had something like that in Ansys, like if we wanted something like this, we would have to program it ourselves.
00:26:26.898 --> 00:26:32.555
And uh, yeah, sometimes we we do some attempts not as fancy as the solver in fds.
00:26:32.555 --> 00:26:35.041
I'm highly envious in this regard.
00:26:35.041 --> 00:26:38.090
Perhaps we need to recruit jason to write one for us.
00:26:38.792 --> 00:26:41.804
The hvc nodes are also something you can use to model your jet fan.
00:26:41.804 --> 00:26:52.444
So, as I said previously, we have the fan boundary condition in answers, which allows us to define the performance of the fan based on what comes in, what comes out, what's the losses and so on.
00:26:52.444 --> 00:26:58.281
You could actually do the same thing with HVAC nodes in FDS to efficiently model your jet fans.
00:26:58.281 --> 00:27:02.577
I'm not sure if you can add the tangential swill to your flow in FDS.
00:27:02.577 --> 00:27:06.567
Probably you can, but please don't quote me on that.
00:27:06.567 --> 00:27:11.244
You have to submit an issue on issue tracker and figure out if you can or not.
00:27:11.244 --> 00:27:12.816
If someone knows, let me know.
00:27:12.816 --> 00:27:16.730
I'm actually curious now because I have not fact-checked it before.
00:27:16.730 --> 00:27:19.840
I've never done it in this detail in FDS.
00:27:20.382 --> 00:27:24.714
Anyway, this would be a quick summary of the important flow boundaries.