# Volume Output
Volume Output in Flow360 allows you to visualize flow field variables throughout the entire computational domain. This is essential for understanding 3D flow structures, vortex development, shockwaves, and other volumetric flow features.
# 📋 Available Options
Option | Description | Unit |
---|---|---|
Name | A descriptive name for the output | |
Output Format | Format for saving volume data | |
Output Fields | Flow variables to include in the output | |
Frequency | How often to save outputs | time steps |
Frequency Offset | Time step at which to start the output animation | time steps |
# 🔍 Detailed Descriptions
# Name
A descriptive identifier for this volume output.
- Default:
Volume output
- Example:
Main Flow Volume
- Notes: Choose a name that helps identify the purpose of this output.
# Output Format
The file format used to save the volume output data.
- Default:
paraview
- Example:
both
- Notes: Options include "paraview", "tecplot", or "both".
# Output Fields
Select the flow variables to include in the volume output.
- Default: None selected
- Example:
Mach, pressure, qcriterion
- Notes: See detailed field descriptions below. Only select fields you need to analyze to keep file sizes manageable.
# Frequency
How often to save outputs, in number of physical time steps.
- Default:
-1
(only at the end of simulation) - Example:
100
- Notes: Higher frequencies provide better temporal resolution but increase storage requirements.
# Frequency Offset
The time step at which to start the output animation.
- Default:
0
(beginning of simulation) - Example:
1000
- Notes: Useful when you want to skip initial transient flow development.
Note: For time-averaged volume output settings, see the Time-Averaged Volume Output documentation.
# 📊 Available Output Fields
# Universal Variables (non-dimensional)
Cp
- Coefficient of pressureCpt
- Coefficient of total pressuregradW
- Gradient of primitive solutionkOmega
- k and omegaMach
- Mach numbermut
- Turbulent viscositymutRatio
- Turbulent viscosity and freestream dynamic viscosity rationuHat
- Spalart-Almaras variableprimitiveVars
- Density, velocities (u,v,w), and pressureqcriterion
- Q criterion for vortex identificationresidualNavierStokes
- N-S residualresidualTransition
- Transition residualresidualTurbulence
- Turbulence residuals
- EntropysolutionNavierStokes
- N-S solutionsolutionTransition
- Transition solutionsolutionTurbulence
- Turbulence solutionT
- Temperaturevelocity
- Velocity vectorvelocity_x
- X-component of velocityvelocity_y
- Y-component of velocityvelocity_z
- Z-component of velocityvelocity_magnitude
- Magnitude of velocity vectorpressure
- Pressurevorticity
- VorticityvorticityMagnitude
- Vorticity MagnitudewallDistance
- Wall distancenumericalDissipationFactor
- NumericalDissipationFactor sensorresidualHeatSolver
- Heat equation residualVelocityRelative
- Velocity with respect to non-inertial framelowMachPreconditionerSensor
- Low-Mach preconditioner factor
# Dimensioned Variables
velocity_m_per_s
- Velocity vector (in m/s)velocity_x_m_per_s
- X-component of velocity (in m/s)velocity_y_m_per_s
- Y-component of velocity (in m/s)velocity_z_m_per_s
- Z-component of velocity (in m/s)velocity_magnitude_m_per_s
- Magnitude of velocity vector (in m/s)pressure_pa
- Pressure (in Pa)
# Volume-Specific Variables (non-dimensional)
betMetrics
- BET MetricsbetMetricsPerDisk
- BET Metrics per DisklinearResidualNavierStokes
- Linear residual of Navier-Stokes solverlinearResidualTurbulence
- Linear residual of turbulence solverlinearResidualTransition
- Linear residual of transition solverSpalartAllmaras_hybridModel
- Hybrid RANS-LES output for Spalart-Allmaras solverkOmegaSST_hybridModel
- Hybrid RANS-LES output for kOmegaSST solverlocalCFL
- Local CFL number
💡 Tips
# Q-Criterion
The qcriterion
field is extremely valuable for visualizing vortices in the flow field. To effectively use this field:
- Create isosurfaces of Q-criterion to identify vortical structures
- The default isosurface value is calculated as
RefMach² / (all walls' bounding box length)²
- For aircraft simulations: a good starting value is approximately
Mach² / WingSpan²
- For rotor flows: try
TipMach² / RotorDiameter²
- Smaller values show more vortical structures but may clutter visualization
- Larger values show only the strongest vortices
Note: Q-criterion can also be directly exported as an isosurface with a specific iso value using the Isosurface Output feature, which provides better control over the visualization.
# BET Visualization
When using Blade Element Theory (BET) models for propellers or rotors, the betMetrics
field provides valuable data for analyzing:
- Blade loading distributions
- Induced velocities
- Local angle of attack
- Flow conditions at each blade element
These metrics are essential for understanding propeller and rotor performance characteristics.
# ❓ Performance Considerations
Volume outputs can generate very large files, especially for fine meshes. Consider the following to manage file sizes:
- Limit the frequency of volume outputs
- Be selective about which fields to include
- Use time-averaged volume outputs for statistical analysis of unsteady flows
- Consider using slices or isosurfaces instead for targeted analysis
❓ Frequently Asked Questions
How large are volume output files typically?
File sizes depend on mesh size, selected output fields, and output format. For a mesh with several million cells:
- Each field adds approximately 4-8 bytes per cell
- A full domain output with 5 fields might be 1-5GB per time step for 100M mesh
- Consider using time-averaged outputs or selective fields to reduce storage requirements
What's the difference between ParaView and Tecplot formats?
- ParaView format (.vtu): Open-source visualization tool with excellent performance for large datasets. Provides a wide range of visualization and analysis capabilities.
- Tecplot format (.szplt): Commercial visualization software with specialized aerodynamic analysis tools. May provide more streamlined workflows for certain aerospace applications.
- Choose "both" if you're unsure which tool you'll need or if different team members use different tools.
How do I choose the right frequency for volume outputs?
Consider these factors:
- For steady-state simulations: Set to
-1
(final solution only) or use a high number (e.g., every 1000 steps) - For unsteady simulations: Ensure you capture the relevant time scales (e.g., for vortex shedding, ensure at least 20-30 snapshots per shedding cycle)
- Storage constraints: Higher frequencies generate more data
- A good starting point for unsteady flows is 50-100 time steps between outputs
- For steady-state simulations: Set to
Why are my volume outputs missing data in certain regions?
Missing data in volume outputs typically occurs for these reasons:
- For parallel simulations, check that all partitions are being correctly combined
- Ensure the simulation has valid data in those regions (check convergence)
- For moving mesh simulations, ensure mesh movement is properly configured
How can I visualize specific flow features effectively?
For different flow features:
- Vortices: Use Q-criterion (isosurfaces) with values around
Mach²/Length²
- Shock waves: Density gradient or Mach number gradients work well
- Boundary layers: Use slices with velocity profiles near walls
- Wake structures: Combine Q-criterion with velocity magnitude contours
- Vortices: Use Q-criterion (isosurfaces) with values around
Can I add custom output fields to volume output?
Currently, Flow360 supports only the predefined output fields listed in this documentation. If you need additional derived quantities:
- Export the primitive variables and calculate derived quantities in your visualization tool
- Use Python post-processing with the Flow360 API to create custom fields
- Contact support if you need a specific field that might benefit other users
🐍 Python Example Usage
# Example of configuring volume output using Flow360 Python API
import flow360 as fl
# Define volume output settings
volume_output = fl.VolumeOutput(
name="Main Flow Volume",
output_format="paraview",
output_fields=["Mach", "pressure", "qcriterion", "velocity"],
frequency=100, # Save every 100 time steps
frequency_offset=1000, # Start at time step 1000
)
# Add volume output to simulation parameters
simulation_params = fl.SimulationParams(
# ... other simulation parameters ...
outputs=[volume_output]
)