View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004055 | OpenFOAM | Bug | public | 2024-02-21 15:04 | 2024-02-21 16:24 |
| Reporter | agustinvo | Assigned To | henry | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | Any | OS | Any | OS Version | Any |
| Product Version | 11 | ||||
| Fixed in Version | 11 | ||||
| Summary | 0004055: turbulenceFields function object does not access to fluidThermophysicalTransportModel | ||||
| Description | It is not possible to retrieve the kappaEff field, included in the functionObject turbulenceFields, because the if-condition of line 161 https://github.com/OpenFOAM/OpenFOAM-11/blob/642b6a1f5c7bc501ca9ebc78d4e54051ba32cb2d/src/functionObjects/field/turbulenceFields/turbulenceFields.C#L161C4-L161C73 is never true. The postProcess application enters into another else-condition block and it crashes because no kappaEff field is found. | ||||
| Steps To Reproduce | 1. Run a simulation with a fluid solver 2. Run foamPostprocess with the turbulenceFields function and the field kappaEff 3. Get the error: --> FOAM FATAL ERROR: Invalid field selection From function virtual bool Foam::functionObjects::turbulenceFields::execute() in file turbulenceFields/turbulenceFields.C at line 269. FOAM exiting | ||||
| Additional Information | Substituting the line 161 if (obr_.foundObject<fluidThermophysicalTransportModel>(phaseName_)) by this one if (obr_.foundType<fluidThermophysicalTransportModel>(phaseName_)) has worked for me. | ||||
| Tags | No tags attached. | ||||
|
|
I just tested the turbulenceFields functionObject in OpenFOAM-dev and kappaEff is generated without any problem. Could you please confirm that this issue does not occur for you with OpenFOAM-dev? |
|
|
The commit in the dev branch https://github.com/OpenFOAM/OpenFOAM-dev/commit/2779442d2a1ff03694f41e6a80e95ed0a1821792 does indeed add the same line than the one I indicated, but in OF-11 the bug is there. A fix could be done into this file in OF-11 as the one in OF-dev |
|
|
Resolved by commit c7c47ff3f7b39ba0240b9bf5753c7e86bddaeb92 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-02-21 15:04 | agustinvo | New Issue | |
| 2024-02-21 15:12 | henry | Note Added: 0013198 | |
| 2024-02-21 15:33 | agustinvo | Note Added: 0013199 | |
| 2024-02-21 16:24 | henry | Assigned To | => henry |
| 2024-02-21 16:24 | henry | Status | new => resolved |
| 2024-02-21 16:24 | henry | Resolution | open => fixed |
| 2024-02-21 16:24 | henry | Fixed in Version | => 11 |
| 2024-02-21 16:24 | henry | Note Added: 0013200 |
