|
[Sponsors] |
getting cutplanes of a custom vector field (vorticity in my case) |
![]() |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
![]() |
![]() |
#1 |
New Member
Jacques
Join Date: Jul 2019
Posts: 17
Rep Power: 7 ![]() |
Starting with openfoam, and I am amazed at how it works, but having some trouble to get "simple" things done
![]() Here is my issue : I have quite big and uneasy to process data (in paraview at least, it's.... bad) and would like to do some pre-postprocessing with openfoam functions. I managed to get vorticity fields in all my output directories with a rhoPimpleFoam -postprocess -func vorticity. I also managed to practice with a custom function and vorticity type/library (need to get used to the vocabulary) I also managed to make some cut planes of the native variables, like U, p. What I could'nt manage was : getting cutplanes or even probes of either the vorticity filed I created (and is in all my output directories), or probes of some simple calculated fields like mag(U) or curl(U) or mag(vorticity). I probably don't understand how i works but i would appreciate some help ![]() For example : Code:
/*--------------------------------*- C++ -*----------------------------------*\ ========= | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox \\ / O peration | Version: v2212 \\ / A nd | Website: www.openfoam.com \\/ M anipulation | ------------------------------------------------------------------------------- Description Writes out surface files with interpolated field data in VTK format, e.g. cutting planes, iso-surfaces and patch boundary surfaces. This file includes a selection of example surfaces, each of which the user should configure and/or remove. \*---------------------------------------------------------------------------*/ #includeEtc "caseDicts/postProcessing/visualization/surfaces.cfg" fields (U p curl(U) vorticity); surfaces ( xNormal { $cuttingPlane; pointAndNormalDict { basepoint (-0.0146432 -0.0169135 0.20984) normalVector $x; // Overrides default normalVector (1 0 0) } // $y: macro for (0 1 0) } ); // ************************************************************************* // Code:
Cannot find registered field matching 1(curl(U)) Code:
Cannot find registered field matching 1(vorticity) I also tried : Code:
V1 { // Mandatory entries type vorticity; libs (fieldFunctionObjects); field U; } magV { // Mandatory entries type mag; libs (fieldFunctionObjects); field V!; } but again I probably am thinking in the wrong direction... So how does it work ? How do i combine several functions/postprocess to create new fields/make probes or surfaces ? |
|
![]() |
![]() |
![]() |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Changing the grid on the same set-up | Katya | FLUENT | 7 | October 8, 2009 17:31 |
Free surface boudary conditions with SOLA-VOF | Fan | Main CFD Forum | 10 | September 9, 2006 13:24 |
transform navier-stokes eq. to euler-eq. | pxyz | Main CFD Forum | 37 | July 7, 2006 09:42 |
Turbulent Flat Plate Validation Case | Jonas Larsson | Main CFD Forum | 0 | April 2, 2004 11:25 |
Body force - Does it work? | Jan Rusås | CFX | 5 | August 27, 2002 10:50 |