|
[Sponsors] |
Using the matchedFlowRateOutletVelocity boundary condition |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
September 16, 2019, 23:28 |
Using the matchedFlowRateOutletVelocity boundary condition
|
#1 |
New Member
Brent Shambaugh
Join Date: Nov 2018
Posts: 8
Rep Power: 8 |
Forgive me, I am not sure what to ask. I am trying to use the matchedFlowRateOutletVelocity boundary condition for compressible flow, and I am not sure what sorts of things are allowable for boundary conditions with this condition. I came up with some questions:
When matchedFlowRateOutletVelocity is applied as a boundary condition for U, what should the boundary conditions be for p, T, nut, k, epsilon, and alpat when running with rhoSimpleFoam? More simply when matchedFlowRateOutletVelocity is applied as a boundary condition for U, what should p and T be when running rhoPimpleFoam? I usually get an error like this. Maybe I cannot use the calculated b.c. Perhaps, fixedValue? --> FOAM FATAL ERROR: cannot be called for a calculatedFvPatchField on patch fineMeshOutletLeft of field e in file "/home/brent/OpenFOAM/brent-7/run/tutorials/compressible/rhoPimpleFoam/laminar/b2_forwardStep/0/e" You are probably trying to solve for a field with a default boundary condition. From function Foam::tmp<Foam::Field<Type> > Foam::calculatedFvPatchField<Type>::gradientIntern alCoeffs() const [with Type = double] in file fields/fvPatchFields/basic/calculated/calculatedFvPatchField.C at line 188. object T; type calculated; value $internalField; object p; type calculated; value $internalField; |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
sliding mesh problem in CFX | Saima | CFX | 46 | September 11, 2021 08:38 |
Centrifugal fan | j0hnny | CFX | 13 | October 1, 2019 14:55 |
Accessing multiple boundary patches from a custom boundary condition file | ripudaman | OpenFOAM Programming & Development | 0 | October 22, 2014 19:34 |
Radiation interface | hinca | CFX | 15 | January 26, 2014 18:11 |
An error has occurred in cfx5solve: | volo87 | CFX | 5 | June 14, 2013 18:44 |