|
[Sponsors] |
August 6, 2020, 08:43 |
Calling fvPatchField::internalField.name()
|
#1 |
Senior Member
Gerry Kan
Join Date: May 2016
Posts: 350
Rep Power: 10 |
Howdy Foamers:
While I am debugging my code I came across something quite strange. I have an fvPatchField defined, and it calls a function fvPatchField::internalField.name() to identify which variable it is. When this call is made before the time loop, I get the normal variable (say "p", "T", "U"). However, the same call inside the time loop, I end up getting the "_0" attached to it (i.e., "p_0", "T_0", "U_0"). I am wondering why this is the case? Is it because the "_0" variable refers to the variables in the current time step, and those without refers to the variable being solved towards the end of the time step? Thanks in advance, Gerry. |
|
August 6, 2020, 08:45 |
|
#2 |
Senior Member
Gerry Kan
Join Date: May 2016
Posts: 350
Rep Power: 10 |
Okay, it seems that my hypothesis is correct according to this link.
What are h_0 and h_0_0 in chtMultiRegionFoam solver? Gerry. |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problem calling foamDictionary in docker from a python notebook | Hisham | OpenFOAM Pre-Processing | 0 | January 7, 2020 07:52 |
argument deduction/substitution failed when calling fvc::ddt | Zhangyy | OpenFOAM Programming & Development | 0 | May 8, 2019 12:51 |
Error calling calculated vector field as boundary condition in dynamic mesh | paoching | OpenFOAM Programming & Development | 0 | August 31, 2018 18:01 |
Calling zone name, zone id and total pressure from Fluent scheme to UDF | kuldip | Fluent UDF and Scheme Programming | 2 | October 6, 2014 00:23 |
Calling Fluent from IDL. Help! | justinclouds | FLUENT | 0 | May 19, 2013 18:37 |