|
[Sponsors] | |||||
Dimensional forces in history/screen and forces breakdown file |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|
|
#1 |
|
New Member
Tomas Perez Zapico
Join Date: Mar 2023
Posts: 17
Rep Power: 4 ![]() |
Hello,
I was wondering if it's possible to obtain the dimensional value of the forces directly in the screen/history output and in the forces breakdown file without having to multiply it by the reference factor given. Does anyone know how to do it? Thank you |
|
|
|
|
|
|
|
|
#2 |
|
Senior Member
bigfoot
Join Date: Dec 2011
Location: Netherlands
Posts: 818
Rep Power: 22 ![]() |
Probably with custom outputs:
Code:
% User defined expressions of solver variables and other history outputs.
% The syntax to define a custom output is 'name : type{expression}[markers]'.
% NOTE: To obtain the list of available solver variables write an invalid
% expression (e.g. 'x : AreaAvg{INVALID}[]') and run SU2.
% Different outputs need to be separated by ";". The available types are:
% - Macro: Introduces a new field that can only be used in other expressions,
% it is not an output by itself (note the "$" symbol to reference macros).
% - Function: Introduces a new scalar output that is a function of other scalar
% outputs, it cannot reference fields (e.g. velocity).
% - AreaAvg and AreaInt: Computes an area average or integral of a field (the
% expression) over the list of markers.
% - MassFlowAvg and MassFlowInt: Computes a mass flow average or integral.
% - Probe: Evaluates the expression using the values of the mesh point closest
% to the coordinates specified inside "[]", [x, y] or [x, y, z] (2 or 3D).
% NOTE: Each custom output can only use one type, e.g. it is not possible to
% write 'p_drop : AreaAvg{PRESSURE}[inlet] - AreaAvg{PRESSURE}[outlet]'. This
% would need to be separated into two AreaAvg outputs and one Function to
% compute their difference.
CUSTOM_OUTPUTS= 'velocity : Macro{sqrt(pow(VELOCITY_X, 2) + pow(VELOCITY_Y, 2) + pow(VELOCITY_Z, 2))};\
avg_vel : AreaAvg{$velocity}[z_minus, z_plus];\
var_vel : AreaAvg{pow($velocity - avg_vel, 2)}[z_minus, z_plus];\
dev_vel : Function{sqrt(var_vel) / avg_vel};\
probe1 : Probe{$velocity}[0.005, 0.005, 0.05]'
%
% "COMBO" is the name and group of the output for the objective function
% (regardless of definition). "CUSTOM" is the group for all custom outputs.
SCREEN_OUTPUT= INNER_ITER, RMS_DENSITY, RMS_ENERGY, LINSOL_RESIDUAL, FORCE_Z,\
SURFACE_MASSFLOW, SURFACE_TOTAL_TEMPERATURE, avg_vel, dev_vel, probe1, COMBO
HISTORY_OUTPUT = ITER, AERO_COEFF, FLOW_COEFF, FLOW_COEFF_SURF, CUSTOM, COMBO
|
|
|
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [openSmoke] LaminarSMOKE compilation error | mdhfiz | OpenFOAM Community Contributions | 8 | July 2, 2024 11:32 |
| [Other] Tabulated thermophysicalProperties library | chriss85 | OpenFOAM Community Contributions | 62 | October 2, 2022 04:50 |
| SU2 v7: Forces breakdown file? | CSMDakota | SU2 | 2 | December 10, 2019 09:58 |
| OpenFOAM 1.6.x - CentOS 5.3 x86_64 | linnemann | OpenFOAM Installation | 68 | April 22, 2013 12:03 |
| friction forces icoFoam | ofslcm | OpenFOAM | 3 | April 7, 2012 11:57 |