Keywords:
hydrodynamics, Kelvin-Helmholtz Instability
This problem demonstrates the Kelvin-Helmholtz instability for the case of a velocity difference across the interface between two different fluids that differ in density by a factor 2. A finite-width shear layer is used to ensure results converge at finite resolution. For the two-dimensional version of the problem setup considered here, we use a domain
\((-PAR_{LENGTH}/2,-PERP_{LENGTH}/2) \times (PAR_{LENGTH}/2,PERP_{LENGTH}/2)\)
with periodic boundary conditions in the PAR direction and reflecting wall boundary conditions in the PERP direction. For the three-dimensional version of the problem setup considered here, we use a domain
\((-PAR_{LENGTH}/2,-PERP_{LENGTH}/2,-PAR_{LENGTH}/2) \times (PAR_{LENGTH}/2,PERP_{LENGTH}/2,PAR_{LENGTH}/2)\)
with periodic boundary conditions in the PAR directions and reflecting wall boundary conditions in the PERP direction. A single mode perturbation is used to seed the instability.
This simulation can be performed with a USimBase license.
The Kelvin-Helmholtz Instability example is accessed from within USimComposer by the following actions:
The basic example variables are editable in the Editor pane of the Setup window as shown below. After any change is made, the Save and Process Setup button must be pressed again before a new run may commence.
The input file allows the user to set a variety of problem parameters related to the physics, initial conditions, domain and solver used for the Kelvin-Helmholtz instability.
The following parameters control the physics of the Kelvin-Helmholtz instability:
The following parameters control the shear layer that drives Kelvin-Helmholtz instability and the perturbation used to seed the Kelvin-Helmholtz instability:
The following parameters control the dimensionality, domain size and resolution of the simulation:
The following parameters the length of the simulation and data output:
The following parameters control the USim solvers used to evolve the Kelvin-Helmholtz instability:
After performing the above actions, continue as follows:
You will also see the engine log output in the Logs and Output Files pane. The run has completed when you see the output, “Engine completed successfully.”
After performing the above actions, continue as follows: