WEBVTT 00:00.260 --> 00:01.040 Hello everyone. 00:01.040 --> 00:04.790 Welcome back to the CFD using Openfoam beginner to intermediate course. 00:05.300 --> 00:06.770 So this is our class eight. 00:06.770 --> 00:11.750 In this class we'll be seeing importing Ansys workbench mesh into Openfoam. 00:11.750 --> 00:14.480 Importing Ansys fluent machine to Openfoam. 00:15.320 --> 00:17.930 Flow over a cylinder using workbench. 00:17.930 --> 00:25.940 Meshing done mesh so you will use the workbench mesh uh, imported into Openfoam and do a flow over 00:25.940 --> 00:26.870 a cylinder case. 00:28.100 --> 00:34.550 Okay, importing Ansys workbench mesh into Openfoam is a very simple process, but the purpose is it. 00:34.550 --> 00:38.210 Use high quality Ansys workbench mesh in Openfoam simulations. 00:38.210 --> 00:45.740 If you are someone who uses Openfoam and you get a project where they have a workbench mesh from Ansys, 00:45.740 --> 00:51.620 which is the most popular commercial software, you should not be in a position to not use those mesh 00:51.620 --> 00:55.950 and do the simulation, because Openfoam is basically a solver for CFD. 00:57.180 --> 01:05.340 So you can use high quality CFD mesh inside Openfoam and do your simulation so it leverages Ansys. 01:05.340 --> 01:13.230 Robust machine tools are for complex geometries which cannot be highly capturable in block, mesh or 01:13.230 --> 01:14.880 snap in some cases. 01:14.880 --> 01:22.200 Snap mesh is definitely one of the best tools for meshing in hex, but if you want a data mesh, then 01:22.200 --> 01:25.800 Asus might be the, uh, commercial software which will help you. 01:25.800 --> 01:32.130 There is also other software called CF mesh, which you can use as open source in Openfoam, but we 01:32.130 --> 01:35.130 are just interested in importing Ansys mesh as of now. 01:36.450 --> 01:36.840 Okay. 01:36.840 --> 01:42.780 The process is you have to export the mesh from Ansys workbench, save it in the format of dot mesh, 01:42.780 --> 01:44.790 which is called workbench mesh format. 01:45.180 --> 01:51.270 Then you have to ensure the compatibility with Openfoam requirements, which we will see the commands 01:51.270 --> 01:52.110 to check that. 01:52.110 --> 01:59.640 Then you will convert the mesh, use the command Fluent mesh to form our fluent 3D mesh to form. 01:59.640 --> 02:03.210 If it is a 3D case using those command, you can import it. 02:03.210 --> 02:08.020 So the usage of that command is like fluent mesh to form space. 02:08.020 --> 02:14.290 The file name dot mesh or fluent 3D mesh to form space, file name, dot message. 02:15.070 --> 02:21.040 And you can always use the check mesh command because anyways, if you are import, even if you are 02:21.040 --> 02:27.430 importing Ansys workbench mesh, it is going to get stored in the format of poly mesh inside Openfoam. 02:27.430 --> 02:29.860 So you can always do the check mesh command. 02:30.100 --> 02:32.320 Verify the mesh integrity using check mesh. 02:32.320 --> 02:37.000 Then address any inconsistencies or errors using Ansys meshing. 02:38.440 --> 02:42.580 So importing Ansys fluent mesh is a different process. 02:42.580 --> 02:46.240 So you have to export the mesh from Ansys fluent. 02:46.840 --> 02:52.810 Uh, but in a different way, because Ansys fluent meshing will generate a file called dot mesh dot 02:52.810 --> 02:55.760 h file, which is not supported in openfoam. 02:55.760 --> 02:57.650 You can only use dot msh. 02:58.550 --> 03:02.600 So to do that you have to use the standalone fluent machine. 03:02.600 --> 03:06.350 So our application and not the one which comes with the workbench. 03:06.350 --> 03:10.520 So you have to use the standalone fluent machine to generate the mesh. 03:10.700 --> 03:12.470 Then you have to save the mesh. 03:12.470 --> 03:20.270 Mesh has dot msh dot h file which is fluent mesh and export the generated mesh in Ascii format and not 03:20.270 --> 03:21.110 in binary. 03:21.470 --> 03:28.070 So by default it will be in binary and you have to export it uh, in Ascii format. 03:28.070 --> 03:35.780 We will see how to change it, and after exporting you can rename the file to dot msh dot h5 while saving 03:35.780 --> 03:36.350 itself. 03:36.350 --> 03:41.570 So when you do that it will get saved as dot msh instead of dot msh dot h. 03:41.750 --> 03:46.160 But uh, always remember that it doesn't work with workbench. 03:46.760 --> 03:48.590 Uh, kind of meshing. 03:48.590 --> 03:55.070 I mean, when Openfoam is trying to accept dot mesh dot h file, it won't be able to read. 03:55.070 --> 03:59.690 So you have to use standalone fluent meshing instead of the fluent mesh which comes with the open, 03:59.900 --> 04:02.150 uh, with the Ansys workbench. 04:04.340 --> 04:04.730 Okay. 04:04.730 --> 04:08.540 The command, as you already know, is fluent mesh to form space. 04:09.030 --> 04:10.620 Uh, file name dot mesh. 04:10.620 --> 04:13.890 In this example it is called mesh mesh dot mesh. 04:14.100 --> 04:20.520 So for this tutorial we have done a machine using SolidWorks. 04:20.520 --> 04:23.370 We have created the geometry in SolidWorks. 04:23.370 --> 04:31.890 I mean you can see the dimensions here and it is saved as dot IG is file and it is imported inside Ansys 04:31.890 --> 04:33.960 workbench which is Design modeler. 04:34.380 --> 04:42.720 In Design Modeler, you have to choose the object and you have to change it to fluid instead of solid. 04:42.720 --> 04:45.030 You can find this panel on the left bottom. 04:45.690 --> 04:51.480 Only then Openfoam can understand that this is a fluid region, and also if you are going to try to 04:51.480 --> 04:59.760 make it as a 2D case, then you might have to use the convert utilities in uh, Design Modeler and take 04:59.760 --> 05:02.760 a face from the SolidWorks thing. 05:02.760 --> 05:11.220 If you want to know how to import SolidWorks, uh, 3D geometry into Ansys or Design Modeler and convert 05:11.220 --> 05:15.060 it into 2D, you can check the video in our YouTube channel for dynamics. 05:15.240 --> 05:17.580 So I have made a video on that. 05:18.300 --> 05:23.020 After we convert it into 2D Ansys workbench, then we can do the mesh. 05:23.020 --> 05:28.210 So in this case I have done a generic hex mesh you can do with any mesh. 05:28.210 --> 05:32.140 I have also added some inflation layers near the cylinder. 05:32.830 --> 05:38.950 Okay, in the naming selections, I have also given the left as inlet, right as outlet and named the 05:38.950 --> 05:41.920 cylinder as cylinder and upper and upper and lower. 05:42.640 --> 05:50.830 Okay, now to uh, change while saving the file in workbench machine, you can, uh, click on export. 05:50.830 --> 05:54.490 Then after export you can choose options from there. 05:54.490 --> 06:04.990 If you go inside your export uh, options of meshing, you can change the format of input file as Ascii 06:05.530 --> 06:07.960 instead of binary and click on okay. 06:08.110 --> 06:13.040 Then you have to export the mesh in fluent input file method. 06:13.040 --> 06:15.110 So this is what you have to do. 06:15.140 --> 06:20.870 You can see the process I click on export, then mesh, then fluent input mesh, then I export. 06:20.870 --> 06:23.810 But before that you have to go to the options and change this. 06:24.530 --> 06:31.190 After we do that we would get the file in dot mesh which we can see now okay. 06:33.770 --> 06:37.940 Okay I am I'm in class eight first case. 06:37.940 --> 06:42.680 So as you can see I have the flow over cylinder workbench mesh dot mesh here. 06:42.710 --> 06:48.140 Now we are going to use this and import it into Openfoam. 06:48.260 --> 06:51.410 So I am in the working directory. 06:51.440 --> 06:58.640 Now you know the command since it is 2D mesh is fluent mesh to form space. 06:58.640 --> 07:01.220 The file name which is flow over cylinder. 07:01.370 --> 07:02.900 Workbench mesh dot msh. 07:03.050 --> 07:10.610 I'll click enter and you can see it is writing the mesh to constants slash poly mesh and it is done. 07:11.810 --> 07:15.440 Now we can see the mesh by clicking on Paraview. 07:18.650 --> 07:19.940 I'll click on apply. 07:21.260 --> 07:25.260 As you can see though, we said it is a 2D mesh. 07:26.910 --> 07:33.000 It came with a 3D surface because it's going to set the Z to one cell automatically. 07:33.000 --> 07:34.080 You don't have to do that. 07:34.080 --> 07:38.370 Unlike, uh, making a block mesh, setting the front end back to empty. 07:38.400 --> 07:39.870 You don't have to do those things. 07:40.320 --> 07:42.330 It is already set to empty. 07:42.330 --> 07:45.420 I mean, the front and back by default while importing. 07:45.420 --> 07:47.700 So this is the nice thing about openfoam Openfoam. 07:48.360 --> 07:50.100 It already does it. 07:51.120 --> 07:53.130 Okay, now we are seeing the internal mesh. 07:53.220 --> 07:56.520 As you can see, we have inlet outlet upper and lower. 07:56.550 --> 08:01.080 All the naming selection, whatever we gave in Ansys, it is still there in Openfoam. 08:01.080 --> 08:01.470 Also. 08:01.470 --> 08:03.150 Now we have the mesh. 08:03.180 --> 08:10.230 Now you can decompose, run the simulation, do whatever you want because you have the, uh, polymesh 08:10.230 --> 08:10.890 folder. 08:10.890 --> 08:14.700 You can just copy and paste it in any tutorial and you can do it. 08:14.970 --> 08:18.990 So this is one nice way to import workbench mesh. 08:20.700 --> 08:21.090 Okay. 08:21.090 --> 08:28.710 Now we are going to see how this uh, okay, we saw on how it is adding front and back planes. 08:28.740 --> 08:32.310 Now we will see how to import fluent mesh. 08:32.340 --> 08:39.070 So the geometry is made uh, in Design Modeler and you have to give the boundary names, which is naming 08:39.070 --> 08:41.050 selection in the design modeler itself. 08:41.560 --> 08:48.730 Otherwise you can't name it in Ansys fluent meshing and like how you did it in workbench machine because 08:48.730 --> 08:51.010 we are going to use standalone fluent meshing. 08:51.010 --> 08:53.230 It doesn't have those things, it can only mesh. 08:54.010 --> 08:57.070 So you have to create the naming selection and design modeler itself. 08:57.130 --> 09:01.720 And you also have to assign the body to fluid instead of solid. 09:02.290 --> 09:08.530 After that, you have to save the design modular file and then open the standalone fluid machine, uh, 09:08.530 --> 09:09.220 application. 09:09.220 --> 09:13.480 And you have to import the mesh file and you have to generate the mesh using Ansys fluid. 09:13.510 --> 09:16.300 So that is not the tutorial which we are going to see. 09:16.300 --> 09:18.430 It is about Openfoam or not Ansys fluent. 09:18.970 --> 09:23.200 But if you want to see how to use Ansys Fluent Mesh, you can check out our YouTube channel and check 09:23.200 --> 09:23.770 the tutorial. 09:24.280 --> 09:29.270 Okay, now the methodology to export the Fluent Mesh is. 09:29.270 --> 09:29.990 Through this. 09:29.990 --> 09:33.620 You just click on file and write and then mesh. 09:33.770 --> 09:38.150 But in the mesh you have to deselect the write binary files. 09:38.180 --> 09:38.870 Okay. 09:38.870 --> 09:46.220 And you also have to uh, change the file name to dot mesh. 09:46.340 --> 09:47.030 Okay. 09:47.360 --> 09:54.290 Uh, instead of saving it as c f CF mesh files, you just choose all files and save it as whatever name 09:54.290 --> 09:55.790 you want to give Dot a message. 09:55.970 --> 09:56.510 Always. 09:56.510 --> 09:59.000 You have to make sure that it is not written in binary. 09:59.270 --> 10:04.640 Okay, while saving you just save it as dot mesh and it is just fine again. 10:05.000 --> 10:11.840 Uh, a new thing about fluent mesh is regardless of whether it is 2D or 3D, the command to import it 10:11.840 --> 10:13.490 is fluent mesh to form only. 10:13.490 --> 10:19.640 So if you are running fluent 3D mesh to form for some mesh, even if it is from workbench mesh and if 10:19.640 --> 10:22.550 it is not working, just do fluent mesh to form. 10:22.670 --> 10:23.960 Just give a try. 10:23.960 --> 10:25.040 And mostly it would work. 10:25.040 --> 10:27.020 Either of the command would definitely work. 10:27.800 --> 10:36.650 So now in the second tutorial we are going to see how to import fluent generated mesh. 10:36.650 --> 10:40.260 So this is dot mesh which is generated by fluent. 10:40.260 --> 10:45.240 And we, uh, have to see whether it is compatible in open form or not. 10:46.050 --> 10:50.280 To do that, you can just open the mesh file using VS code. 10:50.370 --> 10:55.680 And if it makes some sense then it is a good file. 10:55.680 --> 10:58.290 It is open, form readable and it can be converted. 10:58.290 --> 11:04.410 But if you open it and it is just gibberish and if it doesn't make any sense at all, if there are no 11:04.410 --> 11:11.520 characters, only boxes or X marks, then it is in binary, then Openfoam can't understand it. 11:11.520 --> 11:15.090 So you shouldn't export in binary. 11:15.090 --> 11:18.120 Just make sure if you are getting the mesh file from someone else. 11:18.120 --> 11:23.580 If it is a consultancy work and someone is giving the mesh, then you have to ensure before even trying. 11:23.670 --> 11:27.270 Otherwise, it's just waste of time for you to check whether it is working or not. 11:27.600 --> 11:29.460 Just open it should make sense. 11:30.480 --> 11:33.480 Okay, now we will import this. 11:36.870 --> 11:37.140 Okay. 11:37.140 --> 11:39.840 Now I will do low end. 11:43.140 --> 11:44.430 Mesh to form. 11:44.700 --> 11:47.610 And the file name. 11:48.330 --> 11:49.890 Now it has converted. 11:50.070 --> 11:52.540 We can view it using Paraview. 11:57.430 --> 12:03.520 Now, as you can see, we have inlet outlet and walls which we designed, which we gave in the design 12:03.520 --> 12:06.490 modeler and not in fluent machine. 12:07.120 --> 12:09.100 Fluent machine was used just for machine. 12:09.280 --> 12:13.930 But we still have it here from the design modeler assigned names. 12:15.100 --> 12:17.770 Okay, so this is a nice thing. 12:19.840 --> 12:20.980 This is the mesh. 12:20.980 --> 12:22.120 This is a poor mesh. 12:22.120 --> 12:24.160 But for demonstration this is fine. 12:25.090 --> 12:25.390 Okay. 12:25.390 --> 12:28.060 Now we will see the vortex shedding case. 12:28.060 --> 12:34.060 How to set up a vortex shedding case from the mesh which got imported from the workbench mesh the same 12:34.060 --> 12:36.220 as the one which we use for the first tutorial. 12:37.360 --> 12:40.390 Okay, now we are going to use this model. 12:40.390 --> 12:44.110 We already saw K-epsilon and K-omega SST. 12:44.140 --> 12:49.840 So this tutorial will be about Spalart-allmaras, which is the third most popular, uh, turbulence 12:49.840 --> 12:54.460 model and most probably the most commonly used one for external aerodynamics. 12:55.300 --> 13:00.340 Uh, so we will be using one equation model instead of two equation model in Spalart-allmaras. 13:00.340 --> 13:01.360 That is the advantage. 13:01.480 --> 13:07.190 We are going to use a 2D flow or cylinder mesh to make a transient case in a simple form with Spalart-allmaras 13:07.190 --> 13:08.090 turbulence model. 13:08.990 --> 13:15.650 So this is what we are, uh, trying to expect out of this simulation of vortex shedding animation since 13:15.650 --> 13:16.520 it is transient. 13:17.810 --> 13:18.050 Okay. 13:18.050 --> 13:21.440 So I will go to the vortex shedding case. 13:21.470 --> 13:22.070 Okay. 13:22.070 --> 13:26.450 Now I'll just close this. 13:29.420 --> 13:32.900 Enter the folder. 13:33.050 --> 13:36.650 We have zero constant, the mesh file and system. 13:36.650 --> 13:45.560 So I can import the fluent mesh to form for flow over a cylinder dot mesh. 13:46.430 --> 13:48.770 It got converted okay. 13:49.250 --> 13:50.930 Now I'll go to system. 13:51.530 --> 14:00.090 As you can see I have the decomposed verdict right now, and I have set it to my processor capabilities. 14:00.240 --> 14:07.590 So I will decompose power and it will decompose the mesh we just imported. 14:07.590 --> 14:13.650 Because it is in poly mesh, it doesn't know it is from as fluent or Salome or mesh or block generator. 14:13.650 --> 14:16.830 It just knows that it is in the mesh is in poly mesh folder. 14:17.610 --> 14:21.300 Okay, now we have to copy and paste the zero dot original file. 14:21.330 --> 14:25.590 I generally like to do it from the terminal itself. 14:28.230 --> 14:31.260 Okay, now we also have the zero folder. 14:31.500 --> 14:34.980 I'll go here and show you what this palette model is all about. 14:35.340 --> 14:39.360 In constant we have G five which is gravity. 14:40.440 --> 14:48.060 We have set the gravity to negative direction of y axis in the value of 9.81m/s². 14:48.210 --> 14:49.350 This is a unit. 14:49.650 --> 14:56.160 So I will go to transport properties and we are using air as the fluid one into ten power minus five. 14:56.550 --> 15:01.170 And in the turbulence properties we are using Spalart-allmaras model. 15:01.290 --> 15:03.060 So that is the change here. 15:03.060 --> 15:04.380 It is also a race type. 15:04.380 --> 15:06.490 So we are using Spalart-allmaras. 15:07.690 --> 15:08.920 We will look at the zero file. 15:09.130 --> 15:19.270 So in the velocity file we have inlet outlet cylinder upper and lower walls and front and back patches. 15:19.570 --> 15:22.180 Uh inlet velocity is ten meters per second. 15:22.180 --> 15:24.460 The outlet is set to gradient zero. 15:24.460 --> 15:24.940 Gradient. 15:24.940 --> 15:27.340 The cylinder will have no slip because it is a wall. 15:27.340 --> 15:31.480 And we don't want the upper and lower wall to have any effect on the flow. 15:31.480 --> 15:37.300 So we are setting it to slip, which means it is a wall, but it will act as slip. 15:37.300 --> 15:40.900 Then front and back planes will be empty because this is a 2D case. 15:41.500 --> 15:46.840 Now we can see the pressure file since we defined the inlet for velocity. 15:46.870 --> 15:50.830 We don't have to define for pressure, so we have zero gradient in inlet. 15:50.830 --> 15:56.560 And outlet is set to a fixed value of zero Newton per meter squared. 15:56.920 --> 16:00.100 It is an AC unit, so the cylinder will be zero gradient. 16:00.100 --> 16:04.120 Upper and lower wall will be zero gradient, which means the solver will calculate it for us. 16:04.120 --> 16:06.580 Front and back planes are obviously empty. 16:07.150 --> 16:17.440 Then we have our turbulent kinematic viscosity, which is uh, set to calculated and set to zero as 16:17.440 --> 16:18.160 initial values. 16:18.160 --> 16:20.030 So this is what we generally for. 16:20.030 --> 16:25.910 Follow new t k wall function for all the walls and all the patches will be set to calculated with a 16:25.910 --> 16:26.630 value of zero. 16:26.630 --> 16:28.010 Front and back will be empty. 16:28.940 --> 16:34.520 And finally the main file of this turbulence model which is new tilde. 16:35.060 --> 16:40.610 If you want to understand what new tilde is and how this one equation model for parallel turbulence 16:40.610 --> 16:44.460 works, there is a beautiful documentation from Openfoam. 16:44.460 --> 16:49.860 Also there is a beautiful video from YouTube, the channel Fluid Mechanics 101. 16:50.040 --> 16:51.060 You can check. 16:51.060 --> 16:53.100 It is beautifully explained. 16:53.820 --> 17:00.660 Uh, so the inlet is set the value of zero outlet cylinder, upper and lower wall. 17:00.660 --> 17:03.930 Everything is zero gradient and front and back planes are empty. 17:05.070 --> 17:08.310 Okay, now we are going to run the simulation. 17:08.310 --> 17:08.610 Okay. 17:08.610 --> 17:10.440 I actually made a mistake. 17:10.440 --> 17:14.730 I changed the name of zero dot original to zero after decomposing. 17:14.730 --> 17:16.290 So it was throwing an error. 17:16.290 --> 17:25.020 So I deleted all the processor files, and then I decomposed it again so that it would copy zero perfectly. 17:25.290 --> 17:30.870 And now we can run the simulation using Mpirun NP eight. 17:33.630 --> 17:41.460 Simple for parallel, hit enter and it will start doing the calculation. 17:41.460 --> 17:43.890 So let's just wait for it to end. 17:45.720 --> 17:47.910 Okay, now the simulation is over. 17:47.910 --> 17:52.080 As you can see, the maximum current number was set to one, so it is around one. 17:52.410 --> 17:59.460 And delta t also varied a bit to adjust for the time and it took definitely a long time. 17:59.490 --> 18:02.190 A full five minutes to run this. 18:02.490 --> 18:05.280 Okay, now we can reconstruct this. 18:05.640 --> 18:09.000 I'll search for the command which I use. 18:09.660 --> 18:11.100 I don't want to type it fully. 18:12.420 --> 18:17.430 Okay, I'll hit enter to reconstruct all the time steps. 18:29.170 --> 18:31.780 So this definitely is going to take a lot of time. 18:31.780 --> 18:33.400 I'll get back to you once it is over. 18:34.870 --> 18:42.010 So I thought while it is still running, I will tell you how to view the results while it is still, 18:42.400 --> 18:44.770 uh, reconstructing. 18:46.810 --> 18:51.460 I mean, it is still in the process of 027, right? 18:51.460 --> 18:53.800 So we can view it as decompose decays. 18:54.580 --> 18:58.780 So I'm just going to open instead of reconstructing it completely because it's going to take a lot of 18:58.780 --> 18:59.230 time. 18:59.800 --> 19:01.780 I'm going to choose decompose case. 19:01.780 --> 19:06.910 Click on apply and we can choose velocity. 19:07.210 --> 19:09.010 And I'll play it. 19:09.340 --> 19:14.500 So as you can see, we are getting the flow slowly developed. 19:17.740 --> 19:20.440 And it is starting to separate. 19:25.270 --> 19:27.430 Now we are getting the vortex shedding. 19:27.940 --> 19:35.540 If you are very well versed with CFD and you set up a lot of flow or cylinder case for vortex shedding. 19:35.540 --> 19:39.200 You will know this is not how the pattern actually works. 19:39.440 --> 19:46.070 I mean, these area if you look at these euro gradient of the outlet, this is not how usually you would 19:46.070 --> 19:46.940 expect it. 19:46.940 --> 19:53.420 Also the domain would be so long than this, not just this length, it would be much longer. 19:53.450 --> 19:59.480 I didn't want to make the number of cells high because it would cause the simulation to take a lot of 19:59.480 --> 20:03.170 time to end, so I kept the number of cells low. 20:03.170 --> 20:09.140 But now you understood how to set up a separate case and perform a vortex shedding using the mesh generated 20:09.140 --> 20:11.720 by Ansys workbench. 20:12.560 --> 20:15.950 So this is the animation which we have got. 20:15.950 --> 20:20.210 If you want you can go on and save it as an animation if you want. 20:20.210 --> 20:22.220 You can also see the new tilde. 20:22.220 --> 20:25.740 It is going to be completely zero throughout the case. 20:25.740 --> 20:34.500 And same for new T and obviously pressure is going to change so you get the point of doing this. 20:35.160 --> 20:41.040 But if you are really into flow or cylinders have seen a lot of tutorials, you would also notice that 20:41.040 --> 20:43.230 the vortex wouldn't look much like this. 20:43.230 --> 20:44.760 It is a bit weird. 20:44.940 --> 20:47.070 That is what Spalart-allmaras does. 20:47.190 --> 20:57.480 So it, uh, makes both the equations k epsilon and k omega and makes it into one equation by dividing 20:57.480 --> 20:58.830 those two parameters. 20:59.130 --> 21:02.400 So it is a bit of approximation. 21:02.400 --> 21:06.090 That's why we are getting uh values here and there. 21:06.180 --> 21:08.250 But it is usually good. 21:08.250 --> 21:15.330 So if you just want to do a simple case on, uh, vertex shading or external aerodynamics, then spalart-allmaras 21:15.360 --> 21:15.960 is fine. 21:16.470 --> 21:23.730 But if you are working with a deep aerodynamic case, then K Omega SSD might be the best choice, especially 21:23.730 --> 21:29.430 when if you are working with inflation layers, boundary layers want to calculate y plus and R like 21:29.430 --> 21:32.250 in this case I have added some inflation layers. 21:32.250 --> 21:37.120 So in those cases k omega SSD might be the best choice in my opinion. 21:38.380 --> 21:42.460 As you can see, it is still reconstructing is going to take a lot of time. 21:42.460 --> 21:50.890 So you can try to reconstruct it, give it some time and uh, maybe practice by running a reconstructed 21:50.890 --> 21:51.400 case. 21:51.400 --> 21:58.870 But I am ending this tutorial here, so if you have any questions, please, please feel free to contact 21:58.870 --> 21:59.380 me. 21:59.950 --> 22:01.270 See you in the next class.