Using a specified discrete velocity profile as a inflow boundary condition
Dear all, I'm now trying to define a inflow boundary condition using a specified discrete velocity profile when simulating with the IncNavierStokesSolver. Specially, the inflow velocity profile I use here is a Blasius profile. Since it is numerically solved by an external code, the profile here is in discrete form (i.e. velocity on discrete points). While from the user guide, I can see that a profile with an explicit expression can be directly implemented as a boundary condition in the .xml file, it seems that there is few examples on how to deal with a specified discrete velocity profile. I wonder if there is any way to implement this kind of boundary condition in Nektar++? P.S.: To solve this problem, I wonder if the module "interppointdatatofld" of FieldConvert should be used? If so, how to use it for the boundary? Besides, I think here a ".bc" file which is mentioned in 3.3.5.5 Boundary conditions from file in user guide might be needed, but I don't know how to construct this kind of files? Thanks in advance for the help. Best Regards, Mona
Hi Mona, The way that worked for me was to: 1. Extract the boundary from the mesh .xml file using the NekMesh extract module, remember to request the boundary information to be given with /detectbnd/. (You can do NekMesh -p proc:extract to see the options). 2. I did not use the /interppointdatatofld/ (I was using a solution from another simulation) but you could probably use it to produce an "inflow.fld" file using the mesh extracted in the first step. 3. Rename the "inflow.fld" to "inflow.*bc*" and use it as a boundary condition just as the manual states. Best, SG // On 27.11.2017 09:46, 李 依然 wrote:
Dear all,
I'm now trying to define a inflow boundary condition using a specified discrete velocity profile when simulating with the IncNavierStokesSolver. Specially, the inflow velocity profile I use here is a Blasius profile. Since it is numerically solved by an external code, the profile here is in discrete form (i.e. velocity on discrete points).
While from the user guide, I can see that a profile with an explicit expression can be directly implemented as a boundary condition in the .xml file, it seems that there is few examples on how to deal with a specified discrete velocity profile. I wonder if there is any way to implement this kind of boundary condition in Nektar++?
P.S.:
To solve this problem, I wonder if the module "/interppointdatatofld/" of /FieldConvert /should be used? If so, how to use it for the boundary?
Besides, I think here a ".bc" file which is mentioned in /3.3.5.5 Boundary conditions from file /in user guide might be needed, but I don't know how to construct this kind of files?
Thanks in advance for the help.
Best Regards,
Mona
_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users
Hi Both, This seems a sensible way forward to me. Hopefully this worked for you Mona. Best regards, Spencer. On 27 Nov 2017, at 11:17, Stanisław Gepner <sgepner@meil.pw.edu.pl<mailto:sgepner@meil.pw.edu.pl>> wrote: Hi Mona, The way that worked for me was to: 1. Extract the boundary from the mesh .xml file using the NekMesh extract module, remember to request the boundary information to be given with detectbnd. (You can do NekMesh -p proc:extract to see the options). 2. I did not use the interppointdatatofld (I was using a solution from another simulation) but you could probably use it to produce an "inflow.fld" file using the mesh extracted in the first step. 3. Rename the "inflow.fld" to "inflow.bc" and use it as a boundary condition just as the manual states. Best, SG On 27.11.2017 09:46, 李 依然 wrote: Dear all, I'm now trying to define a inflow boundary condition using a specified discrete velocity profile when simulating with the IncNavierStokesSolver. Specially, the inflow velocity profile I use here is a Blasius profile. Since it is numerically solved by an external code, the profile here is in discrete form (i.e. velocity on discrete points). While from the user guide, I can see that a profile with an explicit expression can be directly implemented as a boundary condition in the .xml file, it seems that there is few examples on how to deal with a specified discrete velocity profile. I wonder if there is any way to implement this kind of boundary condition in Nektar++? P.S.: To solve this problem, I wonder if the module "interppointdatatofld" of FieldConvert should be used? If so, how to use it for the boundary? Besides, I think here a ".bc" file which is mentioned in 3.3.5.5 Boundary conditions from file in user guide might be needed, but I don't know how to construct this kind of files? Thanks in advance for the help. Best Regards, Mona _______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk<mailto:Nektar-users@imperial.ac.uk> https://mailman.ic.ac.uk/mailman/listinfo/nektar-users _______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk<mailto:Nektar-users@imperial.ac.uk> https://mailman.ic.ac.uk/mailman/listinfo/nektar-users Spencer Sherwin FREng, FRAeS Head, Aerodynamics, Professor of Computational Fluid Mechanics, Department of Aeronautics, Imperial College London South Kensington Campus, London, SW7 2AZ, UK s.sherwin@imperial.ac.uk<mailto:s.sherwin@imperial.ac.uk> +44 (0)20 7594 5052 http://www.imperial.ac.uk/people/s.sherwin/
participants (3)
-
Sherwin, Spencer J
-
Stanisław Gepner
-
李 依然