View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003351 | OpenFOAM | Bug | public | 2019-09-18 10:28 | 2019-09-18 11:11 |
Reporter | emjay | Assigned To | henry | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | docker 2.1.0.2 | OS | Other | OS Version | (please specify) |
Summary | 0003351: boundaryFoam with postProcess option is invalid | ||||
Description | it is not possible to execute the postProcess option | ||||
Steps To Reproduce | execute the tutorial boundaryFoam/boundaryWallfunctions/ case execute boundaryFoam -postProcess --> FOAM FATAL ERROR: Invalid option: -postProcess | ||||
Tags | No tags attached. | ||||
|
errorReport.txt (1,242 bytes)
OpenFOAM-6(574) boundaryFoam -postProcess Usage: boundaryFoam [OPTIONS] options: -case <dir> specify alternate case directory, default is the cwd -fileHandler <handler> override the fileHandler -listFunctionObjects List functionObjects -listFvOptions List fvOptions -listRegisteredSwitches List switches registered for run-time modification -listScalarBCs List scalar field boundary conditions (fvPatchField<scalar>) -listSwitches List switches declared in libraries but not set in etc/controlDict -listTurbulenceModels List turbulenceModels -listUnsetSwitches List switches declared in libraries but not set in etc/controlDict -listVectorBCs List vector field boundary conditions (fvPatchField<vector>) -noFunctionObjects do not execute functionObjects -srcDoc display source code in browser -doc display application documentation in browser -help print the usage Using: OpenFOAM-6 (see www.OpenFOAM.org) Build: 6-1a0c91b3baa8 --> FOAM FATAL ERROR: Invalid option: -postProcess FOAM exiting |
|
That is correct, boundaryFoam does not currently support postProcessing because most post-processing tools are not applicable to this specialized solver. Which post-processing tools do you want to use with boundaryFoam? |
|
i need checking the yPlus values. In the meantime i've found a workaround functions { #includeFunc yPlus } |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-09-18 10:28 | emjay | New Issue | |
2019-09-18 10:28 | emjay | File Added: errorReport.txt | |
2019-09-18 10:46 | henry | Note Added: 0010757 | |
2019-09-18 10:55 | emjay | Note Added: 0010758 | |
2019-09-18 11:11 | henry | Assigned To | => henry |
2019-09-18 11:11 | henry | Status | new => closed |
2019-09-18 11:11 | henry | Resolution | open => no change required |