|
[Sponsors] |
April 13, 2018, 06:28 |
coordination Transform -functional object
|
#1 |
Member
Chris Schäfer
Join Date: Apr 2017
Posts: 34
Rep Power: 9 |
Hello,
I tried to change the coordination system from (of course )cartesian to cylindrical via functional object. I added in the controldict: functions { coordinateSystems { type fieldCoordinateSystemTransform; functionObjectLibs ("libmeshTools.so"); log yes; coordinateRotation cylindrical; origin (0 0 0); writeControl timeStep; writeInterval 1; mode magnitude; fields ( U ); } unfortunately without success. Error: --> FOAM FATAL ERROR: Attempt to return primitive entry ITstream : ...controlDict.functions.coordinateSystems.coordin ateRotation, line 70, IOstream: Version 2.0, format ASCII, line 0, OPENED, GOOD primitiveEntry 'coordinateRotation' comprises on line 70 the word 'cylindrical' Obviously my entry "cylindrical" is wrong but I have no idea how to serve the keyword coordinateRotation and specify cylindricalcoordinates Any idea? |
|
August 17, 2021, 12:47 |
|
#2 |
New Member
Join Date: Nov 2020
Posts: 5
Rep Power: 5 |
Do you have any suggestion how to use the function object?
I am trying to perform a transformation from Cartesian coordinates to cylindrical coordinates, where the y-coordinate is the axial component along the domain. Code:
coordinateSystem { type cylindrical; origin (0 1 0); rotation { type cylindrical; axis (0 1 0); } } The function object fieldCoordinateSystemTransform produces an output. However, checking the result doesn't seem plausible. |
|
July 8, 2022, 02:01 |
|
#3 | |
Member
Pablo Alarcón
Join Date: Mar 2018
Location: Liège
Posts: 59
Rep Power: 8 |
I am facing exactly the same problem now, does anybody know how to do it?
Quote:
|
||
July 8, 2022, 05:07 |
|
#4 |
Senior Member
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,686
Rep Power: 40 |
The coordinate specification itself looks OK, but I generally find the "cylindrical" specification for the rotation a bit confusing.
You should know that the cylindrical coordinate systems were pretty odd/faulty when used to transform fields (the mesh locations were not properly used for the cylindrical coordinates). This was massively reworked for the OpenFOAM-v1812 version and should now be working correctly, I believe. Here is a reference to a commit with some details: https://develop.openfoam.com/Develop...237eea184abb46 |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
error in fireFoam, when running the case wallFireSpread2D | zhoubiao1088 | OpenFOAM Running, Solving & CFD | 9 | February 1, 2018 18:45 |
[foam-extend.org] Error compiling OpenFOAM-1.6-ext | Canesin | OpenFOAM Installation | 137 | January 20, 2016 14:56 |
[OpenFOAM] Annoying issue of automatic "Rescale to Data Range " with paraFoam/paraview 3.12 | keepfit | ParaView | 60 | September 18, 2013 03:23 |
Compilation error OF1.5-dev on Suse10.3 | darenyang | OpenFOAM Installation | 0 | April 29, 2009 04:55 |
[blockMesh] BlockMeshmergePatchPairs | hjasak | OpenFOAM Meshing & Mesh Conversion | 11 | August 15, 2008 07:36 |