-
Configuration File
Mesh File
Restart File
Solver Setup
Physical Definition
Markers and Boundary Conditions
Convective Schemes
Slope Limiters and Shock Resolution
History and Solution Output
Linear Solvers and Preconditioners
Basics of Multi-Zone Computations
Execution
Aeroacoustic analysis of unsteady pressure
Flamelet Solver — Python Wrapper Wall Boundary Conditions
Output Fields Reference
Error Messages
-
Setup Guide: Steady RANS for External Aerodynamics
Setup Guide: Incompressible Flows
Setup Guide: Unsteady Flows and DES
Setup Guide: Laminar-Turbulent Transition
Setup Guide: Turbomachinery
Setup Guide: Heat Transfer and Conjugate Heat Transfer
Setup Guide: Species Transport and Combustion
Setup Guide: Shape Optimization with the Discrete Adjoint
Setup Guide: Non-Ideal Compressible Flows
-
Option Reference
Problem Definition
FluidModel
Data-driven fluid model parameters
Freestream Conditions
Reference Conditions
Boundary Markers
Time-marching
Linear solver definition
Convergence
Multi-grid
Spatial Discretization
Adjoint and Gradient
Sobolev Gradient Solver Parameters
Input/output files and formats
Dynamic mesh definition
Aeroelastic Simulation (Typical Section Model)
Wind Gust
Equivalent Area
Grid deformation
Deformable mesh
FEM flow solver definition
FEA solver
Multizone definition
Radiation solver
Heat solver
Visualize Control Volumes
Inverse design problem
Unsupported options
FFD point inversion
Automatic Differentation options
Python Options
Hybrid_RANSLES Options
Output Options
libROM options
Renamed and Removed Options
-
GIT-ting Started
Developing SU2 on GitHub (Internal Developers)
Running Regression Tests
Code Review
Code Structure
Style Guide
Advanced AD Techniques
Containers for Development
Writing Unit Tests
Integrating Tracy Profiler with SU2
Automatic Differentiation (AD)
Code Reference (Doxygen)
Debugging SU2
Documentation Improvements and Status
Glossary
Docs Check
SU2 on Windows
SU2 supports Windows platforms from Windows 7 and Windows 10 for x86 (64-bit). You have the option between a serial version and a parallel version. For the latter it is required that you install Microsoft MPI (the SDK is not required).
Installation
Download and unpack the archive
Download the .zip for your operating system and unzip it where you want it to be installed.
Add SU2 environment variables
This is done through the Environment Variables control panel. You can access these by typing “environ” in the search/run box of the start menu. Start a New System variable. Assign the Variable Name SU2_RUN, and assign the Variable Value to be the path to your SU2 Executables (the folder that contains SU2_CFD.exe for example). This variable will allow you to quickly navigate to the SU2 directory using cd %SU2_RUN%, and run the executables using %SU2_RUN%\<executable>.
Note: if the directory name contains white space, the executables may not work without appending “.exe”, and the python scripts may not work. Additionally, when setting the enviornment variables and paths, quotes must be added, for example: C:\Program Files\"Stanford ADL"\SU2\
Add SU2 to the system path
Access the system variables by typing “environ” in the search/run box of the start menu, select “edit the system environment variables”, and then select “Environment Variables” from the System Properties menu. Edit the “Path” system variable (or select “New” if no “Path” system variable exists) and add the path to the SU2 executables. When there is more than one directory listed in “Path” they must be separated by semicolons. This will allow you to use the executables from any directory without explicitly specifying the path to the executable.
Optional: Install Microsoft MPI to enable parallel mode
As the well-known, freely-available, open-source implementations of MPI listed in the Install section may not support Windows, you may want to install Microsoft MPI.
Running SU2 in Windows
Running SU2 in Windows is identical to running in Linux or Mac OS environments and is run from the command line (whether cmd.exe or the freely-available Console2 for Windows). If your executable path contains white space you may need to add “.exe”. Note, however, that you may need to use mpiexec instead of mpirun.