|
[Sponsors] |
[swak4Foam] funkySetFields fatal error - Unknown patchField - hotRoom |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
February 15, 2020, 07:50 |
funkySetFields fatal error - Unknown patchField - hotRoom
|
#1 |
Member
Petros Ampatzidis
Join Date: Oct 2018
Location: Bath, UK
Posts: 64
Rep Power: 7 |
Dear all,
I am trying to reproduce Bernhard's latest tutorial on swak4Foam from OFW14 using v-1906. I have gone successfully through the first steps of the hotRoom case but when I try to implement the "column of fire" initial condition with Code:
funkySetFields -time 0 -keepPatches -valuePatches "floor" -field T -expression "600" -condition "(pos().x>4.5 && pos().x<5.5 && pos().z>4.5 && pos().z<5.5)" Code:
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // swakVersion: 0.4.3 (Release date: Next release) // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // Create time Create mesh for time = 0 Time = 0 Using command-line options Creating field TFahrenheit Putting "T*(9/5)-459.67" into field TFahrenheit at t = "0" if condition "true" is true swak4Foam: Allocating new repository for sampledMeshes swak4Foam: Allocating new repository for sampledGlobalVariables --> FOAM FATAL IO ERROR: Unknown patchField type lumpedMassWallTemperature for patch type wall Valid patchField types : 68 ( advective calculated codedFixedValue.... Code:
Current OpenFOAM version is v1906. Previously compiled for OpenFOAM (v1906) /home/petros/OpenFOAM/petros-v1906/swak4Foam/privateRequirements/bin existing. Prepending to PATH-variable (private version of Bison) Reading variables from 'swakConfiguration' Looking for Python 2 Found Python 2.7 Configuring Python 2.7 Using python2.7 at /usr/bin/python2.7-config for python2 Looking for Python 3 Found Python 3.6 Configuring Python 3.6 Using python3.6 at /usr/bin/python3.6-config for python3 Using our own Lua at /home/petros/OpenFOAM/petros-v1906/swak4Foam/privateRequirements Checking swak4Foam-version and generating file Swak version is 0.4.3 hg info: f4fb37df715d (develop) tip Bison: /home/petros/OpenFOAM/petros-v1906/swak4Foam/privateRequirements/bin/bison Flex: /usr/bin/flex Bison at /home/petros/OpenFOAM/petros-v1906/swak4Foam/privateRequirements/bin/bison is version 3.4 (Major 3 Minor 4) Flex is version 2.6.4 (Minor version: 4) No change to swak4FoamParsers/foamVersion4swak.H Petros |
|
February 15, 2020, 09:03 |
|
#2 |
Senior Member
Herpes Free Engineer
Join Date: Sep 2019
Location: The Home Under The Ground with the Lost Boys
Posts: 931
Rep Power: 13 |
Not sure, but main functionalities of swak4Foam were transferred into OF starting from v1912. Please have a go to see if it helps.
__________________
The OpenFOAM community is the biggest contributor to OpenFOAM: User guide/Wiki-1/Wiki-2/Code guide/Code Wiki/Journal Nilsson/Guerrero/Holzinger/Holzmann/Nagy/Santos/Nozaki/Jasak/Primer Governance Bugs/Features: OpenFOAM (ESI-OpenCFD-Trademark) Bugs/Features: FOAM-Extend (Wikki-FSB) Bugs: OpenFOAM.org How to create a MWE New: Forkable OpenFOAM mirror |
|
February 15, 2020, 09:30 |
|
#3 | |
Member
Petros Ampatzidis
Join Date: Oct 2018
Location: Bath, UK
Posts: 64
Rep Power: 7 |
Quote:
Allow me to comment more on that issue though, hoping that it might be of any help. Using the 'banana' trick and running just the buoyantPimpleFoam it is clear that OpenFOAM offers 116 possible patchField types, including lumpedMassWallTemperature. Code:
--> FOAM FATAL IO ERROR: Unknown patchField type banana for patch type wall Valid patchField types : 116 ( MarshakRadiation MarshakRadiationFixedTemperature advective alphatJayatillekeWallFunction atmBoundaryLayerInletEpsilon atmBoundaryLayerInletK . . . lumpedMassWallTemperature mapped . . . Code:
--> FOAM FATAL IO ERROR: Unknown patchField type banana for patch type wall Valid patchField types : 68 ( advective calculated codedFixedValue codedMixed cyclic . . . |
||
May 22, 2020, 06:17 |
|
#4 | |
New Member
Tim Taylor
Join Date: May 2020
Posts: 2
Rep Power: 0 |
I have had exactly the same problem, Petros.
Have you found a solution to this? regards, Tim Quote:
|
||
May 22, 2020, 09:20 |
|
#5 |
Member
Petros Ampatzidis
Join Date: Oct 2018
Location: Bath, UK
Posts: 64
Rep Power: 7 |
Hi Tim,
Unfortunately I haven't found what caused this. Petros |
|
March 7, 2021, 17:33 |
Same problem for alphaContactAngle
|
#6 | |
New Member
Join Date: Dec 2020
Posts: 9
Rep Power: 5 |
Dear Petros
I also have a similar problem during initializing files for the multiphaseInterFoam solver. Unfortunately does not "alphaContactAngle" did you figure out how to solve it? Code:
--> FOAM FATAL IO ERROR: Unknown patchField type alphaContactAngle for patch type patch Valid patchField types are : 118 ..... Quote:
|
||
March 20, 2024, 14:48 |
|
#7 |
Member
Thiago Parente Lima
Join Date: Sep 2011
Location: Diamantina, Brazil.
Posts: 64
Rep Power: 15 |
Hi all,
For further reference, I have a workaround for that issue. If funkySetFields complains about a specific patch type, you can first set a dummy patch type for your boundary condition, say: Code:
yourPatchName01 { type calculated; value uniform 0; } After that, you can change the patch type to the type you want, using a changeDictionaryDict. For example: Code:
T { boundaryField { yourPatchName01 { type externalWallHeatFluxTemperature; kappa solidThermo; Ta uniform 300; h uniform 1; value uniform 300; kappaName none; } } }
__________________
Fields of interest: buoyantFoam, chtMultRegionFoam. |
|
Tags |
funkysetfields |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help with if statement | CHARLES | OpenFOAM Programming & Development | 17 | August 22, 2021 03:14 |
--> FOAM FATAL IO ERROR: Unknown patchField type patch for patch type patch | haddad | OpenFOAM | 1 | March 4, 2019 04:20 |
[blockMesh] FOAM FATAL IO ERROR_Cannot find patchField entry | mohsen.boojari | OpenFOAM Meshing & Mesh Conversion | 2 | January 21, 2016 08:51 |
adding compressible option to ptot | immortality | OpenFOAM Programming & Development | 13 | June 15, 2015 15:00 |
error while compiling the USER Sub routine | CFD user | CFX | 3 | November 25, 2002 15:16 |