|
[Sponsors] |
May 28, 2021, 17:10 |
Passing variables to a codedBC
|
#1 |
Member
Tony Ladd
Join Date: Aug 2013
Posts: 48
Rep Power: 12 |
I am using a coded BC for an initial condition and a boundary condition (U.txt). I define omega as a parameter at the top of the file and then use it in setting the internal field via #codestream and in a rotating wall bc. I would also like to use it in a codedBC but the variable is not seen in the code. So $omega*y is interpreted as *y (an error of course). It works fine with a value (2) hardwired in (as in U.txt).
I understand that it's probably a scoping issue and we have encountered it before with coded BC's. But I was surprised it worked with codestream. My questions are: 1) Why is the scoping different in coded BC and codestream (if that is what it is) 2) Is there any way to get a parameter defined in the BC file into the coded BC. We know how to read parameters from a dictionary but this seems overly complicated. Thanks Tony Last edited by tladd; May 28, 2021 at 17:28. Reason: PS. The case is in the zip file |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[swak4Foam] How to define boundary condition variables by using previosly defined variables? | pawlo | OpenFOAM Community Contributions | 8 | September 13, 2020 11:37 |
Optimal tolerance and variables scaling settings | 4513645ygq | Main CFD Forum | 0 | July 28, 2020 08:56 |
SU2 violates the lower bound of the FFD design variables | cfdjetman | SU2 | 4 | October 2, 2019 16:15 |
Some variables not loading in Tecplot | nick.l.thomas | Tecplot | 1 | October 25, 2018 17:48 |
Passing fortran variables to C in mixed programmin | Quarkz | Main CFD Forum | 1 | January 9, 2008 06:17 |