Development issueshttps://develop.openfoam.com/groups/Development/-/issues2020-10-08T06:15:26Zhttps://develop.openfoam.com/Development/openfoam/-/issues/1870no match for argument: openfoam2006-default2020-10-08T06:15:26ZAndrig T Millerno match for argument: openfoam2006-default<!--
*** 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 re...<!--
*** 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 -->
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
### 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 :2006
- Operating system :Fedora 32
- Hardware info :AMD Ryzen 9 (3900 12 core)
- Compiler :N/A
### 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
-->
I'm not sure I should enter this, but I couldn't find any other way to contact someone that might be able to help. I enabled the copr repo openfoam/openfoam on Fedora 32, and then tried to install openfoam2006-default, as the wiki shows, but I get the following error:
no match for argument:openfoam2006-default
I tried others like openfoam, and openfoam-devel, but it can't find the packages. I have verified that the repo is enabled, but nothing.
Anyone know what's going on? I would love to put openfoam to use, but can't get it installed from the repo.https://develop.openfoam.com/Development/openfoam/-/issues/1871replace autoPtr/tmp combination with refPtr2021-12-03T16:44:51ZMark OLESENreplace autoPtr/tmp combination with refPtrSome of the optimization code uses a combination of autoPtr and tmp to manage the referenced or local turbulence fields. This is ugly but works and was previously the only way to handle these variants.
In the meantime have a `refPtr` (f...Some of the optimization code uses a combination of autoPtr and tmp to manage the referenced or local turbulence fields. This is ugly but works and was previously the only way to handle these variants.
In the meantime have a `refPtr` (formerly called tmpNrc) which can wrap a reference or handle pointer management. Both `tmp` and `refPtr` now have three types of storage:
- PTR : Managing a pointer (not ref-counted)
- CREF : Using (const) reference to an object
- REF : Using (non-const) reference to an object
Can thus have storage with deletion, reference an external object, or a nullptr.
Using a `refPtr` instead of a `tmp` means that we shouldn't accidentally clear memory. Also no reference counting to get in the way.Vaggelis PapoutsisVaggelis Papoutsishttps://develop.openfoam.com/Development/openfoam/-/issues/1872BUG: foamMeshToFluent writes empty brackets in msh file2023-01-11T10:54:09ZDaveBUG: foamMeshToFluent writes empty brackets in msh file### Summary
foamMeshToFluent writes empty brackets in the msh file in the "caption" of the very last section when the names ans types of the domains and the boundaries are declared, p.e.
`(12 (1 1 a94fc 1 0)(`
` 4 4 ... 4 4)`**_`()`_...### Summary
foamMeshToFluent writes empty brackets in the msh file in the "caption" of the very last section when the names ans types of the domains and the boundaries are declared, p.e.
`(12 (1 1 a94fc 1 0)(`
` 4 4 ... 4 4)`**_`()`_**`)`
`(39 (1 fluid fluid-1)())`
`(39 (2 interior interior-1)())`
`...`
Those empty brackets **_`()`_** cause ICEM to throw the following error when importing the mesh file:
`icem read_rampant_file() expecting '(' and got 41`
Although, the mesh is imported, the boundary and domain names aren't.
### Steps to reproduce
Export a mesh from any OpenFoam test case to Fluent msh via `foamMeshToFluent`
### Environment information
- OpenFOAM version : v2006
- Operating system : ubuntu1804@WSL@Win10
### Possible fixes
Removing the empty brackets in the mentioned header enables ICEM to properly read in all mesh informations.https://develop.openfoam.com/Development/openfoam/-/issues/1873foamToEnsight lagrangian fails in parallel2020-10-12T11:50:47ZMark OLESENfoamToEnsight lagrangian fails in parallel- as noted in EP1406 (@Prashant), converting Lagrangian fields in parallel fails for some simulations. Converting to VTK works without issue.- as noted in EP1406 (@Prashant), converting Lagrangian fields in parallel fails for some simulations. Converting to VTK works without issue.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1874support multiple faceZones/patches in sampling and surfaceFieldValue2021-02-01T18:50:37ZMark OLESENsupport multiple faceZones/patches in sampling and surfaceFieldValueItems raised in EP1415, EP1416
- should sampling onto faceZones.
Currently does not exist, even although they are supported in surfaceFieldValue.
- no support for multiple patches or faceZones in surfaceFieldValue.
Sampling onto mult...Items raised in EP1415, EP1416
- should sampling onto faceZones.
Currently does not exist, even although they are supported in surfaceFieldValue.
- no support for multiple patches or faceZones in surfaceFieldValue.
Sampling onto multiple patches works, so why not surfaceFieldValue.
@Prashantv2012Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1875BUG: forces FO: adds forces and moments beyond binMax to the last bin2024-01-11T18:15:10ZKutalmış BerçinBUG: forces FO: adds forces and moments beyond binMax to the last bin<!--
*** 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 re...<!--
*** 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 -->
In `forces` FO, when `binData == true` with a user-defined `binMax`, forces and moment estimations for the patch region outside the bin are added into the last bin if `binMax` is less than the extent of a given patch in the binning direction.
For example, in the following sketch, the forces and moments outside the linear bin are added into the bin-3.
![image](/uploads/5eeb391bf9891d0b6c09f6f68c8aed1e/image.png)
The error arises from the `applyBins` func:
```
...
const scalarField dd((d & binDir_) - binMin_);
forAll(dd, i)
{
label bini = min(max(floor(dd[i]/binDx_), 0), force_[0].size() - 1); // PROBLEM
force_[0][bini] += fN[i];
...
```
### 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 : 73057447a2v2012Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1876icoUncoupledKinematicParcelFoam description2021-11-02T10:12:25ZAndrew RobertsicoUncoupledKinematicParcelFoam descriptionHello,
I hope this is not an inconvenient time, I am using icoUncoupledKinematicParcelFoam and I just wondered if you knew of any mathematical description of the approach (esp parcel definition, governing equations, integration)? I am on...Hello,
I hope this is not an inconvenient time, I am using icoUncoupledKinematicParcelFoam and I just wondered if you knew of any mathematical description of the approach (esp parcel definition, governing equations, integration)? I am only interested for academic purposes. I've been told to tag @Sergio. Cheers!
Kind regards,
Andyhttps://develop.openfoam.com/Development/openfoam/-/issues/1877ptscotch not found on arch linux2020-10-12T11:50:47ZMark OLESENptscotch not found on arch linuxMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1878add face::copyFace method2020-10-13T12:30:50ZMark OLESENadd face::copyFace methodIdea to replace some repetitive code that occurs when collecting faces from various processors (for example).
Existing code:
```
for (const face& f : allFaces[Pstream::myProcNo()])
{
face& newF = faces[nFaces++];
newF.resize(f.s...Idea to replace some repetitive code that occurs when collecting faces from various processors (for example).
Existing code:
```
for (const face& f : allFaces[Pstream::myProcNo()])
{
face& newF = faces[nFaces++];
newF.resize(f.size());
forAll(f, fp)
{
newF[fp] = f[fp] + nPoints;
}
}
```
With the definition:
```
//- Return a copy of the face with given offset of its labels
inline face copyFace(const label offset) const;
```
This would simplify:
```
for (const face& f : allFaces[Pstream::myProcNo()])
{
faces[nFaces] = f.copyFace(nPoints);
++nFaces;
}
```
Naming similarity to `reverseFace()`Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1879construct token::compound from object2020-10-21T14:51:02ZMark OLESENconstruct token::compound from object@Mattijs@MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1882regionToFace not working2020-10-26T16:36:05ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comregionToFace not working<!--
*** 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 re...<!--
*** 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 -->
regionToFace does not limit walk so all is assigned a single region
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Happens only in some conditions so hard to reproduce.
### 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
-->
See ep1420Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1883Missing contributors...2021-12-03T15:45:19ZBruno SantosMissing contributors...In the file CONTRIBUTORS.md, the first one I can see that is missing is Richard Smith from Symscape. Given his contributions to porting OpenFOAM to Windows, his name should also be listed there!
PS: @mark Many thanks for mentioning the ...In the file CONTRIBUTORS.md, the first one I can see that is missing is Richard Smith from Symscape. Given his contributions to porting OpenFOAM to Windows, his name should also be listed there!
PS: @mark Many thanks for mentioning the contributors file at the forum... I managed to catch a glimpse of your post the other day!https://develop.openfoam.com/Development/openfoam/-/issues/1884surfaceFieldValue : doesn't handle volumeField2020-11-17T12:06:40ZPrashant SonakarsurfaceFieldValue : doesn't handle volumeField### Functionality to add/problem to solve
surface field value doesn't handle volume fields when using in faceZone mode.
Cross reference: EP#1316 and EP#1415
@mark @andy### Functionality to add/problem to solve
surface field value doesn't handle volume fields when using in faceZone mode.
Cross reference: EP#1316 and EP#1415
@mark @andyMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1885foamNewBC incorrect for Function1 member data2020-10-24T09:01:27ZHåkanfoamNewBC incorrect for Function1 member data<!--
*** 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 re...<!--
*** 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
foamNewBC incorrect for Function1 member data. It is not possible to compile the default output.
<!-- Summarize the bug encountered concisely -->
### Steps to reproduce
foamNewBC -f -v XYZ
wmake XYZ
<!-- How one can reproduce the issue - this is very important -->
### Example case
N/A
<!--
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?
Compilation fails
<!-- What actually happens -->
### What is the expected *correct* behavior?
It should compile, so that the user gets a good example from the script.
<!-- 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 : v2006
- Operating system : Ubuntu 20.04
- 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
-->
In last three constructors in the initialization (XYZ...C), it should be corrected to (from translatingWallVelocityFvPatchVectorField.C):
timeVsData_(ptf.timeVsData_.clone()),Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1886checkMesh reports nonManifoldPoints on faceZones, which it shouldn't2022-04-27T08:43:49ZHåkancheckMesh reports nonManifoldPoints on faceZones, which it shouldn't<!--
*** 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 re...<!--
*** 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
checkMesh reports nonManifoldPoints on faceZones, which it shouldn't.
<!-- Summarize the bug encountered concisely -->
### Steps to reproduce
Use:
pimpleFoam/LES/channel395
Run:
blockMesh
Just change the faceZones file to include some internal faces, see attached file:
[faceZones](/uploads/60f4e75ec2ee69d15aad4c1fad0d5f45/faceZones)
Then run:
checkMesh
<!-- How one can reproduce the issue - this is very important -->
### Example case
pimpleFoam/LES/channel395
plus attached file
<!--
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?
It gives error message:
```
Checking faceZone topology for multiply connected surfaces...
FaceZone Faces Points Surface topology
someFaces 5 11 multiply connected (shared edge)
<<Writing 2 conflicting points to set nonManifoldPoints
```
<!-- What actually happens -->
### What is the expected *correct* behavior?
It should not give an error message, since faces are always nonManifold (as far as I understand).
<!-- What you should see instead -->
### Relevant logs and/or images
See above
<!--
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 : v2006
- Operating system : Ubuntu
- Hardware info :
- Compiler : gcc
### 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
-->v2206Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1887Using the -case argument with extrudeMesh to specify the case directory does ...2020-11-02T09:15:54ZGerhard HolzingerUsing the -case argument with extrudeMesh to specify the case directory does not apply to paths stated in extrudeMeshDict<!--
*** 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 re...<!--
*** 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 -->
The utility extrudeMesh fails to read a triSurface file, when I provide the case directory using the '-case' command line flag. The path to the triSurfaceFile is provided in the extrudeMeshDict as 'constant/triSurface/filename'.
Using a working directory which is the case directory, all is well. However, if I call extrudeMesh from the case's parent directory, and provide the case directory using the '-case' argument, the triSurface file can not be found.
Maybe, this is a bug of the VTK-file reader; and not of extrudeMesh itself. However, the unexpected behaviour of extrudeMesh described here is the symptom I encountered. The root-problem may be well something else.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Go to the 'overRhoSimpleFoam/hotCylinder' tutorial case.
Change to 'cylinderMesh', and call 'extrudeMesh' -> all is well
Go back up (call 'cd ..'), clear the case (call './Allclean'), and call 'extrudeMesh -case cylinderMesh' -> error: 'Cannot read file "constant/triSurface/cylinder.vtk"'
### 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
-->
Use the 'overRhoSimpleFoam/hotCylinder' tutorial case.
### What is the current *bug* behaviour?
<!-- What actually happens -->
extrudeMesh fails to read the provided triSurface file, which is provided in extrudeMeshDict.
If I change the entry in the file extrudeMeshDict from 'constant/triSurface/cylinder.vtk' to 'cylinderMesh/constant/triSurface/cylinder.vtk', then extrudeMesh finds the file.
`Extruding surfaceMesh read from file "cylinderMesh/constant/triSurface/cylinder.vtk"`
### What is the expected *correct* behavior?
<!-- What you should see instead -->
I would expect extrudeMesh to take the path from extrudeMeshDict, i.e. 'constant/triSurface/cylinder.vtk', and form a path from the specified case directory.
The output of extrudeMesh lists the correct case directory:
`Case : /home/gerhard/OpenFOAM/OpenFOAM-v2006/tutorials/compressible/overRhoSimpleFoam/hotCylinder/cylinderMesh`
I would expect, that the path to the triSurface file is treated as a relative path, which is combined with the provided case directory.
### Relevant logs and/or images
```
gerhard@host:~/OpenFOAM/OpenFOAM-v2006/tutorials/compressible/overRhoSimpleFoam/hotCylinder$ ls
Allclean Allrun Allrun.pre cylinderAndBackground cylinderMesh
gerhard@host:~/OpenFOAM/OpenFOAM-v2006/tutorials/compressible/overRhoSimpleFoam/hotCylinder$ extrudeMesh -case cylinderMesh
/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: v2006 |
| \\ / A nd | Website: www.openfoam.com |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : _b45f8f6f58-20200629 OPENFOAM=2006
Arch : "LSB;label=32;scalar=64"
Exec : extrudeMesh -case cylinderMesh
Date : Oct 20 2020
Time : 14:09:57
Host : host
PID : 20346
I/O : uncollated
Case : /home/gerhard/OpenFOAM/OpenFOAM-v2006/tutorials/compressible/overRhoSimpleFoam/hotCylinder/cylinderMesh
nProcs : 1
trapFpe: Floating point exception trapping enabled (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 5, maxFileModificationPolls 20)
allowSystemOperations : Allowing user-supplied system call operations
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time
Create mesh for time = 0
Selecting extrudeModel linearNormal
Selected extrudeModel for linearNormal using coeffs
{
thickness 0.7;
}
Extruding from surface using model linearNormal
Not collapsing any edges after extrusion
Extruding surfaceMesh read from file "constant/triSurface/cylinder.vtk"
--> FOAM FATAL ERROR:
Cannot read file "constant/triSurface/cylinder.vtk"
From bool Foam::fileFormats::VTKsurfaceFormat<Face>::read(const Foam::fileName&) [with Face = Foam::face]
in file surfaceFormats/vtk/VTKsurfaceFormat.C at line 98.
FOAM exiting
gerhard@host:~/OpenFOAM/OpenFOAM-v2006/tutorials/compressible/overRhoSimpleFoam/hotCylinder$
```
### 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 : 2006
- Operating system : Ubuntu-18.04
- Hardware info :
- Compiler : gcc
### 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/-/issues/1888Dockerhub container sources2021-12-22T16:31:49ZGonzaloDockerhub container sourcesI am not able to find the source files used to create the containers published to dockerhub. Are these available somewhere?
In #73 this same issue was closed suggesting that the sources are available in the Snippets, but this does not ...I am not able to find the source files used to create the containers published to dockerhub. Are these available somewhere?
In #73 this same issue was closed suggesting that the sources are available in the Snippets, but this does not appear to be the case anymore (or at least, I cannot find them).
Also, that issue is about it being good practice to link the docker container sources to the dockerhub repository, so that those wanting to inspect what is actually in the container can quickly do so. This is currently not the case.https://develop.openfoam.com/Development/openfoam/-/issues/1889setExprFields floatingPointException evaluating log of variable2020-10-28T23:15:34ZJoshua DysonsetExprFields floatingPointException evaluating log of variable<!--
*** 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 re...<!--
*** 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 using an expressing in setExprFields containing log of a variable it exits with a floating point exception.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Run setExprFields using a an expression that contains log(variable)
### 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
-->
Modify `tutorials/compressible/rhoPimpleFoam/RAS/TJunctionAverage/system/setExprFieldsDict` so that the expression is:
```
expression
#{
300
+ log(radius)
#};
```
Additionally this also doesn't work:
```
expression
#{
300
+ log(10*radius)
#};
```
However this works correctly:
```
expression
#{
300
+ log(1/radius)
#};
```
### What is the current *bug* behaviour?
<!-- What actually happens -->
Exits with a floating point exception when a strange set of criteria is met.
### What is the expected *correct* behavior?
<!-- What you should see instead -->
The variable is evaluated correctly and the correct field values are applied.
### 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.
-->
```
/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 2006 |
| \\ / A nd | Website: www.openfoam.com |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : _295eef47-20201012 OPENFOAM=2006 patch=201012
Arch : "LSB;label=32;scalar=64"
Exec : setExprFields
Date : Oct 21 2020
Time : 10:01:35
Host : chimera
PID : 18880
I/O : uncollated
Case : /****/TJunctionAverage
nProcs : 1
trapFpe: Floating point exception trapping enabled (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 5, maxFileModificationPolls 20)
allowSystemOperations : Allowing user-supplied system call operations
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time
Create mesh for time = 0
Time = 0
Modify field: T (type volScalarField) time=0
Expression:
>>>>
300
+ log(10*radius)
<<<<
Condition:
>>>>
(mag(pos() - vector(0.21,0,0.01)) < radius)
&& pos((pos() - vector(0.21,0,0.01)).y()) > 0
<<<<
#0 Foam::error::printStack(Foam::Ostream&) at ??:?
#1 Foam::sigFpe::sigHandler(int) at ??:?
#2 ? in /lib64/libpthread.so.0
#3 log in /lib64/libm.so.6
#4 Foam::log(Foam::Field<double>&, Foam::UList<double> const&) at ??:?
#5 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > Foam::log<Foam::fvPatchField, Foam::volMesh>(Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > const&) at ??:?
#6 ? at volumeExprLemonParser.cc:?
#7 Foam::expressions::volumeExpr::parser::parse(int, Foam::expressions::volumeExpr::scanToken*) at ??:?
#8 Foam::expressions::volumeExpr::scanner::process(std::string const&, unsigned long, unsigned long, Foam::expressions::volumeExpr::parseDriver&) at ??:?
#9 Foam::expressions::volumeExpr::parseDriver::parse(std::string const&, unsigned long, unsigned long) at ??:?
#10 ? at ??:?
#11 ? at ??:?
#12 __libc_start_main in /lib64/libc.so.6
#13 ? at ??:?
Floating point exception (core dumped)
```
### 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 : v2006
- Operating system : centoOS 7
- Hardware info : Intel E5-1620, 64GB RAM
- Compiler : gcc 4.8.5
OpenFOAM installed using the yum package manager as described in the release notes.
### 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
-->Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1890Clearly mark Allrun scripts etc that use bash2020-10-23T15:35:21ZPetros AmpatzidisClearly mark Allrun scripts etc that use bashWhen I try to run the `Allrun` script in the new `$FOAM_TUTORIALS/verificationAndValidation/atmosphericModels/atmForestStability` tutorial case in v2006 I get:
```
./Allrun: 13: ./Allrun: declare: not found
./Allrun: 14: ./Allrun: decla...When I try to run the `Allrun` script in the new `$FOAM_TUTORIALS/verificationAndValidation/atmosphericModels/atmForestStability` tutorial case in v2006 I get:
```
./Allrun: 13: ./Allrun: declare: not found
./Allrun: 14: ./Allrun: declare: not found
./Allrun: 15: ./Allrun: declare: not found
./Allrun: 17: ./Allrun: stabilityStates[0]=veryStable: not found
./Allrun: 18: ./Allrun: stabilityStates[1]=stable: not found
./Allrun: 19: ./Allrun: stabilityStates[2]=slightlyStable: not found
./Allrun: 20: ./Allrun: stabilityStates[3]=neutral: not found
./Allrun: 21: ./Allrun: stabilityStates[4]=slightlyUnstable: not found
./Allrun: 22: ./Allrun: stabilityStates[5]=unstable: not found
./Allrun: 24: ./Allrun: Lmaxs[0]=5.0: not found
./Allrun: 25: ./Allrun: Lmaxs[1]=13.0: not found
./Allrun: 26: ./Allrun: Lmaxs[2]=25.5: not found
./Allrun: 27: ./Allrun: Lmaxs[3]=41.0: not found
./Allrun: 28: ./Allrun: Lmaxs[4]=80.75: not found
./Allrun: 29: ./Allrun: Lmaxs[5]=200.0: not found
./Allrun: 31: ./Allrun: qPlants[0]=-20.0: not found
./Allrun: 32: ./Allrun: qPlants[1]=-9.0: not found
./Allrun: 33: ./Allrun: qPlants[2]=-5.0: not found
./Allrun: 34: ./Allrun: qPlants[3]=0.0: not found
./Allrun: 35: ./Allrun: qPlants[4]=15.0: not found
./Allrun: 36: ./Allrun: qPlants[5]=60.0: not found
./Allrun: 39: ./Allrun: Bad substitution
```
It seems that something's wrong with the `declare` command. Do you think it is related to my OpenFOAM installation or is an inherent bug?Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1891handle out-of-range surface sampling2021-12-10T13:16:03ZMark OLESENhandle out-of-range surface samplingIssue raised on EP974. When sampling onto a meshed surface, we have the possibility of using `cells`, `insideCells`, `boundaryFaces`. However, when using `cells` (for example), it takes the closest cell. If sampling surface happens to be...Issue raised on EP974. When sampling onto a meshed surface, we have the possibility of using `cells`, `insideCells`, `boundaryFaces`. However, when using `cells` (for example), it takes the closest cell. If sampling surface happens to be out of the domain, for example since it extends into various mesh regions, the value of the closest cell will be wildly incorrect and misleading.
The proposed solution is to add in support for specifying a max search radius and a default value.
For example,
```
maxSearch 0.005;
defaultValues
{
"p.*" 0;
T 273.15;
U (-100 -100 -100);
...
}
```
Note that sampling onto a meshed surface is the only surface sampler that this affects.Mark OLESENMark OLESEN