View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002416 | OpenFOAM | Bug | public | 2016-12-31 12:05 | 2017-06-30 12:34 |
Reporter | Svensen | Assigned To | chris | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | GNU/Linux | OS | Ubuntu | OS Version | 14.04 |
Product Version | dev | ||||
Summary | 0002416: surfacenormalfixedvalue. failed with timevarying boundary conditions | ||||
Description | I've tried to use a time-varying boundary conditions with the type surfaceNormalFixedValue. However, when I start pimpleFoam it says that: -------------------------------------- Reading field p Reading field U --> FOAM FATAL IO ERROR: wrong token type - expected Scalar, found on line 32 the word 'tableFile' file: /home/sergey/simulation/prothmann_fusiform/0/U.boundaryField.inlet1.refValue at line 32. From function Foam::Istream& Foam::operator>>(Foam::Istream&, Foam::doubleScalar&) in file lnInclude/Scalar.C at line 93. FOAM exiting -------------------------------------- Code snippet is here: inlet1 { type surfaceNormalFixedValue; refValue uniform tableFile; uniformValueCoeffs { fileName "$FOAM_CASE/bc/U.bc"; } } | ||||
Tags | boundary conditions | ||||
|
Nothing in the documentation of "surfaceNormalFixedValue", nor the code itself, indicates that this is a valid use of this boundary condition. Therefore, this is not a bug. So I have to ask: What lead you to believe that this boundary condition would support that feature? I ask this because the documentation doesn't mention anything list that and I can't find any indication in the release notes that would imply that: - http://openfoam.org/release/2-1-0/boundary-conditions-time-dependent/ - http://openfoam.org/release/4-0/ |
|
I've thought that time-varying value is also supported in surfaceNormalFixedValue as it was done for uniformFixedValue (using Function1), however it is not implemented yet. It seems that scalarField refValue_; should be replaced by something like autoPtr<Function1<Type>> refValue_; but I'm not sure if it will work. I will try to check this in the nearest days and will report the results. |
|
No feedback from reporter |
Date Modified | Username | Field | Change |
---|---|---|---|
2016-12-31 12:05 | Svensen | New Issue | |
2016-12-31 12:05 | Svensen | Tag Attached: boundary conditions | |
2017-01-01 17:43 | wyldckat | Note Added: 0007575 | |
2017-01-02 07:35 | Svensen | Note Added: 0007581 | |
2017-01-08 23:52 | wyldckat | Severity | minor => feature |
2017-06-30 12:34 | chris | Assigned To | => chris |
2017-06-30 12:34 | chris | Status | new => closed |
2017-06-30 12:34 | chris | Resolution | open => fixed |
2017-06-30 12:34 | chris | Note Added: 0008307 |