OpenFOAM-plus issueshttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues2020-01-07T01:32:11Zhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/289BUG: invalid type while accessing fields2020-01-07T01:32:11ZPrashant SonakarBUG: invalid type while accessing fieldsAttached case which replicates issue while accessing pressure field (develop branch).
[pitzDaily-develop.tgz](/uploads/c2213bc9d7442d4e1e0d0b37974279c5/pitzDaily-develop.tgz)
fails with error
```
Reading p
--> FOAM Warning :
--> FO...Attached case which replicates issue while accessing pressure field (develop branch).
[pitzDaily-develop.tgz](/uploads/c2213bc9d7442d4e1e0d0b37974279c5/pitzDaily-develop.tgz)
fails with error
```
Reading p
--> FOAM Warning :
--> FOAM FATAL IO ERROR:
unexpected class name volScalarField expected volVectorField
while reading object p
file: /hosts/pnq073/home/sonakar/share/pitzDaily-develop/5/p at line 15.
From function Foam::Istream& Foam::regIOobject::readStream(const Foam::word&)
in file db/regIOobject/regIOobjectRead.C at line 295.
End
```Version v1612Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1309foamExec file is missing2019-12-11T16:55:44ZAlifoamExec file is missingHi,
I have noticed that foamExec is not present in bin directory. Then I was tracking down the changes of that file and found that it was removed. I usually use qtcreator to compile my own solvers/utilities to keep my development update...Hi,
I have noticed that foamExec is not present in bin directory. Then I was tracking down the changes of that file and found that it was removed. I usually use qtcreator to compile my own solvers/utilities to keep my development updated and I need foamExec file for the compilation process. I am not sure, any other file can be used for that purpose or not.
solution: Just need to reinstate the file. I just copied foamExec file from the previous version and working with it.
Regards,
Ali
MUN, CanadaMark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/938illegal instruction constexpr v1712 v18062019-12-11T16:42:55ZCole Muellerillegal instruction constexpr v1712 v1806Trying to compile a new solver on windows 10 bash with ubuntu. Compiler returns an error saying illegal instruction constexpr. This has occurred on versions 1712 and 1806 in the header file floatScalar.H. I believe it has been a repeated...Trying to compile a new solver on windows 10 bash with ubuntu. Compiler returns an error saying illegal instruction constexpr. This has occurred on versions 1712 and 1806 in the header file floatScalar.H. I believe it has been a repeated issue from what I have seen on the forums so others will probably be able to provide more information. I don't know if this is a version issue because I updated all my compilers. I only come because the only solution I have seen found to this anywhere is revert to OF5. I have seen this exact issue reported on v1706 as well.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1007source bashrc in WSL causes bash: eval: line 38: syntax error near unexpected...2019-12-11T12:50:50ZFoadsource bashrc in WSL causes bash: eval: line 38: syntax error near unexpected token `('I tried to load the bashrc in WSL but I get the error:
> bash: eval: line 38: syntax error near unexpected token `('
similar problem [here](https://stackoverflow.com/questions/51345463/syntax-error-near-unexpected-token-when-sourcing-b...I tried to load the bashrc in WSL but I get the error:
> bash: eval: line 38: syntax error near unexpected token `('
similar problem [here](https://stackoverflow.com/questions/51345463/syntax-error-near-unexpected-token-when-sourcing-bashrc-to-setup-openfoam-e).Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1506wrong sampling in arraySet.C line 722019-11-28T11:53:39ZPer Jørgensenwrong sampling in arraySet.C line 72please change
`point pt(i*dx*i , j*dy, k*dz);`
to
`point pt(i*dx , j*dy, k*dz);`
- i am not allowed...please change
`point pt(i*dx*i , j*dy, k*dz);`
to
`point pt(i*dx , j*dy, k*dz);`
- i am not allowed...Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1504maintenance-v1812 does not compile: getOrDefault is not defined2019-11-19T14:33:58ZIlya Popovmaintenance-v1812 does not compile: getOrDefault is not definedCommit d11cfca introduced use of getOrDefault, but this in not present in version 1812.Commit d11cfca introduced use of getOrDefault, but this in not present in version 1812.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1501RASModelVariables::SpalartAllmaras cannot be combined with an fvMotionSolver ...2019-11-19T13:33:06ZVaggelis PapoutsisRASModelVariables::SpalartAllmaras cannot be combined with an fvMotionSolver diffusivity which depends on wall distances### Summary
When an fvMotionSolver using a distance-dependent diffusivity is used, wallDist names the distance field as "yPatch". However, RASModelVariables::SpalartAllmaras expects to find a field named "yWall" in the database. Since g...### Summary
When an fvMotionSolver using a distance-dependent diffusivity is used, wallDist names the distance field as "yPatch". However, RASModelVariables::SpalartAllmaras expects to find a field named "yWall" in the database. Since getObjectPtr returns a nullptr if the field is not found in the database, this bug is silenced but manifests later on when the pointer is dereferenced in adjointSpalartAllmaras.
### Possible fixes
Replace
```c++
dPtr_ = mesh_.getObjectPtr<volScalarField>("yWall");
```
with
```c++
dPtr_ = &(const_cast<volScalarField&>(wallDist::New(mesh_).y()));
```
so that wallDist.y() is retrieved, no matter what the actual name of the variable is.v1912Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1498BUG: reading a labelList preceded by its size in a binary-format dictionary t...2019-11-19T13:33:06ZKutalmış BerçinBUG: reading a labelList preceded by its size in a binary-format dictionary throws FatalError<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
You can see how your report will be ...<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
You can see how your report will be rendered on the platform by using the
"preview" tab above
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
<!-- Summarize the bug encountered concisely -->
When `FoamFile.format` is `binary` in a dictionary, a labelList keyword preceded by its size, e.g. `labelList 1(1);` is not read, and `FatalError` is thrown due to [operator>>](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/OpenFOAM-v1906/src/OpenFOAM/containers/Lists/UList/UListIO.C#L201). The problem in practice is that [CSV.C](https://develop.openfoam.com/Development/OpenFOAM-plus/blame/master/src/OpenFOAM/primitives/functions/Function1/CSV/CSV.C#L281) writes out a labelList entry with its size at writeTime. When a restart is needed, the simulation fails.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
`tutorials/combustion/reactingFoam/RAS/chokedNozzle`
Make the following changes thereat:
```
format binary;
```
```
componentColumns 1( 2 );
```
`./Allrun`
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : dev-13Nov
- Operating system : osuse 15.1
- Compiler : gcc
cross-ref EP[#1176](https://exchange.openfoam.com/node/1176)
@markMark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1502adjointSolverName not set correctly in adjointWallVelocityLowRe2019-11-19T11:08:58ZVaggelis PapoutsisadjointSolverName not set correctly in adjointWallVelocityLowRe## Description
"Ua" is passed as the solverName argument in the adjointBoundaryCondition constructors of adjointWallVelocityLowRe. As a result, adjointWallVelocityLowRe cannot be used if useSolverNameForFields has been set to `true` in ...## Description
"Ua" is passed as the solverName argument in the adjointBoundaryCondition constructors of adjointWallVelocityLowRe. As a result, adjointWallVelocityLowRe cannot be used if useSolverNameForFields has been set to `true` in `optimisationDict`.
## Possible fixes
Replace
```c++
adjointBoundaryCondition(p, iF, "Ua")
```
with
```c++
adjointBoundaryCondition(p, iF, ptf.adjointSolverName_)
```
and
```c++
adjointBoundaryCondition(p, iF, dict.get<word>("solverName"))
```
in the second and third constructors of adjointWallVelocityLowRe.v1912Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1500surfaceRedistributePar needs a dictionary2019-11-14T22:16:02ZJustin GraupmansurfaceRedistributePar needs a dictionary### Functionality to add/problem to solve
surfaceRedistributePar could benefit from having its own dictionary similar to decomposeParDict or surfaceFeatureExtractDict. That way we won't have to run the command line multiple times for mu...### Functionality to add/problem to solve
surfaceRedistributePar could benefit from having its own dictionary similar to decomposeParDict or surfaceFeatureExtractDict. That way we won't have to run the command line multiple times for multiple surfaces.
### Target audience
Anyone decomposing multiple surfaces
### Proposal
Have surfaceRedistributePar read a surfaceRedistributeParDict which has a list of surfaces and requires the distributionType to be listed for each surface (or use a global distributionType specified in this file).
### What does success look like, and how can we measure that?
When surfaceRedistributePar reads from a dictionary, I'll be happy.
### Funding
Nonehttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/815vanDriestDelta documentation - the default value of Cdelta2019-11-14T18:32:54ZKutalmış BerçinvanDriestDelta documentation - the default value of CdeltaHi,
Please see the two remarks below for `vanDriestDelta` implementation:
1. As can be seen in `vanDriestDelta.C` lines: [87-91], the van Driest function formulation (doi: 10.2514/8.3713, 1956) is slightly different from its original ...Hi,
Please see the two remarks below for `vanDriestDelta` implementation:
1. As can be seen in `vanDriestDelta.C` lines: [87-91], the van Driest function formulation (doi: 10.2514/8.3713, 1956) is slightly different from its original form. A *minimum switch* was introduced by de Villiers (http://bit.ly/1unTPaB, 2006) as shown in pages: [124, 260]. IMHO, it would be nice of you as well as useful to some users if his heuristic modification/work is noted and cited in the Extended Code Guide, which is currently absent.
2. In addition, `vanDriestCoeffs`'s `Cdelta` is (most of the time) kept equal to `0.158` by default in the tutorials as can be found in `tutorials/incompressible/pimpleFoam/LES/channel395DFSEM/constant/turbulenceProperties` of v1712, for instance. However, as shown in de Villiers, the unnumbered equation in page 260, `Cdelta` is actually `Cs`. This may suggest, at least for `channel395DFSEM` tutorial, that `Cdelta` needs to equate `Cdelta=Cs=0.065` rather than `0.158`. Not sure if it is of practical importance though. Just an observation :)
Kind regards,Kutalmış BerçinKutalmış Berçin2018-12-31https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1108turbulentDFSEMInlet; Removal of 'mapMethod' causes FOAM FATAL IO ERROR2019-11-13T13:01:17ZKutalmış BerçinturbulentDFSEMInlet; Removal of 'mapMethod' causes FOAM FATAL IO ERROR### Summary
When `mapMethod` option of `turbulentDFSEMInlet` BC is removed, it raises `FOAM FATAL IO ERROR` although under `turbulentDFSEMInletFvPatchVectorField.H` was stated for its usage was stated to be optional:
Property ...### Summary
When `mapMethod` option of `turbulentDFSEMInlet` BC is removed, it raises `FOAM FATAL IO ERROR` although under `turbulentDFSEMInletFvPatchVectorField.H` was stated for its usage was stated to be optional:
Property | Description | Required | Default value
mapMethod | Method to map reference values | no | planarInterpolation
```
--> FOAM FATAL IO ERROR:
'mapMethod' not found in dictionary "/home/snoopy2/kuta/OpenFOAM/kuta-v1806/run/channel395DFSEM/0/U.boundaryField.inlet"
file: /home/snoopy2/kuta/OpenFOAM/kuta-v1806/run/channel395DFSEM/0/U.boundaryField.inlet
From function const Foam::entry& Foam::dictionary::lookupEntry(const Foam::word&, bool, bool) const
in file db/dictionary/dictionary.C at line 332.
FOAM exiting
```
### Steps to reproduce
Please consider `tutorials/incompressible/pimpleFoam/LES/channel395DFSEM` case.
Remove `mapMethod` under `0/U`:
```
inlet
{
type turbulentDFSEMInlet;
...
mapMethod nearestCell;
...
}
```
to
```
inlet
{
type turbulentDFSEMInlet;
...
}
```
Then execute the following respectively:
`blockMesh`
`decomposePar`
### What is the expected *correct* behavior?
Either the documentation in `turbulentDFSEMInletFvPatchVectorField.H` should be corrected, or the method according to the documentation.v1906Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1479Broken link on openfoam.com2019-11-12T21:12:22ZVolker WeißmannBroken link on openfoam.comOn [this website](https://www.openfoam.com/documentation/guides/latest/doc/openfoam-guide-input-types.html) and many other sites, you have a button labeled "Create an issue" with a link to [this site](https://develop.openfoam.com/Communi...On [this website](https://www.openfoam.com/documentation/guides/latest/doc/openfoam-guide-input-types.html) and many other sites, you have a button labeled "Create an issue" with a link to [this site](https://develop.openfoam.com/Community/Documentation/issues/new?issue[title]=Doc%20improvement:%20Add%20your%20title%20here&issue[description]=Page:%20openfoam-guide-input-types%0A%0ADescribe%20your%20proposed%20changes%0A%0A%3C!--%20Do%20not%20edit%20below%20this%20line%20--%3E%0A%0A%2Flabel%20~improvement) . The link is HTTP 404 Not found.
I would recommend fixing this link and the use of an automatic broken link checker.https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1429Suggestions for the Submitting Issues page2019-11-12T14:37:03ZGerasimos ChourdakisSuggestions for the Submitting Issues page# Problem
During the OpenFOAM Workshop 2019, it was noted that several people are not sure how to submit (good) bug reports, mainly due to not knowing how to report system-related technical information. @bgschaid @mark
# Suggested fix...# Problem
During the OpenFOAM Workshop 2019, it was noted that several people are not sure how to submit (good) bug reports, mainly due to not knowing how to report system-related technical information. @bgschaid @mark
# Suggested fixes
## Patches for page "Submitting Issues"
I had a look into the page [Submitting Issues](https://develop.openfoam.com/Development/OpenFOAM-plus/wikis/page-submitting-issues) and I added a bit more information, trying to keep the text short and the instructions precise and platform-independent. Since I cannot open merge requests or even fork the repository, I attach a set of patches here (they are for the Wiki repository, anyway). These patches are based on d8c4d7 and I have tested them locally.
[wiki_Submitting-Issues_patches.tar.gz](/uploads/3ad5ce768f455724b1077150d59c21ab/wiki_Submitting-Issues_patches.tar.gz)
<p>
<details>
<summary>Here is a preview:</summary>
![Screenshot_from_2019-09-05_16-40-55](/uploads/422c9f0ab4f069a1bdbc713814bc87fb/Screenshot_from_2019-09-05_16-40-55.png)
</details>
</p>
## Add link on openfoam.com
A link to the page [Bug Reporting](https://www.openfoam.com/code/bug-reporting.php) is very prominent both in the side menu and in the "Code" drop-down. :+1:
However, the statement:
> Bug and issue reporting is provided via the repository hosting site https://develop.openfoam.com described [here](https://www.openfoam.com/code/repositories.php)
leads to a generic page, while it should lead to the page [Submitting Issues](https://develop.openfoam.com/Development/OpenFOAM-plus/wikis/page-submitting-issues).https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1410FDICSmoother and SPDP2019-11-12T14:20:41ZMarkus TowaraFDICSmoother and SPDPHi, just a small one:
Should the following members of `FDICSmoother.H` be `solveScalarFields` instead?
```
scalarField rD_;
scalarField rDuUpper_;
scalarField rDlUpper_;
```
Like its done in DICSmoother.H.Hi, just a small one:
Should the following members of `FDICSmoother.H` be `solveScalarFields` instead?
```
scalarField rD_;
scalarField rDuUpper_;
scalarField rDlUpper_;
```
Like its done in DICSmoother.H.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1413`apt update` missing from the System Requirement instructions2019-11-12T14:03:21ZBruno Santos`apt update` missing from the System Requirement instructionsI've noticed a few minutes ago, while looking into this thread: https://www.cfd-online.com/Forums/openfoam-installation/220196-question-cmake-ubuntu-prerequisite.html - that the "System Requirements" page: https://www.openfoam.com/docum...I've noticed a few minutes ago, while looking into this thread: https://www.cfd-online.com/Forums/openfoam-installation/220196-question-cmake-ubuntu-prerequisite.html - that the "System Requirements" page: https://www.openfoam.com/documentation/system-requirements.php - is missing a critical command:
```
sudo apt-get update
```
for Ubuntu/Debian instructions; without this, `apt` and `apt-get` will fail miserably if the auto-update system didn't kick-in soon enough or because it never does when using WSL.
As a side note, you can change `apt-get` to `apt` for the more recent versions of Ubuntu/Debian, which provides a nicer interface and progress bar... even though it still doesn't run `update` on its own...https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1435There are some mistakes at the example of Periodic hill on OpenFOAM: User Gui...2019-11-12T13:59:22ZXu ZhaoyueThere are some mistakes at the example of Periodic hill on OpenFOAM: User Guide v1906<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
You can see how your report will be ...<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
You can see how your report will be rendered on the platform by using the
"preview" tab above
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
<!-- Summarize the bug encountered concisely -->At the web site, Periodic hills describtion function is wrong.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
open the website [https://www.openfoam.com/documentation/guides/latest/doc/verification-validation-turbulent-periodic-hill.html#sec-verification-validation-turbulent-periodic-hill-overview]
At the Mesh Table, you will see
hills described by the function:
<img src="http://latex.codecogs.com/gif.latex?y(x) = \begin{cases} a_1 + b_1 x + c_1 x^2 + d_1 x^3 & 0 \le x \textless 9, \\ a_2 + b_2 x + c_2 x^2 + d_2 x^3 & 9 \le x \textless 14, \\ a_3 + b_3 x + c_3 x^2 + d_3 x^3 & 14 \le x \textless 20, \\ a_4 + b_4 x + c_4 x^2 + d_4 x^3 & 20 \le x \textless 30, \\ a_5 + b_5 x + c_5 x^2 + d_5 x^3 & 30 \le x \textless 40, \\ \max(0, a_6 + b_6 x + c_6 x^2 + d_6 x^3) & 40 \le x \textless 54. \\ \end{cases}" />
as the first equation could be large than 1, the function should be corrected as:
<img src="http://latex.codecogs.com/gif.latex?y(x) = \begin{cases} \min(1, a_1 + b_1 x + c_1 x^2 + d_1 x^3) & 0 \le x \textless 9, \\ a_2 + b_2 x + c_2 x^2 + d_2 x^3 & 9 \le x \textless 14, \\ a_3 + b_3 x + c_3 x^2 + d_3 x^3 & 14 \le x \textless 20, \\ a_4 + b_4 x + c_4 x^2 + d_4 x^3 & 20 \le x \textless 30, \\ a_5 + b_5 x + c_5 x^2 + d_5 x^3 & 30 \le x \textless 40, \\ \max(0, a_6 + b_6 x + c_6 x^2 + d_6 x^3) & 40 \le x \textless 54. \\ \end{cases}" />
and the number in the table of c2 should be -1.016116352781×10−1 rather than 1.016116352781×10−1
### Example case
<!--
If possible, please create a SMALL example and attach it to your report
If you are using an older version of OpenFOAM this will also determine
whether the bug has been fixed in a more recent version
-->
### What is the current *bug* behaviour?
<!-- What actually happens -->
### What is the expected *correct* behavior?
<!-- What you should see instead -->
### Relevant logs and/or images
<!--
Paste any relevant logs - please use code blocks (```) to format console
output, logs, and code as it's very hard to read otherwise.
-->
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version :
- Operating system :
- Hardware info :
- Compiler :
### Possible fixes
<!--
If you can, link to the line of code that might be responsible for the
problem
The "/label ~bug" text is a gitlab flag that will add the "bug" label to this
issue
-->
https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1286foamToEnsight leaks memory2019-11-11T15:14:49ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfoamToEnsight leaks memory<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
-->
<!--
All text between these marker...<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
<!-- Summarize the bug encountered concisely -->
valgrind reports some in-use memory after finishing. E.g. foamToVTK does not.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
valgrind --leak-check=full foamToEnsight
```
==3683== HEAP SUMMARY:
==3683== in use at exit: 171 bytes in 4 blocks
==3683== total heap usage: 67,611 allocs, 67,607 frees, 6,829,195 bytes allocated
==3683==
==3683== 143 (72 direct, 71 indirect) bytes in 1 blocks are definitely lost in loss record 4 of 4
==3683== at 0x4C2A6F0: operator new(unsigned long) (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==3683== by 0x6921081: Foam::IOobjectList::IOobjectList(Foam::objectRegistry const&, Foam::fileName const&, Foam::fileName const&, Foam::IOobject::readOption, Foam::IOobject::writeOption, bool) (in /home/preston2/mattijs/OpenFOAM/work/develop/OpenFOAM-plus/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so)
==3683== by 0x44F58C: main (in /home/preston2/mattijs/OpenFOAM/work/develop/OpenFOAM-plus/platforms/linux64GccDPInt32Opt/bin/foamToEnsight)
```
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
OpenFOAM version : developMark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1488surfaceField FO fails on interpolate2019-11-11T10:57:01ZMark OLESENsurfaceField FO fails on interpolatecross-ref EP1101 @Prashantcross-ref EP1101 @PrashantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1482MinGW doesn't appear to have a download link2019-11-09T16:01:41ZCaleb OlesenMinGW doesn't appear to have a download linkhttps://www.openfoam.com/download/install-binary-windows-mingw.php
@Pawan @andyhttps://www.openfoam.com/download/install-binary-windows-mingw.php
@Pawan @andyAndrew HeatherAndrew Heather